Two-way sync
Changes in Citus or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Epicor ERP 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 Quotes, AR invoices, Shipments, Bills of materials from Epicor ERP into Citus and keeps both sides consistent in real time. Whatever Epicor ERP 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 Epicor ERP with its validations respected.
Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
Choose exactly which tables and fields may flow from Citus back into Epicor ERP, keeping the ERP authoritative.
Records from Epicor ERP live in Citus as ordinary tables or collections, joinable with the rest of your data.
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 | Epicor ERP objects | |
|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Sales orders Created from won CRM opportunities; status and line changes sync back out. | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | Purchase orders Synced with procurement systems and matched against receipts. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Jobs Production jobs whose status feeds shop-floor dashboards and delivery-date updates. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Quotes Estimates that pair with CRM opportunities during the sales cycle. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | AR invoices Billing records surfaced in CRM or finance tools for collections visibility. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Shipments Fulfillment confirmations synced to customer portals and commerce systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Epicor ERP connection.
Changes in Citus or Epicor ERP instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Epicor ERP data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or Epicor ERP record.
Track your Citus ⇄ Epicor ERP sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Epicor ERP.
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 Citus and Epicor ERP 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 Citus and Epicor ERP 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 Citus and Epicor ERP: authenticate both systems, choose the objects to sync (such as Citus's Views and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Epicor ERP: Polling on change-date fields; outbound calls can be wired through BPM directives, but there is no standard webhook subscription surface. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Citus side: Distributed tables, Reference tables, Local tables, Schemas, plus custom fields where Citus exposes them. On the Epicor ERP side: Quotes, AR invoices, Shipments, Bills of materials. 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 Citus and Epicor ERP: Where Epicor ERP is the HR system of record: people data for internal systems; Controlled write-back; Read ERP records with a query. Worker and org records stay current in Citus for provisioning, access, and reporting systems that read from the database.
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). Epicor ERP: REST API (OData) over Epicor business objects, plus BAQ (Business Activity Query) endpoints. Authentication: API key combined with basic or token authentication, depending on version and deployment. Stacksync manages authentication, retries, and rate limits on both sides.
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 Citus and Epicor ERP.