Migrate your LiveHire data

The primary talent record in LiveHire. Candidates have profiles with work history, skills, contact details, and engagement status. We migrate Candidate records 1:1, preserving all standard fields. Custom candidate properties require field-level mapping to destination schema.

Distinct from active Applicants, Talent Community members have expressed interest in the employer brand but are not currently in an active hiring process. We migrate these as Candidate records with a community membership flag to preserve the engagement relationship in the destination system.

Active job requisitions with title, description, location, employment type (permanent or contingent), department, and status. We map Job records including approved job templates used for recurring postings. Job associations to sourcing channels are preserved as custom fields.

The joining record between a Candidate and a Job, capturing the application date, source channel, and current stage in the hiring pipeline. Application status history and stage transition timestamps are migrated to preserve audit trails.

Recruiter-curated collections of candidates segmented by skills, roles, availability, or engagement level. Talent Pool membership is a many-to-many relationship. We create corresponding audience segments or tags in the destination system and map pool membership accordingly.

Configurable stage sequences defining the hiring process for different job types. Custom workflows require field-level mapping because stage names, required approvals, and automation rules vary by organization configuration.

Recruiter and hiring manager commentary attached to candidates and applications. Notes may include ratings, interview scores, and internal commentary. We migrate notes as linked records; formatting and rich text elements require normalization during import.

Email, SMS, and in-platform messaging history between recruiters and candidates. 2-way text messaging is a distinctive LiveHire feature. Message threads are mapped to candidate activity timelines in the destination, though native threading structure may not transfer identically.

Offer records including proposed compensation, start date, and acceptance status. Offer history attached to applications is migrated to preserve compensation negotiation records for compliance and audit purposes.

Resumes, cover letters, portfolio files, and signed agreements attached to candidate profiles. Binary file migration is handled separately from structured records. We map file associations to candidate IDs and preserve original filenames for downstream retrieval.

Organization-specific data fields added to standard objects like Candidates, Jobs, and Applications. Custom field schema varies significantly between LiveHire tenants, requiring explicit field mapping to destination object schemas.

Audit trails, approval signatures, background check results, and right-to-work documentation. Compliance data sensitivity requires careful handling during migration. We flag compliance records for explicit customer sign-off before transfer.

Historical metrics such as time-to-hire, source effectiveness, and pipeline conversion rates are derived from the underlying transaction data and do not require separate migration. We recommend rebuilding key reports in the destination system using migrated records.

LiveHire integrates with job boards, background check providers, HRIS systems, and calendar tools. Integration credentials and OAuth tokens cannot be migrated and must be re-established in the destination platform by the customer's IT team.