Migrate from LiveHire to Recruit CRM & ATS

LiveHire Candidate records migrate to Recruit CRM Contact records. The primary contact fields (name, email, phone, location, current title, work history, skills) map directly. We preserve the candidate's source channel and engagement status as custom fields in Recruit CRM. Any candidate rating or star score migrates to a Recruit CRM custom rating field.

LiveHire Talent Community members are distinct from active applicants, representing passive talent who have expressed brand interest but are not in an active hiring process. We migrate these as Recruit CRM Contacts with a 'Talent Community' tag applied. The original interest date and opt-in status migrate to corresponding Recruit CRM custom fields.

LiveHire Job records map directly to Recruit CRM Jobs. We preserve job title, description, location, employment type (permanent or contingent), department, and status. Approved job templates used for recurring positions migrate as reusable job drafts in Recruit CRM. Active versus archived status is preserved; closed jobs are migrated as archived records.

The Application record linking a Candidate to a Job migrates to Recruit CRM's Application object. Application date, source channel, current pipeline stage, and stage transition timestamps preserve. Stage names from LiveHire's configurable hiring pipelines are mapped to Recruit CRM pipeline stages, with any non-matching stages flagged for configuration during the sandbox phase.

LiveHire Talent Pools are recruiter-curated candidate segments with automated membership criteria. Pool membership lists migrate as Recruit CRM tags on the corresponding Contact records. The automated criteria and re-pooling rules that govern LiveHire Talent Pool membership do not export as structured data; we deliver a Talent Pool inventory document listing each pool name, its member count, and the membership criteria for manual reconstruction in Recruit CRM.

LiveHire manages contingent and contractor records through VMS integration paths that attach external vendor IDs to candidate profiles. These external IDs have no Recruit CRM equivalent and must be stripped before import to prevent ID collision. We run permanent and contingent worker exports as separate extraction streams, strip vendor IDs from the contingent stream, and tag contingent records with a 'Contingent' tag in Recruit CRM. Customers using VMS integrations in Recruit CRM re-establish those connections post-migration.

LiveHire configurable stage sequences define the hiring process for different job types. We map each LiveHire pipeline name and its stage sequence to a Recruit CRM Pipeline with corresponding stages. Custom stage names, required approval gates, and automation rules require manual setup in Recruit CRM post-migration; we provide a written pipeline inventory listing each pipeline, its stages, and any conditional logic for the customer's admin to rebuild.

LiveHire Offer records including proposed compensation, start date, and acceptance status migrate to Recruit CRM Offers attached to the relevant Application. Offer history preserving compensation negotiation records migrates as offer version records. We flag any LiveHire offer templates for the customer's team to re-create as Recruit CRM offer templates.

Recruiter and hiring manager notes attached to candidates and applications, including ratings and interview scores, migrate as Recruit CRM Notes linked to the corresponding Contact or Application. Formatting and embedded media may simplify during migration; we document any formatting loss so the customer can supplement during post-migration review.

LiveHire email, SMS, and in-platform messaging history migrates to Recruit CRM Activities or Notes attached to the Contact record. 2-way text messaging threads migrate as Activity records with the message content preserved. We flag any communication threads that exceed typical volume for the customer's admin to review for data quality before migration.

Resumes, cover letters, portfolio files, and signed agreements attached to candidate profiles migrate as Files linked to the corresponding Recruit CRM Contact or Job record. Binary file migration runs separately from structured record migration. We map file associations from LiveHire to the correct Recruit CRM record and provide a file inventory listing filename, file type, associated record, and upload timestamp.

LiveHire organization-specific custom fields on Candidates, Jobs, and Applications vary significantly between tenants and require explicit field-level mapping. We extract the full custom field schema during discovery, map each field to a Recruit CRM custom field of the matching type (text, number, date, picklist, checkbox, or multi-select), and create the fields in Recruit CRM before the main migration batch begins.