Skip to content
Database ⇄ ERP

Citus to Microsoft Dynamics NAV integration — real-time, two-way sync

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.

  • 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 Microsoft Dynamics NAV

Give your engineers Microsoft Dynamics NAV'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 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.

Common use cases

  • 01 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.
  • 02 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • 03 Push ecommerce orders into NAV sales orders through published page services.
  • 04 Replicate G/L and ledger entries into a warehouse for consolidated finance reporting.

Common sync patterns

Read ERP records with a query

Records from Microsoft Dynamics NAV live in Citus as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Microsoft Dynamics NAV interface, limits, and retries.

React to ERP changes

Updates in Microsoft Dynamics NAV arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.

What you can sync between Citus and Microsoft Dynamics NAV

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.

How changes propagate between Citus and Microsoft Dynamics NAV

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 Microsoft Dynamics NAV 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 Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.

Microsoft Dynamics NAV Citus Sub-second propagation

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.

What ships with Citus ⇄ Microsoft Dynamics NAV

Connect Citus and Microsoft Dynamics NAV for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Microsoft Dynamics NAV connection.

Real-time

Two-way sync

Changes in Citus or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Microsoft Dynamics NAV 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 Microsoft Dynamics NAV record.

Observability

Monitoring

Track your Citus ⇄ Microsoft Dynamics NAV 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 Microsoft Dynamics NAV.

How the Citus and Microsoft Dynamics NAV 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

Microsoft Dynamics NAV

Integration surface
SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
Authentication
Windows authentication or NavUserPassword credentials
Change detection
Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
Capabilities
read · write · CDC
How it works

How to connect Citus to Microsoft Dynamics NAV — 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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Microsoft Dynamics NAV connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ Microsoft Dynamics NAV
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Citus Microsoft Dynamics NAV
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Citus and Microsoft Dynamics NAV integration FAQ

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 430 integrations available for Citus and Microsoft Dynamics NAV.

Popular · 5 of 430
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.