Migrate from CIPHR to Bullhorn ATS & CRM

CIPHR applicant records map to Bullhorn Candidate. We extract candidate name, contact details, source, application date, status, and any candidate custom properties. CIPHR application stage maps to a Bullhorn custom field application_status__c since Bullhorn stage is managed via JobSubmission records tied to JobOrder. Candidate documents (CVs, resumes) migrate as ContentDocument records linked via ContentDocumentLink.

CIPHR vacancy records map to Bullhorn JobOrder. The CIPHR job title, job description, location, employment type, and vacancy status map to corresponding Bullhorn JobOrder fields (title, description, address, employmentType, status). We resolve the owning recruiter in CIPHR to a Bullhorn User by email match. Custom vacancy fields in CIPHR map to Bullhorn custom fields on JobOrder.

CIPHR application-to-vacancy associations map to Bullhorn JobSubmission records that link Candidate to JobOrder. The submission date, current stage, rejection reason, and submission notes migrate. Bullhorn's Application V2 entity (with its history records) is the target; we preserve submission stage history as JobSubmission custom fields where the Bullhorn edition supports it.

CIPHR employee records that originated as recruitment applicants and have been hired map to Bullhorn Candidate records with a placement record attached. We use the employee identifier in CIPHR to link back to the original applicant Candidate in Bullhorn, preserving the source application history. Manager relationships from CIPHR map to Bullhorn custom fields or User lookups.

CIPHR employment details (start date, job title, department, cost centre, employment type, contract terms) attach to hired candidates as Bullhorn Placement records. The Placement holds start date, end date (for contract workers), pay rate, and bill rate. Employment type (permanent, contract, temp) maps to Bullhorn's employmentType field. Contract terms and cost centre data map to custom fields on the Placement or Candidate.

CIPHR onboarding task checklists and document acceptance records do not have a direct Bullhorn ATS equivalent. We export onboarding completion status and document acceptance flags, then map them to Bullhorn Onboarding task records or Candidate custom fields (onboarding_complete__c, documents_signed__c). Bullhorn Onboarding is a separate product; configuration of onboarding workflows requires the customer's admin to set up in Bullhorn Onboarding post-migration.

CIPHR employee and applicant documents (contracts, signed policies, ID records, CVs) migrate as Bullhorn ContentDocument records linked to the parent Candidate or ClientContact via ContentDocumentLink. Document type in CIPHR maps to a custom field doc_type__c on ContentDocument. We extract document metadata and binary content where accessible via CIPHR export; filenames and type labels are preserved for identification in Bullhorn.

CIPHR custom fields on applicant and employee records map to Bullhorn custom fields on Candidate, JobOrder, or JobSubmission. Bullhorn editions limit custom fields by entity: Candidate supports up to 55 custom fields depending on field type mix. If the CIPHR schema exceeds Bullhorn's per-entity field limit, we propose Custom Objects (Front Office Growth/Enterprise: up to 10 Custom Objects with 55 fields each; Bullhorn ATS: 2; ATS Growth: none) and configure them during schema design.

CIPHR payroll histories (historical pay data, deductions, tax codes, pension contributions, year-to-date figures) do not map to Bullhorn ATS. Bullhorn Time and Expense handles timesheet and expense tracking for placed contractors, not historical payroll. We export the payroll record set from CIPHR as a separate data package for the customer's payroll team to load into their preferred payroll system or Bullhorn Time and Expense post-migration.

CIPHR leave balances (sickness, holiday, accrual history) have no Bullhorn ATS equivalent. Bullhorn Onboarding tracks onboarding task completions but not absence management. We export current leave balances and leave history from CIPHR as a separate data package. If the customer manages contractor absence in Bullhorn Time and Expense, we provide a custom field mapping for absence records to be configured post-migration.

CIPHR learning completions, course assignments, and quiz results map to Bullhorn only if the customer licenses Bullhorn Learning separately. Standard Bullhorn ATS does not include an LMS. We export training history as a separate data package and flag Bullhorn Learning or a third-party LMS as the destination if the customer requires training record continuity.

CIPHR user accounts, roles, and permission sets do not map directly to Bullhorn User records. Bullhorn Users must be provisioned within Bullhorn's admin interface, not imported. We extract the CIPHR user list (names, emails, roles) as a provisioning reference for the customer's Bullhorn admin. We resolve CIPHR recruiter assignments on job orders and candidates by email match against Bullhorn User records after provisioning.

CIPHR org hierarchy (departments, locations, cost centres) does not have a direct Bullhorn ATS equivalent. Bullhorn ClientCorporation stores client company records, not internal org structure. We map CIPHR departments and locations to Bullhorn custom fields on Candidate and JobOrder (dept__c, location__c). If the customer manages temporary or contract workers in Bullhorn, we use Bullhorn's corporate structure for client-side org tracking rather than the internal HR org tree.

CIPHR appraisal records, ratings, and 360 feedback do not have a standard Bullhorn ATS equivalent. If the customer licenses Bullhorn Front Office Growth or Enterprise, we configure a Custom Object (appraisal_history__c) with fields for appraisal date, rating, reviewer, and comments linked to the Candidate record. Custom appraisal templates in CIPHR require manual mapping or recreation in Bullhorn.