Two-way sync
Changes in Apache Cassandra or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Cassandra 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 G/L Entries, Item Ledger Entries, Dimensions, Companies from Microsoft Dynamics NAV into Apache Cassandra 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 Apache Cassandra sync back into Microsoft Dynamics NAV with its validations respected.
Records from Microsoft Dynamics NAV live in Apache Cassandra 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 Apache Cassandra, 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.
| Apache Cassandra objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Collections List, set, and map columns handled with type-aware field mapping. | Dimensions Analytical codes carried on documents and entries for reporting splits. | Collections is specific to Apache Cassandra and Dimensions to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Counters Increment-only counter columns, usually read-only in syncs. | Companies Per-company data partitions that scope every sync. | Counters is specific to Apache Cassandra and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Keyspaces Top-level namespaces with replication settings that scope a sync connection. | Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Keyspaces is specific to Apache Cassandra and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Tables Wide-column tables addressed by partition key, the unit of row-level sync. | Vendors Vendor cards aligned with procurement and AP tools. | Tables is specific to Apache Cassandra and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Partitions and Rows Records located by partition and clustering keys during reads and upserts. | Items Item cards and availability mirrored to ecommerce and planning systems. | Partitions and Rows is specific to Apache Cassandra and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Materialized Views Server-maintained denormalized views; considered experimental and disabled by default in recent releases. | Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Materialized Views is specific to Apache Cassandra and Sales Orders & Invoices 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 Apache Cassandra are captured at the source via change data capture — no polling loop against its API. Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns.
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 written to Apache Cassandra through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Cassandra–Microsoft Dynamics NAV connection.
Changes in Apache Cassandra or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Cassandra 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 Apache Cassandra or Microsoft Dynamics NAV record.
Track your Apache Cassandra ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Cassandra 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 Apache Cassandra 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 Apache Cassandra 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 428 integrations available for Apache Cassandra and Microsoft Dynamics NAV.