Migrate from Cegid Talent to Crelate

Cegid Candidates are stored in the Hello Talent ATS module and exposed via the Jobseeker endpoints under a Brand-scoped URL. We extract the full candidate profile including contact details, customFields in camelCase, application status, and source attribution. The candidate record is the join key we use to reunify any records split across the dual-stack (e.g., if an employee record in Talentsoft Hub references a candidate ID from Hello Talent). Crelate Person records receive the mapped fields with source system attribution stored in a custom field for audit. Duplicate detection uses email as the primary dedupe key with a secondary check on phone number.

Cegid Employee records live in the Talentsoft Hub Core HR module, which uses a different API surface from Hello Talent (APIKey on CegidLife portal vs client_id/secret on Recruiting FrontOffice). We extract employee profiles, manager relationships, department assignments, and organizational unit references. Crelate Person or Contact receives the mapped fields. Employee status (active, inactive, terminated) maps to Crelate's status field. Manager hierarchy from the Talentsoft Hub org tree is preserved as a custom manager relationship field on the Person record.

Cegid JobAds are the published representation of a JobOffer, returned by the JobadService API with reference, description, properties, and location. One vacancy with multiple locations generates one JobAd record per Cegid's API contract. We extract the full ad payload including all metadata properties and customFields in camelCase. Crelate Job records receive the ad content, job status, and location data. JobAd status (Draft, Published, Closed) maps directly to Crelate's job status field.

JobOffers aggregate vacancy metadata before publication. They are referenced by Brand in Cegid and carry customFields in camelCase. We export the full offer payload including all metadata properties and link it to the corresponding JobAd during migration so that Crelate's Job record carries the full vacancy context including requisition number, department, and hiring manager.

Applications link a Candidate to a JobAd and carry status history (Applied, Screening, Interview, Offer, Hired, Rejected). We extract the full application timeline, status transitions, and interviewer assignments. Each application is created as a Crelate Job Order entry with the Person and Job lookups resolved at migration time. Status history is preserved as Activity records attached to the Job Order.

The org tree structure is accessible via the Talentsoft Hub API. We export the full hierarchy including department assignments, parent-child relationships, and manager relationships. Crelate does not have a native org chart object, so we map the hierarchy to Crelate Departments and store the parent-child relationship as a custom field for downstream reporting. The customer configures any org visualization in Crelate post-migration.

Performance review records include objectives, ratings, and review cycle data. The Talentsoft Hub review schema is highly customizable per tenant, and the review template builder creates different field sets for each organization. We extract review records where the API returns a consistent schema and map them to Crelate Activity records or a custom Performance Review object depending on the volume and structure. Highly customized review templates that do not map to a standard schema are flagged for manual reconciliation.

Compensation data (salary history, bonuses, equity) lives in a Cegid Talent module that is often restricted by HRIS permissions not exposed on all API tiers. We request explicit API permission during scoping. If accessible, we extract compensation records and store them as Crelate Activity entries or a custom compensation record linked to the Person, with the understanding that Crelate's compensation module may be light. Compensation records that cannot be accessed via API are documented as a manual export item.

The learning module manages a training catalog with course content, enrollment records, and completion tracking. We extract course metadata and training enrollment history from the LMS API. SCORM content packages and interactive learning objects are not migrated. Enrollments and completion records map to Crelate Activity entries or a custom training record linked to the Person. If the customer requires LMS functionality post-migration, Crelate does not offer a native LMS and a separate LMS platform (e.g., TalentLMS, Docebo) is recommended.

Cegid Talent stores custom fields in a CamposUtil-style extension object defined per-tenant and per-module. There is no single API endpoint that returns all custom field definitions across all modules. We query each module's schema endpoint separately (Hello Talent for ATS-related custom fields, Talentsoft Hub for Core HR custom fields) and generate destination-side custom properties in Crelate that mirror the source definitions. Deeply nested custom field groups require a manual review step with the customer's admin.

Documents attached to candidates, employees, or training records—such as resumes, contracts, and certificates—are not accessible via the published Cegid Talent REST APIs. Document export requires either a manual 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. In Crelate, the customer uploads key documents manually or uses Crelate's file management to attach them post-migration.

A Brand in Cegid Talent is the configuration set that drives a career website and Jobboard URL, including language settings and brand metadata. Brands are created in Recruiting Back Office by a Super Admin. We extract the Brand configuration metadata as a written inventory document. Career site language settings, branding elements, and Jobboard URL mappings do not transfer programmatically to Crelate's career site configuration; the customer's admin rebuilds these in Crelate's settings using the extracted metadata as a reference.