Migrate from Homerun to Bullhorn ATS & CRM

Homerun Candidate records map to Bullhorn Candidate. We extract candidate name, email, phone, address, stage history, source, and any custom properties via paginated API. Bullhorn Candidate has a rich field model with dedicated fields for skills, certifications, and tax terms. We normalize the stage history as a series of CandidateCertification or note records appended with timestamps for audit. Custom properties on Candidate require pre-creation in Bullhorn via the Field Mappings tool before import.

Homerun Job Openings map to Bullhorn JobOrder. Each job's title, description, department, location, employment type, and salary range transfer directly. Homerun's pipeline stage names map to Bullhorn's JobOrder status field, with each pipeline becoming a Bullhorn JobOrder track configuration. JobOrder is imported before Candidate to satisfy the JobOrderID lookup on CandidateApplication records.

Homerun application records (candidates applied to jobs) map to Bullhorn CandidateApplication, linking a Candidate to a JobOrder with a status. The application date and current pipeline stage transfer as the CandidateApplication status and lastModifiedDate. This object has a 1:1 relationship only when both Candidate and JobOrder are imported into Bullhorn.

Homerun Employee records introduced with the 2025 HR module map to Bullhorn as Candidate records with employment-type fields. Since Bullhorn does not have a standalone Employee object, we create Candidate records for each Homerun Employee with employment status, start date, and department stored in Bullhorn's Candidate custom fields. Employment history is appended as CandidateEmployment records linked to each Candidate.

Homerun Time Off balances and requests migrate as a Bullhorn Custom Object (if the Professional tier or above is provisioned) or as Note records attached to the relevant Candidate. We export current-state balances with effective dates and map accrual patterns to the destination's accrual engine. Bullhorn's standard Time Off module is available in some editions but requires explicit configuration to match Homerun's balance model. The customer chooses the storage strategy during scoping.

Homerun Offer letters map to Bullhorn Placement records in the Offer phase. We transfer compensation details (salary, hourly rate, fee percentage), start date, conditional terms, and offer status. Bullhorn Placement is the primary object for tracking a candidate's placement with a client and includes a status workflow that mirrors the offer-to-placement lifecycle. Offer PDFs are stored as ContentDocument records linked to the Placement.

Homerun evaluation scorecards and ratings normalize to Bullhorn CandidateCertification records or Note records. Score values may not map 1:1 to Bullhorn's rating schema, so we preserve raw numeric values alongside a normalized rating in a custom field. Evaluator comments transfer as the certification description. Rating normalization rules are defined during scoping.

Homerun team members and user accounts map to Bullhorn Users by email match. We preserve role assignments and ownership relationships as Bullhorn role mappings. Users without an email match in the destination go to a reconciliation queue for the Bullhorn admin to provision. Bullhorn User provisioning is a prerequisite before any record import because OwnerId references are required on JobOrder, Candidate, and Placement.

Homerun custom fields on any object require pre-creation in Bullhorn via Field Mappings. We enumerate all custom properties during scoping, map data types (text to customtextblock or customtextarea, date to customdate, picklist to custompicklist, number to customfloat or customint, boolean to customcheckbox), and create the Bullhorn field before import. Bullhorn's field naming limit of 37 characters applies; longer Homerun field names are truncated to 37 characters per Bullhorn's standard.

Employee documents stored in Homerun HR export as file metadata and content URLs. We retrieve document content via Homerun's API, then upload to Bullhorn as ContentVersion records with the file linked via ContentDocumentLink to the relevant Candidate or Placement. Large files use chunked retrieval and multipart upload to Bullhorn's content API. We preserve original file names and MIME types.

Homerun's configurable pipeline stages map to Bullhorn JobOrder status values and CandidateJobSubmission status values. Each pipeline becomes a Bullhorn track with stage names, ordering, and probabilities configured in Bullhorn's Field Mappings. We flag any stages that exceed Bullhorn's 20-stage maximum per track and propose consolidation or mapping to a custom picklist field. Stage probabilities transfer as percentages rounded to Bullhorn-allowed values.

Homerun tags stored as multi-checkbox properties on Candidate migrate to Bullhorn custom picklist or multi-select fields. We enumerate the tag vocabulary during scoping, create the Bullhorn picklist values, and map each Candidate's tag set to the destination field. Tags used for candidate segmentation also map to Bullhorn's Category or Skill fields where applicable. The customer chooses tag strategy during scoping based on their recruiting taxonomy.

If the Homerun account has Placement records (post-2025 HR module), these map directly to Bullhorn Placement with Client, Candidate, JobOrder, start date, end date, bill rate, pay rate, and employment type. Bullhorn Placement is the billing and compliance anchor for temporary and direct-hire placements; we preserve the full placement history including status transitions and termination records.