Migrate from Bullhorn Connexys ATS to BambooHR

Bullhorn Candidate records split at migration time based on status. Candidates with no associated Placement and an active Application status map to BambooHR Applicant records via the BambooHR ATS Hiring API. Candidates with an associated Placement record (a hire outcome) map to BambooHR Employee records with the Placement start date, salary, and status preserved as the Employee start date and employment status. We flag any Candidate record with GDPR consent flags for the customer's admin to review before import, since BambooHR handles consent tracking differently from Bullhorn's native GDPR consent management.

Bullhorn Account records representing client companies map to BambooHR Company records, which store the client's name, industry, and address. Bullhorn's billing and company-size fields map to custom fields in BambooHR. Account is created before any linked Contact or Placement import so that the relationship is satisfied at insert time. Multi-office Bullhorn Accounts (where one client has multiple offices) require a decision during scoping: flatten to one Company in BambooHR or use BambooHR's Locations feature to distinguish offices.

Bullhorn Contact records representing hiring managers and client-side contacts map to Employee records in BambooHR if they are internal employees of the company, or to Applicant contact fields if they are external contacts being tracked for reference. We preserve the Contact's email, phone, title, and any custom fields and map them to the corresponding BambooHR standard or custom fields. Account-Contact associations are preserved via the Company relationship in BambooHR.

Bullhorn JobOrder records map to BambooHR Job Openings, which represent active and historical job postings. The JobOrder title, description, requirements, and salary range migrate as Job Opening fields. Bullhorn's job status (Open, Filled, Cancelled) maps directly to BambooHR Job Opening status. We map custom job fields as BambooHR custom fields on the Job Opening object. Any Bullhorn job fields that have no BambooHR equivalent are flagged as configuration items for the customer's admin to address post-migration.

Bullhorn Placement records, representing confirmed hires that link Candidate to JobOrder with start date, salary, and placement status, map to BambooHR Employee records. The Placement start date becomes the Employee hire date. The placement fee (if tracked) migrates as a custom field. Placement status (Active, Extended, Terminated, Declined) requires a scoping decision: Active and Extended map to active Employee records; Terminated and Declined require a decision on whether to import as terminated Employee records or to exclude from the active migration scope.

Bullhorn's Job Reporting junction object tracks each Candidate's movement through pipeline stages with timestamps and associated User. BambooHR's ATS models applicant stages as a configurable pipeline (Applied, Phone Screen, Interview, Offer, Hired, Rejected). Bullhorn stage history (which tracks every transition through Application, Submittal, Interview, Offer, Placement) does not have a direct BambooHR equivalent. We migrate the most recent stage and the date of that transition as an Applicant custom field; full stage history is documented as a manual-rebuild item. Incomplete or inaccurate Job Reporting records in Bullhorn are flagged during discovery for the customer's admin to address before migration.

Bullhorn User records representing recruiters, administrators, and managers map to BambooHR Employee records with the BambooHR user role set to reflect the Bullhorn access level. Owner assignment on Candidate, JobOrder, and Placement records links to the corresponding BambooHR Employee via the hireUserId field on Job Openings and Applicants. We resolve owners by email match and flag any Bullhorn User without a matching BambooHR Employee for the customer's admin to provision before record import.

Bullhorn Custom Objects (extending Candidate, Contact, Account, Job, and Placement) with up to 55 fields each do not have a standalone equivalent in BambooHR. We migrate each Custom Object as a set of BambooHR custom fields on the corresponding standard object (Employee, Applicant, Company, Job Opening). Limits vary by Bullhorn edition: 2 Custom Objects on Bullhorn ATS, 10 on Front Office Growth/Enterprise. We audit the field types during discovery and map text, number, date, and picklist fields to their BambooHR equivalents; Bullhorn-specific types (Picker:Candidate, Picker:Client) require manual mapping decisions during scoping.

Bullhorn resume files and attachments export via the REST API. We chunk large attachment batches to stay within Bullhorn's 100,000 API call monthly ceiling and 50 concurrent session cap. Resume files migrate to BambooHR Documents attached to the corresponding Applicant (for candidate resumes) or Employee (for onboarding documents) record. Parsed resume data from Bullhorn's resume parser migrates as standard and custom fields on the Applicant record rather than as raw file attachments alone.

Bullhorn Candidate Tax Info captures federal filing status and exemptions that may be relevant for placed employees. GDPR consent flags on Candidate records require special handling: we map consent status to BambooHR Employee custom fields for GDPR-relevant records and flag any consent records that need explicit re-collection under the customer's data governance policy post-migration. Regional compliance fields vary by Bullhorn instance configuration and are mapped individually during discovery.

Bullhorn activity feeds and notes on Candidate, Contact, JobOrder, and Placement records export via API with timestamps and note body text. We map note content to BambooHR Notes on the corresponding Applicant or Employee record. Activity type (email, call, meeting, task) does not have a structured equivalent in BambooHR; we store the activity type as a Note tag or custom field. Bullhorn's activity timeline ordering is preserved by sorting on the original timestamp during import.