Migrate from Cegid Talent to BambooHR

Cegid Candidates are stored in the Hello Talent Recruiting FrontOffice API under a Brand-scoped URL via Jobseeker endpoints. We extract the full candidate profile including application status, source channel, and custom CamposUtil fields. BambooHR Hiring stores applicants per Job. The mapping preserves the candidate's email address as the dedupe key, application date as the submission timestamp, and any sourced application stage as a BambooHR Custom Field. Candidates without a corresponding BambooHR Job are held in a staging table for the customer to create the job posting first.

Cegid JobAds are the published representation of a JobOffer, returned by the JobadService API with reference, description, properties, and location. BambooHR Jobs capture title, description, department, location, and employment status. One Cegid vacancy with multiple locations generates one JobAd per location in Cegid; we consolidate these into a single BambooHR Job with the location field set to the primary location and additional locations noted in the job description or as a custom field. Job status (open/closed) migrates as the BambooHR Employment Status field.

Cegid JobOffers aggregate vacancy metadata before publication and carry customFields in camelCase. We extract offer-level properties including job level, employment type, and compensation range (where available from the API) and map them to BambooHR Job custom fields. The BambooHR Jobs object does not have a native offer letter feature at this tier; if the customer uses Cegid offer letter workflows, we flag those as requiring manual rebuild in BambooHR's offer template tool.

Cegid Employee records live in the Talentsoft Hub Core HR module, which uses a separate API from the Hello Talent Recruiting FrontOffice. We extract the full employee file including personal info, employment dates, department assignment, manager relationship, and custom fields. BambooHR Employee stores these directly. We resolve the manager relationship by matching the Talentsoft Hub manager employee ID to a BambooHR Employee supervisor field using the imported employee email as the join key. Any Employee record without a resolved manager is placed in a reconciliation queue.

Cegid Org Units are exported from the Talentsoft Hub API with the full hierarchical tree including department assignments and manager relationships. BambooHR uses a flat Department list. We map the Cegid org hierarchy to BambooHR Departments by name, preserving the parent-child structure in a custom department_parent__c field and using the top-level department as the BambooHR Department value on the Employee record. The BambooHR org chart feature renders the flat department structure; nested org visualizations require a separate rebuild.

Cegid Talent's LMS module manages course catalog entries, enrollment records, and completion tracking. BambooHR has no native LMS — training data lands as Training History entries on the Employee file with fields for course name, date, status, and description. We extract course metadata (title, description, duration) and enrollment history (employee, enrollment date, completion date, pass/fail status) from the Talentsoft Hub API. SCORM content packages are not transferred. If the customer requires ongoing LMS capability, we flag that BambooHR does not have a native LMS module and recommend a separate LMS migration scope.

Cegid Performance Reviews include objectives, ratings, and review cycle data with a schema that varies significantly between Talentsoft Hub tenants due to customizable review templates. We extract review records with cycle name, reviewer, reviewee, overall rating, and objective completion status. BambooHR Performance stores goals, 1:1 notes, and review ratings on the Employee file. We map the Cegid review structure to BambooHR custom fields or the Performance Goals section, with the understanding that complex multi-section review templates may require manual rebuild in BambooHR's Performance module or a workaround via custom fields.

Cegid Compensation records include salary history, bonuses, and equity from the Talentsoft Hub compensation module, which is often restricted by HRIS permissions and not exposed on all API tiers. We request explicit API access during scoping and extract salary effective dates, amounts, currency, bonus amounts, and equity grants where visible. BambooHR stores compensation data as Pay rate and Pay type fields on the Employee file, with historical compensation requiring custom fields or a separate compensation history table. A flat pay rate is the only natively supported compensation field in BambooHR Core; multi-component compensation (base plus bonus plus equity) requires a custom field strategy designed during scoping.

Both Cegid Talent modules store custom fields using a CamposUtil-style extension pattern defined per-tenant with no single API endpoint returning all custom field definitions across all modules. We query each module's schema endpoint separately during discovery, extract the full custom field definitions, and generate equivalent BambooHR custom properties (text, date, number, dropdown, or checkbox) before initiating data transfer. Deeply nested custom field groups require a manual review step with the customer's HR admin to confirm mapping logic. Custom field values transfer as string representations for non-primitive types.

A Cegid 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. BambooHR provides its own hosted job listings page and career site builder. We do not migrate the Cegid career site or Brand configuration. We deliver a written map of each Cegid Brand with its languages, job board URL, and branding metadata so the customer's admin can configure the BambooHR career site to match.

Documents attached to candidates, employees, or training records in Cegid Talent — including resumes, employment contracts, and training 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. BambooHR supports document storage on the Employee file via the file upload API, but the source files must first be exported from Cegid manually.