Migrate from CIPHR to BambooHR

CIPHR Employee records map to BambooHR Employee with contact details, national insurance number, address, and emergency contacts transferred field by field. CIPHR's stand-alone HR fields (employment type, location, cost centre) map to the corresponding BambooHR employee fields. Custom CIPHR properties on the employee record are extracted, their data types verified against BambooHR's supported field types (text, date, number, dropdown, checkbox), and mapped to either standard BambooHR fields or BambooHR custom fields. This is the first object migrated because all other records attach to it.

CIPHR stores start date, job title, department, employment type, and contract terms as sub-fields of the employee record. We preserve each field individually. Job title maps to BambooHR job title; department maps to BambooHR department (which must be created as a BambooHR department entry before employee import); employment type maps to BambooHR employee status and full/part-time indicator. Contract terms and cost centre data migrate to BambooHR custom fields.

CIPHR's payroll module holds pay history, tax codes, pension contributions, and year-to-date figures. We extract current-year payroll history and map it to BambooHR's payroll module if the customer selects BambooHR payroll. Note that BambooHR's payroll is US-centric; UK organisations migrating from CIPHR's RTI-compliant payroll typically select a separate UK payroll vendor. We export all historical payroll data for the customer's new payroll administrator to configure and enter. RTI submission history does not migrate through BambooHR; it must be retrieved from HMRC CISRTI filings or archived P60/P45 documents.

CIPHR sickness, holiday, and other leave types map to BambooHR Time Off types. We export current balance and full leave history for each employee, preserving CIPHR leave type names. A key risk is accrual calculation discrepancy: CIPHR's entitlement engine may produce different opening balances than BambooHR's entitlement rules depending on how carry-over, anniversary increments, and part-time proration are configured. We present source accrual values for customer review during scoping and recommend a pre-migration leave audit to identify discrepancies before go-live.

CIPHR vacancy records and candidate profiles map to BambooHR Job Openings and Applicants. Job title, department, location, and job description transfer directly. CIPHR custom pipeline stages are mapped to BambooHR stage values, with any stages that have no BambooHR equivalent flagged for manual creation post-migration. Candidate contact details, application history, and status are preserved. Note that BambooHR's ATS limits the number of open job postings by tier (5, 25, or 50 depending on plan), which must be verified against the customer's vacancy volume during scoping.

CIPHR onboarding task checklists and document acceptance records map to BambooHR Onboarding. We capture which documents have been signed and which tasks are marked complete at migration time. CIPHR custom onboarding templates do not have direct BambooHR equivalents; we create a task-by-task mapping table during scoping that pairs each CIPHR task with its BambooHR counterpart or flags it for manual recreation by the customer's HR admin.

CIPHR LMS course assignments, completion dates, and quiz results export as training history records. Course names and completion dates map to BambooHR's training tracking fields. CIPHR off-the-shelf content library references are exported as text; they do not automatically create a live course in BambooHR's LMS (which requires a separate LMS integration or manual course creation). We document the full learning history for the customer's L&D team to rebuild course structure in BambooHR or maintain in a dedicated LMS.

CIPHR employee documents (contracts, policies, ID records) are exported as file metadata and content where accessible via the CIPHR API. Documents are mapped by document type and associated employee. File names and types are preserved; the employee name and document type are indexed so the HR team can locate documents in BambooHR after migration. Binary document content requires a file attachment migration step in addition to the employee record import.

CIPHR flexible benefits enrolments and plan selections export as benefit plan names, employee enrolment records, and contribution amounts. These map to BambooHR's benefits module if the customer subscribes to it, or to BambooHR custom fields on the employee record for basic enrolment tracking. Complex benefit election histories with multiple plan years may require a benefits data specialist to configure correctly in BambooHR; we flag this complexity during scoping.

CIPHR appraisal records, ratings, and 360 feedback submissions export as review history in BambooHR Performance. Completed appraisal cycles map to BambooHR review records with ratings preserved. Custom appraisal templates built in CIPHR do not migrate; we deliver a field-level audit of the template structure so the customer's HR admin can recreate it in BambooHR's review builder. Active review cycles in progress at migration time are flagged as a separate workstream requiring admin coordination to avoid data loss.

Organisations that have defined custom fields on CIPHR employee or related objects extract these as named-value pairs with explicit data type annotations. We map each custom property to a BambooHR custom field of the matching type (text, number, date, dropdown, checkbox, or dependent field). Dropdown-style custom properties require the destination picklist values to be pre-created in BambooHR before import. This mapping step happens during scoping and is validated in a pre-migration sandbox before production import.

CIPHR's org hierarchy including departments, locations, and cost centres exports with parent-child relationships preserved. We create departments in BambooHR before employee import so that the department assignment on each employee record resolves correctly at insert time. Cost centre data has no direct BambooHR equivalent; it migrates to a custom text field on the employee or department record and is documented for the customer's finance team.