Skip to content
Accounting and finance ⇄ ERP

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

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

Keep Logisense and Microsoft Dynamics NAV 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 Account, Contact, Package and Service, Account Service in Logisense with Customers, Vendors, Items, Sales Orders & Invoices in Microsoft Dynamics NAV 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 Write new signups from a product database into LogiSense as Accounts with the correct Package and Account Services.
  • 02 Stream Usage records from a warehouse or product event pipeline into LogiSense for rating and usage-based Invoices.
  • 03 Keep inventory availability current in storefronts and customer portals.
  • 04 Run parallel sync during a NAV-to-Business Central migration so both systems stay usable.

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 Logisense serves a business unit and Microsoft Dynamics NAV is the group system, transactions and customer records roll up continuously, so consolidation starts from live data.

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

Logisense objects Microsoft Dynamics NAV objects How this pairing syncs
Contact People attached to an Account (billing, technical); synced two-way with CRM contacts and warehouse person records. G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Contact is specific to Logisense and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Package and Service Product catalog of offerings and their chargeable services (one-time, recurring, usage-based); read for reporting or written from a catalog source. Item Ledger Entries Inventory movement history read for stock and costing analytics. Package and Service is specific to Logisense and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Account Service Billable line item of a Package assigned to an account; written when provisioning or changing a subscription, read for entitlement checks. Dimensions Analytical codes carried on documents and entries for reporting splits. Account Service is specific to Logisense and Dimensions to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Usage Metered usage records fed to the rating engine and classified by Usage Class and Unit; written in from product or warehouse event data. Companies Per-company data partitions that scope every sync. Usage is specific to Logisense and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Invoice Generated billing documents with items, history, and status; typically read out to ERPs and warehouses for finance and reconciliation. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Invoice is specific to Logisense and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Payment Payment records whose status changes emit webhooks; read for cash reconciliation and to drive dunning and provisioning workflows. Vendors Vendor cards aligned with procurement and AP tools. Payment is specific to Logisense and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

How changes propagate between Logisense 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.

Logisense Microsoft Dynamics NAV Sub-second propagation

DetectionLogisense notifies Stacksync of record changes through webhook events. Webhook event subscriptions push near-real-time notifications on record status changes (e.g.

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

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

Rate-limit considerations

  • Logisense: No publicly documented fixed request cap; JWT access tokens are short-lived, and high-volume usage is ingested through mediation feeds rather than per-record API writes.
What ships with Logisense ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Logisense and Microsoft Dynamics NAV connectors work

Logisense

Integration surface
REST API (versioned, e.g. v9/v10)
Authentication
JSON Web Token (JWT) bearer tokens obtained via the API and refreshed before expiry
Change detection
Webhook event subscriptions push near-real-time notifications on record status changes (e.g. Payment Status Updated), with a Webhook Monitor for retries; entities without webhook coverage are polled via filtered REST queries
Capabilities
read · write · webhooks
Rate limits
No publicly documented fixed request cap; JWT access tokens are short-lived, and high-volume usage is ingested through mediation feeds rather than per-record API writes.
Logisense setup guide

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

    Choose tables

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

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

Popular · 7 of 397
All Logisense 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