Migrate from Cegid Talent to Bullhorn ATS & CRM

Cegid Talent candidates are managed in the Hello Talent ATS module via Jobseeker endpoints under a Brand-scoped URL. We extract the full candidate file including application status, contact fields, custom fields, and source attribution. Bullhorn Candidate is the target with email or phone used as the dedupe key. Custom CamposUtil fields from Cegid require explicit remapping to Bullhorn custom fields; we generate the Bullhorn Field Maps configuration for each custom field before migration begins.

Cegid Talent JobOffers aggregate vacancy metadata (title, description, department, employment type, salary range) before publication. The JobOfferService API returns these by Brand with customFields in camelCase. We map each JobOffer to a Bullhorn JobOrder, preserving salary information in custom fields since Bullhorn JobOrder standard fields do not include a native salary range structure.

Cegid Talent JobAds are the published form of a JobOffer. The JobAdService API returns the job ad by reference, description, properties, and location. One vacancy with multiple locations generates multiple JobAds in Cegid; Bullhorn JobOrder stores a single location per order. We split multi-location JobAds into separate Bullhorn JobOrder records and maintain a parent-reference custom field to preserve the original Cegid grouping.

Cegid Talent application records (candidate applied to JobOffer) map to Bullhorn JobSubmission records linked to the migrated Candidate and JobOrder. Application status (applied, screened, interviewed, rejected, offer extended) migrates to JobSubmission status and is preserved in a custom field for audit. Applications without a matching Bullhorn JobOrder or Candidate are held in a reconciliation queue.

Cegid Talent employee records live in the Talentsoft Hub Core HR module with separate API authentication (APIKey on CegidLife portal). We extract employee organizational assignments, manager relationships, and department affiliations. These map to Bullhorn ClientCorporation records representing the candidate's employing organization. Bullhorn ClientCorporation supports a hierarchical structure that we use to represent Talentsoft Hub's organizational tree.

The Talentsoft Hub org tree (departments, sub-departments, manager relationships) is accessible via the Talentsoft Hub API. We export the full hierarchy including department assignments and manager IDs, then reconstruct it as a Bullhorn ClientCorporation parent-child hierarchy. Org unit IDs are preserved as a custom field for reconciliation. Bullhorn does not have a native standalone org chart object; the hierarchy is represented through ClientCorporation parent links.

Cegid Talent Owner records from both Hello Talent and Talentsoft Hub are matched by email to Bullhorn User records in the destination org. Owners without a Bullhorn User match are placed in a reconciliation queue. The customer provisions any missing Bullhorn users before record import resumes. User provisioning is validated before any record migration begins.

Cegid Talent stores user-defined fields in a CamposUtil extension pattern defined per-tenant across both Hello Talent and Talentsoft Hub modules. There is no single API call returning all custom field definitions across both stacks. We query each module's schema endpoint separately, extract the full custom field definitions, generate Bullhorn custom field configurations for each, and create them in the destination Bullhorn org via Bullhorn Support or Field Maps. Deeply nested custom field groups may require a manual review step with the customer.

Cegid Talent performance review records (objectives, ratings, review cycle data) have no direct Bullhorn standard object equivalent because Bullhorn is a recruitment ATS rather than a performance management system. We extract review metadata and ratings as a Bullhorn Custom Object (Front Office Growth or Enterprise edition required for more than two custom objects per entity) with fields for cycle name, reviewer, reviewee, rating, and status. Bullhorn Support provisions the custom object via a setup spreadsheet ticket. If Bullhorn Performance Management is not licensed, this data migrates as a standalone configuration outside the standard recruitment workflow.

Cegid Talent's learning module manages a training catalog with course metadata, enrollment records, and completion tracking. We extract course metadata and enrollment history but SCORM content packages are excluded as binary content not accessible via API. Training completion data migrates as a Bullhorn Custom Object attached to the Candidate record to preserve the candidate's development history. This approach requires Bullhorn Support to provision the custom object with 55 fields per Bullhorn custom object limit.

Cegid Talent compensation data (salary history, bonuses, equity) lives in the Talentsoft Hub module, often restricted by HRIS permissions not exposed on all API tiers. We request explicit permission during discovery and extract the data if accessible. Compensation migrates to Bullhorn as a custom object; placement-based compensation maps to the Bullhorn Placement record. Compensation data requires Bullhorn Professional or higher and a custom object setup through Bullhorn Support.

A Cegid Talent Brand is the configuration set driving a career website and Jobboard URL, created in Recruiting Back Office by a Super Admin with language settings and brand metadata. Bullhorn's career portal and job distribution integrations replace the Cegid career site. We document the active Brands and their configurations for the customer's admin to configure the equivalent Bullhorn JobBoard and LinkedIn Recruiter seat mappings post-migration.

Cegid Talent engagement records (recruiter notes, call records, internal tasks) from both stacks map to Bullhorn Task records. Bullhorn Task supports TaskSubtype (Call, Email, Note) for classification. We preserve activity timestamps, assign tasks to the migrated Candidate or ClientCorporation, and maintain the full activity chronology by setting ActivityDate to the original Cegid timestamp. Bullhorn Bulk API 2.0 handles large engagement volumes with chunking and parent-record lookup resolution.

Documents attached to candidates, employees, or training records in Cegid Talent are not accessible via the public REST APIs. Resume files, contracts, and certificates require 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. We document the file naming conventions and record associations so that the customer can manually attach files post-migration if needed.