Two-way sync
Changes in Citus or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Microsoft Dynamics NAV 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 Customers, Vendors, Items, Sales Orders & Invoices from Microsoft Dynamics NAV into Citus and keeps both sides consistent in real time. Whatever Microsoft Dynamics NAV 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 Microsoft Dynamics NAV with its validations respected.
Records from Microsoft Dynamics NAV live in Citus as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Microsoft Dynamics NAV interface, limits, and retries.
Updates in Microsoft Dynamics NAV arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
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 | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Schemas is specific to Citus and Purchase Orders to Microsoft Dynamics NAV — 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. | G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Views is specific to Citus and G/L Entries to Microsoft Dynamics NAV — 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. | Item Ledger Entries Inventory movement history read for stock and costing analytics. | Sequences is specific to Citus and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Dimensions Analytical codes carried on documents and entries for reporting splits. | Distributed tables is specific to Citus and Dimensions to Microsoft Dynamics NAV — 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. | Companies Per-company data partitions that scope every sync. | Reference tables is specific to Citus and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Local tables is specific to Citus and Customers to Microsoft Dynamics NAV — 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.
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 Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.
DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Microsoft Dynamics NAV connection.
Changes in Citus or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Microsoft Dynamics NAV 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 Microsoft Dynamics NAV record.
Track your Citus ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Microsoft Dynamics NAV.
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 Microsoft Dynamics NAV 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 Microsoft Dynamics NAV 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.
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 430 integrations available for Citus and Microsoft Dynamics NAV.