Migrate from Talent Genie to Zoho Recruit

Talent Genie stores a single Candidate record that may be applied to multiple Jobs, with pipeline stage held as a property on the application relationship. Zoho Recruit splits this into a Candidate module (the person) and a Job Application module (the junction linking a Candidate to a specific Job Opening). We extract every Talent Genie candidate application, produce a Candidate record and a corresponding Job Application record per application, and link them via the Candidate-Application relationship in Zoho Recruit. Social media verification flags from Talent Genie migrate as boolean custom fields on the Candidate.

Talent Genie Job requisitions (title, department, location, description, posting status) map directly to Zoho Recruit Job Opening records. We preserve open, paused, and archived statuses and flag archived jobs during migration so they import in the correct state. The job board posting status in Talent Genie does not carry forward because Zoho Recruit manages job board distribution through its own posting module.

Talent Genie configurable stages (Application Received, Screening, First Interview, Final Interview, Offer, and any custom stages) map to Zoho Recruit pipeline stage picklist values. We capture the live stage configuration during the discovery scan and configure matching picklist values in Zoho Recruit before any candidate data is imported. Stage probability percentages carry forward to Zoho Recruit stage setup if the customer uses stage-based forecasting.

Talent Genie Interview Scorecards are fully tenant-specific: rating scales (numeric, star, boolean), mandatory flags, and free-text criteria vary between organisations. We run a discovery scan of the live scorecard template and all submitted evaluations before defining any field mapping. Rating scale types map to Zoho Recruit picklist or multi-select picklist fields; free-text notes map to text area fields. Custom fields require Zoho Recruit Standard tier or above. We flag Standard-plan customers who need to upgrade before migration begins if scorecard fields are tier-gated.

Talent Genie stores parsed resume content as structured fields and the original file attachment. We transfer both: structured fields map to standard Zoho Recruit Candidate fields (Name, Email, Phone, Skills, Experience, Education), and the raw file attachment is linked to the Candidate record via Zoho Recruit's attachment mechanism. The parsed resume text does not duplicate the attachment; both coexist so the recruiter can view structured data at a glance and open the original file on demand.

Talent Genie users (Admin, Recruiter, Hiring Manager roles) map to Zoho Recruit User records by email address. We resolve each Talent Genie user email against the destination Zoho Recruit User table. Any Talent Genie user without a matching Zoho Recruit User account is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission flags transfer as a written mapping note rather than a direct field migration because Zoho Recruit role configuration is administered separately via Setup > Users & Control.

Talent Genie's chronological event feed (stage changes, user assignments, scorecard submissions, status updates) is unstructured in the UI. We extract the full event log per candidate, reconstruct each event as a Zoho Recruit Activity record (Task for discrete actions, Event for scheduled interactions), and link it to the corresponding Candidate or Job Application via the Zoho Recruit related-record mechanism. WhoId and WhatId on the activity record point to the migrated Candidate and Job Application respectively. We note that the original Talent Genie event formatting cannot be fully replicated; the structured Activity record is the destination-native representation.

Talent Genie interview scheduling generates calendar entries synced with Google Calendar or Outlook. The linked calendar event ID and timestamps are exported as part of the interview record. We import these as Zoho Recruit Event records with StartDateTime, EndDateTime, and Location preserved, linked to the Candidate or Job Application. Note that Google Meet and Microsoft Teams integration for video interviews requires Zoho Recruit Enterprise tier; we flag this requirement during scoping if interview video links are present in the source data.

Talent Genie allows recruiters to add custom fields to candidate or job records. We detect all custom properties during the discovery scan, export their values per record, and create matching custom fields in Zoho Recruit before migration. Custom field type mapping is defined by Zoho Recruit field types: single-select properties map to picklist, multi-select to multi-select picklist, free text to text or text area, and dates to date fields. Custom fields are not available in Zoho Recruit's Forever Free edition; we confirm the customer's Zoho Recruit plan tier during scoping and advise on any upgrade needed before migration begins.

Talent Genie cross-references candidate profiles against social media signals and stores verification flags as custom boolean or status fields on the candidate record. We map these flags to equivalent Zoho Recruit custom fields (Checkbox for boolean flags, Picklist for status values) on the Candidate record. The flag names from Talent Genie carry forward as the custom field labels, and the verification data populates as values during candidate import.

Talent Genie aggregates metrics such as time-to-hire, source effectiveness, and pipeline conversion rates on-read from underlying data rather than storing them as exportable records. We do not migrate calculated analytics because they are not persisted records. We do migrate the underlying raw data (candidate timestamps, source attribution, stage-change timestamps) so that equivalent reports can be rebuilt in Zoho Recruit's standard reporting module. The rebuild work is documented separately as part of the post-migration handoff.

Talent Genie's onboarding module uses its own document storage and compliance schema for e-signatures and onboarding artefacts. We do not migrate onboarding data. The onboarding module is out of scope for standard ATS-to-ATS migration because document storage, e-signature compliance, and HR onboarding workflows belong to a separate system category (HRIS or HR service delivery platform) rather than an ATS. We document the existence of onboarding records for the customer's HR team to assess separately.