Real-time
Two-way sync
Changes in Citus or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ ERP
Citus to Dynamics 365 Business Central integration — real-time, two-way sync
Keep Citus and Dynamics 365 Business Central 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 Dynamics 365 Business Central
Give your engineers Dynamics 365 Business Central'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 Purchase Orders, General Ledger Entries, Journals, Dimensions from Dynamics 365 Business Central into Citus and keeps both sides consistent in real time. Whatever Dynamics 365 Business Central 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 Dynamics 365 Business Central 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 Sync vendor and purchase order data with procurement or AP automation tools.
- 04 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.
Common sync patterns
React to ERP changes
Updates in Dynamics 365 Business Central arrive as row changes in Citus, so jobs and triggers can respond as the business record changes.
Where Dynamics 365 Business Central 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 Dynamics 365 Business Central, keeping the ERP authoritative.
What you can sync between Citus and Dynamics 365 Business Central
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 | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Reference tables is specific to Citus and Purchase Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. | Local tables is specific to Citus and General Ledger Entries to Dynamics 365 Business Central — 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. | Journals Staging records for financial postings created by integrations before posting. | Schemas is specific to Citus and Journals to Dynamics 365 Business Central — 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. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Views is specific to Citus and Dimensions to Dynamics 365 Business Central — 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. | Payments Customer and vendor payment records reconciled against invoices. | Sequences is specific to Citus and Payments to Dynamics 365 Business Central — 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. | Customers Core master data synced with CRMs so sales and finance share one customer list. | Distributed tables is specific to Citus and Customers to Dynamics 365 Business Central — each maps to any object or custom field on the other side. |
How changes propagate between Citus and Dynamics 365 Business Central
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 Dynamics 365 Business Central 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 written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
Dynamics 365 Business Central Citus Sub-second propagation
DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.
DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.
What ships with Citus ⇄ Dynamics 365 Business Central
Connect Citus and Dynamics 365 Business Central for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Dynamics 365 Business Central connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Citus or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.
Observability
Monitoring
Track your Citus ⇄ Dynamics 365 Business Central 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 Dynamics 365 Business Central.
How the Citus and Dynamics 365 Business Central 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
Dynamics 365 Business Central
- Integration surface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- OAuth 2.0 via Microsoft Entra ID
- Change detection
- API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
- Capabilities
- read · write · webhooks
How it works
How to connect Citus to Dynamics 365 Business Central — 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 Dynamics 365 Business Central 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
Dynamics 365 Business Central
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Citus and Dynamics 365 Business Central 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 ⇄ Dynamics 365 Business CentralCustomers 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 Dynamics 365 Business CentralCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Citus and Dynamics 365 Business Central integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Citus and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Citus's Reference tables and Local tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Citus: Citus is a PostgreSQL extension, not a fork: clients connect with ordinary Postgres drivers and SQL, and the coordinator routes queries to shards. Dynamics 365 Business Central: Custom API pages written in AL extend the same OData surface, letting partner-specific tables participate in syncs like standard entities. Stacksync's field mapping accounts for these differences between Citus and Dynamics 365 Business Central 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 Dynamics 365 Business Central records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Citus and Dynamics 365 Business Central connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Citus–Dynamics 365 Business Central integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Citus and Dynamics 365 Business Central. 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 Dynamics 365 Business Central: API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime. 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 435 integrations available for Citus and Dynamics 365 Business Central.
Popular · 5 of 435
-
Citus ⇄ NetSuite -
Dynamics 365 Business Central ⇄ SingleStore -
Dynamics 365 Business Central ⇄ Amazon Aurora -
Dynamics 365 Business Central ⇄ Amazon Lightsail -
Dynamics 365 Business Central ⇄ Apache Cassandra
No integrations match .
