Migrate from Talent Connects to Zoho Recruit

Talent Connects Jobs map to Zoho Recruit Job Opening records. We migrate Job title, description (rich text), status (active/closed/archived), department, and location fields. The Zoho Job Opening API name is "Openings" in the module structure. Pipeline stage values from Talent Connects map to Zoho's Job Stage field. Growth-tier migrations must verify active job count against the 10-job ceiling before migration; any excess jobs require archiving or upgrade before import.

Talent Connects Candidate records map directly to Zoho Recruit Candidates. Standard fields (first name, last name, email, phone, resume URL, current company, current title) migrate as typed fields. Last Name is mandatory in Zoho Recruit — any Candidate records without a last name value are flagged during scoping and populated with a placeholder ("Not Provided") before import to prevent record rejection. Resume files are migrated as attachments linked to the Candidate record via Zoho's file upload API.

Talent Connects stores the applicant-to-job relationship as an Application record linking a Candidate to a Job. Zoho Recruit models this relationship via the Candidate Job Opening module (junction object) or as a status update on the Job Opening linked to the Candidate. We split Application records into Candidate linkage and Job Opening association, preserving application date, current stage, rejection reason (if applicable), and source attribution. If Talent Connects tracks multiple applications per Candidate, each application maps to a separate Candidate-Job Opening junction.

Talent Connects interview records (date, attendees, outcome notes, calendar sync metadata) map to Zoho Recruit Interview records. The built-in video interview URL from Talent Connects migrates as a text field on the Interview record since Zoho Recruit's video conferencing is an integration (Zoom, Google Meet) rather than native. Interview outcome notes and disposition migrate as custom fields on the Zoho Interview record. Calendar sync metadata does not transfer — interviewers re-link calendar after migration.

Talent Connects Enterprise Talent Pool records — passive candidates sourced outside active applications — migrate as Zoho Recruit Candidates with a custom "Sourcing_Source__c" field tagged "Talent Pool". The Talent Pool workflow (ongoing engagement cadence, sourcing channel tags) does not transfer. Candidate records retain their name, email, phone, resume, and any notes but lose the Talent Pool-specific sourcing metadata (source channel, sourcer assignment, talent pool tier) unless those are stored as custom fields in Talent Connects.

Talent Connects User accounts (email, name, role, permission level) map to Zoho Recruit Users. We match by email address during migration. If a Talent Connects user has already provisioned a separate Zoho Recruit account, Zoho's own migration guide notes that those users must close the separate account before they can be imported into the company's Zoho Recruit org. User provisioning is a manual pre-requisite; we flag any unmatched users in a reconciliation queue before production migration.

Talent Connects role assignments (single-role on Growth, multi-level on Enterprise) map to Zoho Recruit Profiles and Permission Sets. We document the role-to-profile mapping during scoping and deliver it as a configuration plan. Multi-level permission hierarchies from Talent Connects Enterprise require manual rebuild in Zoho Recruit's Setup > Users & Control section. We do not create Zoho profiles automatically — we deliver the mapping so the customer's admin configures Profiles and assigns Users post-migration.

Talent Connects career page templates, branding settings, and URL structure cannot be exported as structured data — the platform treats these as system-generated UI configurations. We do not migrate Career Page templates. We document the existing career page URL and suggest recreating the career page in Zoho Recruit's Setup > Career Site Builder post-migration. Any custom career page fields (additional questions, required disclosures) are migrated as custom fields on the Job Opening.

Talent Connects bulk email campaigns (templates, send history, recipient lists) migrate as Zoho Recruit Email Templates and a documented Campaign list. Email engagement metrics (open rate, click rate, reply rate) are Talent Connects analytics data and do not export — these are noted as non-migratable for the customer's awareness. Candidate lists used for mass email migrate as Zoho Recruit Candidate lists or can be recreated as Zoho CRM contacts if the customer runs Zoho CRM in parallel.

Talent Connects AI-Assistant add-on ($49/month) generates resume ranking scores and candidate fit signals that do not persist as structured exportable fields — they are computed on-demand in the UI. We cannot migrate AI scores. If Talent Connects stored any AI-derived scores as custom fields, those migrate as text or number fields in Zoho Recruit. Zoho's own Zia AI candidate matching operates on Zoho Recruit data post-migration rather than inheriting Talent Connects signals.

Talent Connects dashboards (funnel metrics, time-to-hire, source performance) are rendered from internal data stores with no export capability. Analytics cannot migrate. We do not attempt to export analytics data. The customer should export screenshots of any dashboards they need to preserve before migration day. Post-migration, Zoho Recruit's own reporting module (accessible from the Reports tab) rebuilds standard recruiting metrics from the migrated data.

Any custom fields defined by the customer in Talent Connects (beyond standard name, email, phone, resume, status fields) migrate to Zoho Recruit custom fields created during schema setup. We create Zoho custom fields with matching data types (text, number, date, picklist, checkbox, etc.) before any record import begins, using Zoho's Create Field API or the Setup UI. Custom field values populate during the Candidate and Job Opening migration phases. The customer approves the custom field mapping during scoping.