Migrate from Talent Pool Builder to Zoho Recruit

Talent Pool Builder Candidate records map directly to Zoho Recruit Candidate. We map first name, last name (required in Zoho — any Talent Pool Builder records without a last name receive the value 'Not Provided' per Zoho's import requirement), email, phone, source, current stage, and any custom screening fields to Zoho custom Candidate fields. We validate all Last Name values before import because Zoho silently ignores records missing this mandatory field.

Talent Pool Builder Job postings map to Zoho Recruit Job Opening records. Job title, department, location, and posting date migrate directly. Pipeline stage configuration from Talent Pool Builder maps to Zoho's Hiring Pipeline stages, which we configure before migration to match the source stage names and ordering.

Talent Pool Builder Application records (linking a Candidate to a Job with a timestamp and stage) map to Zoho Recruit Job Application. We preserve the full application timeline including stage transitions and recruiter notes as Activity records linked to the Job Application. Parent record lookup resolution (Candidate ID and Job Opening ID) is validated before import so that no application record lands orphaned.

Talent Pool Builder's named Talent Pools (segmented candidate lists) map to a Zoho Recruit Hiring Pipeline segment plus Candidate Tags. We export each Talent Pool name as a Zoho Candidate tag value and create a corresponding Hiring Pipeline pool segment if the destination Zoho account has multiple pipeline segments configured. Pool-specific custom fields migrate to Zoho custom Candidate fields; pool membership is preserved as the tag plus a linked Candidate Pool record.

Talent Pool Builder Requisitions (hiring manager requests and approvals) map to Zoho Recruit Job Opening records with the requisition number stored in a custom Job Opening field. Stage and status fields vary by Talent Pool Builder account configuration — we map these to Zoho's Job Opening status picklist values (Open, On Hold, Closed, Cancelled) and flag any statuses with no direct equivalent as custom field candidates.

Talent Pool Builder interview scheduling data and structured scores map to Zoho Recruit Interview records. Interview date, interviewer name, candidate, and job opening migrate directly. Score values and structured feedback migrate to Zoho custom Interview fields. Free-text interview notes may require truncation or cleaning depending on Zoho's text field character limits for custom fields in the destination edition.

Talent Pool Builder Offer records (template placeholders, status, and digital signature state) map to Zoho Recruit Offer records. We preserve offer template content as text, salary and compensation fields as custom Offer fields, and status (Extended, Accepted, Declined, Withdrawn) as Zoho Offer status values. Digital signature state is flagged as a post-migration item because Zoho Recruit's Offer module handles e-signatures through its own template workflow that the customer's admin configures after migration.

Talent Pool Builder accounts frequently create custom fields for screening answers, rating scores, source attribution, and compliance data. We request a full field inventory from the source account during scoping, then pre-create each custom field in Zoho Recruit (Setup > Customization > Modules > Candidates) before import. Field types map as follows: text answers to Text fields, numeric scores to Number or Long Integer, multi-select values to Picklist or Multi-select Picklist, and dates to Date fields. Custom fields with no Zoho equivalent are logged in the remediation report for manual post-migration entry.

Talent Pool Builder's union membership flags and seniority-based ranking are platform-specific features with no direct Zoho Recruit equivalent. We export the raw seniority date and union membership fields as custom Candidate Date and Picklist fields respectively so the data is preserved in Zoho. The compliance logic (union preference ranking, collective bargaining rules) does not activate automatically — that requires post-migration configuration by the customer's IT or legal team within Zoho's custom field rules and workflow conditions.

Talent Pool Builder email, SMS, and call logs attached to Candidate records export as discrete communication events, but chronological thread context is not guaranteed. We export each communication event as a Zoho Candidate Note record with the communication type (Email, SMS, Call), timestamp, direction (Inbound/Outbound), and content preserved. Thread continuity gaps are flagged in the data validation report. For SMS and call records, content migrates to custom Candidate text fields if the customer requires structured records rather than notes.

Resume files and uploaded documents export as binary blobs or file references depending on Talent Pool Builder's export method. We map resume attachments to Zoho Recruit Candidate record Attachments. File naming conventions vary by source account and are preserved as-is. The Zoho Data Migration tool supports attaching files via the Attachments checkbox during import, and we validate that each attachment links to the correct Candidate record before confirming the migration.

Talent Pool Builder Owner and Recruiter assignments on Candidate, Job, Application, and Offer records map to Zoho Recruit User records. We resolve by email match. Any Talent Pool Builder owner without a matching Zoho Recruit User is placed in a reconciliation queue — the customer's Zoho admin provisions the missing user before record import continues because OwnerId references are required on most standard Zoho objects. Note: existing Zoho Recruit users with separate accounts must close those accounts before they can be imported into a company's Zoho Recruit org.