Migrate from LiveHire to Zoho Recruit

LiveHire Candidate records map 1:1 to Zoho Recruit Candidate records, preserving name, email, phone, address, work history, skills, and current status. Zoho Recruit requires Last Name as a mandatory field on every Candidate record; LiveHire records without a last name value are written as 'Not Provided' per Zoho's import specification to prevent record rejection. The LiveHire employment type flag (permanent versus contingent) maps to a custom Zoho Recruit field or Candidate status value that we configure during schema setup.

LiveHire Talent Community Members are distinct from active Applicants and represent candidates who have expressed interest in the employer brand but are not currently in a hiring process. We migrate these as Zoho Recruit Candidate records with a custom status field or tag (e.g., 'Talent Community - Inactive') that distinguishes them from active applicants. The original Talent Community join date and engagement source migrate as custom fields for future segmentation.

LiveHire Job records map to Zoho Recruit Job Opening records, preserving job title, description, location, department, employment type, and status (active, on-hold, closed). The job's approved template used for recurring positions migrates as reference metadata. Active job counts must align with the target Zoho Recruit tier: Free limits 1 active job per recruiter, Standard caps 10 per recruiter, and Enterprise caps 20 per recruiter. We validate active job count against the destination tier during scoping and flag any overages for tier upgrade or archival decisions.

LiveHire Application records (the joining entity between Candidate and Job) map to the Candidate Job association in Zoho Recruit. The application date, source channel, and current pipeline stage migrate as fields on the association. Stage transition history and stage change timestamps preserve as activity log entries or custom fields. The application status history is written as a structured note on the Candidate record to maintain audit trail.

LiveHire Talent Pools are recruiter-curated candidate segments with optional automated re-pooling rules. Zoho Recruit has no native Talent Pool equivalent. We migrate the current pool member roster by creating Zoho Recruit Tags corresponding to each pool name and applying them to the relevant Candidate records. Automated re-pooling rules do not export as structured data and must be rebuilt manually as Zoho Recruit Workflow Rules or Custom View filters. We deliver a Talent Pool inventory document listing each pool name, member count, and the criteria logic for manual recreation.

LiveHire configurable stage sequences for different job types map to Zoho Recruit Workflow Rules, which Zoho Recruit supports at 5 per module on Standard and 50 on Enterprise. We do not migrate workflow logic as executable code. Instead, we produce a written inventory of each LiveHire workflow: stage names, required approvals, automation triggers, and candidate actions. The customer's admin uses this inventory to configure equivalent Zoho Recruit Workflow Rules post-migration. Pipeline-to-Record Type mapping is documented for any structural differences between the two systems.

LiveHire recruiter and hiring manager notes attached to Candidates and Applications map to Zoho Recruit Notes linked to the corresponding Candidate record. Ratings, interview scores, and internal commentary preserve in the note body. Formatting and attachments (e.g., scoring rubrics attached to notes) migrate as text content within the note or as linked file references for the customer's admin to re-attach.

LiveHire email, SMS, and in-platform message history between recruiters and candidates maps to Zoho Recruit Tasks and Events. 2-way text messaging threads from LiveHire migrate as Task records with thread content preserved in the description field and timestamp set to the original LiveHire engagement date. Email history migrates as Tasks or as a linked email log depending on the target Zoho Recruit configuration. Thread ordering against the Candidate timeline is preserved by ActivityDate mapping.

LiveHire Offer records including proposed compensation, start date, and acceptance status map to Zoho Recruit Candidate Offer fields or a custom Offer subform. Offer history attached to applications preserves for compliance and audit trail purposes. If the target Zoho Recruit plan includes Offer Letter Templates (Standard allows 50 per org; Enterprise allows 100 per org), we map the offer template reference as a field for admin to reconnect post-migration.

Resumes, cover letters, portfolio files, and signed agreements attached to Candidate profiles migrate as Zoho Recruit Candidate Attachments. Binary file migration runs as a parallel transfer to the structured record migration to prevent the file transfer from blocking the structured data pipeline. File associations (which file attaches to which Candidate record) are resolved via the LiveHire attachment-to-candidate lookup and re-established in Zoho Recruit by filename and candidate email match.

LiveHire organization-specific custom fields on Candidates, Jobs, and Applications require explicit field-level mapping against Zoho Recruit's schema. Custom field data types (text, number, date, picklist, multi-select) are mapped to equivalent Zoho Recruit field types during schema design. Zoho Recruit Standard tier allows 50 custom fields per module; Enterprise allows 300 per module. We validate custom field count against the destination tier and flag any overflow for field consolidation or tier upgrade before migration.

LiveHire compliance records including audit trails, approval signatures, background check results, and right-to-work documentation are migrated as linked attachments or custom field entries depending on record type. Due to the sensitivity of compliance data, we flag these records for explicit customer authorization before migration and apply a restricted handling process. We recommend the customer's compliance team review migrated compliance records post-migration for accuracy and completeness.

LiveHire Owner records (recruiters and hiring managers) map to Zoho Recruit User records by email match. Any LiveHire Owner without a matching Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision before Candidate and Job import begins. Active versus inactive status on the User record is preserved from LiveHire where available.

LiveHire contingent worker records follow a distinct data path from permanent candidates, often including external VMS vendor IDs that do not map to standard candidate fields. We separate contingent and permanent candidate exports during extraction and apply different mapping logic to each subset. Contingent worker records are imported into Zoho Recruit as Candidate records with a custom employment type tag and external vendor ID preserved in a custom field. This prevents ID collision with permanent candidate records in the destination system.