Two-way sync
Changes in DuckDB or Sage X3 instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Sage X3 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 sits behind interfaces built for the ERP's own modules, not for your internal systems. Teams that need those records, for reporting services, internal tools, or automations, end up writing integration code against a strict API and maintaining it through every upgrade.
Stacksync mirrors Bills of Material, GL Journals, Deliveries, Business Partners (Customers and Suppliers) from Sage X3 into DuckDB and keeps both sides consistent in real time. Whatever Sage X3 is the system of record for, whether financials, operations, people, or procurement, those records become rows your code can query, and changes written in DuckDB sync back into Sage X3 with its validations respected.
Updates in Sage X3 arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in DuckDB for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from DuckDB back into Sage X3, keeping the ERP authoritative.
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.
| DuckDB objects | Sage X3 objects | |
|---|---|---|
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Stock / Inventory by site On-hand and allocated quantities per site, synced to storefronts and WMS. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Bills of Material Product structures read for planning and costing. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | GL Journals Financial entries replicated to warehouses for group reporting. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Deliveries Shipment documents synced to logistics providers and customer portals. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Business Partners (Customers and Suppliers) Shared partner master synced with CRMs and procurement systems. | |
| Views SQL views used to shape or filter data for downstream consumers. | Products Item master with units, costing, and site data, synced to commerce and PLM tools. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Sage X3 connection.
Changes in DuckDB or Sage X3 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Sage X3 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DuckDB or Sage X3 record.
Track your DuckDB ⇄ Sage X3 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Sage X3.
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 DuckDB and Sage X3 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 DuckDB and Sage X3 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 DuckDB and Sage X3: authenticate both systems, choose the objects to sync (such as DuckDB's External files (Parquet/CSV/JSON) and Attached databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for DuckDB and Sage X3: React to ERP changes; Where Sage X3 is the HR system of record: people data for internal systems; Controlled write-back. Updates in Sage X3 arrive as row changes in DuckDB, so jobs and triggers can respond as the business record changes.
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Sage X3: SOAP and REST web services published from X3 business objects; direct SQL access to the underlying database on-prem. Authentication: Dedicated web-service user credentials (Basic auth) against configured connection pools. Stacksync manages authentication, retries, and rate limits on both sides.
DuckDB: DuckDB runs in-process like SQLite; there is no server, so integrations embed the engine or operate on the single-file databases it produces. Sage X3: One X3 instance can run multiple companies, sites, and legislations, and integrations must carry that context (company, site) on each document. Stacksync's field mapping accounts for these differences between DuckDB and Sage X3 without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DuckDB and Sage X3 records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and Sage X3 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–Sage X3 integration in-house.
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 386 integrations available for DuckDB and Sage X3.