Skip to content
CRM ⇄ ERP

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

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

Close the gap between front office and back office: Kustomer and Microsoft Dynamics NAV share customers and status in real time, in both directions.

Kustomer holds the customer relationship; Microsoft Dynamics NAV runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.

Stacksync syncs Companies, Custom Objects (Klasses), Users, Teams in Kustomer with Dimensions, Companies, Customers, Vendors in Microsoft Dynamics NAV field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Keep customer attributes updated from billing systems so routing rules and SLAs reflect account value
  • 02 Escalate conversation-derived signals into the CRM as tasks or opportunities
  • 03 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.
  • 04 Sync customers, items, and orders between NAV and a CRM in both directions.

Common sync patterns

Where Microsoft Dynamics NAV is the finance system of record: money status on the account

Invoice and payment state from Microsoft Dynamics NAV shows on the account in Kustomer, so reps see balances before promising the next order.

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

Where Microsoft Dynamics NAV manages people and org data: keep Kustomer aligned

Owners, territories, and org structure informed by Microsoft Dynamics NAV stay current in Kustomer.

What you can sync between Kustomer 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.

Kustomer objects Microsoft Dynamics NAV objects How this pairing syncs
Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. 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.
Companies Organization records group customers and map to CRM accounts. Companies Per-company data partitions that scope every sync. 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.
Custom Objects (Klasses) Structured external records such as orders and subscriptions synced in to appear on the customer timeline. Items Item cards and availability mirrored to ecommerce and planning systems. Custom Objects (Klasses) is specific to Kustomer and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Users Agent records map conversation ownership to people in other systems. Sales Orders & Invoices Sales documents created from external orders and read back for posting status. Users is specific to Kustomer and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Teams Team assignments support routing parity and reporting. Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Teams is specific to Kustomer and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Tags Labels on conversations and customers sync for categorization and analytics. G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Tags is specific to Kustomer and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

How changes propagate between Kustomer and Microsoft Dynamics NAV

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.

Kustomer Microsoft Dynamics NAV Sub-second propagation

DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.

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

Microsoft Dynamics NAV Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Kustomer: Subject to the platform's API rate limits.
What ships with Kustomer ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Kustomer and Microsoft Dynamics NAV connectors work

Kustomer

Integration surface
REST API
Authentication
API key used as a bearer token, scoped by role
Change detection
Outbound webhooks on record events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits

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

    Choose tables

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

Kustomer and Microsoft Dynamics NAV 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 416 integrations available for Kustomer and Microsoft Dynamics NAV.

Popular · 5 of 416
All Kustomer integrations All Microsoft Dynamics NAV 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