Migrate from SeamlessHR to BambooHR

Active SeamlessHR Employee records map to BambooHR Employee. We export full profile data including custom properties via the HRIS spool endpoint, map SeamlessHR fields to BambooHR field names using the documented API field list, and insert by employee number or email as the dedupe key. Any custom fields that do not exist in BambooHR are created during the schema phase before data import. Exported records include job title, department, employment status, hire date, and all custom fields on the profile.

Exited employees use a separate export path in SeamlessHR's HRIS and must be requested explicitly alongside the active employee export. We pull terminated records with their exit date, final compensation, termination reason, and any attached documents. These map to BambooHR Employee records with employmentStatus set to Terminated and the hire and termination dates preserved. Any payroll records attached to exited profiles are flagged for compensation summary generation rather than direct migration.

SeamlessHR exposes the org chart and hierarchy as a distinct object with parent-child reporting relationships. We preserve the full department tree and map each SeamlessHR department to a BambooHR Department with the correct parent-child hierarchy. The BambooHR Employee department field is populated using the resolved department ID from the imported hierarchy.

Leave balances, entitlement policies, and request history are exportable from SeamlessHR. We map leave types to BambooHR Time Off types (Annual, Sick, Personal, or custom equivalents), and migrate accrual balances as of the migration date. Pending leave requests are flagged for customer resolution before cutover; approved and taken history migrates as historical records with dates preserved.

SeamlessHR payroll runs are tied to employee records and exported separately from the HRIS module. Because BambooHR Payroll is a separate add-on product and historical payroll records are not portable between platforms, we generate a compensation summary report from SeamlessHR payroll data for the customer's records. The migration does not insert payroll run history into BambooHR as native records. If the customer activates BambooHR Payroll post-migration, historical compensation data remains in SeamlessHR or the summary document.

Job requisitions with custom fields are supported in SeamlessHR. We extract the requisition data, custom field values, and workflow stage history. Migration to BambooHR requires the BambooHR ATS add-on to be active; without it, requisitions are documented as a written inventory. If ATS is present, we create corresponding Job Openings and preserve stage names, order, and which stages each requisition has passed through.

SeamlessHiring workflow stages export as an ordered sequence with stage names and applicant progression history. We preserve the stage sequence and applicant count per stage. If the customer does not activate BambooHR ATS, the stage workflow is documented as a reference for manual rebuild in BambooHR's ATS or a third-party ATS.

Performance and potential ratings, review cycle data, and goal information are available on SeamlessHR Core tier and above. We map review period dates and rating scores to BambooHR's Performance Review structure. Rating scales may differ between platforms; we document the SeamlessHR scale and map each score to the nearest BambooHR equivalent or store the original score in a custom field for administrative reference.

Custom fields on SeamlessHR Employee profiles require separate schema extraction via API before data export. We retrieve the field definition list, construct a field mapping table, create matching custom fields in BambooHR, then pull values per record. Any custom field that does not exist in BambooHR is skipped unless the customer has pre-created it. Field types (text, date, number, dropdown) are mapped to equivalent BambooHR field types.

Custom fields on SeamlessHR Requisitions follow the same extraction process as Employee custom fields. We retrieve the schema, pre-create matching fields in BambooHR (requiring the ATS add-on), then migrate the values. If the customer does not activate BambooHR ATS, custom requisition fields are documented in the requisition inventory rather than migrated.