Two-way sync
Changes in Exasol or Syspro instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol and Syspro in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Syspro carries financials, operations, workforce data, or all three, the analysis belongs in Exasol next to everything else the company measures.
Stacksync syncs AR invoices, GL journals, Warehouses, Customers from Syspro into tables in Exasol continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Exasol can be written back to fields in Syspro where that is useful.
Combine Syspro's records with data synced from other systems in Exasol for consolidated views no single system can produce.
Classifications or reference values computed in Exasol sync back onto the corresponding records in Syspro.
Financial records land in Exasol as they change, so period-end reporting queries current numbers rather than last night's extract.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Exasol objects | Syspro objects | How this pairing syncs | |
|---|---|---|---|
| Users and roles Grant read/write access for the dedicated integration account. | Warehouses Stocking locations that scope inventory balances. | Users and roles is specific to Exasol and Warehouses to Syspro — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Customers AR customer master records matched against CRM accounts. | Schemas is specific to Exasol and Customers to Syspro — each maps to any object or custom field on the other side. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | Suppliers AP supplier records synced with procurement and payment systems. | Tables is specific to Exasol and Suppliers to Syspro — each maps to any object or custom field on the other side. | |
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Inventory items The stock master, kept aligned with WMS and e-commerce catalogs. | Views is specific to Exasol and Inventory items to Syspro — each maps to any object or custom field on the other side. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Sales orders Orders written in from storefronts and CRMs, with status read back out. | Virtual schemas is specific to Exasol and Sales orders to Syspro — each maps to any object or custom field on the other side. | |
| UDF scripts In-database functions that can transform synced data after load. | Purchase orders Procurement documents synced with supplier portals and receiving. | UDF scripts is specific to Exasol and Purchase orders to Syspro — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.
DeliveryEach detected change is written to Syspro through its API, with automatic retries and rate-limit backoff.
DetectionStacksync polls Syspro for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is applied to Exasol as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Syspro connection.
Changes in Exasol or Syspro instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol or Syspro data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Exasol or Syspro record.
Track your Exasol ⇄ Syspro sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol and Syspro.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Exasol and Syspro with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Exasol and Syspro objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Exasol and Syspro: authenticate both systems, choose the objects to sync (such as Exasol's Users and roles and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Exasol side: Schemas, Tables, Views, Virtual schemas, plus custom fields where Exasol exposes them. On the Syspro side: AR invoices, GL journals, Warehouses, Customers. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Exasol and Syspro: Group reporting across systems; Write-back where Syspro exposes writable fields; Where Syspro holds the books: finance reporting from live data. Combine Syspro's records with data synced from other systems in Exasol for consolidated views no single system can produce.
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). Syspro: E.net Solutions business objects, exposed over REST and WCF interfaces in SYSPRO 8. Authentication: SYSPRO operator credentials exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
Exasol: Bulk loading uses the IMPORT statement, which is more efficient than row-by-row inserts for sync workloads. Syspro: Business objects exchange XML documents for both input and output, which the integration layer maps to flat records. Stacksync's field mapping accounts for these differences between Exasol and Syspro without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 432 integrations available for Exasol and Syspro.