Real-time
Two-way sync
Changes in Citus or Sage X3 instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Citus to Sage X3 integration — real-time, two-way sync
Keep Citus 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Citus and Sage X3
Give your engineers Sage X3's data in Citus: read it with normal queries, write back through the sync, and skip the ERP API entirely.
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 Stock / Inventory by site, Bills of Material, GL Journals, Deliveries from Sage X3 into Citus 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 Citus sync back into Sage X3 with its validations respected.
Common use cases
- 01 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- 02 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- 03 Feed work order and BOM data to MES or planning tools on the shop floor.
- 04 Sync business partners and products between Sage X3 and a CRM so global sales teams quote from current ERP masters.
Common sync patterns
Internal tools and automations without API code
Scripts and services read and write the synced tables; Stacksync handles the Sage X3 interface, limits, and retries.
React to ERP changes
Updates in Sage X3 arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Where Sage X3 is the HR system of record: people data for internal systems
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
What you can sync between Citus and Sage X3
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.
| Citus objects | Sage X3 objects | How this pairing syncs | |
|---|---|---|---|
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Bills of Material Product structures read for planning and costing. | Distributed tables is specific to Citus and Bills of Material to Sage X3 — each maps to any object or custom field on the other side. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | GL Journals Financial entries replicated to warehouses for group reporting. | Reference tables is specific to Citus and GL Journals to Sage X3 — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Deliveries Shipment documents synced to logistics providers and customer portals. | Local tables is specific to Citus and Deliveries to Sage X3 — each maps to any object or custom field on the other side. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Business Partners (Customers and Suppliers) Shared partner master synced with CRMs and procurement systems. | Schemas is specific to Citus and Business Partners (Customers and Suppliers) to Sage X3 — each maps to any object or custom field on the other side. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Products Item master with units, costing, and site data, synced to commerce and PLM tools. | Views is specific to Citus and Products to Sage X3 — each maps to any object or custom field on the other side. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Sales Orders Order documents written from external channels and read for fulfillment status. | Sequences is specific to Citus and Sales Orders to Sage X3 — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Sage X3
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.
Citus Sage X3 Sub-second propagation
DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.
DeliveryEach detected change is applied to Sage X3 as a row-level write, with types converted between the two schemas.
Sage X3 Citus Interval-based propagation
DetectionStacksync polls Sage X3 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
What ships with Citus ⇄ Sage X3
Connect Citus and Sage X3 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Sage X3 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Sage X3 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Citus or Sage X3 record.
Observability
Monitoring
Track your Citus ⇄ Sage X3 sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Citus and Sage X3.
How the Citus and Sage X3 connectors work
Citus
- Integration surface
- PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
- Authentication
- Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
- Change detection
- PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
- Capabilities
- read · write · CDC
Sage X3
- Integration surface
- 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
- Change detection
- Scheduled polling; no general webhook surface on the classic web services layer
- Capabilities
- read · write
How it works
How to connect Citus to Sage X3 — three steps, no code
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.
- 01
Connect your apps
Authenticate Citus 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.
Citus
connected
Sage X3
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus 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.
objects · Citus ⇄ Sage X3Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Citus Sage X3Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Sage X3 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Sage X3: authenticate both systems, choose the objects to sync (such as Citus's Distributed tables and Reference tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Citus: Because shard data lives on worker nodes, log-based CDC is more involved than on single-node Postgres and depends on the Citus version and hosting (including the Azure managed service). Sage X3: X3 web services are generated from its business objects, so payloads mirror the on-screen entry transactions and enforce the same validation as manual entry. Stacksync's field mapping accounts for these differences between Citus 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 Citus 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 Citus and Sage X3 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Sage X3 integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Sage X3. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On Sage X3: Scheduled polling; no general webhook surface on the classic web services layer. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 434 integrations available for Citus and Sage X3.
Popular · 6 of 434
-
Citus ⇄ Infor LN - Citus ⇄ Infor M3
-
Sage X3 ⇄ SingleStore -
Sage X3 ⇄ Amazon Aurora -
Sage X3 ⇄ Amazon Lightsail -
Sage X3 ⇄ Apache Cassandra
No integrations match .
