Migrate from Cegid Talent to Zoho Recruit

Candidates in Cegid Talent's Hello Talent Recruiting FrontOffice API map to Zoho Recruit Candidates. The Hello Talent Jobseeker endpoints expose first name, last name, email, phone, address, skills, experience, and custom fields under a Brand-scoped URL. We extract all candidate file data including application history and custom CamposUtil fields, then map each to Zoho Recruit's Candidate module. Zoho requires Last Name as a mandatory field; candidates where last name is absent in Cegid are assigned a placeholder value ('Not Provided') that Zoho accepts without blocking import.

Each application a candidate submitted in Cegid Talent becomes either a sub-record in Zoho Recruit's candidate file (via the Notes or Attachments tab) or a custom sub-module record linked by CandidateID. We preserve application status (applied, screening, interview, offer, hired, rejected), submission date, source channel, and the job reference. If Cegid stores multiple applications per candidate, we create multiple sub-module records in Zoho so the full application history is intact.

JobOffers in Cegid Talent aggregate vacancy metadata before publication and are referenced by Brand. They carry customFields in camelCase and include job title, description, location, department, employment type, salary range, and requirements. We map JobOffer to Zoho Recruit Job, preserving all standard fields. Zoho's Job module supports Industry, Functional Area, and Job Type as picklist fields; we transform Cegid values to match Zoho's picklist entries during the export transform phase.

JobAds are the published representation of a JobOffer in Cegid Talent, returned by the JobAdService API with reference, description, properties, and location. One vacancy with multiple locations in Cegid generates one JobAd record. We map JobAd to Zoho Recruit Job and preserve the published status flag, job board distribution list, and opening date. Zoho supports job posting to 75+ job boards; the job board assignment list migrates as comma-separated values in a custom field if the customer wishes to replicate the distribution.

Employee records in Cegid Talent's Talentsoft Hub Core HR module map to Zoho Recruit Client (or Contact within Client, depending on whether the employee is a hiring manager or an internal candidate). Talentsoft Hub uses a separate API from Hello Talent with different authentication (APIKey on CegidLife vs client_id/secret for recruiting). We extract employee name, title, department, manager relationship, employment status, and organizational unit assignment from Talentsoft Hub and map these to Zoho Recruit Client fields plus custom fields for organizational metadata.

The organizational tree structure exported from Talentsoft Hub API maps to Zoho Recruit in one of two ways: as a custom OrgUnit module with parent-child lookup relationships mirroring the hierarchy, or as a department taxonomy on the Client record. We preserve org unit IDs and manager relationships so that hiring manager assignments on Job records can be resolved. The customer chooses the organizational mapping strategy during scoping.

Training catalog entries (course metadata, enrollment records, completion tracking) from Cegid Talent's LMS module map to a Zoho Recruit custom module if the customer requires training data continuity. We extract course name, description, duration, enrollment date, completion date, and score. SCORM content packages and media files do not migrate; we flag these as out-of-scope for standard API-based migration. Course metadata migrates as a lookup-free data table in Zoho.

Performance review records include objectives, ratings, and review cycle data. Cegid Talent's review template builder is highly customizable per tenant, so the schema varies significantly between implementations. We export the review records as structured rows (reviewer, reviewee, cycle, rating, objective text, feedback) into a Zoho Recruit custom module with one field per distinct review field detected during the schema extraction phase. If the customer uses fewer than 10 distinct review fields, we use Notes attached to the Client record as an alternative.

Compensation data (salary history, bonuses, equity where configured) lives in Talentsoft Hub and is often restricted by HRIS permissions not exposed on all API tiers. We request explicit permission scopes before extraction. Compensation records map to a Zoho Recruit custom module as read-only entries attached to the Client record, with fields for salary amount, currency, effective date, bonus amount, and compensation type. Zoho Recruit does not have a native compensation module; the custom module approach provides data continuity without requiring a separate HRIS.

Both Cegid Talent modules store user-defined fields in a CamposUtil extension pattern that is defined per-tenant and per-module. There is no single API endpoint returning all custom field definitions across both stacks. We query each module's schema endpoint separately (Hello Talent Recruiting FrontOffice schema and Talentsoft Hub schema) before data extraction begins, then generate Zoho Recruit custom field definitions of equivalent type (text, number, date, picklist, checkbox, multi-select) and map source values during the transfer. Deeply nested custom field groups may require a manual review step.

A Brand in Cegid Talent is the configuration set driving a career website and Jobboard URL, created by a Super Admin and including language settings and brand metadata. Zoho Recruit has its own career page builder (Zoho Recruit's Job Opening portal) that replaces the Cegid career site. We do not migrate Brand configuration; we deliver a written inventory of each Cegid Brand's URL, language settings, and posted jobs so the customer's admin can recreate the career site in Zoho Recruit.

Documents attached to candidates, employees, or training records in Cegid Talent are not accessible via the published REST APIs for either Hello Talent or Talentsoft Hub. Resumes, contracts, certificates, and course materials require a manual file-level export through the Cegid admin portal or a Cegid Professional Services engagement. We flag document attachment export as out-of-scope for standard API-based migrations and offer a file-level export option at additional cost if documents are migration-critical. If pursued, documents are uploaded to Zoho Recruit's Attachments tab or Zoho WorkDrive and linked to the corresponding Candidate or Client record.

Workflows and automations built in Cegid Talent's ATS or performance modules do not migrate to Zoho Recruit's workflow builder because the two platforms use incompatible rule-definition formats. We deliver a written inventory of every active Cegid Talent workflow with its trigger, conditions, actions, and recommended Zoho Recruit Workflow Rule equivalent. The customer's admin rebuilds these in Zoho Recruit's Setup > Workflow Rules after go-live. This inventory is part of the standard migration deliverable, not a separate engagement.