Migrate from Adapt to BambooHR

Adapt Employee records map directly to BambooHR Employee. Core fields (firstName, lastName, bestEmail, dateOfBirth, hireDate, jobTitle, employeeNumber) migrate 1:1. We use the Adapt Employee ID as the source reference and configure BambooHR's employee number field to match. Custom Employee properties migrate to BambooHR custom fields, but only if they are text, date, number, or single-select picklist types; Information fields, Section headers, and Multiple Selection List fields cannot pass through BambooHR's API and are documented in the migration inventory for manual post-import entry.

Adapt Department records map to BambooHR Departments. The Adapt department hierarchy (parent-child relationships) migrates to BambooHR's nested department structure. We extract every distinct department, resolve the parent-department reference, and create department records in dependency order so that parent departments exist before their children. Department ID remapping is tracked in a lookup table that we hand off to the customer.

Adapt Contact records include name, email, company association, and extension metadata. In BambooHR, contact data lives on the Employee record. We map Adapt contact email to BambooHR's bestEmail, and any contact-specific custom properties to BambooHR custom fields on Employee. If Adapt stores contacts separately from Employees (non-employee contacts), we flag this as a separate object to be imported into BambooHR's directory as pending-hire or contractor records, or excluded if the customer chooses to manage non-employee contacts in a separate system.

Adapt Company records map to BambooHR's Company field on the Employee record (for organizations using BambooHR as an HRIS that references the employing entity). If BambooHR is configured to track the employing company separately, we create company entries in BambooHR's directory and map the company name, domain, and industry fields. Custom company properties require field-level transformation during migration.

Adapt Job titles and position records migrate to BambooHR's Job Title field on the Employee. BambooHR does not have a separate Job/Position object; job title is an attribute on Employee. We extract distinct job titles from Adapt, import them as Job Title values in BambooHR, and map employee records to the correct title at import time. If Adapt uses a structured position taxonomy, we discuss flattening or multi-field decomposition during scoping.

Adapt supports custom fields on the Employee object. We migrate these as BambooHR custom fields, preserving data type (text, date, number, picklist) where supported. We pre-create all custom fields in BambooHR before import, matching the Adapt field name as the field label and generating an API-compatible field name. BambooHR's API cannot pass Information fields, Section headers, or Multiple Selection List fields; these are flagged in the pre-migration inventory and handed off for manual entry after cutover.

Adapt PTO data includes current balance and accrual history. We export the current balance as an effective-dated row and import it into BambooHR's Time Off module as the opening balance for each policy type. BambooHR's time-off management supports accrual policies; if the customer uses BambooHR's accrual calculation, we import the current balance as the starting point. Accrual history (transaction log) migrates as a separate row set if the destination plan supports historical time-off transactions; otherwise, only the current balance snapshot transfers.

Salary and compensation records are available in Adapt's higher tiers. We export the full compensation timeline including salary amount, effective date, pay frequency, and currency. In BambooHR, compensation is managed through the Pay Compensation section on the Employee record or through integrations with payroll providers. We import compensation as Pay Change records in BambooHR, with the effective date preserved. Mapping to BambooHR's pay structure requires a pre-migration field mapping session to align Adapt's compensation fields with BambooHR's expected input format.

Adapt's browser extension stores email-find history and contact enrichment metadata as custom fields on Contact records. This data does not have a native equivalent in BambooHR. We export the enrichment metadata as-is, store it in a custom text or long-text field on the BambooHR Employee record where possible, and document any fields that cannot migrate in the written inventory. The customer decides whether to surface this data in BambooHR or archive it.

Adapt stores manager assignments on Employee records. We extract the supervisor reference for each employee and resolve it to the BambooHR supervisorEmployeeId field during import. The import sequence ensures that manager records are imported before their direct reports so that the supervisor relationship is satisfied at the moment of insert. Any unresolved supervisor references (e.g., for contractors or external managers) go to a reconciliation queue for the customer's admin to resolve before go-live.