Migrate your BambooHR data

The central entity in BambooHR. Each employee gets an immutable, company-scoped ID. We map all standard fields (name, contact, employment status, hire date, termination date, supervisor link) and flag any custom employee fields for value-mapping against the destination schema.

BambooHR stores division, department, job title, employment type, and location as first-class attributes on the Employee record. We preserve these as-is and handle renames where the destination uses different terminology (e.g., 'Department' vs. 'Business Unit').

Pay rate, pay type (salary/hourly/exempt), currency, and pay frequency are native fields. Levels and Bands (compensation grades) can be exported via CSV and imported back, but we treat them as supplemental compensation context rather than standalone records.

Requests, balances, and policies are first-class objects. We map accrued balances as effective-dated values, and time-off types as categories. The export of Timesheet Entries and Time-Off Schedule reports includes separate Amount and Units columns added in a 2025 product update.

Benefits enrollment data is stored per employee but the schema is highly customer-specific. We map what is present in the export report but flag that not all benefit plan details (carriers, coverage tiers, effective dates) are guaranteed to export cleanly without custom field handling.

BambooHR's applicant tracking stores candidates, applications, job postings, and pipeline stages. Pipeline stage names and custom application fields vary by account, so we map stage-to-stage manually and flag any custom fields that lack a destination equivalent.

Onboarding tasks, checklists, and document requests are tied to new hires. The schema does not expose a standalone onboarding object via the standard report export; we reconstruct the onboarding state from the employee's onboarding task list and document completion flags.

BambooHR is highly customizable. Any field not in the standard schema is a custom field with its own field type. We inventory all custom fields during scoping, validate types against the API field type reference (bool, currency, date, country, etc.), and apply type coercion where the destination schema differs.

Documents attached to employee records (offer letters, contracts, signed forms) are accessible via the API. We flag document retention as a manual step or optional add-on since document binary storage and access controls vary significantly between source and destination.

Performance reviews, goals, and review cycles exist as distinct modules but are not fully exposed in the standard employee export. We map review completion status and scores where the report exposes them and note that review history may require supplemental API calls.

BambooHR's report engine is the primary export mechanism. Standard and custom reports can be downloaded as CSV or Excel. We use the report export as the foundation of the migration dataset and supplement with API reads for real-time fields not included in saved reports.

Pay stubs, tax withholding, and journal entries are stored in BambooHR Payroll. Tax filing history and pay stub PDFs are not directly accessible via the standard export API; we handle payroll records as supplemental mapping subject to the destination's payroll module capabilities.