BambooHR to Bullhorn ATS & CRM migration
We migrate Candidate and Contact records from BambooHR into Bullhorn with the HRIS-to-ATS schema gap resolved upfront, BambooHR custom fields mapped to Bullhorn custom fields, and Applicant data from BambooHR's ATS layer transferred into Bullhorn's Candidate and JobOrder model.
FlitStack AI migrates contact or candidates, candidates, joborders, candidatesubmission or placements and users from BambooHR to Bullhorn ATS & CRM, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-8 weeks.

What moves from BambooHR to Bullhorn ATS & CRM?
Migrating from BambooHR to Bullhorn is a platform-category transition from an HRIS to a staffing-focused ATS and CRM.
Read the full summary
The two systems share a Contact-like entity, but BambooHR organizes around Employees (current staff, employment history, compensation, PTO), while Bullhorn organizes around Candidates, ClientCorporations, JobOrders, and Placements. We migrate the overlapping record types — BambooHR Applicants to Bullhorn Candidates, BambooHR Employee contact fields to Bullhorn Contact records, and any applicant-stage candidates — and flag what cannot map because Bullhorn's data model is purpose-built for the staffing placement lifecycle, not HR record-keeping. Bullhorn's custom import tool limits to 1,000 records per batch for Candidates, Contacts, and Leads; larger migrations require our API pipeline with Bullhorn REST API batch handling and rate-limit backoff. Workflows, BambooHR onboarding checklists, and payroll data do not migrate; we deliver a written inventory for admin rebuild.
Employee → Contact or Candidate (split required)
BambooHR Employee records split into two Bullhorn targets depending on employment lifecycle stage.
How it maps
Employees who are currently active candidates for new roles (internal mobility, secondments, or sourcing candidates) map to Bullhorn Candidate records. Employees being recorded as placed staff from a prior agency engagement map to Bullhorn Contact records attached to a ClientCorporation. The split rule is defined during scoping based on the customer's use case — internal mobility cases go to Candidate; agency placement records go to Contact. Basic name, email, phone, address, and emergency contact fields migrate directly; BambooHR employment status, termination date, and hire date are stored as custom fields on the Bullhorn record because Bullhorn's standard fields are recruitment-focused.
Applicant → Candidate
BambooHR ATS Applicant records map directly to Bullhorn Candidate.
How it maps
Pipeline stage names (Applied, Phone Screen, Interview, Offer, Hired, Rejected) from BambooHR map to Bullhorn Candidate status and leadStatus fields, with manual mapping per customer because BambooHR pipeline stages are customer-defined. Resume files attached to BambooHR applicants migrate as Bullhorn Candidate resumes (file upload via Bullhorn REST API or document management). Custom application fields from BambooHR (any field beyond name, email, phone, resume, and stage) migrate as Bullhorn custom fields on the Candidate entity, with field type validation against Bullhorn's supported types (text, number, date, dropdown, multi-select, checkbox).
Job Information → JobOrder
BambooHR job postings in the ATS layer map to Bullhorn JobOrder records.
How it maps
BambooHR job title, job description, employment type (full-time, part-time, contract), and location map to Bullhorn JobOrder title, description, employmentType, and addressCity/addressState fields. The BambooHR job status (Open, Filled, Closed) maps to Bullhorn JobOrder status (Open, Interviewing, Offer, Closed, Cancelled). Any BambooHR custom job fields migrate as custom fields on Bullhorn JobOrder.
Job Application → CandidateSubmission or Placement (conditional)
BambooHR applications (Applicant-to-Job associations with application date, source, and custom fields) map to Bullhorn CandidateSubmission when the candidate is submitted to a job but not yet placed, and to Bullhorn Placement when the candidate is hired into the role.
How it maps
The mapping type is conditional based on BambooHR application status. Placements carry startDate, endDate, payRate, billRate, and client assignment — these map from BambooHR offer details and employment terms fields.
Employee → User (owner resolution)
BambooHR Employee records that have an email address matching an existing Bullhorn User account resolve to that User record for OwnerId assignment on Candidate, JobOrder, and Placement records.
How it maps
BambooHR employees without a Bullhorn User account go into a reconciliation queue; the customer's Bullhorn admin provisions User accounts for those employees before record import resumes. This is a prerequisite step before Candidate import can proceed because Bullhorn requires a non-null OwnerId on record creation.
Time-Off → Custom Field or Task
BambooHR time-off balances (accrued PTO, sick leave, personal days) and request history have no native Bullhorn equivalent because Bullhorn is an ATS, not an HRIS.
How it maps
We map time-off balances as Bullhorn custom fields on the Candidate or Contact record (if the customer uses Bullhorn for internal staffing and wants to track candidate availability). Time-off request history migrates as Task records with a custom type field for audit purposes, but Bullhorn does not enforce or process these as active policies.
- EmployeeContact or Candidatesplit
- ApplicantCandidate1:1
- Job InformationJobOrder1:1
- Job ApplicationCandidateSubmission or Placementtransformed
- EmployeeUsertransformed
- Time-OffCustom Field or Tasktransformed
+ 6 more in the mapping below
How BambooHR and Bullhorn ATS & CRM differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | BambooHR | Bullhorn ATS & CRM |
|---|---|---|
| Platform type | HRIS: employee records, payroll, PTO, benefits, performance | ATS & CRM: candidates, job orders, placements, client management, sales pipeline |
| Core entity model | Employees and Applicants as separate schemas with employment history | Candidates, JobOrders, ClientCorporations, Placements, and Opportunities |
| Primary pricing unit | Per-employee, per-month (active headcount) | Per-user, per-month (Bullhorn Starter $99, Core $165, Pro tier-based) |
| Candidate data scope | Basic applicant tracking; pipeline stages and custom application fields | Deep recruitment CRM with resume parsing, skills, employment history, credentials, and sourcing channels |
| Custom field limits | Unlimited custom fields with per-account type variation | Per-entity custom field allocation; custom objects require Bullhorn Support ticket to create |
| Import batch size | Report engine exports without batch constraints | Custom Import tool caps at 1,000 records per batch for Candidates, Contacts, Leads only |
| Automation scope | BambooHR workflows and onboarding checklists scoped to HR process | Bullhorn Automation (Herefish) and Bullhorn Onboarding (Able) as separate products |
What to watch for in a BambooHR to Bullhorn ATS & CRM migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
BambooHR ATS and Bullhorn ATS serve different purposes, not a direct upgrade
BambooHR's ATS module handles job postings and basic applicant tracking for companies hiring employees.
How we handle it
Bullhorn is purpose-built for staffing agencies managing clients, job orders from clients, and high-volume candidate pipelines with placement billing. The data models diverge significantly: BambooHR tracks Employees, Employment History, Compensation, and PTO; Bullhorn tracks Candidates, ClientCorporations, JobOrders, Placements, and Invoices. We clearly scope which BambooHR records are candidate-like (Applicants, job-stage employees) versus employee-only (HR records, payroll, PTO), and we do not attempt to force HR data into Bullhorn's placement-focused schema.
Bullhorn's Custom Import caps at 1,000 records per batch for three entity types only
Bullhorn's admin-level Custom Import tool imports up to 1,000 records per batch and supports only Candidate, Contact, and Lead entities.
How we handle it
Companies, JobOrders, and Placements must be created separately (Company via API, JobOrder via API or manual, Placement via API). Migrations exceeding 1,000 records per entity require our Bullhorn REST API pipeline with batch chunking, rate-limit handling (50 requests per second burst, 500 per minute sustained), and retry logic. BambooHR's per-employee report exports have no batch constraints, so we handle the output side segmentation during data transform.
Bullhorn custom objects require a Bullhorn Support ticket, not admin self-service
Unlike Bullhorn custom fields on standard entities (Candidate, JobOrder, ClientCorporation), which Bullhorn admins can create via Admin > Field Mappings, Bullhorn custom objects (customObject1s through customObject10s) require opening a Support ticket with Bullhorn to provision.
How we handle it
This adds a pre-migration step that is outside our API pipeline. We include custom object provisioning in the scoping timeline and recommend the customer open the Support ticket as soon as the migration scope is signed, since Bullhorn's support SLA on custom object requests varies.
BambooHR API rate limits are undocumented, Bullhorn's are documented
BambooHR's API documentation explicitly states that rate limits are not published and implementations should always be ready for 503 responses, with no stated per-minute or per-day ceiling.
How we handle it
We monitor for 503 responses during export, implement exponential backoff with jitter, and proactively throttle our request pipeline if throttling patterns emerge. Bullhorn's API documents a 50 req/s burst and 500 req/min sustained limit with 429 responses and a Retry-After header. We use Bullhorn's documented limits for the import pipeline and BambooHR's adaptive approach (backoff on 503) for the export pipeline.
BambooHR onboarding and payroll data have no Bullhorn equivalent in standard scope
BambooHR onboarding task lists, checklist states, and document request workflows do not migrate to Bullhorn Onboarding (Able) because Able handles candidate-facing onboarding post-placement, not HR onboarding.
How we handle it
We inventory the BambooHR onboarding state per new hire and deliver a written handoff with task names, current states, and recommended Bullhorn Onboarding equivalents. Bullhorn Onboarding is a separate product activation and configuration not included in standard ATS scope. Similarly, BambooHR payroll data (pay stubs, tax withholding, direct deposit info, journal entries) has no Bullhorn equivalent; we flag payroll data as a manual reconciliation step with the customer's HR and finance teams.
How the migration runs
Scoping and platform classification
We audit the BambooHR account across installed modules (HRIS, ATS, Payroll, Performance), record counts per object type (Employees, Applicants, Job Postings, Custom Fields, Benefits enrollments, PTO balances), and active onboarding workflows.
What this step covers
We identify which records are candidate-like (Applicants in the BambooHR ATS layer, job-stage employees for internal mobility) versus HR-only (payroll, PTO, benefits, performance reviews). We pair this with a Bullhorn edition review (Starter at $99/user for 1-2 users, Core at $165/user for small growing teams, Pro tier-based for AI and automation features) to determine which Bullhorn features are available for the target schema. The scoping output is a written migration object inventory and Bullhorn edition recommendation.
Schema provisioning and field mapping design
We design the Bullhorn destination schema during this step.
What this step covers
This includes creating Bullhorn custom fields on Candidate, JobOrder, ClientCorporation, and Placement entities via Admin > Field Mappings (for custom fields) and via Bullhorn Support ticket (for custom objects). We map BambooHR pipeline stage names to Bullhorn Candidate status values per customer configuration. We define the Employee-to-Candidate or Employee-to-Contact split rule based on the customer's use case. Bullhorn admin credentials and Field Mappings write access are required before this step proceeds.
Sandbox migration and reconciliation
We run a full migration into a Bullhorn sandbox environment (or a named subset of the production database if no sandbox is available) using representative data volume.
What this step covers
The customer's Bullhorn admin reconciles record counts (Candidates in, Contacts in, JobOrders in, Placements in), spot-checks 25-50 random records against the BambooHR source for field accuracy, and validates custom field data. Any mapping corrections — wrong field types, missed custom fields, stage name mismatches — happen here before production migration begins. This step also validates that Bullhorn's field-level security and validation rules do not block the import batch.
Owner and User reconciliation
We extract every distinct BambooHR employee with an email address who is referenced as an owner or hiring manager on a BambooHR Applicant, Job Posting, or Employee record.
What this step covers
We match these by email against Bullhorn's User table in the destination org. BambooHR employees without a matching Bullhorn User go to a reconciliation queue. The customer's Bullhorn admin provisions any missing User accounts before production migration proceeds. Bullhorn requires a non-null OwnerId on Candidate, JobOrder, and Placement records — migration cannot proceed past this step without owner resolution.
Production migration in dependency order
We run production migration in record-dependency order: Bullhorn Users (manual, validated in step 4), ClientCorporations (from any employer/agency client data in BambooHR), JobOrders (from BambooHR job postings), Candidates (from BambooHR Applicants and split Employee records), Placements (for hired applicants with employment terms), then custom fields and documents.
What this step covers
Bullhorn's Custom Import tool (up to 1,000 records per batch for Candidates, Contacts, Leads) handles records within the limit; records exceeding the batch cap migrate via Bullhorn REST API with rate-limit handling. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and onboarding rebuild handoff
We freeze BambooHR write access during the cutover window, run a final delta migration for any records modified during the migration window, then enable Bullhorn as the system of record for recruiting operations.
What this step covers
We deliver the onboarding task inventory document to the customer's Bullhorn admin. We support a one-week hypercare window where we resolve any reconciliation issues raised by the recruiting team. We do not configure Bullhorn Onboarding (Able) workflows, Bullhorn Automation (Herefish) sequences, or Bullhorn payroll integrations inside the migration scope; those are separate product activations or implementation engagements.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and whether BambooHR's ATS layer (Applicants, job postings, pipeline stages) is included in scope. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for BambooHR to Bullhorn ATS & CRM →Why teams move from BambooHR to Bullhorn ATS & CRM
- Staffing and recruitment agencies outgrow BambooHR's ATS layer. BambooHR's applicant tracking lacks resume parsing depth, skills-based searching, mass candidate communication, job board distribution at scale, and the Candidate-to-Placement-to-Invoice staffing workflow that Bullhorn automates natively. G2 and Capterra reviews cite BambooHR's ATS as adequate for micro-SMBs but insufficient for agencies placing ten or more candidates per month.
- Bullhorn combines ATS and CRM in one platform purpose-built for staffing. BambooHR stores client and contact data in a flat Employee model with no placement, commission, or job-order tracking. Bullhorn's ClientCorporation, Opportunity, and Placement objects let staffing firms manage the full client relationship from job order through placement billing without a separate CRM. Reddit r/recruiting threads confirm that teams moving to Bullhorn cite its unified ATS-plus-sales CRM as a primary reason.
- Companies with 150-200+ employees report BambooHR's customization ceiling. Limited advanced reporting, non-configurable performance review workflows, and weak permissions granularity force HR teams to evaluate enterprise alternatives. Bullhorn scales to 10,000+ candidate records per database with real-time analytics and configurable record-level permissions by department and user role.
- Bullhorn's 350+ partner marketplace and native API support deeper integrations for staffing operations (background check vendors, payroll providers, job boards, LinkedIn RSC) than BambooHR's integration surface. Bullhorn's REST API with documented rate limits (50 requests per second burst, 500 requests per minute sustained) provides a migration-friendly interface that BambooHR's undocumented-limit API does not.
- Outbound recruitment and sales engagement requires Bullhorn's messaging automation and candidate outreach tools. BambooHR has no candidate engagement, no outbound email sequencing for talent sourcing, and no pipeline visualization for recruiter activity. Bullhorn Automation (formerly Herefish) provides cadence-based outreach, task automation, and data quality tools that BambooHR's HR-centric feature set does not include.
Questions, answered
BambooHR to Bullhorn ATS & CRM migration questions
How long does a BambooHR to Bullhorn migration take?
Most migrations land between four and eight weeks for accounts with fewer than 5,000 candidate and contact records and no complex ATS pipeline history. Migrations that include full BambooHR ATS pipeline data (hundreds of application records with stage history, multiple job postings, and extensive custom fields on Candidates) move to ten to fourteen weeks because Bullhorn's batch import cap of 1,000 records per run requires API-level chunking and the Employee-to-Candidate or Employee-to-Contact split adds reconciliation work. Bullhorn's own onboarding documentation cites two to six weeks for standard agency implementations; our migration timeline is additive to that baseline for data that does not fit Bullhorn's standard import paths.
Does BambooHR onboarding task data migrate to Bullhorn Onboarding (Able)?
No. BambooHR onboarding checklists and document request workflows do not migrate to Bullhorn Onboarding (Able) because Able is a candidate-facing onboarding product that activates after a placement is made, not an HR onboarding tool. BambooHR onboarding tasks tied to new hire provisioning have no direct Bullhorn equivalent in the ATS layer. We inventory the BambooHR onboarding state per new hire and deliver a written handoff document listing each task name, current checklist state, and the recommended Bullhorn Onboarding configuration. Bullhorn Onboarding activation and configuration is a separate engagement, either with Bullhorn professional services or an independent Bullhorn implementation partner.
Can BambooHR payroll data migrate to Bullhorn?
No. BambooHR payroll data — pay stubs, tax withholding, direct deposit information, journal entries, and pay rate history — has no native Bullhorn equivalent because Bullhorn ATS is not a payroll system. Bullhorn's placement-focused payRate and billRate fields capture compensation for staffing placements but not HR payroll history. We map BambooHR pay rate and pay type to Bullhorn custom fields on Candidate and Placement records for current/past placement data, but BambooHR payroll processing history, tax filing records, and journal entry exports are out of scope. The customer's finance team reconciles payroll records separately, typically with their payroll provider or accountant.
Do BambooHR workflows and performance review workflows migrate to Bullhorn Automation?
No. BambooHR workflows (approval chains, automated reminders, onboarding triggers, and HR-process automations) do not migrate to Bullhorn Automation (Herefish) because they are different automation systems with different trigger models and action types. Bullhorn Automation is a sales engagement and candidate outreach tool, not an HR workflow engine. We deliver a written inventory of every active BambooHR workflow with its trigger conditions, actions, and recommended Bullhorn Automation equivalent, and the customer's Bullhorn admin or implementation partner rebuilds them post-migration. Performance review workflows (review cycles, reminder dates, multi-step approval chains) are similarly out of scope.
What BambooHR records can realistically migrate to Bullhorn?
The practical migration scope is the BambooHR ATS layer: Applicants, job postings, application history (stage transitions), candidate resumes, and any custom fields on the applicant record. Employee contact data (name, email, phone, address) migrates to Bullhorn Contact records if the company uses Bullhorn for internal recruiting or agency staffing where placed candidates become contacts. BambooHR HR data — payroll, PTO balances, benefits enrollment, performance reviews, employment history, compensation grades — does not map to Bullhorn's placement-focused schema and is flagged as manual reconciliation scope. We are transparent about this boundary during scoping so there are no surprises at cutover.
How does Bullhorn handle BambooHR's custom fields?
Bullhorn supports custom fields on all standard entities (Candidate, JobOrder, ClientCorporation, Placement, Opportunity) via Admin > Field Mappings, accessible to Bullhorn admins without a Support ticket. Bullhorn custom fields support types including text, number, date, currency, dropdown, multi-select, and checkbox. BambooHR custom employee and applicant fields are inventoried during scoping, validated for type compatibility, and mapped to Bullhorn custom fields created before migration. Bullhorn custom objects (customObject1s through customObject10s) require a Bullhorn Support ticket to provision and are used when the customer needs structured sub-entities beyond what custom fields on standard entities can capture.
Can FlitStack AI migrate BambooHR document attachments to Bullhorn?
Yes, with a qualification. We migrate documents attached to BambooHR Employee and Applicant records (offer letters, resumes, signed contracts, certifications) as Bullhorn ContentDocument records linked via ContentDocumentLink to the corresponding Candidate or Contact record. Resume files on BambooHR Applicants migrate to Bullhorn Candidate resume attachments. Bullhorn's Custom Import tool does not handle documents — this is an API-level migration step performed after record import. Document type classification (resume, offer letter, contract) is mapped to a Bullhorn custom field for organizational clarity. Binary document exports from BambooHR are accessed via the BambooHR API file endpoint and uploaded to Bullhorn via the Bullhorn REST API.
Related migrations
Sources: official documentation
- Understanding Custom Objects — Bullhorn ATS
- Understanding Bullhorn Field Edit Types
- A guide to data hygiene for staffing firms — Bullhorn
- How to Import Data into Bullhorn — Bullhorn ATS
- Import Tool Training — BambooHR Partners
- Custom Dashboards: Import CSV Data — BambooHR Product Updates
- Importing Data into BambooHR — BambooHR Support
Get a quote
Moving from BambooHR to Bullhorn ATS & CRM?
Tell us roughly how many records and objects you have. We scope the mapping and the Bullhorn ATS & CRM setup with you, then send a quote.
Get a quote