Skip to content
Data warehouse ⇄ ERP

Apache Druid to Dynamics 365 Business Central integration — real-time, two-way sync

Keep Apache Druid 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 Apache Druid and Dynamics 365 Business Central

Put Dynamics 365 Business Central's records in Apache Druid as live tables for reporting and analysis, without extract jobs, and write results back where Dynamics 365 Business Central can use them.

ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Dynamics 365 Business Central carries financials, operations, workforce data, or all three, the analysis belongs in Apache Druid next to everything else the company measures.

Stacksync syncs Sales Orders, Sales Invoices, Purchase Orders, General Ledger Entries from Dynamics 365 Business Central into tables in Apache Druid continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Apache Druid can be written back to fields in Dynamics 365 Business Central where that is useful.

Common use cases

  • 01 Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.
  • 02 Feed operational records into Druid via batch ingestion so analysts get interactive slice-and-dice on fresh data.
  • 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

Where Dynamics 365 Business Central is the HR system of record: workforce analytics

Worker and organization data syncs into Apache Druid for headcount, cost, and planning analysis alongside other company data.

Where Dynamics 365 Business Central runs operations: order and supply analysis

Operational records become queryable tables in Apache Druid, joinable with sales and finance data.

Group reporting across systems

Combine Dynamics 365 Business Central's records with data synced from other systems in Apache Druid for consolidated views no single system can produce.

What you can sync between Apache Druid 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.

Apache Druid objects Dynamics 365 Business Central objects How this pairing syncs
Dimensions String and categorical columns used for filtering and grouping in synced queries. Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Sales Invoices Billing documents synced to CRMs and payment platforms. Metrics is specific to Apache Druid and Sales Invoices to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Purchase Orders Procurement documents exchanged with supplier-facing systems. Ingestion Supervisors is specific to Apache Druid and Purchase Orders to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Lookups Key-value mappings joined at query time, refreshable from external systems. General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Lookups is specific to Apache Druid and General Ledger Entries to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Journals Staging records for financial postings created by integrations before posting. Tasks is specific to Apache Druid and Journals to Dynamics 365 Business Central — each maps to any object or custom field on the other side.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Payments Customer and vendor payment records reconciled against invoices. Datasources is specific to Apache Druid and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid 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.

Apache Druid Dynamics 365 Business Central Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Dynamics 365 Business Central Apache Druid 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 Apache Druid as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
What ships with Apache Druid ⇄ Dynamics 365 Business Central

Connect Apache Druid and Dynamics 365 Business Central for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Dynamics 365 Business Central connection.

Real-time

Two-way sync

Changes in Apache Druid or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid 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 Apache Druid or Dynamics 365 Business Central record.

Observability

Monitoring

Track your Apache Druid ⇄ 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 Apache Druid and Dynamics 365 Business Central.

How the Apache Druid and Dynamics 365 Business Central connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

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 Apache Druid 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.

  1. 01

    Connect your apps

    Authenticate Apache Druid 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Druid connected
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Druid ⇄ Dynamics 365 Business Central
    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
    Apache Druid Dynamics 365 Business Central
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and Dynamics 365 Business Central 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 443 integrations available for Apache Druid and Dynamics 365 Business Central.

Popular · 7 of 443
All Apache Druid integrations All Dynamics 365 Business Central integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own