Migrate from LiveHire to Crelate

LiveHire Candidate records map directly to Crelate Person records. The Person record carries contact details (name, email, phone, address), work history, and skills. We preserve the original LiveHire candidate_id in a custom field for reconciliation. Any candidate tied to a contingent worker VMS record is flagged during extraction and processed through the contingent path separately to prevent ID collision.

LiveHire Talent Community members (candidates who expressed interest but are not in an active hiring process) map to Crelate Person records with a Tag applied denoting their community origin. The original community join date migrates as a custom date field. Community members without a current application are imported at lower priority and may be batched separately during the migration window.

LiveHire Job records (active requisitions with title, description, location, employment type, department, status) map to Crelate Job records. Employment type (permanent or contingent) maps to a custom field or Job type attribute in Crelate. Closed or archived LiveHire jobs may be imported as historical records or excluded based on customer preference during scoping.

The Application record (the join between Candidate and Job, capturing application date, source channel, and current stage) maps to Crelate Job Submission. Stage progression history migrates as a series of activity or note records attached to the Job Submission, preserving the hiring pipeline audit trail. Stage names require mapping against the destination pipeline configuration.

LiveHire Talent Pools are many-to-many candidate collections with automated membership criteria. Pool membership criteria and auto-repooling rules do not export as structured data. We export the current member list for each named pool, create corresponding Tags in Crelate, and assign the tag to each Person record. The pool names are preserved in the tag label. Automated refresh rules require manual recreation in Crelate as periodic list updates or dynamic candidate searches.

LiveHire configurable stage sequences for different job types require field-level mapping because stage names, required approvals, and automation triggers vary by organization and job category. We document each LiveHire pipeline stage and its corresponding Crelate workflow stage, including any conditional branching logic. Crelate workflows are rebuilt using Crelate's workflow builder; the customer or a Crelate implementation specialist executes the rebuild using our written inventory as the specification.

Recruiter and hiring manager notes attached to candidates and applications migrate as Crelate Notes linked to the corresponding Person or Job Submission. Ratings, interview scores, and internal commentary transfer as note body text. Formatting and attachments within notes may require normalization depending on the source format.

LiveHire email, SMS, and in-platform messaging history between recruiters and candidates maps to Crelate Activity records. 2-way text message threads (a distinctive LiveHire feature) are preserved as message-type Activities attached to the Person record. Message timestamps and participant information transfer; rich media content within messages may require format normalization.

LiveHire Offer records (proposed compensation, start date, acceptance status, negotiation history) map to Crelate Offer records attached to the relevant Job Submission. Offer history is preserved for compliance and audit purposes. Offer attachments (signed agreements, counter-offers) migrate as linked documents.

Resumes, cover letters, portfolio files, and signed agreements attached to candidate profiles migrate as Crelate Documents linked to the Person record. Binary file migration is handled separately from structured records. We map file associations to candidate records and preserve original file names and MIME types. Large resume attachments may be batched by size tier to manage transfer throughput.

LiveHire organization-specific custom fields on standard objects require explicit field-level mapping because schema varies significantly between tenants. We extract the full custom field schema during discovery, map field types to compatible Crelate custom field types, and pre-create the destination custom fields in Crelate before importing any records. Dropdown and multi-select custom fields require value mapping against the destination picklist.

LiveHire compliance records (audit trails, approval signatures, background check results, right-to-work documentation) are flagged for explicit handling due to data sensitivity. We separate compliance documents from standard attachments and map them to Crelate Documents with restricted visibility. Background check status fields map to custom fields on the Person record. The customer determines whether compliance records require re-verification post-migration.

LiveHire contingent worker records follow a distinct data path through VMS integrations and carry external vendor IDs that do not map to standard candidate fields. We extract contingent and permanent records as separate datasets during the migration, apply distinct field mapping logic to each subset, and import them into Crelate in separate phases to prevent ID collision. Supplier references in contingent records map to custom fields rather than standard Crelate fields unless the customer has a VMS integration configured.

LiveHire Users and Owners referenced on candidate, job, and application records map to Crelate Users by email match. We extract every distinct user reference and reconcile against the destination Crelate user list. Any LiveHire Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes.