Migrate from Ceipal ATS to Bullhorn ATS & CRM

Ceipal Applicants map directly to Bullhorn Candidate records. The Ceipal applicant record carries contact details, skills, education, work history, and resume file—all of which transfer to Bullhorn Candidate. We extract the resume binary alongside structured fields so Bullhorn's parsing engine runs on intake rather than storing raw text. Ceipal's encrypted applicantId requires an ID-mapping table in staging so that Submission and Placement lookups resolve correctly in Bullhorn.

Ceipal Job Postings map to Bullhorn JobOrder records. The job title, description, location, requirements, and pipeline stages transfer directly. Ceipal job stages map to Bullhorn JobOrder status values (Open, Interview, Offer, etc.). We preserve the job owner (recruiter assignment) via User lookup by email match against Bullhorn User records.

Ceipal Submissions link an Applicant to a Job with submission status, submittal date, and recruiter assignment. This maps to Bullhorn JobSubmission, which is a junction object connecting Candidate to JobOrder. We resolve both the Candidate foreign key and the JobOrder foreign key via the ID-mapping tables built during the discovery phase. CSV-only migrations break this chain—we use the API to preserve the Applicant-to-Submission-to-Job relationship in Bullhorn.

Ceipal Client records (company name, contact info, billing details) map to Bullhorn ClientCorporation. Address data, client status, and industry classification transfer to Bullhorn's corresponding fields. ClientCorporation is created before any Candidate or JobOrder import so that all foreign-key lookups are satisfied at the moment of insert.

Ceipal Leads are distinct from Clients and carry different status fields and source attribution. They map to Bullhorn Lead records, which exist separately from ClientCorporation in Bullhorn's schema. Lead status, source, and any custom lead-routing fields migrate to Bullhorn Lead with the original Ceipal lead status preserved in a custom field for reporting continuity.

Ceipal Placements (final hiring outcome tying Applicant to Job under Client) map to Bullhorn Placement. Start date, compensation, billing rate, and placement status transfer directly. We resolve the Candidate foreign key, the JobOrder foreign key, and the ClientCorporation foreign key via ID-mapping tables. Bullhorn Placement also requires a ClientContact reference—we either map from Ceipal's Client contact record or create a placeholder ClientContact during ClientCorporation migration.

Ceipal tracks submission status and submittal date as fields on the Submission record. Bullhorn splits this across JobSubmission status and Application V2 history. We map the current status directly and preserve the full submission timeline in Application V2 Note fields. If the customer uses Ceipal's submission stage tracking for audit, we replicate this in Bullhorn via a custom field on JobSubmission.

Ceipal WorkForce module stores employee profiles, compensation, department, and location under a separate pricing tier. Bullhorn does not have a native HCM/HRMS module; workforce data typically maps to Bullhorn Custom Objects (available from Bullhorn ATS tier with 2 Custom Objects or Bullhorn Front Office Growth/Enterprise with up to 10 Custom Objects with 55 fields each). We scope WorkForce migration separately and pre-create the destination Custom Object schema before any employee records load.

Timesheet records in Ceipal WorkForce (hours per employee per period, approver metadata) map to Bullhorn Custom Object records on the Employee Custom Object. Period, hours worked, and approval status transfer to custom fields. If the customer uses Bullhorn Workforce Management (a separate product line), we scope this as a parallel migration with its own schema design.

Expense records in Ceipal WorkForce (amount, category, employee reference, submission date) map to Bullhorn Custom Object records linked to the Employee Custom Object. Category mappings are defined during discovery against Bullhorn's picklist options. Full line-item detail migrates to custom fields on the Expense Custom Object.

Ceipal allows admins to add custom columns to grids on Applicants, Jobs, and Placements. These are organization-specific with no public schema reference. We enumerate every custom field during discovery by querying Ceipal's API for entity metadata, then map them to Bullhorn Custom Object fields (if the data is entity-level) or to Bullhorn Custom Fields on standard entities (Candidate, JobOrder, Placement). Edition constraints apply: Bullhorn ATS supports 2 Custom Objects, ATS Growth supports none, and Front Office Growth/Enterprise supports up to 10 Custom Objects with 55 fields each.

Ceipal stores documents against Applicants, Jobs, and Placements—resumes, offer letters, contracts. We transfer documents as binary blobs via Bullhorn's REST API using the file upload endpoint, linking them to the parent record (Candidate, JobOrder, Placement) via ContentDocumentLink. Resume files trigger Bullhorn's parsing pipeline on upload to populate structured Candidate fields. Non-resume documents (offer letters, contracts) attach as ContentDocuments with the appropriate ContentDocumentLink visibility setting.

Ceipal Owner records on Applicants, Jobs, Submissions, and Placements map to Bullhorn User records. We resolve by email match against Bullhorn User. Any Ceipal Owner without a matching Bullhorn User enters a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. OwnerId references are required on most standard Bullhorn entities, so this step gates the entire migration.

Ceipal TalentBench is a searchable resume repository with parsed fields (structured skills, work history, education) alongside raw resume text. We migrate parsed resume data as structured fields on Bullhorn Candidate records and preserve the raw resume as a ContentDocument attachment so Bullhorn's own parsing engine runs on intake. Skills migrate to Bullhorn Candidate skills fields; if the customer's skill taxonomy is complex, we map to a Skills Custom Object linked to Candidate.