Migrate from Ceipal ATS to BambooHR

Ceipal Applicants map to BambooHR Employee records via the BambooHR Employee API. We transfer name, email, phone, address, and employment status fields directly. Ceipal's resume file migrates as an Employee Document attached via BambooHR's document endpoint. Any Ceipal custom properties on the Applicant record are enumerated during discovery and mapped to BambooHR custom Employee fields created in the destination tenant before import. Ceipal's encrypted applicant IDs require an ID-mapping table in staging so downstream references (Submission-to-Applicant) resolve correctly.

Ceipal Job Postings carry title, description, location, requirements, and pipeline stages. We map job title and description to the BambooHR Hiring Job record. Ceipal pipeline stages do not map to BambooHR stages because BambooHR's Hiring module uses a simplified stage model (Applied, Screening, Interview, Offer, Hired, Rejected). We transform Ceipal stage values to the closest BambooHR stage during migration and document any non-mapping stages for manual disposition post-import.

Ceipal Submissions link an Applicant to a Job with submission date, status, and recruiter assignment. In BambooHR Hiring, the Applicant record is the candidate record tied to the Job. We preserve the Applicant-to-Job linkage by creating BambooHR Applicants linked to the migrated Job records and set the submission date as the BambooHR application date. Recruiter assignment from Ceipal migrates to the BambooHR Hiring user field if the assignee exists in BambooHR; otherwise it is stored in a custom field.

Ceipal Client records (company name, contact info, billing details) have no direct BambooHR equivalent because BambooHR does not have a staffing Client object. We migrate Client data as a custom field group on the related Placement or Employee record. For staffing firms, the Client name is stored in a BambooHR custom Employee field or a custom Company field so that the relationship data is preserved even without the standalone Client object.

Ceipal Leads are distinct from Clients and carry status fields and source attribution. BambooHR has no Lead object. We preserve the Lead status and source data by migrating it to a custom field on the closest BambooHR equivalent (Employee or Job Applicant). The customer chooses during scoping whether leads become unprocessed Employee records, Job Applicants in the Hiring add-on, or notes on the relevant Employee record.

Ceipal Placements tie an Applicant to a Job under a Client and carry start date, compensation, and billing information. We map Placement records to BambooHR Employee records with hire date set from the Placement start date, compensation mapped to BambooHR Pay Rate or a custom Pay field, and Client name stored as a custom field. The Placement-to-Applicant chain is preserved because the Employee record carries the original Ceipal applicant ID in a custom field for reconciliation.

Ceipal WorkForce stores employee profiles, compensation, department, and location on a separate pricing tier. We map WorkForce employee records to BambooHR Employee records with department mapped to BambooHR Department, compensation to Pay Rate or custom pay fields, and location to the Employee address or custom location field. WorkForce custom fields are enumerated during discovery and mapped to BambooHR custom Employee fields. If the customer used WorkForce Premium, the advanced payroll and asset management data is noted as requiring manual re-entry or a separate payroll integration post-migration.

Ceipal WorkForce timesheet records track hours per employee per period. We map timesheet entries to BambooHR Time Tracking entries with the period, hours, and approver metadata preserved. Time off balances from Ceipal WorkForce migrate to BambooHR Time Off balances where the types align; custom time-off types from Ceipal are created as new Time Off types in BambooHR before migration.

Expense records from Ceipal WorkForce capture amount, category, employee, and submission date. We map expense records to BambooHR as Employee Documents with category stored as a custom field if BambooHR's native Benefits module does not cover the use case. Expense categories are mapped to the closest BambooHR equivalent; custom expense categories require pre-configuration of custom fields in BambooHR before import.

Ceipal stores documents against Applicants, Jobs, and Placements (resumes, offer letters, contracts). We transfer resume files as Employee Documents via BambooHR's document API, preserving the association to the correct Employee record. Offer letters and contracts are stored as documents on the Employee record with a document type custom field. Binary file transfer is handled through BambooHR's file upload endpoint with appropriate MIME type handling.

Ceipal allows organization-level custom columns on Applicants, Jobs, and Placements. These are enumerated during scoping and mapped to BambooHR custom Employee fields (for applicant-person data) and BambooHR custom Job fields (for job-requisition data). BambooHR's custom field API supports text, number, date, dropdown, and checkbox types. Ceipal multi-select or complex custom field types that do not map directly to BambooHR types are stored as text fields with the original value preserved. Custom field enumeration is a discovery-phase step, not a migration-phase surprise.

TalentBench is Ceipal's parsed resume repository containing skills, work history, education, and the raw resume document. The parsed fields migrate as custom Employee fields in BambooHR; the raw resume file migrates as an Employee Document. BambooHR has no Talent Pool object, so the searchable resume database capability does not transfer — we flag this for the customer's admin to evaluate BambooHR's Hiring add-on or a third-party sourcing tool post-migration.