Real-time
Two-way sync
Changes in Hibob or Microsoft Dynamics 365 instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ Business productivity
Hibob to Microsoft Dynamics 365 integration — real-time, two-way sync
Keep Hibob and Microsoft Dynamics 365 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 365
Keep the people, teams, and status that Microsoft Dynamics 365 and Hibob share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Microsoft Dynamics 365 keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Hibob is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.
Stacksync syncs Opportunities, Cases (Incidents), Quotes, Orders & Invoices, Products in Microsoft Dynamics 365 with Named lists, People (Employees), Employment, Work in Hibob bi-directionally and in real time. A person added, moved, or offboarded in Hibob creates or updates the matching user in Microsoft Dynamics 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft Dynamics 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to Hibob in whichever direction you configure.
Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.
Common use cases
- 01 Replicate standard and custom Dataverse tables into a warehouse for reporting.
- 02 Enrich leads from external data sources and write scores back onto Dynamics records.
- 03 Sync Time off requests and who's-out data into a scheduling or workforce-planning database for coverage and capacity reporting.
- 04 Two-way sync People (employee) profiles and Work records with a Postgres database so internal apps and directories read profiles in SQL while HR corrections flow back into Bob.
Common sync patterns
Where Microsoft Dynamics 365 routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Hibob, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.
Onboarding: access ready on day one
A new hire recorded in Hibob creates the matching user in Microsoft Dynamics 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
Offboarding: no standing access after a departure
When someone is marked as leaving in Hibob, the matching account in Microsoft Dynamics 365 is deactivated or flagged, so departures do not leave open access behind.
What you can sync between Hibob and Microsoft Dynamics 365
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 365 objects | How this pairing syncs | |
|---|---|---|---|
| Lifecycle Hire, termination, and leave status changes at /people/{id}/lifecycle; read-only and the source of lifecycle webhook events. | Products Catalog records aligned with ERP item masters. | Lifecycle is specific to Hibob and Products to Microsoft Dynamics 365 — 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. | Activities Emails, calls, and tasks captured for engagement analytics. | Documents is specific to Hibob and Activities to Microsoft Dynamics 365 — 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. | Custom Tables Dataverse tables that carry business-specific entities through the same API surface. | Named lists is specific to Hibob and Custom Tables to Microsoft Dynamics 365 — 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. | Accounts Company records synced bi-directionally with ERPs, databases, and billing systems. | People (Employees) is specific to Hibob and Accounts to Microsoft Dynamics 365 — 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. | Contacts Person records kept consistent with marketing, support, and data-warehouse copies. | Employment is specific to Hibob and Contacts to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. | |
| Work Reporting line, department, site, and title under /people/{id}/work; drives the org chart and is synced two-way to directories. | Leads Inbound records enriched and routed from external sources into sales queues. | Work is specific to Hibob and Leads to Microsoft Dynamics 365 — each maps to any object or custom field on the other side. |
How changes propagate between Hibob and Microsoft Dynamics 365
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 365 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 written to Microsoft Dynamics 365 through its API, with automatic retries and rate-limit backoff.
Microsoft Dynamics 365 Hibob Sub-second propagation
DetectionMicrosoft Dynamics 365 pushes changes as they happen — webhook events backed by change data capture. Change data capture (CDC) via the Dynamics 365 Change Tracking feature.
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 365
Connect Hibob and Microsoft Dynamics 365 for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Hibob–Microsoft Dynamics 365 connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Hibob or Microsoft Dynamics 365 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 365 record.
Observability
Monitoring
Track your Hibob ⇄ Microsoft Dynamics 365 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 365.
How the Hibob and Microsoft Dynamics 365 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.
Microsoft Dynamics 365
- Integration surface
- REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface
- Authentication
- Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities)
- Change detection
- Change data capture (CDC) via the Dynamics 365 Change Tracking feature; standard entities have change tracking enabled by default, custom entities require enabling "Track Changes" in Power Apps/Dataverse table properties
- Capabilities
- read · write · CDC · webhooks
How it works
How to connect Hibob to Microsoft Dynamics 365 — 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.
- 01
Connect your apps
Authenticate Hibob and Microsoft Dynamics 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Hibob
connected
Microsoft Dynamics 365
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Hibob and Microsoft Dynamics 365 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.
objects · Hibob ⇄ Microsoft Dynamics 365Customers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Hibob Microsoft Dynamics 365Company company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Hibob and Microsoft Dynamics 365 integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Hibob and Microsoft Dynamics 365: authenticate both systems, choose the objects to sync (such as Hibob's Lifecycle and Documents), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Hibob and Microsoft Dynamics 365: Where Microsoft Dynamics 365 routes or assigns work by person: assignments follow the org; Onboarding: access ready on day one; Offboarding: no standing access after a departure. When someone changes teams or managers in Hibob, the queues, ownership, or approvals in Microsoft Dynamics 365 update to match, so work reaches whoever holds the role now.
-
Hibob: 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. Microsoft Dynamics 365: REST API (Dataverse Web API, OData v4); Finance & Operations apps expose a separate OData data-entity surface. Authentication: Microsoft OAuth sign-in: user provides the D365 environment URL, signs in with Microsoft credentials, and accepts the Stacksync app (permissions to read CRM data and interact with OData entities). Stacksync manages authentication, retries, and rate limits on both sides.
-
Microsoft Dynamics 365: Authorization may be blocked by a 'Need admin approval for this app' screen requiring a Microsoft directory admin to grant consent to the Stacksync app before syncing can begin. Hibob: The GET Read-all-company-employees and Read-by-ID endpoints are legacy; Bob steers reads to POST /people/search, which the docs rate-limit at 50 requests per minute. Stacksync's field mapping accounts for these differences between Hibob and Microsoft Dynamics 365 without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Hibob and Microsoft Dynamics 365 records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Hibob and Microsoft Dynamics 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Hibob–Microsoft Dynamics 365 integration in-house.
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
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 513 integrations available for Hibob and Microsoft Dynamics 365.
Popular · 8 of 513
-
Hibob ⇄ Quip -
Hibob ⇄ Smartsheet -
Hibob ⇄ Sysaid -
Hibob ⇄ Wrike -
Microsoft Dynamics 365 ⇄ D2l Brightspace -
Microsoft Dynamics 365 ⇄ Oracle Fusion Cloud HCM -
Microsoft Dynamics 365 ⇄ Smartrecruiters -
Microsoft Dynamics 365 ⇄ Ukg Pro
No integrations match .
