Skip to content
ERP

Linnworks to Microsoft Dynamics NAV integration — real-time, two-way sync

Keep Linnworks 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 Linnworks and Microsoft Dynamics NAV

Two ERPs, one set of facts: Stacksync keeps Linnworks and Microsoft Dynamics NAV 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 Stock Items, Stock Levels, Locations, Purchase Orders in Linnworks with Vendors, Items, Sales Orders & Invoices, Purchase Orders in Microsoft Dynamics NAV 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

  • Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
  • Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
  • Sync customers, items, and orders between NAV and a CRM in both directions.
  • Push ecommerce orders into NAV sales orders through published page services.

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 Linnworks 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.

Linnworks objects Microsoft Dynamics NAV objects
Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Sales Orders & Invoices Sales documents created from external orders and read back for posting status.
Locations Warehouse and fulfillment location records scope stock data during mapping. Purchase Orders Purchasing documents reconciled with receiving and vendor systems.
Purchase Orders Replenishment POs sync with suppliers and accounting systems. G/L Entries Posted ledger entries replicated to warehouses for finance reporting.
Suppliers Vendor records keep procurement data consistent across tools. Item Ledger Entries Inventory movement history read for stock and costing analytics.
Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. Dimensions Analytical codes carried on documents and entries for reporting splits.
Returns & Refunds Post-sale records flow to finance and support systems. Companies Per-company data partitions that scope every sync.
What ships with Linnworks ⇄ Microsoft Dynamics NAV

Connect Linnworks and Microsoft Dynamics NAV for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Linnworks 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 Linnworks 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 Linnworks or Microsoft Dynamics NAV record.

Observability

Monitoring

Track your Linnworks ⇄ 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 Linnworks and Microsoft Dynamics NAV.

How the Linnworks and Microsoft Dynamics NAV connectors work

Linnworks

Integration surface
REST API
Authentication
Application credentials and an install token exchanged for a session token
Change detection
Polling on order and stock endpoints
Capabilities
read · write
Rate limits
Per-endpoint rate limits apply on the Linnworks API

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 Linnworks 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 Linnworks 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
    Linnworks connected
    Microsoft Dynamics NAV connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Linnworks 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 · Linnworks ⇄ 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
    Linnworks Microsoft Dynamics NAV
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Linnworks 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 Linnworks 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.