Skip to content
CRM ⇄ Accounting and finance

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

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

Sync customers, invoices, and payment status between Navan and Microsoft Dynamics 365 Sales in real time, so sales sees the money and finance sees the relationship.

Finance and sales describe the same customers in different systems. Microsoft Dynamics 365 Sales knows the relationship: who the contacts are and what is in motion with the account. Navan knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.

Stacksync links Connect Transactions, Manual Transactions, Bookings, Custom Fields in Navan to Contacts, Leads, Opportunities, Quotes in Microsoft Dynamics 365 Sales with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.

Common use cases

  • 01 Sync Card Transactions and Manual Transactions into Postgres or a warehouse so finance analyzes corporate spend in SQL without manual CSV exports.
  • 02 Push coded expense transactions into an accounting system, then set their ERP sync status in Navan so the same records are not exported twice.
  • 03 Bi-directional sync of accounts, contacts, and opportunities with a SQL database so teams query CRM data without OData or FetchXML.
  • 04 Write product usage and warehouse-computed scores onto Dataverse tables so sellers see them in the model-driven app.

Common sync patterns

Payment status on the account

Invoice and payment status from Navan appears on the account in Microsoft Dynamics 365 Sales, so reps see overdue balances before they promise the next order.

Billing detail changes flow back

When a contact or address is corrected in Microsoft Dynamics 365 Sales, Navan gets the update before the next invoice goes out.

Collections with context

Finance sees the account owner and relationship history from Microsoft Dynamics 365 Sales when chasing a balance, and sales sees that the chase is happening.

What you can sync between Microsoft Dynamics 365 Sales 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 Sales objects Navan objects How this pairing syncs
Leads Prospect records; written in from enrichment or web forms, read out on qualification. 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. Leads is specific to Microsoft Dynamics 365 Sales and Bookings to Navan — each maps to any object or custom field on the other side.
Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. Custom Fields Company metadata such as cost centers and project codes; discovered via GET and their option lists created or updated via async POST. Opportunities is specific to Microsoft Dynamics 365 Sales and Custom Fields to Navan — each maps to any object or custom field on the other side.
Quotes Pricing proposals; often synced with CPQ or ERP pricing data. Receipts Receipt images tied to each transaction; fetched read-only through presigned URLs for archival in a warehouse or document store. Quotes is specific to Microsoft Dynamics 365 Sales and Receipts to Navan — each maps to any object or custom field on the other side.
Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. Orders is specific to Microsoft Dynamics 365 Sales and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side.
Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Invoices is specific to Microsoft Dynamics 365 Sales and Users to Navan — each maps to any object or custom field on the other side.
Activities Emails, calls, appointments, and tasks; read out for activity analytics. Card Transactions Navan physical and virtual card spend; read via GET, then GL codes, cost centers, and ERP sync status are written back per transaction through the transaction update endpoint. Activities is specific to Microsoft Dynamics 365 Sales and Card Transactions to Navan — each maps to any object or custom field on the other side.

How changes propagate between Microsoft Dynamics 365 Sales 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 Sales Navan Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

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

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

Rate-limit considerations

  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
  • 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 Sales ⇄ Navan

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

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

Real-time

Two-way sync

Changes in Microsoft Dynamics 365 Sales 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 Sales 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 Sales or Navan record.

Observability

Monitoring

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

How the Microsoft Dynamics 365 Sales and Navan connectors work

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.

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 Sales 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 Sales 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 Sales connected
    Navan connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 6 of 426
All Microsoft Dynamics 365 Sales 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