Skip to content
Database ⇄ ERP

AWS Aurora MySQL to Dynamics 365 Business Central integration — real-time, two-way sync

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.

  • 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 AWS Aurora MySQL and Dynamics 365 Business Central

Give your engineers Dynamics 365 Business Central's data in AWS Aurora MySQL: read it with normal queries, write back through the sync, and skip the ERP API entirely.

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.

Common use cases

  • 01 Build a customer-facing order portal on Aurora backed by live Business Central Sales Orders.
  • 02 Maintain Item and Vendor master data in Aurora and push changes to Business Central.
  • 03 Join Sales Invoices with operational data in Aurora for margin and aging reports.
  • 04 Sync a production Aurora cluster with an analytics database while filtering out sensitive columns.

Common sync patterns

ERP tables in Aurora

Business Central Customers, Vendors, and Items replicate into Aurora MySQL tables for application access.

Order status sync

Sales Orders and Purchase Orders mirror to Aurora rows so operations tools track fulfillment state.

Invoice reporting feed

Sales Invoices land in an Aurora table for finance dashboards and reconciliation queries.

What you can sync between AWS Aurora MySQL 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.

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.

How changes propagate between AWS Aurora MySQL 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.

AWS Aurora MySQL Dynamics 365 Business Central Sub-second propagation

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.

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

What ships with AWS Aurora MySQL ⇄ Dynamics 365 Business Central

Connect AWS Aurora MySQL and Dynamics 365 Business Central for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in AWS Aurora MySQL 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 AWS Aurora MySQL 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 AWS Aurora MySQL or Dynamics 365 Business Central record.

Observability

Monitoring

Track your AWS Aurora MySQL ⇄ 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 AWS Aurora MySQL and Dynamics 365 Business Central.

How the AWS Aurora MySQL and Dynamics 365 Business Central connectors work

AWS Aurora MySQL

Integration surface
SQL wire protocol (MySQL-compatible), standard MySQL drivers and JDBC
Authentication
Database credentials, optionally AWS IAM database authentication, over TLS
Change detection
Log-based CDC via the MySQL binary log (binlog), with polling on timestamp columns as a fallback
Capabilities
read · write · CDC

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 AWS Aurora MySQL 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 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    AWS Aurora MySQL connected
    Dynamics 365 Business Central connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

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

AWS Aurora MySQL 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.

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:

Coworkers laughing in front of a laptop in a casual office setting

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