Migrate from Cegid Talent to Recruit CRM & ATS

Cegid Talent Candidates live in the Hello Talent Recruiting FrontOffice API under the Jobseeker endpoints, scoped by Brand. We extract full candidate files including name, email, phone, address, application status, source channel, and any attached CamposUtil custom field values. The candidate's Cegid unique ID is preserved as an external reference field in Recruit CRM for reconciliation. Recruit CRM's Contact record type 'Candidate' holds the migrated data. Applications tied to the candidate migrate as Pipeline entries linked to the Contact.

JobOffers from the Hello Talent API carry vacancy metadata including job title, description, location, employment type, salary range, and customFields in camelCase. We extract the full offer payload including Brand reference and all metadata properties. The JobOffer maps to a Recruit CRM Job record with description, location, and salary fields populated from source.

JobAds are the published representation of a JobOffer in Cegid Talent, accessible via the JobAdService API with reference, description, properties, and location. One vacancy with multiple locations generates one JobAd record. We map the JobAd status to the Recruit CRM Job published flag, and JobAd location fields to Recruit CRM Job location properties.

Applications in Cegid Talent link a Candidate (Jobseeker) to a JobOffer with a stage and step status. We extract each application as a Pipeline Entry in Recruit CRM, resolving the Contact and Job references at migration time. Application stage and step labels from Cegid's step_labels field map to Recruit CRM Pipeline stage values; Cegid withdrawal or refusal statuses map to Recruit CRM Disqualified or Archived pipeline states.

Employee records live in the Talentsoft Hub Core HR API, separate from the Hello Talent ATS API. We extract employee name, department, job title, manager relationship, hire date, employment status, and any Talentsoft Hub custom field values. The employee record joins to its Cegid Talent candidate record via candidate ID if the employee previously applied; otherwise it imports as a Contact with record type 'Employee' in Recruit CRM. The Talentsoft Hub API uses APIKey authentication on the CegidLife portal, distinct from the Hello Talent OAuth flow.

The organizational tree structure is accessible via the Talentsoft Hub API and includes department assignments and manager relationships. We export the full org hierarchy and map each Cegid Organizational Unit to a Recruit CRM Department. Org unit IDs are preserved as foreign keys for manager relationship mapping. This is a prerequisite import before employee records are loaded because Recruit CRM Department is referenced on Contact.

Cegid Talent stores custom fields in a CamposUtil-style extension object that varies by tenant and by module. The Hello Talent API does not expose a single endpoint that returns all custom field definitions across all modules. We query each module's schema endpoint separately during discovery, generate equivalent Recruit CRM custom properties per module, and map field values during the transfer. If the source tenant has deeply nested custom field groups (nested CamposUtil structures), mapping requires a manual review step before migration.

Talentsoft Hub custom fields follow the same CamposUtil pattern but are defined against a different API surface than Hello Talent. We extract the Talentsoft Hub custom field definitions separately and generate matching Recruit CRM custom properties for the employee-facing fields. Custom field data types (text, number, date, picklist, multi-select) are mapped to Recruit CRM equivalent field types during the schema generation phase.

A Brand in Cegid Talent is the configuration set driving a career website and Jobboard URL, created in Recruiting Back Office by a Super Admin and including language settings and brand metadata. We export Brand configurations as metadata and map career site settings to Recruit CRM's Job Board configuration. This is a configuration-level migration rather than a data migration — the career site URL and branding are noted for manual reconfiguration in Recruit CRM if the customer wishes to maintain the same candidate-facing domain.

Performance review records include objectives, ratings, and review cycle data from Talentsoft Hub. The review template builder in Talentsoft Hub is highly customizable, so schema varies significantly between tenants. We extract review records as structured Note records in Recruit CRM linked to the relevant Contact (Employee). The customer's admin reviews the review template structure post-migration to determine whether Recruit CRM's native notes or a separate performance management tool better suits the review cycle workflow.