Two-way sync
Changes in Infor M3 or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep Infor M3 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.
Companies run two ERPs for structural reasons: a two-tier setup with subsidiaries on lighter systems, an acquisition that brought its own stack, a split by function or region, or a migration that will take quarters. In all of these, some of the same organizations, people, and transactions exist in both systems, and keeping them aligned by hand is a standing tax on the back office.
Stacksync syncs Items, Customers, Suppliers, Customer Orders in Infor M3 with General Ledger Entries, Journals, Dimensions, Payments in Dynamics 365 Business Central bi-directionally and in real time, with field-level mapping across the two data models and conflict rules you define. A record changed in either system is reflected in the other within seconds, not at the next interface run.
When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.
Where one system is the people or finance suite and the other runs operations, the records both sides depend on, such as organizations, cost centers, and reference data, stay in agreement.
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.
| Infor M3 objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Items Item master records provide the SKU, unit, and attribute data other systems price and sell against. | Items Product and inventory records aligned with e-commerce and warehouse systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Customers Customer master records sync with CRM account records to keep one shared customer file. | Customers Core master data synced with CRMs so sales and finance share one customer list. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Purchase Orders PO headers and lines sync outward so buyers and receiving teams see the same demand. | Purchase Orders Procurement documents exchanged with supplier-facing systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Customer Orders Orders created in commerce or CRM systems land in M3 for fulfillment and invoicing. | Journals Staging records for financial postings created by integrations before posting. | Customer Orders is specific to Infor M3 and Journals to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Manufacturing Orders Production order status feeds portals and CRMs so promised dates reflect the shop floor. | Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. | Manufacturing Orders is specific to Infor M3 and Dimensions to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Inventory Balances On-hand quantities by warehouse drive available-to-promise in downstream channels. | Payments Customer and vendor payment records reconciled against invoices. | Inventory Balances is specific to Infor M3 and Payments 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.
DetectionInfor M3 notifies Stacksync of record changes through webhook events. Event publishing through Infor ION (Business Object Documents), configured in ION, or scheduled polling of API endpoints.
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 written to Infor M3 through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Infor M3–Dynamics 365 Business Central connection.
Changes in Infor M3 or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Infor M3 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 Infor M3 or Dynamics 365 Business Central record.
Track your Infor M3 ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Infor M3 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 Infor M3 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 Infor M3 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 Infor M3 and Dynamics 365 Business Central: authenticate both systems, choose the objects to sync (such as Infor M3's Items and Customers), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Infor M3 side: Items, Customers, Suppliers, Customer Orders, plus custom fields where Infor M3 exposes them. On the Dynamics 365 Business Central side: General Ledger Entries, Journals, Dimensions, Payments. 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 Infor M3 and Dynamics 365 Business Central: Migration in parallel; Shared master data; Split by function. When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.
Infor M3: REST API (M3 API programs exposed through the Infor ION API gateway). Authentication: OAuth 2.0 via Infor OS / ION API authorization. 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.
Infor M3: M3 business logic is exposed through M3 API programs (MI programs), which Infor publishes as REST endpoints through the ION API gateway rather than as a single flat resource model. Dynamics 365 Business Central: Custom API pages written in AL extend the same OData surface, letting partner-specific tables participate in syncs like standard entities. Stacksync's field mapping accounts for these differences between Infor M3 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 508 integrations available for Infor M3 and Dynamics 365 Business Central.