Migrate from CIPHR to Recruit CRM & ATS

CIPHR iRecruit stores candidate records as part of its recruitment module. These map directly to Recruit CRM Candidates. We extract first name, last name, email, phone, current employer, CV/resume content, application date, and any custom candidate properties. CIPHR's candidate status stages (custom pipelines) map to Recruit CRM job-specific pipeline stages. Employee records that were never part of the CIPHR recruitment module do not automatically become Recruit CRM Candidates; the customer identifies the overlap during scoping.

CIPHR iRecruit vacancies map to Recruit CRM Job records. We extract job title, department, location, employment type, salary range, job description, and board posting history. CIPHR's multi-board posting configuration (which job boards each vacancy was published to) is stored as a text list and mapped to the Recruit CRM job board field; the customer re-publishes from Recruit CRM's integrations post-migration.

The CIPHR application record (which links a candidate to a vacancy with a specific status and date) maps to Recruit CRM's candidate-job association. We preserve the application date, current stage, source channel, and any interviewer assignments. Recruit CRM's associated_fields endpoint (POST /v1/candidates/associated-field/{candidate}/{job}) handles custom fields on the candidate-job relationship.

CIPHR custom candidate properties and custom vacancy properties map to Recruit CRM custom fields on Candidate and Job respectively. Recruit CRM exposes custom fields through its API as typed fields (text, number, date, dropdown). We pre-create the destination custom field schema before import and map CIPHR property values by name and data type. Any CIPHR custom property with no Recruit CRM equivalent is flagged for manual field creation.

For customers who used CIPHR's recruitment module alongside its HR module, the employee record and the candidate record may be separate CIPHR objects. We identify the overlap during scoping and offer a merge-by-email strategy where an employee record and a candidate record with the same email address are combined into a single Recruit CRM Candidate. This requires the customer to define the merge rule and confirm which CIPHR source (iRecruit vs HR module) takes precedence for each field.

CIPHR user accounts with name, email, role, and permissions map to Recruit CRM Users. We extract the CIPHR role name and map it to Recruit CRM's permission structure (Admin, Recruiter, Hiring Manager, Read-only). Any CIPHR user who only had HR access (no recruitment access) is flagged as a candidate record rather than a user in Recruit CRM unless the customer specifies otherwise.

CIPHR absence balances (holiday, sickness, other leave) and accrual histories have no equivalent object in Recruit CRM. Recruit CRM is a recruitment ATS and CRM; leave management is outside its scope. We extract absence records for the customer's HR team to review, and flag this data for manual archiving or for import into a separate HR system if one is deployed alongside Recruit CRM.

Historical payroll data, tax codes, pension contributions, and year-to-date earnings in CIPHR have no equivalent in Recruit CRM. If the customer is also switching payroll providers, payroll history must be migrated separately into the new payroll system. For CIPHR payroll bureau clients, RTI submission records and P60/P45 documents must be retrieved from HMRC independently of the Recruit CRM migration.

CIPHR stores employee contracts, policies, and ID documents as employee-linked files. Recruit CRM does not have a native document storage object equivalent for employee records. We extract document metadata (filename, type, associated employee, upload date) as a structured list. The customer decides whether to re-upload documents to a linked cloud storage system or recreate them in Recruit CRM's notes on the candidate record.

CIPHR LMS tracks course completions, quiz results, and training assignments. Recruit CRM does not include an LMS module. Training history migrates as a written record (employee name, course name, completion date, result) in CSV format for the customer's admin to review. We do not import training data as Recruit CRM records because there is no target object.

Appraisal records, ratings, and 360 feedback stored in CIPHR have no equivalent in Recruit CRM. We extract appraisal cycle names, employee ratings, and reviewer comments as a structured CSV for the customer's HR team to archive separately. Custom appraisal templates require manual rebuild in the destination HR system.

CIPHR benefits module holds enrolment records, flexible benefit selections, and contribution amounts. Recruit CRM does not support benefits administration. We extract the benefit plan names, employee enrolments, and contribution amounts as a structured record set for the customer's HR team to handle outside the Recruit CRM migration scope.