Skip to content
ERP ⇄ Accounting and finance

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

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

Keep Navan and Microsoft Dynamics GP agreeing on customers, invoices, and balances, whether they split the finance workload or one is replacing the other.

A dedicated finance tool and an ERP end up side by side for practical reasons: a subsidiary runs lighter software than headquarters, billing runs in a specialist system while the enterprise system holds the wider view, or the company is mid-migration and both are live. Whatever the split, the two systems describe overlapping customers and transactions, and that overlap drifts without a live connection.

Stacksync syncs Receipts, Repayments, Fees, and Adjustments, Users, Card Transactions in Navan with Inventory Items (IV), GL Accounts & Journal Entries, Receivables & Payables Transactions, Company Databases in Microsoft Dynamics GP in real time and in both directions. You decide which system wins on which field, and every change made in one is reflected in the other within seconds instead of at the next batch run.

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 Keep item and inventory data aligned with an ecommerce storefront.
  • 04 Run continuous sync between GP and a replacement cloud ERP during migration.

Common sync patterns

Migration without a hard cutover

When one system is replacing the other, run both in parallel with records matching until the switch is complete.

One customer and vendor master

Where both systems keep records of the same organizations, corrections made in either propagate to the other.

Subsidiary to headquarters

Where Navan serves a business unit and Microsoft Dynamics GP is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

What you can sync between Microsoft Dynamics GP 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 GP objects Navan objects How this pairing syncs
GL Accounts & Journal Entries Financial ledger data replicated to warehouses for consolidated reporting. Repayments, Fees, and Adjustments Money-movement records including repayments, FX and platform fees, and credit or debit memos; read-only for reconciliation ledgers. GL Accounts & Journal Entries is specific to Microsoft Dynamics GP and Repayments, Fees, and Adjustments to Navan — each maps to any object or custom field on the other side.
Receivables & Payables Transactions Open and historical AR/AP transactions read for cash and aging reporting. Users Employee and cardholder records referenced by every transaction; usually provisioned from an HRIS and used to map spend to people and departments. Receivables & Payables Transactions is specific to Microsoft Dynamics GP and Users to Navan — each maps to any object or custom field on the other side.
Company Databases Per-company SQL databases that define the scope of any sync. 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. Company Databases is specific to Microsoft Dynamics GP and Card Transactions to Navan — each maps to any object or custom field on the other side.
Customers Receivables master records (RM tables) synced with CRMs and billing tools. Connect Transactions External and personal card feed matched into Navan; retrieved read-only and coded with custom-field values through the transaction update endpoint. Customers is specific to Microsoft Dynamics GP and Connect Transactions to Navan — each maps to any object or custom field on the other side.
Vendors Payables master records aligned with procurement and AP automation. Manual Transactions Out-of-pocket reimbursements and payroll submissions; synced for approval and reimbursement, then GL-coded back into Navan. Vendors is specific to Microsoft Dynamics GP and Manual Transactions to Navan — each maps to any object or custom field on the other side.
Sales Documents (SOP) Quotes, orders, and invoices created via eConnect from web or CRM orders. 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. Sales Documents (SOP) is specific to Microsoft Dynamics GP and Bookings to Navan — each maps to any object or custom field on the other side.

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

DetectionChanges in Microsoft Dynamics GP are captured at the source via change data capture — no polling loop against its API. SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps.

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

Navan Microsoft Dynamics GP 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 applied to Microsoft Dynamics GP as a row-level write, with types converted between the two schemas.

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 GP ⇄ Navan

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Microsoft Dynamics GP and Navan connectors work

Microsoft Dynamics GP

Integration surface
SQL Server database access plus the eConnect stored-procedure API; Web Services for GP on some deployments
Authentication
SQL Server credentials or Windows authentication
Change detection
SQL Server change tracking or log-based CDC on the company database, or polling on row timestamps
Capabilities
read · write · CDC

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

    Choose tables

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

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

Popular · 8 of 500
All Microsoft Dynamics GP 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