Migrate from TalentLyft to Zoho Recruit

TalentLyft Candidate records map directly to Zoho Recruit Candidate. The candidate's email address serves as the primary dedupe key. We retrieve all Candidate-level Custom Fields via GET /v2/custom_fields before migration and pre-create matching custom fields in Zoho Recruit, respecting the 50/module cap on Standard and 300/module on Enterprise. Last Name is mandatory in Zoho Recruit; any TalentLyft candidate without a last name receives a placeholder value of 'Not Provided' per Zoho's import requirements.

TalentLyft Job records map to Zoho Recruit Job Opening. The job's status (Active/Paused/Closed) maps to Zoho's Job Opening status picklist. Department assignments from TalentLyft map to Zoho Recruit Department lookups. Location records from GET /v2/codes/locations map to Zoho Job Opening Location.

TalentLyft Applications are the junction between Candidate and Job with a Pipeline Stage. Zoho Recruit does not have a native Application object; instead, candidate status within a job is tracked via Candidate-Job Opening association records and stage-based Custom Views. We model the TalentLyft Application as a Zoho Candidate record with custom fields capturing the original application date, source, and pipeline stage name. Applications with Application-level Custom Fields (interview scores, offer details) map to additional custom fields on the Zoho Candidate record.

TalentLyft Pipeline Stage names and ordering do not have a native Zoho Recruit equivalent. We create a custom picklist field on the Candidate module (or Candidates module depending on Zoho Recruit edition) with values matching the TalentLyft pipeline stages. Stage probability percentages migrate as a separate numeric custom field. The customer chooses between picklist and tag-based stage tracking during scoping.

TalentLyft Talent Pools are curated candidate collections with no direct Zoho Recruit equivalent. We model Talent Pool membership using Zoho Candidate Tags with a naming convention of Pool:[PoolName]. For customers with many Talent Pools (10+), we propose a custom Candidates Pool module with a Lookup relationship to the standard Candidate module, created in the Zoho Recruit Enterprise edition before migration.

Education records are nested under Applications in TalentLyft and require both candidate ID and application ID in the API path. We resolve the parent-record chain (Application staged first, then Education[] pulled per application) before mapping. Education data migrates as a custom Education section on the Zoho Candidate record with fields for degree, institution, field of study, start date, and end date.

Experience records follow the same two-pass approach as Education. The employer, title, dates, and description fields migrate to a custom Experience section on the Zoho Candidate record. We preserve the chronological ordering using the from_date and to_date fields. Any Experience records without a valid parent Application after the split are mapped directly to the Candidate record.

TalentLyft Pipelines define ordered stage sequences per Job. Zoho Recruit uses Custom Views and Candidate Tags to represent pipeline logic. We map each TalentLyft Pipeline to a Zoho Custom View with a filter on the stage picklist field, enabling the recruiting team to view candidates by pipeline at the destination.

TalentLyft Departments map directly to Zoho Recruit Departments via GET /v2/codes/departments. Department IDs and names are preserved and linked to Job Opening records at the destination.

TalentLyft Team Member records map to Zoho Recruit Users by email match. Zoho Recruit requires that users with existing separate Zoho Recruit accounts close those accounts before import; we flag this during scoping. Owner assignments on Candidate and Job Opening records are resolved via the User mapping table after User import completes.

TalentLyft Locations from GET /v2/codes/locations map to Zoho Recruit Location records and are linked to Job Opening records at the destination.

TalentLyft Custom Fields vary per account and are user-defined. We retrieve field definitions via GET /v2/custom_fields before migration, extracting field IDs, labels, and types. Each custom field is pre-created in Zoho Recruit at the Candidate module level before import. Customers with more than 50 custom fields on Candidate (Standard tier limit) must upgrade to Enterprise or reduce field count during scoping.

Application-level Custom Fields (interview scores, offer details, compliance flags) from TalentLyft migrate as additional custom fields on the Zoho Candidate record. We flatten Application-level metadata into the Candidate-level custom field schema to preserve the data within Zoho's single-candidate record model.