Skip to content
ERP

E2 Shop System to Microsoft Dynamics NAV integration — real-time data sync

Keep E2 Shop System 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.

  • 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 E2 Shop System and Microsoft Dynamics NAV

Two ERPs, one set of facts: Stacksync keeps E2 Shop System and Microsoft Dynamics NAV consistent in real time, whether they split the business or one is replacing the other.

E2 Shop System is a read-only source: Stacksync reads its data in real time and delivers it into Microsoft Dynamics NAV, so Microsoft Dynamics NAV 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.

Common use cases

  • Keep purchase order data visible to planning or supplier-facing tools without direct ERP access.
  • Replicate job and work order status into a reporting database to power shop-floor and delivery dashboards.
  • Replicate G/L and ledger entries into a warehouse for consolidated finance reporting.
  • Keep inventory availability current in storefronts and customer portals.

Two-tier roll-up

Where subsidiaries run one system and headquarters runs the other, shared records and transactions flow up continuously, so consolidation starts from live data.

Migration in parallel

When one system is replacing the other, run both fully live during the transition and cut over without a data freeze.

Shared master data

Where both systems keep records of the same customers, suppliers, or organizations, a correction in either updates the other.

What you can sync between E2 Shop System and Microsoft Dynamics NAV

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 Microsoft Dynamics NAV objects
Parts Part masters with routings and material definitions specific to each shop. Items Item cards and availability mirrored to ecommerce and planning systems.
Routings / Operations Per-part operation sequences that carry estimated and actual times. Sales Orders & Invoices Sales documents created from external orders and read back for posting status.
Purchase orders Outside material and service purchases tied to jobs. Purchase Orders Purchasing documents reconciled with receiving and vendor systems.
Time tickets Labor collection records used for job costing. G/L Entries Posted ledger entries replicated to warehouses for finance reporting.
Invoices Billing records synced to accounting for AR reporting. Item Ledger Entries Inventory movement history read for stock and costing analytics.
Quotes / Estimates Job shop quotes with material and routing cost buildups; the start of the order lifecycle. Dimensions Analytical codes carried on documents and entries for reporting splits.
What ships with E2 Shop System ⇄ Microsoft Dynamics NAV

Connect E2 Shop System and Microsoft Dynamics NAV for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every E2 Shop System–Microsoft Dynamics NAV connection.

Real-time

Real-time sync

Changes in E2 Shop System or Microsoft Dynamics NAV instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever E2 Shop System or Microsoft Dynamics NAV 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 E2 Shop System or Microsoft Dynamics NAV record.

Observability

Monitoring

Track your E2 Shop System ⇄ Microsoft Dynamics NAV sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between E2 Shop System and Microsoft Dynamics NAV.

How the E2 Shop System and Microsoft Dynamics NAV connectors work

E2 Shop System

Integration surface
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
Change detection
Polling database tables or scheduled exports
Capabilities
read
Rate limits
Not API-bound; constrained by on-premises database access windows

Microsoft Dynamics NAV

Integration surface
SOAP and OData web services published from NAV pages and codeunits; direct SQL Server access on-premises
Authentication
Windows authentication or NavUserPassword credentials
Change detection
Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases; no native webhooks
Capabilities
read · write · CDC
How it works

How to connect E2 Shop System to Microsoft Dynamics NAV — 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 E2 Shop System 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    E2 Shop System connected
    Microsoft Dynamics NAV connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the E2 Shop System 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · E2 Shop System ⇄ Microsoft Dynamics NAV
    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
    E2 Shop System Microsoft Dynamics NAV
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

E2 Shop System and Microsoft Dynamics NAV integration FAQ

SECURITY

Security teams love 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
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for E2 Shop System and Microsoft Dynamics NAV.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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