Two-way sync
Changes in AWS Aurora MySQL or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Keep AWS Aurora MySQL 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 AWS Aurora MySQL 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 AWS Aurora MySQL sync back into Microsoft Dynamics NAV with its validations respected.
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 AWS Aurora MySQL, so jobs and triggers can respond as the business record changes.
Worker and org records stay current in AWS Aurora MySQL for provisioning, access, and reporting systems that read from the database.
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.
| AWS Aurora MySQL objects | Microsoft Dynamics NAV objects | How this pairing syncs | |
|---|---|---|---|
| Tables The primary sync unit; each table maps one-to-one to a table or object in the paired system. | Companies Per-company data partitions that scope every sync. | Tables is specific to AWS Aurora MySQL and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Rows Inserted, updated, and deleted individually or in bulk during two-way syncs. | Customers Customer cards synced with CRMs so sales sees ERP balances and terms. | Rows is specific to AWS Aurora MySQL and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Columns MySQL data types are mapped to the paired system's field types during schema setup. | Vendors Vendor cards aligned with procurement and AP tools. | Columns is specific to AWS Aurora MySQL and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Primary keys and indexes Used to match rows across systems and keep incremental syncs efficient. | Items Item cards and availability mirrored to ecommerce and planning systems. | Primary keys and indexes is specific to AWS Aurora MySQL and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Views Can serve as read-only sync sources for derived or filtered datasets. | Sales Orders & Invoices Sales documents created from external orders and read back for posting status. | Views is specific to AWS Aurora MySQL and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side. | |
| Foreign keys Express relationships that syncs preserve when mapping to related objects elsewhere. | Purchase Orders Purchasing documents reconciled with receiving and vendor systems. | Foreign keys is specific to AWS Aurora MySQL and Purchase Orders 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 AWS Aurora MySQL are captured at the source via change data capture — no polling loop against its API. Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback.
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 AWS Aurora MySQL as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every AWS Aurora MySQL–Microsoft Dynamics NAV connection.
Changes in AWS Aurora MySQL or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever AWS Aurora MySQL 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 AWS Aurora MySQL or Microsoft Dynamics NAV record.
Track your AWS Aurora MySQL ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL 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 AWS Aurora MySQL 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 AWS Aurora MySQL 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 448 integrations available for AWS Aurora MySQL and Microsoft Dynamics NAV.