Two-way sync
Changes in BambooHR or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Keep BambooHR and Microsoft 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.
Each tool in Microsoft 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. BambooHR 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 Mail Messages, Calendar Events, Contacts, OneDrive Files (driveItems) in Microsoft 365 with Time Off, Employment Status, Departments and Divisions, Custom Tables in BambooHR bi-directionally and in real time. A person added, moved, or offboarded in BambooHR creates or updates the matching user in Microsoft 365 within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Microsoft 365 captures details of its own, such as a corrected contact or a login identity, those can flow back to BambooHR 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.
A new hire recorded in BambooHR creates the matching user in Microsoft 365 with the right team and manager already set, so people can start working without waiting on a provisioning ticket.
When someone is marked as leaving in BambooHR, the matching account in Microsoft 365 is deactivated or flagged, so departures do not leave open access behind.
A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.
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.
| BambooHR objects | Microsoft 365 objects | How this pairing syncs | |
|---|---|---|---|
| Employees The core person record with personal and work fields; read out to identity, payroll, and IT systems, and written back from recruiting or onboarding tools. | Users Entra ID user accounts synced with HR and identity systems. | Employees is specific to BambooHR and Users to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Job Information Effective-dated job title, department, division, location, and reporting line; synced so org charts and provisioning systems track internal moves. | Groups Microsoft 365 and security groups kept aligned with org structure and access rules. | Job Information is specific to BambooHR and Groups to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Compensation Effective-dated pay rate, schedule, and change reason; read into planning and payroll systems with access restricted to authorized fields. | Mail Messages Exchange Online messages read for logging, archiving, or activity capture. | Compensation is specific to BambooHR and Mail Messages to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Time Off Requests, balances, and policies; read for absence calendars and capacity planning, with approved requests written from an external scheduling tool. | Calendar Events Events synced with scheduling tools and CRMs for meeting visibility. | Time Off is specific to BambooHR and Calendar Events to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Employment Status Effective-dated hire, leave, and termination status; drives automated provisioning and deprovisioning in downstream identity and license systems. | Contacts Personal and org contacts kept consistent with CRM contact records. | Employment Status is specific to BambooHR and Contacts to Microsoft 365 — each maps to any object or custom field on the other side. | |
| Departments and Divisions Org-structure list values; synced to keep cost centers and team groupings consistent across ERP, identity, and analytics systems. | OneDrive Files (driveItems) File and folder metadata synced for document workflows and audits. | Departments and Divisions is specific to BambooHR and OneDrive Files (driveItems) to Microsoft 365 — each maps to any object or custom field on the other side. |
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.
DetectionBambooHR notifies Stacksync of record changes through webhook events. The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling.
DeliveryEach detected change is written to Microsoft 365 through its API, with automatic retries and rate-limit backoff.
DetectionMicrosoft 365 notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) plus delta queries for incremental sync.
DeliveryEach detected change is written to BambooHR through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every BambooHR–Microsoft 365 connection.
Changes in BambooHR or Microsoft 365 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever BambooHR or Microsoft 365 data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single BambooHR or Microsoft 365 record.
Track your BambooHR ⇄ Microsoft 365 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between BambooHR and Microsoft 365.
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.
Authenticate BambooHR and Microsoft 365 with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the BambooHR and Microsoft 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between BambooHR and Microsoft 365: authenticate both systems, choose the objects to sync (such as BambooHR's Employees and Job Information), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed BambooHR and Microsoft 365 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom BambooHR–Microsoft 365 integration in-house.
Yes — Stacksync ships production-grade connectors for both BambooHR and Microsoft 365. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on BambooHR: The Get Updated Employee IDs endpoint (last-changed timestamps) returns employees inserted, updated, or deleted since a cursor for efficient polling; webhooks can fire on monitored field changes. On Microsoft 365: Graph change notifications (webhooks) plus delta queries for incremental sync. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Microsoft 365 side: Mail Messages, Calendar Events, Contacts, OneDrive Files (driveItems), plus custom fields where Microsoft 365 exposes them. On the BambooHR side: Time Off, Employment Status, Departments and Divisions, Custom Tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 363 integrations available for BambooHR and Microsoft 365.