Skip to content
Business productivity ⇄ Accounting and finance

Microsoft Dynamics 365 to Navan integration — real-time, two-way sync

Keep Microsoft Dynamics 365 and Navan 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 365 and Navan

Connect the financial records in Navan with the work happening in Microsoft Dynamics 365, so both stay current without exports or copy-paste.

Navan holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft Dynamics 365 is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Custom Fields, Receipts, Repayments, Fees, and Adjustments, Users in Navan and Opportunities, Cases (Incidents), Quotes, Orders & Invoices, Products in Microsoft Dynamics 365 in sync, bi-directionally and in real time. Whatever records Microsoft Dynamics 365 keeps and whatever events it produces, the overlap with Navan is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Pull Bookings by date range into a database to reconcile travel reservations against Card Transactions and monitor travel-policy spend.
  • 02 Sync Users and department mappings from an HRIS into reporting tables so every transaction is attributed to a cost center and manager.
  • 03 Sync cases with external ticketing or product systems so support works one queue.
  • 04 Replicate standard and custom Dataverse tables into a warehouse for reporting.

Common sync patterns

Where Microsoft Dynamics 365 collects payments or triggers charges: events land in Navan

Payment and charge activity flows into Navan as it happens, so the books reflect reality without manual reconciliation.

Where Microsoft Dynamics 365 tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where Microsoft Dynamics 365 handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Navan next to the customer they are helping, without logging into the finance system.

What you can sync between Microsoft Dynamics 365 and Navan

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 365 objects Navan objects How this pairing syncs
Quotes, Orders & Invoices Transaction documents reconciled with the ERP or billing source of truth. Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Quotes, Orders & Invoices is specific to Microsoft Dynamics 365 and Connect Transactions to Navan — each maps to any object or custom field on the other side.
Products Catalog records aligned with ERP item masters. Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Products is specific to Microsoft Dynamics 365 and Manual Transactions to Navan — each maps to any object or custom field on the other side.
Activities Emails, calls, and tasks captured for engagement analytics. Bookings Flight, hotel, rail, and car reservations from the Booking API; pulled read-only by createdFrom/createdTo date range for trip and travel-spend reporting. Activities is specific to Microsoft Dynamics 365 and Bookings to Navan — each maps to any object or custom field on the other side.
Custom Tables Dataverse tables that carry business-specific entities through the same API surface. Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Custom Tables is specific to Microsoft Dynamics 365 and Custom Fields to Navan — each maps to any object or custom field on the other side.
Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. Accounts is specific to Microsoft Dynamics 365 and Receipts to Navan — each maps to any object or custom field on the other side.
Contacts Person records kept consistent with marketing, support, and data-warehouse copies. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Contacts is specific to Microsoft Dynamics 365 and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 and Navan

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 365 Navan Sub-second propagation

DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.

DeliveryEach detected change is written to Navan through its API, with automatic retries and rate-limit backoff.

Navan Microsoft Dynamics 365 Sub-second propagation

DetectionNavan notifies Stacksync of record changes through webhook events. Navan's Expense API supports webhooks for transaction and expense events.

DeliveryEach detected change is written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Navan: Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
What ships with Microsoft Dynamics 365 ⇄ Navan

Connect Microsoft Dynamics 365 and Navan for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Microsoft Dynamics 365 or Navan instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Microsoft Dynamics 365 or Navan 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 365 or Navan record.

Observability

Monitoring

Track your Microsoft Dynamics 365 ⇄ Navan 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 365 and Navan.

How the Microsoft Dynamics 365 and Navan connectors work

Microsoft Dynamics 365

Integration surface
REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
Authentication
Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
Change detection
Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
Capabilities
read · write · CDC · webhooks
Microsoft Dynamics 365 setup guide

Navan

Integration surface
REST (Expense API and Booking API)
Authentication
OAuth 2.0 client-credentials flow; an admin creates a client_id and client_secret under Settings > Integrations and exchanges them at Navan's OAuth token endpoint for a short-lived bearer token that is refreshed on expiry (separate US and EU regional hosts)
Change detection
Navan's Expense API supports webhooks for transaction and expense events; sync engines also poll GET endpoints with date-range and updatedAt filters (createdFrom/createdTo for bookings) to backfill history and reconcile. There is no database-level CDC.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled with HTTP 429 and Navan recommends retrying with exponential backoff; the Expense/Public API must first be enabled per account by Navan.
How it works

How to connect Microsoft Dynamics 365 to Navan — 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 365 and Navan 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 365 connected
    Navan connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Microsoft Dynamics 365 and Navan 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
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:

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 508 integrations available for Microsoft Dynamics 365 and Navan.

Popular · 8 of 508
All Microsoft Dynamics 365 integrations All Navan 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