Migrate from Recruit CRM & ATS to Bullhorn ATS & CRM

Recruit CRM Candidates map directly to Bullhorn Candidate records. We map standard profile fields (name, email, phone, location, skills, source) by API field name, then resolve custom field values from Recruit CRM's per-organization custom field schema to Bullhorn custom fields in the Candidate entity. Bullhorn imposes a per-entity custom field limit; we audit the Recruit CRM custom field count during discovery and flag any that exceed Bullhorn's allowance, which may require a custom object or a field reduction strategy agreed upon with the customer before migration.

Recruit CRM Jobs map to Bullhorn Jobs with the full pipeline stage structure preserved. Bullhorn's hiring workflow is configurable per Job, and we map Recruit CRM's pipeline stages to Bullhorn's Workflow Steps so that candidate advancement through stages reflects the original placement pipeline history. Job assignments (assigned recruiter) map to Bullhorn Job Owner.

Recruit CRM Contacts (hiring managers, referrers, business contacts distinct from Candidates) map to Bullhorn Contact records. The Contact-to-Company association in Recruit CRM maps to Bullhorn's Contact-to-Company relationship. Custom fields on Contacts migrate to Bullhorn Contact custom fields following the same field-level audit as Candidates.

Recruit CRM Companies map to Bullhorn Company records with the full contact and job association preserved. Bullhorn's Company entity supports multiple Contacts per Company; we resolve the Recruit CRM Company-to-Contact associations at migration time and link the imported Contacts to the correct Bullhorn Company via the CompanyID lookup.

Recruit CRM Deals track placement or business transactions tied to Companies and Candidates. We map Deals to Bullhorn Opportunities, translating Deal stage names to Bullhorn Opportunity Stage values and preserving Deal value, currency, expected close date, and any custom Deal fields. If the customer uses multiple Deal pipelines in Recruit CRM, we map them to Bullhorn Record Types on Opportunity to preserve pipeline separation.

Recruit CRM Hotlists are curated candidate lists with saved search criteria and member IDs. We extract all candidate IDs from each hotlist during the discovery phase and create Bullhorn Groups (using Bullhorn's Group or List entity) with the original hotlist names preserved. Candidate-to-Group membership is re-established by adding each Candidate's Bullhorn ID to the corresponding Group at migration time. Hotlist search criteria do not migrate as logic; only the member snapshot migrates.

Recruit CRM Tasks linked to Candidates, Contacts, or Jobs migrate to Bullhorn Tasks with assignment, due date, status, and priority preserved. We resolve the owner reference by matching Recruit CRM user emails to Bullhorn User records. Completed versus open task counts are preserved as the Task Status value.

Recruit CRM Meeting records (date, time, attendees, outcome, notes) migrate to Bullhorn Event records. We preserve the meeting start and end time, location, and outcome description. Attendee resolution maps Recruit CRM Contact or Candidate references to Bullhorn Candidate or Contact IDs via the migration lookup table.

Recruit CRM Call Logs with duration, outcome, and linked Contact or Candidate migrate to Bullhorn Task records with TaskSubtype = Call. We preserve the call duration, outcome, timestamp, and the linked Candidate or Contact reference using the parent-record lookup table built during the mapping phase.

Recruit CRM Notes attached to Candidates, Companies, or Jobs are stored as free-text records and migrate to Bullhorn Note records linked via ContentDocumentLink to the parent record. We preserve the full note body, creation timestamp, and the parent object association (Candidate, Contact, Company, or Job) resolved through the Bullhorn ID lookup.

Candidate resumes, company documents, and email attachments stored in Recruit CRM's file storage migrate to Bullhorn as Documents attached to the corresponding Candidate or Company record. Each file is downloaded via the Recruit CRM Files API and re-uploaded to Bullhorn with the same candidate and object associations preserved. Large-volume file migrations require chunked parallel extraction and re-upload; we include file migration time in the timeline estimate during scoping.

Recruit CRM's customizable pipeline stages per Job map to Bullhorn Workflow Steps. We extract the complete stage configuration (stage name, order, automation triggers if any) during discovery and create the equivalent Bullhorn Hiring Workflow with matching steps. Bullhorn's workflow is configured per Job or Job Order type, so we align the migrated workflow to the appropriate Bullhorn Job Record Type.

Recruit CRM user accounts (recruiters, consultants, admins) map to Bullhorn User records by email match. We resolve active user assignments on Jobs, Candidates, and Deals to the corresponding Bullhorn User. Inactive Recruit CRM users without a matching Bullhorn User are held in a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes.

Recruit CRM custom field schemas are fully customer-defined and vary per organization. We audit the actual custom field set during discovery, map each field by data type (text, number, date, picklist, checkbox) to the equivalent Bullhorn custom field type, and create the Bullhorn custom fields in the destination org before any record migration. Fields that exceed Bullhorn's per-entity custom field limits are flagged and resolved with the customer before migration proceeds.

Recruit CRM email sequence enrollments (which candidates are active in which sequences and what step they are on) migrate as Bullhorn Note records on the Candidate, documenting the sequence name and last-known step. The sequence logic itself (cadence steps, timing rules, trigger conditions) is platform-specific and does not transfer. We deliver a written sequence inventory to the customer's Bullhorn admin for rebuild in Bullhorn Automation or the chosen sales engagement tool.