Two-way sync
Changes in AWS Aurora MySQL or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep AWS Aurora MySQL 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.
Teams pair Dynamics 365 Business Central with AWS Aurora MySQL to work with ERP data as regular database tables. Business Central Customers, Items, and Sales Orders sync into Aurora, where custom applications and reports use SQL, and edits to Aurora rows write back to Business Central without per-endpoint API work.
Stacksync mirrors Journals, Dimensions, Payments, Customers from Dynamics 365 Business Central into AWS Aurora MySQL 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 AWS Aurora MySQL sync back into Dynamics 365 Business Central with its validations respected.
Business Central Customers, Vendors, and Items replicate into Aurora MySQL tables for application access.
Sales Orders and Purchase Orders mirror to Aurora rows so operations tools track fulfillment state.
Sales Invoices land in an Aurora table for finance dashboards and reconciliation queries.
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 | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Rows Inserted, updated, and deleted individually or in bulk during two-way syncs. | Journals Staging records for financial postings created by integrations before posting. | Rows is specific to AWS Aurora MySQL and Journals to Dynamics 365 Business Central — 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. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Columns is specific to AWS Aurora MySQL and Dimensions to Dynamics 365 Business Central — 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. | Payments Customer and vendor payment records reconciled against invoices. | Primary keys and indexes is specific to AWS Aurora MySQL and Payments to Dynamics 365 Business Central — 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. | Customers Core master data synced with CRMs so sales and finance share one customer list. | Views is specific to AWS Aurora MySQL and Customers to Dynamics 365 Business Central — 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. | Vendors Supplier master data synced with procurement and AP automation tools. | Foreign keys is specific to AWS Aurora MySQL and Vendors to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Stored procedures and triggers Existing database logic keeps firing on rows written by a sync. | Items Product and inventory records aligned with e-commerce and warehouse systems. | Stored procedures and triggers is specific to AWS Aurora MySQL and Items to Dynamics 365 Business Central — 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 written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.
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 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–Dynamics 365 Business Central connection.
Changes in AWS Aurora MySQL or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever AWS Aurora MySQL or Dynamics 365 Business Central 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 Dynamics 365 Business Central record.
Track your AWS Aurora MySQL ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between AWS Aurora MySQL and Dynamics 365 Business Central.
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 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.
Pick the AWS Aurora MySQL 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between AWS Aurora MySQL and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as AWS Aurora MySQL's Rows and Columns), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the AWS Aurora MySQL side: Primary keys and indexes, Views, Foreign keys, Stored procedures and triggers, plus custom fields where AWS Aurora MySQL exposes them. On the Dynamics 365 Business Central side: Journals, Dimensions, Payments, Customers. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for AWS Aurora MySQL and Dynamics 365 Business Central: ERP tables in Aurora; Order status sync; Invoice reporting feed. Business Central Customers, Vendors, and Items replicate into Aurora MySQL tables for application access.
AWS Aurora MySQL: SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC. Authentication: Database credentials, optionally AWS IAM database authentication, over TLS. Dynamics 365 Business Central: 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. Stacksync manages authentication, retries, and rate limits on both sides.
AWS Aurora MySQL: Aurora MySQL is wire-compatible with MySQL, so any standard MySQL driver, ORM, or CDC tooling works without modification. Dynamics 365 Business Central: Posted documents such as posted invoices and GL entries are immutable by design; corrections happen through new postings, which shapes how bi-directional syncs handle financial data. Stacksync's field mapping accounts for these differences between AWS Aurora MySQL and Dynamics 365 Business Central without custom code.
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 453 integrations available for AWS Aurora MySQL and Dynamics 365 Business Central.