Real-time sync
Changes in E2 Shop System or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Keep E2 Shop System 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.
E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Dynamics 365 Business Central, so Dynamics 365 Business Central always reflects the current state of E2 Shop System — without exports, scripts, or schedulers.
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.
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.
| E2 Shop System objects | Dynamics 365 Business Central objects | How this pairing syncs | |
|---|---|---|---|
| Customers Buyer records synced to CRM or accounting counterparts. | 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 the writable direction. Custom fields on either side are included in the mapping. | |
| Vendors Supplier records referenced on purchasing documents. | Vendors Supplier master data synced with procurement and AP automation tools. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in the writable direction. | |
| Purchase orders Outside material and service purchases tied to jobs. | 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 the writable direction. | |
| Time tickets Labor collection records used for job costing. | Payments Customer and vendor payment records reconciled against invoices. | Time tickets is specific to E2 Shop System and Payments to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Invoices Billing records synced to accounting for AR reporting. | Items Product and inventory records aligned with e-commerce and warehouse systems. | Invoices is specific to E2 Shop System and Items to Dynamics 365 Business Central — each maps to any object or custom field on the other side. | |
| Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. | Sales Orders Order headers and lines created from external channels and read back for fulfillment status. | Quotes / Estimates is specific to E2 Shop System and Sales Orders 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.
DetectionStacksync polls E2 Shop System for changes on an incremental schedule, reading only records changed since the previous pass. Polling database tables or scheduled exports.
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.
DeliveryE2 Shop System does not accept inbound record writes, so this direction carries requests rather than records: E2 Shop System's output flows back as field updates on the originating Dynamics 365 Business Central records.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–Dynamics 365 Business Central connection.
Changes in E2 Shop System or Dynamics 365 Business Central instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever E2 Shop System 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 E2 Shop System or Dynamics 365 Business Central record.
Track your E2 Shop System ⇄ Dynamics 365 Business Central sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between E2 Shop System 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 E2 Shop System 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 E2 Shop System 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 integration between E2 Shop System and Dynamics 365 Business Central — E2 Shop System is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
Common patterns for E2 Shop System 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.
E2 Shop System: No broadly documented public web API; integration typically works through the underlying database or application import/export, depending on deployment. Authentication: Database credentials or application-level export access on the on-premises installation. 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.
E2 Shop System: Job shop ERPs of this class organize data around quotes, jobs, and routings rather than standardized product catalogs, so integrations map job-level cost and status data. Dynamics 365 Business Central: The standard API exposes entities as OData v4 endpoints and supports $filter on lastModifiedDateTime, giving integrations a built-in incremental cursor. Stacksync's field mapping accounts for these differences between E2 Shop System and Dynamics 365 Business Central without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means E2 Shop System and Dynamics 365 Business Central records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed E2 Shop System and Dynamics 365 Business Central connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom E2 Shop System–Dynamics 365 Business Central integration in-house.
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 266 integrations available for E2 Shop System and Dynamics 365 Business Central.