Real-time
Two-way sync
Changes in Acumatica or Citus instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Database
Acumatica to Citus integration — real-time, two-way sync
Keep Acumatica and Citus 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 Acumatica and Citus
Give your engineers Acumatica'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 Projects, Opportunities and Cases, Customers, Vendors from Acumatica into Citus and keeps both sides consistent in real time. Whatever Acumatica 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 Acumatica with its validations respected.
Common use cases
- Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
- Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
- Two-way sync of customers, orders, and invoices between Acumatica and a CRM so sales sees ERP truth without ERP logins.
- Create sales orders in Acumatica from e-commerce platforms and sync shipment and tracking status back to the storefront.
Where Acumatica 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.
Controlled write-back
Choose exactly which tables and fields may flow from Citus back into Acumatica, keeping the ERP authoritative.
Read ERP records with a query
Records from Acumatica live in Citus as ordinary tables or collections, joinable with the rest of your data.
What you can sync between Acumatica and Citus
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.
| Acumatica objects | Citus objects | |
|---|---|---|
| Stock Items Inventory master data with quantities shared with external sales channels. | Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | |
| Shipments Fulfillment documents read to update tracking in storefronts and CRMs. | Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | |
| Payments Customer payment records reconciled against invoices from payment platforms. | Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | |
| Journal Transactions GL entries replicated into reporting databases. | Views Curated projections over distributed data, often used as read-only sync sources. | |
| Projects Project cost and billing structures synced with delivery tools. | Sequences Key generators that matter when external writes must not collide with application inserts. | |
| Opportunities and Cases Built-in CRM records synced with external sales and support tools. | Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. |
What ships with Acumatica ⇄ Citus
Connect Acumatica and Citus for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Acumatica–Citus connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Acumatica or Citus 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 Acumatica or Citus record.
Observability
Monitoring
Track your Acumatica ⇄ Citus sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Acumatica and Citus.
How the Acumatica and Citus connectors work
Acumatica
- Integration surface
- Contract-based REST API (JSON over versioned endpoints), plus SOAP web services and OData access to Generic Inquiries
- Authentication
- OAuth 2.0 or cookie-based session login with Acumatica credentials
- Change detection
- Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields
- Capabilities
- read · write · webhooks
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
How it works
How to connect Acumatica to Citus — 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 Acumatica and Citus with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Acumatica
connected
Citus
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Acumatica and Citus 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 · Acumatica ⇄ CitusCustomers 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.
Acumatica CitusCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Acumatica and Citus integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Acumatica and Citus: authenticate both systems, choose the objects to sync (such as Acumatica's Stock Items and Shipments), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Acumatica and Citus connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Acumatica–Citus integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Acumatica and Citus. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Acumatica: Push notifications configurable on data changes, plus polling on LastModifiedDateTime fields. On Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Citus side: Local tables, Schemas, Views, Sequences, plus custom fields where Citus exposes them. On the Acumatica side: Projects, Opportunities and Cases, Customers, Vendors. 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.
SECURITY
Security teams love 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
CSA STAR
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 386 integrations available for Acumatica and Citus.
Popular · 8 of 386
-
Acumatica ⇄ InterSystems IRIS -
Acumatica ⇄ MarkLogic -
Acumatica ⇄ Neo4j -
Acumatica ⇄ OCI Database (Oracle Cloud) -
Citus ⇄ Infor M3 - Citus ⇄ Infor WMS
-
Citus ⇄ IQMS (DELMIAworks) -
Citus ⇄ JobBOSS²
No integrations match .
