Skip to content
Business productivity ⇄ ERP

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

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

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Gatekeeper and Microsoft Dynamics NAV.

The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Gatekeeper is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.

Stacksync syncs Users, Categories, Contracts, Vendors (Suppliers) in Gatekeeper with Dimensions, Companies, Customers, Vendors in Microsoft Dynamics NAV bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.

Common use cases

  • 01 Stream workflow-form data - intake requests, vendor onboarding, risk assessments - into an operational database for cycle-time and compliance reporting.
  • 02 Write contract or vendor records into Gatekeeper when a deal closes in the CRM to kick off downstream procurement and legal workflows.
  • 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 Gatekeeper collects payments: transactions post through

Payment events sync into Microsoft Dynamics NAV as they occur, keeping the enterprise records current without manual entry.

Where Microsoft Dynamics NAV is the HR or people system of record

Worker and organization data from Microsoft Dynamics NAV stays current in Gatekeeper, so the tools people use daily reflect the org as it actually is.

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

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

Gatekeeper objects Microsoft Dynamics NAV objects How this pairing syncs
Workflow form data The structured data captured on Gatekeeper workflow forms (intake requests, vendor onboarding, risk assessments); exposed by the API since 2025 so form results sync into an operational database, not only contract and vendor records. G/L Entries Posted ledger entries replicated to warehouses for finance reporting. Workflow form data is specific to Gatekeeper and G/L Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Custom data groups Customer-configured custom fields and data groups; because the JSON:API and its docs are dynamic, any custom data added in Configuration exposes the same read/write endpoints as the standard objects and syncs the same way. Item Ledger Entries Inventory movement history read for stock and costing analytics. Custom data groups is specific to Gatekeeper and Item Ledger Entries to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Users Gatekeeper user and team records governed by role-based access; read to map contract and vendor owners, approvers, and internal contacts to CRM or HR records. Dimensions Analytical codes carried on documents and entries for reporting splits. Users is specific to Gatekeeper and Dimensions to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Categories The classification taxonomy applied to contracts and vendors (type, department, business unit); synced so categorization stays consistent between Gatekeeper and downstream reporting or ERP dimensions. Companies Per-company data partitions that scope every sync. Categories is specific to Gatekeeper and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Contracts The core contract records holding value, key dates, renewal terms, status, type, owner, and the linked vendor; created, read, updated, and deleted so contract data moves two-way between Gatekeeper and a database, ERP, or CRM. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Contracts is specific to Gatekeeper and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Vendors (Suppliers) Company records for counterparties and suppliers with onboarding status, compliance, risk, contacts, and spend; read and written to keep vendor master data aligned with a CRM or ERP. Vendors Vendor cards aligned with procurement and AP tools. Vendors (Suppliers) is specific to Gatekeeper and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

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

Gatekeeper Microsoft Dynamics NAV Interval-based propagation

DetectionStacksync polls Gatekeeper for changes on an incremental schedule, reading only records changed since the previous pass. No native developer webhook subscription API and no database change-data-capture log.

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

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

Rate-limit considerations

  • Gatekeeper: Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.
What ships with Gatekeeper ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Gatekeeper and Microsoft Dynamics NAV connectors work

Gatekeeper

Integration surface
RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant.
Authentication
API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently.
Change detection
No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream.
Capabilities
read · write
Rate limits
Gatekeeper publishes no fixed public per-minute request quota; throughput is governed per key by its endpoint permissions, and every call is recorded (parameters, payload, response) under API Logs for monitoring. Pace bulk writes and use JSON:API pagination on list endpoints.

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

    Choose tables

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

Gatekeeper 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 405 integrations available for Gatekeeper and Microsoft Dynamics NAV.

Popular · 6 of 405
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.