Two-way sync
Changes in Databricks or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Keep Databricks 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 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 Microsoft Dynamics NAV carries financials, operations, workforce data, or all three, the analysis belongs in Databricks next to everything else the company measures.
Stacksync syncs Sales Orders & Invoices, Purchase Orders, G/L Entries, Item Ledger Entries from Microsoft Dynamics NAV into tables in Databricks continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Databricks can be written back to fields in Microsoft Dynamics NAV where that is useful.
Operational records become queryable tables in Databricks, joinable with sales and finance data.
Combine Microsoft Dynamics NAV's records with data synced from other systems in Databricks for consolidated views no single system can produce.
Classifications or reference values computed in Databricks sync back onto the corresponding records in 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.
| Databricks objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Change Data Feed Row-level change records on Delta tables that drive incremental reads. | Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Change Data Feed is specific to Databricks and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Catalogs is specific to Databricks and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Schemas Group tables and views; syncs typically target a dedicated schema per source system. | G/L Entries Posted ledger entries replicated to warehouses for finance reporting. | Schemas is specific to Databricks and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | Item Ledger Entries Inventory movement history read for stock and costing analytics. | Delta Tables is specific to Databricks and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Views Curated read-only projections used as sync sources for downstream tools. | Dimensions Analytical codes carried on documents and entries for reporting splits. | Views is specific to Databricks and Dimensions to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. | Companies Per-company data partitions that scope every sync. | Materialized Views is specific to Databricks and Companies 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 Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.
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 Databricks as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Microsoft Dynamics NAV connection.
Changes in Databricks or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Databricks 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 Databricks or Microsoft Dynamics NAV record.
Track your Databricks ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Databricks 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 Databricks 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 Databricks 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 548 integrations available for Databricks and Microsoft Dynamics NAV.