Migrate from Unicorn ATS to Bullhorn ATS & CRM

Unicorn ATS candidate records map directly to Bullhorn Candidate. Standard fields (name, email, phone, address, employment status) transfer as typed Bullhorn fields. Resume files migrate as file attachments on the Candidate record and are available for inline preview in Bullhorn ATS v2. Any candidate deduplication pass runs before migration to avoid inflating the Bullhorn candidate count; Bullhorn's duplicate candidate prevention (10.0 TrustRadius rating) operates post-import on new submissions.

Unicorn ATS Company or employer records map to Bullhorn ClientCorporation. The employer name, address, industry, and contact information transfer to Bullhorn's company entity. ClientCorporation must exist before Candidate records referencing it are imported, so this entity migrates first in dependency order.

Unicorn ATS job records map to Bullhorn JobOrder. Fields include job title, department, location, employment type (full-time, contract, part-time), pay range, description, and hiring manager assignment. Posting status and dates transfer to Bullhorn's job publishing fields. JobOrder must resolve to a ClientCorporation record for proper linkage.

Pipeline stages define the candidate journey from Application through Placement. Bullhorn ATS v1 uses a Job Reporting junction object where each stage (Application, Submittal, Interview, Offer, Closing Report) generates a record with Job Manager Stage Status (Current, Accepted, Rejected). ATS v2 uses a different stage tracking model. We extract the current stage configuration from Unicorn ATS and apply the corresponding Bullhorn stage model. If the customer is on ATS v1, we configure the Job Reporting object; if on ATS v2, we use the native stage fields. Stage automation rules do not migrate and are documented separately.

The link between a Candidate and a JobOrder in Bullhorn is represented by JobSubmission. Each application of a candidate to a job produces a JobSubmission record with its own stage and status. The migration maps each Unicorn ATS application record to a Bullhorn JobSubmission, preserving the application date, source channel, and initial pipeline stage assignment.

Placements (filled positions) in Unicorn ATS map to Bullhorn Placement records. Fields include start date, end date (for contract placements), pay rate, bill rate, placement status, and the recruiter credited for the hire. Placement records reference both the Candidate and the JobOrder and must be imported after both parent records exist.

Unicorn ATS custom fields added to Candidates, Jobs, or Placements map to Bullhorn Custom Fields within each entity. Bullhorn ATS edition limits Custom Objects to two per entity (Job, Candidate, ClientCorporation, Opportunity, Placement). If the migration scope requires more than two Custom Objects on a single entity, the customer must upgrade to the Front Office Growth or Enterprise edition before migration. Custom Component Fields in Bullhorn are reserved for integrations and not supported for general use; we route extended data to Custom Objects instead.

In ATS contexts, active employee records may be represented as Candidates (for internal mobility or alumni rehiring) or as Placements (for current placements). We map each Unicorn ATS employee record to the appropriate Bullhorn object based on employment status. Employee-specific fields (department, manager, start date, compensation) transfer to Placement or Candidate custom fields as appropriate.

Interview records in Unicorn ATS (scheduled date and time, interviewer assignments, interview type, outcome notes) map to Bullhorn Event records. Bullhorn EventRelation records link the interview to the Candidate, the JobOrder, and each interviewer (as User records). Event start and end times, location, and outcome transfer to the Bullhorn Event fields.

Offer records (compensation details, start date, offer status, approval history) in Unicorn ATS map to Bullhorn Placement records in the Offer stage. Bullhorn ATS v1 represents Offer as a stage in the Job Reporting object with status C (Current) or A (Accepted). Approval routing logic is platform-specific and does not migrate; we document the offer approval workflow for the customer's Bullhorn admin to configure in Bullhorn's workflow settings.

Recruiter notes, call logs, and general activity history attached to candidates in Unicorn ATS often export as flat CSV with no candidate record linkage. We run a fuzzy-match process on candidate name, email, and application date to reattach orphaned activity history to the correct Bullhorn Candidate record before import. Notes migrate as Bullhorn Note records linked via ContentDocumentLink to the parent Candidate.

Email engagements attached to candidates in Unicorn ATS migrate to Bullhorn EmailMessage records linked to a Task. Bullhorn requires GDPR or CCPA Support to be enabled for email export; we verify this requirement with the customer during scoping. Inbound emails transfer only; outbound email migration depends on whether the source platform stored them in structured form. The Task record provides the activity timeline entry with WhoId pointing to the Candidate.