Migrate from CIPHR to Zoho Recruit

CIPHR stores candidate-relevant data within employee records — name, email, phone, address, work eligibility, and any custom candidate fields defined in the recruitment module. We extract these fields and create Zoho Recruit Candidate records. CIPHR employee records without recruitment activity become inactive Candidates flagged for review. The original CIPHR employee record ID is preserved in a custom field cihr_employee_id__c for audit traceability.

CIPHR job postings (title, department, location, employment type, job description, requirements) map to Zoho Recruit Job Opening records. The cihr_vacancy_id maps to a custom field on Job Opening. Active and closed statuses map directly. Archived vacancies in CIPHR become inactive Job Openings in Zoho Recruit and are preserved for historical reporting.

Each CIPHR application record linking an employee profile to a vacancy maps to a Zoho Recruit Job Submission. The candidate lookup and job opening lookup are resolved at migration time using the previously created Candidate and Job Opening IDs. Application status from CIPHR (applied, screening, interview, offer, hired, rejected) maps to the closest Zoho Recruit Status value; custom status names in CIPHR require explicit mapping to Zoho Recruit status options during scoping.

CIPHR employee records may contain employment history entries (previous employers, job titles, dates). We extract each employment history row as a separate Work Experience record on the Zoho Recruit Candidate profile. Employer name, job title, start date, end date, and description map to the corresponding Zoho Recruit Work Experience fields. Employment history with no start date is flagged for customer review before import.

CIPHR education records attached to an employee profile (institution, degree, field of study, graduation year) map to Zoho Recruit Education records on the Candidate. Each education entry becomes a separate Zoho Recruit Education record linked to the Candidate. Multiple education entries per candidate are split into individual records at migration time.

CIPHR onboarding tasks and checklist items map to Zoho Recruit Candidate CheckList items. We preserve the task name, assigned owner, and completion status. CIPHR custom onboarding templates are not automatically replicated — we create a custom mapping table during scoping that pairs each CIPHR onboarding task with its Zoho Recruit CheckList equivalent, and flag any tasks with no Zoho Recruit match for manual recreation by the customer's admin.

Any custom fields defined on CIPHR employee records in the recruitment context map to Zoho Recruit custom fields on the Candidate object. Field data types are translated: CIPHR text and number fields map to Zoho Recruit single-line text or number fields; CIPHR date fields map to Zoho Recruit date fields; CIPHR picklist fields map to Zoho Recruit picklist fields with the same option values. Custom field names are preserved as field labels; API names are auto-generated per Zoho Recruit naming convention. Custom properties with no equivalent Zoho Recruit field type are mapped to text fields and flagged in the scoping report.

CIPHR absence and leave data (sickness, holiday, accrual balances) has no equivalent object in Zoho Recruit. We flag this object as out of scope in the scoping report and recommend Zoho People or a dedicated absence management system for ongoing leave tracking. Leave history is not imported into Zoho Recruit.

CIPHR payroll module data (historical pay data, deductions, tax codes, pension contributions) has no equivalent object in Zoho Recruit. Organisations using CIPHR's managed payroll bureau service should retrieve PAYE history from HMRC P60 and P45 documents separately and load into their chosen payroll system. Payroll data is out of scope for the Zoho Recruit migration.

CIPHR benefits module data (enrolment records, flexible benefit selections, contribution amounts) has no equivalent in Zoho Recruit's ATS model. Benefit plan identifiers and employee enrolments are flagged as out of scope and noted in the scoping report for the customer's HR team to address in their chosen benefits management platform post-migration.

CIPHR appraisal records, ratings, and 360 feedback have no Zoho Recruit equivalent. Performance management data is out of scope for the ATS migration. Customers requiring post-hire performance tracking should evaluate Zoho People or a dedicated performance management system.

CIPHR LMS course completions, assignments, and quiz results have no equivalent in Zoho Recruit's ATS. Learning history does not migrate. If the customer uses Zoho Learn or another LMS, learning records can be migrated as a separate engagement scoped to the LMS destination.

CIPHR user accounts mapped as active employees in the recruitment module are provisioned in Zoho Recruit as active User records. We match by email address and set the Zoho Recruit role based on the CIPHR role name. Users without a matching Zoho Recruit account are held in a reconciliation queue for the customer's admin to provision before candidate import begins. Inactive or departed employees from CIPHR are not imported as active Zoho Recruit users.