Migrate your CIPHR data

The core object in CIPHR. Employee records include contact details, employment history, compensation, manager relationships, and org structure. We extract the full employee profile including all standard fields and map any custom properties to the destination schema.

CIPHR stores start dates, job titles, departments, cost centres, employment type, and contract terms as distinct fields within the employee record. We preserve each sub-field and maintain the linkage back to the parent employee during migration.

CIPHR's payroll module holds historical pay data, deductions, tax codes, and pension contributions. We extract payroll histories including year-to-date figures and map them to the destination's payroll or compensation object. Deduction codes and pension schemes require field-level mapping since naming conventions vary between systems.

CIPHR tracks sickness, holiday, and other leave types with accrual balances. We export the current balance and leave history for each employee, preserving the leave type names as they appear in CIPHR.

CIPHR includes a recruitment module for job postings, candidate records, and onboarding workflows. We extract candidate data and vacancy records. Custom stages or workflow statuses defined in CIPHR are mapped to the destination's pipeline stages explicitly.

Onboarding tasks, document acceptance records, and checklist completions are stored in CIPHR. We capture which documents have been signed and what onboarding steps are complete. Custom onboarding templates require manual field mapping before transfer.

CIPHR's LMS tracks course assignments, completion dates, and quiz results. We export learning history and map course names to the destination LMS. CIPHR's off-the-shelf content library references may not have equivalents in all destination systems.

CIPHR stores employee documents including contracts, policies, and ID records. We export document metadata and content where accessible. Documents are mapped by type and associated employee; filename conventions in CIPHR may need normalisation.

CIPHR's benefits module holds enrolment records and flexible benefit selections. We extract benefit plan names, employee enrolments, and contribution amounts. Benefit plan identifiers are mapped to the destination's benefit structure.

CIPHR includes an expenses module. Expense records and receipts are not currently supported for migration due to the complexity of line-item data and receipt attachments in the CIPHR schema. We recommend exporting this data separately as a spreadsheet before migration.

Appraisal records, ratings, and 360 feedback submissions are stored in CIPHR. We extract completed appraisal cycles and map ratings to the destination's review schema. Custom appraisal templates require pre-migration field mapping.

Organisations can define custom fields on employee and related objects in CIPHR. We extract all custom property values and map them explicitly to destination fields. Custom property names and data types are reviewed during scoping to ensure correct type conversion at the destination.

CIPHR stores the org hierarchy including departments, locations, and cost centres. We export the full structure and preserve parent-child relationships in the destination.

CIPHR user accounts, roles, and permission sets control access within the platform. We export user-role assignments. Role names are mapped to the destination's equivalent permission structure since RBAC models differ across systems.