Migrate from Bullhorn ATS & CRM to BambooHR

Bullhorn Candidate records split into two BambooHR destinations. Candidates with a Placement record (hired through the staffing agency) become BambooHR Employees with start dates from the Placement record. Candidates without a Placement but with job submission history become BambooHR Applicants in the BambooHR ATS module. The candidate name, email, phone, address, resume file reference, parsed skills, work history (education, employment), and custom fields migrate to the corresponding BambooHR Employee or Applicant field. Historical salary information from Placement payRate fields maps to BambooHR custom pay-rate fields on Employee.

Bullhorn Candidate employment history (from resume parse) maps to BambooHR Employee employment history entries. Each Bullhorn employment record (company name, title, start date, end date, description) becomes a separate BambooHR Employment History item. Date precision from Bullhorn may exceed BambooHR's field granularity; we normalize to month-year format where BambooHR does not support exact dates.

Bullhorn Placement records carry the pay rate (candidate pay), charge rate (client bill rate), start date, end date, and overtime eligibility flag. These do not map to a native BambooHR object because BambooHR has no staffing-billing model. We map Placement fields to custom Employee-level fields: payRate__c, chargeRate__c, contractStartDate__c, contractEndDate__c, overtimeEligible__c. If the customer no longer manages contractors this way, we recommend archiving Placement records to a CSV inventory rather than populating custom fields.

Bullhorn User records (recruiters, sales staff, administrators) map to BambooHR User accounts for the HR administrators who will manage the BambooHR system. We resolve by email match. Bullhorn Users who were external recruiters or contract staffing consultants have no equivalent in BambooHR and are excluded from the user migration scope. Active/inactive status migrates from Bullhorn isDeleted flag.

Bullhorn JobOrder records (external job postings for staffing assignments) have no direct BambooHR equivalent. BambooHR Jobs represent internal company positions open for hire, not external job postings for client-funded staffing assignments. We do not migrate JobOrders. We deliver a written inventory of all Bullhorn JobOrders with their status, requirements, and location as a CSV for the customer's records-retention file. If the customer is transitioning from external staffing to internal hiring, internal open positions should be created manually in BambooHR after migration.

Bullhorn Client records represent the staffing agency's customer companies—business entities with primary contacts, industry classification, and address. BambooHR has no Client or company-account concept; it manages people (employees), not business relationships. Client records cannot migrate. We deliver a written inventory of all Bullhorn Clients with contact name, company, email, and phone as a CSV for the customer's CRM migration if they adopt a separate CRM post-Bullhorn.

Bullhorn Contact records serve two roles: client-side business contacts (associated with Client records) and candidate references. Business contacts do not map to BambooHR. Candidate reference contacts (professional references listed on a Candidate profile) map to the corresponding BambooHR Employee as Emergency Contact or Reference records with name, relationship, phone, and email.

Bullhorn Opportunities represent recruiting pipeline deals tied to Clients—sales CRM stages like Qualified, Interview, Offer, Placed. BambooHR has no pipeline, deal, or sales-stage concept. Opportunity records cannot migrate. We deliver a written inventory of all Bullhorn Opportunities with their status, stage, value, and associated Client as a CSV. If the customer maintains a separate CRM post-Bullhorn, this CSV serves as the seed data for re-entering pipeline history.

Bullhorn Tasks (to-dos with type, due date, status, and owner assignment) map to BambooHR Note records attached to the corresponding Employee. Task type maps to a Note category field; due date and status become note body content. Open tasks (Status = Open) migrate as active notes for the employee's BambooHR record; completed tasks migrate as historical notes. Bullhorn task ownership resolves via the User-to-Employee mapping before note creation.

Bullhorn CandidateList records represent a Candidate's submission to a specific JobOrder with a status in the recruitment pipeline (Submitted, Interview, Offer, etc.). When the candidate maps to a BambooHR Applicant, the CandidateList submission history migrates as Application History notes on the Applicant record, preserving the original submission date, job title, and stage status.

Bullhorn custom objects (up to 2 on ATS editions, 10 on Front Office) extend core entities with up to 55 fields each. BambooHR supports custom fields on Employee and Applicant records but does not support standalone custom objects. We audit every Bullhorn custom object used on Candidate records during scoping. Fields that map to existing BambooHR Employee fields are redirected; overflow fields are mapped to BambooHR custom fields. If the count of custom fields per entity exceeds BambooHR's practical limit (roughly 20 custom fields per object), we recommend rationalizing or archiving the overflow before migration.