Skip to content
Human resources ⇄ ERP

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

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

Sync the workers, org structure, and cost centers that Microsoft Dynamics NAV and Hibob share in real time, so the people Hibob manages stay current in the system that runs finance and operations.

Hibob is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Microsoft Dynamics NAV runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Items, Sales Orders & Invoices, Purchase Orders, G/L Entries in Microsoft Dynamics NAV with People (Employees), Employment, Work, Salaries in Hibob field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Microsoft Dynamics NAV keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Sync customers, items, and orders between NAV and a CRM in both directions.
  • 02 Push ecommerce orders into NAV sales orders through published page services.
  • 03 Push Salaries and Variable Pay from Bob into a payroll provider or warehouse each pay cycle, using the Payroll-permitted service user.
  • 04 Mirror Work data (department, site, manager, title) into an org-chart or reporting warehouse for headcount and structure analysis.

Common sync patterns

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Hibob keep expense and purchase approval chains in Microsoft Dynamics NAV pointed at the right people.

Where Hibob runs payroll: labor cost in the books

Pay and compensation data from Hibob posts into Microsoft Dynamics NAV as labor cost, so finance sees workforce spend without re-entering it by hand.

Where Hibob is the worker system of record: one employee master

When a worker is hired, moved, or offboarded in Hibob, the matching employee record in Microsoft Dynamics NAV is created, updated, or deactivated, so the business system reflects the workforce as it actually is.

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

Hibob objects Microsoft Dynamics NAV objects How this pairing syncs
Time off Absence requests and who's-out data via /timeoff/employees/{id}/requests and /timeoff/whosout; submit new requests and read balances. Companies Per-company data partitions that scope every sync. Time off is specific to Hibob and Companies to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. Customers Customer cards synced with CRMs so sales sees ERP balances and terms. Lifecycle is specific to Hibob and Customers to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Documents Employee documents accessed under the Docs API; gated behind the Documents permission granted per service user. Vendors Vendor cards aligned with procurement and AP tools. Documents is specific to Hibob and Vendors to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Named lists Dropdown option lists such as departments and sites used to resolve field values when mapping People records during sync. Items Item cards and availability mirrored to ecommerce and planning systems. Named lists is specific to Hibob and Items to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
People (Employees) Core employee records with out-of-the-box and custom fields; read via POST /people/search, created and updated through the /people endpoints. Sales Orders & Invoices Sales documents created from external orders and read back for posting status. People (Employees) is specific to Hibob and Sales Orders & Invoices to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.
Employment Historical table of job terms, contract, and working pattern under /people/{id}/employment; full CRUD, entries keyed by effectiveDate. Purchase Orders Purchasing documents reconciled with receiving and vendor systems. Employment is specific to Hibob and Purchase Orders to Microsoft Dynamics NAV — each maps to any object or custom field on the other side.

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

Hibob Microsoft Dynamics NAV Sub-second propagation

DetectionHibob notifies Stacksync of record changes through webhook events. Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events.

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

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

Rate-limit considerations

  • Hibob: Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
What ships with Hibob ⇄ Microsoft Dynamics NAV

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Hibob and Microsoft Dynamics NAV connectors work

Hibob

Integration surface
REST API (the Bob API)
Authentication
Service User credentials over HTTP Basic auth (Base64-encoded serviceUserId:serviceUserToken); permissions granted per data category (People, Payroll, Documents) in Bob admin
Change detection
Webhooks fire for employee created/updated/deleted, table-entry created/updated, time off, and lifecycle events; the employee.updated payload flags which fields changed and Bob recommends an API call for the full record. There is no CDC stream, and deleting a table entry fires no webhook (Bob has no table-entry deletion event).
Capabilities
read · write · webhooks
Rate limits
Rate limits are enforced per service user; violations return HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. The docs list POST /people/search at 50 requests per minute, and bulk /people/search is preferred over per-record reads.
Hibob 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 Hibob 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 Hibob 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
    Hibob connected
    Microsoft Dynamics NAV connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

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

Popular · 6 of 504
All Hibob 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