Migrate from LiveHire to Bullhorn ATS & CRM

LiveHire Candidate records map 1:1 to Bullhorn Candidate records. The primary fields—firstName, lastName, email, phone, address, skills, employmentType (permanent or contingent), currentStatus, and availabilityDate—map directly. We separate permanent and contingent candidates during extraction because contingent records may carry external VMS supplier IDs that do not map to standard Bullhorn Candidate fields and require a custom field or note for storage in the destination system.

LiveHire Talent Community members who have expressed brand interest but are not active applicants migrate as Bullhorn Candidate records with a custom status field (talent_community__c) set to true. The original registration date and interest preferences migrate as custom fields to preserve the engagement history that drives proactive sourcing.

LiveHire Job records map to Bullhorn JobOrder. The fields title, description, location, employmentType (permanent/contingent), department, salary, and status migrate directly. Job templates used for recurring positions map as Bullhorn JobOrder custom fields. Active and archived job status translates to JobOrder isOpen boolean in Bullhorn.

LiveHire Application records (the join between Candidate and Job) map to Bullhorn JobSubmission. We preserve applicationDate, source channel, current stage in the hiring pipeline, stage transition timestamps, and rejection reason where present. Application status history migrates as Bullhorn custom fields or notes attached to the JobSubmission.

LiveHire Talent Pools are recruiter-curated collections of candidates segmented by skills, roles, or availability. Pool membership does not export as structured criteria, only as a member list. We export the current candidate membership per pool and recreate them as Bullhorn Lists during migration. The customer recreates pool re-pooling rules manually in Bullhorn using saved searches or Bullhorn Automation rules post-migration.

LiveHire company records attached to job postings and applications map to Bullhorn ClientCorporation. The fields companyName, address, industry, website, and primaryContact migrate directly. Bullhorn ClientCorporation is the parent of ClientContact records, establishing the client hierarchy before candidate placements are imported.

Recruiter and hiring manager notes attached to candidates and applications migrate to Bullhorn Note records. We link Note records to the corresponding Candidate via ContentDocumentLink. Interview scores, ratings, and internal commentary from LiveHire migrate as text content within the Note body or as Bullhorn custom fields on the Candidate record, depending on field type availability in the customer's Bullhorn edition.

LiveHire email, SMS, and in-platform message threads map to Bullhorn Note records (for message content) linked to the Candidate timeline, with a Task record created for each communication event to surface in the activity feed. 2-way text messaging threads preserve the conversation direction flag as a custom Task field.

LiveHire Offer records (compensation, start date, acceptance status) map to Bullhorn Placement as a pre-placement record. Bullhorn Placement is the canonical record for a hired candidate; we create the Placement record during migration with the offer details and mark it as pending or confirmed depending on the original offer status. Accepted offers become confirmed Placements with start date and compensation.

Resumes, cover letters, and portfolio files attached to LiveHire candidate profiles migrate as Bullhorn ContentDocument records linked to the Candidate via ContentDocumentLink. We map the original file association (resume, cover letter, portfolio) to a custom ContentDocument Type field during migration. Binary files are transferred separately from structured records.

LiveHire tenant-specific custom fields on Candidates, Jobs, and Applications map to Bullhorn custom fields on the corresponding entity. Bullhorn standard entities support up to 20 custom fields depending on field type (text, dropdown, checkbox, etc.). Fields exceeding the standard custom field limit on Bullhorn ATS (2 custom objects per entity on ATS tier, 10 on Enterprise) require Bullhorn Support pre-configuration as Custom Objects. We flag any custom field that exceeds Bullhorn's standard limits during scoping.

LiveHire compliance records (background check results, right-to-work documentation, approval signatures) migrate to Bullhorn as a Custom Object attached to the Candidate record if the Bullhorn edition supports Custom Objects. If not, compliance documents migrate as ContentDocument records with a custom compliance flag, and the compliance summary migrates as a Note. Sensitive compliance data handling follows the customer's specified data classification during migration.