Skip to content
ERP

Microsoft Dynamics NAV to SAP S/4HANA integration — real-time, two-way sync

Keep Microsoft Dynamics NAV and SAP S/4HANA 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 Microsoft Dynamics NAV and SAP S/4HANA

Two ERPs, one set of facts: Stacksync keeps Microsoft Dynamics NAV and SAP S/4HANA consistent in real time, whether they split the business or one is replacing the other.

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 Purchase Orders, G/L Entries, Item Ledger Entries, Dimensions in Microsoft Dynamics NAV with Products / Materials, Billing Documents (Invoices), Deliveries, Journal Entries in SAP S/4HANA 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.

Common use cases

  • 01 Keep inventory availability current in storefronts and customer portals.
  • 02 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.
  • 03 Surface invoice and payment status from S/4HANA inside the CRM so account teams see open balances.
  • 04 Replicate material master and pricing data to e-commerce and quoting tools.

Common sync patterns

Shared master data

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

Split by function

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.

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.

What you can sync between Microsoft Dynamics NAV and SAP S/4HANA

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.

Microsoft Dynamics NAV objects SAP S/4HANA objects How this pairing syncs
Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Purchase Orders Procurement documents shared with supplier portals and spend-management tools. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Companies Per-company data partitions that scope every sync. Billing Documents (Invoices) Invoice data pushed to CRMs and payment or collections tools for finance visibility. Companies is specific to Microsoft Dynamics NAV and Billing Documents (Invoices) to SAP S/4HANA — each maps to any object or custom field on the other side.
Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Deliveries Outbound delivery status synced to customer-facing systems for order tracking. Customers is specific to Microsoft Dynamics NAV and Deliveries to SAP S/4HANA — each maps to any object or custom field on the other side.
Vendors Vendor cards aligned with procurement and AP tools. Journal Entries Financial postings read into warehouses and consolidation tools for reporting. Vendors is specific to Microsoft Dynamics NAV and Journal Entries to SAP S/4HANA — each maps to any object or custom field on the other side.
Items Item cards and availability mirrored to ecommerce and planning systems. Customer / Supplier Roles Role-specific views of Business Partners mapped to CRM account types. Items is specific to Microsoft Dynamics NAV and Customer / Supplier Roles to SAP S/4HANA — each maps to any object or custom field on the other side.
Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Production Orders Manufacturing order status surfaced in planning and operations tools. Sales Orders & Invoices is specific to Microsoft Dynamics NAV and Production Orders to SAP S/4HANA — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics NAV and SAP S/4HANA

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.

Microsoft Dynamics NAV SAP S/4HANA Sub-second propagation

DetectionChanges in Microsoft Dynamics NAV are captured at the source via change data capture — no polling loop against its API. Polling on modified/timestamp fields, or SQL Server change tracking/CDC on on-premises databases.

DeliveryEach detected change is written to SAP S/4HANA through its API, with automatic retries and rate-limit backoff.

SAP S/4HANA Microsoft Dynamics NAV Interval-based propagation

DetectionStacksync polls SAP S/4HANA for changes on an incremental schedule, reading only records changed since the previous pass. Polling on change timestamps exposed by the OData services.

DeliveryEach detected change is applied to Microsoft Dynamics NAV as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • SAP S/4HANA: Subject to the platform's API rate limits, which vary by edition and communication arrangement.
What ships with Microsoft Dynamics NAV ⇄ SAP S/4HANA

Connect Microsoft Dynamics NAV and SAP S/4HANA for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Microsoft Dynamics NAV–SAP S/4HANA connection.

Real-time

Two-way sync

Changes in Microsoft Dynamics NAV or SAP S/4HANA instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics NAV or SAP S/4HANA 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 Microsoft Dynamics NAV or SAP S/4HANA record.

Observability

Monitoring

Track your Microsoft Dynamics NAV ⇄ SAP S/4HANA sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Microsoft Dynamics NAV and SAP S/4HANA.

How the Microsoft Dynamics NAV and SAP S/4HANA connectors work

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

SAP S/4HANA

Integration surface
OData REST APIs (v2/v4), with SOAP, BAPI/RFC, and IDoc interfaces on on-premise editions
Authentication
OAuth 2.0 with communication arrangements on cloud editions; basic auth or certificate-based on-premise
Change detection
Polling on change timestamps exposed by the OData services; business events can be emitted through SAP's event infrastructure on cloud editions
Capabilities
read · write
Rate limits
Subject to the platform's API rate limits, which vary by edition and communication arrangement
How it works

How to connect Microsoft Dynamics NAV to SAP S/4HANA — 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 Microsoft Dynamics NAV and SAP S/4HANA 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
    Microsoft Dynamics NAV connected
    SAP S/4HANA connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Microsoft Dynamics NAV and SAP S/4HANA 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 · Microsoft Dynamics NAV ⇄ SAP S/4HANA
    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
    Microsoft Dynamics NAV SAP S/4HANA
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Microsoft Dynamics NAV and SAP S/4HANA 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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 507 integrations available for Microsoft Dynamics NAV and SAP S/4HANA.

Popular · 5 of 507
All Microsoft Dynamics NAV integrations All SAP S/4HANA integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own