Migrate from Bullhorn ATS & CRM to Recruit CRM & ATS

Bullhorn Candidates map to Recruit CRM Candidates as the primary ATS record. Bullhorn's parsed resume data (skills, work history, education, certifications) transfers as structured fields in Recruit CRM. We map Bullhorn's status field to Recruit CRM's candidate status, and preserve the original Bullhorn candidate ID as a custom field bh_id__c for cross-reference. Resume files exist as separate attachment objects in Bullhorn and require API retrieval via file reference URLs; CSV-only exports silently omit them.

Bullhorn JobOrder maps to Recruit CRM Job. Bullhorn stores requirements, location, salary information, and job status in JobOrder; these map to Recruit CRM's Title, Description, Location, Salary Range, and Status fields. Recruit CRM's Jobs include a pipeline stage field that we configure to match Bullhorn's job status workflow. Each Job in Recruit CRM links to a Client record, mirroring Bullhorn's ClientCorporation association.

Bullhorn ClientCorporation maps directly to Recruit CRM Client. Company details, primary contact information, industry, and address fields transfer 1:1. The Client record in Recruit CRM serves as the parent for linked Job and Candidate/Contact records, matching Bullhorn's relationship model. We resolve Client IDs before Job or Candidate import so that lookups are satisfied at insert time.

Bullhorn Contacts represent both client-side business contacts and candidate references, sharing a schema but serving different roles. We separate Contacts by Bullhorn's entityType during migration to avoid creating duplicate Contact records in Recruit CRM. Client-facing contacts attach to the Client record; candidate reference contacts attach to the Candidate record. Email deduplication runs against the merged Contact pool before insert.

Bullhorn Opportunities are CRM-level pipeline deals tied to Clients using recruiting-specific stages (Interview, Offer, Extended). These remap to Recruit CRM's Pipeline Deal records. We build a stage mapping table during scoping that maps each Bullhorn opportunity stage to the nearest Recruit CRM pipeline stage. Bullhorn's opportunity billing amount, probability, and close date map to Recruit CRM's Deal value, probability, and expected close date fields.

Bullhorn Placements are transactional records linking Candidate, JobOrder, and Client with billing details including pay rate, charge rate, start date, end date, and overtime rules. Recruit CRM represents placements as a link between the Candidate record and the Job record, with billing fields stored on one or both sides. We decompose each Bullhorn Placement into a Recruit CRM Candidate-Job application record with billing details preserved as custom fields, and the original Bullhorn Placement ID stored as bh_placement_id__c for reconciliation.

Bullhorn Tasks map directly to Recruit CRM Tasks with status, due date, priority, and owner assignment preserved. Task type, description, and association to the parent record (Candidate, Job, Client, or Placement) transfer via the corresponding Recruit CRM ID. Bullhorn's ATS Growth edition caps API subscriptions at 50, which may truncate task export volume for large task histories; we flag this during scoping and use pagination to retrieve all records.

Bullhorn custom objects with up to 55 fields each are available in limited quantities per edition (ATS Growth: none; ATS: 2; Front Office Growth/Enterprise: 10). Recruit CRM has no hard ceiling on custom fields per record. We audit the customer's Bullhorn custom object usage during scoping, map each to a Recruit CRM custom field group on the corresponding record, and flag any that exceed Recruit CRM's field type coverage for the admin to review. Overflow fields not accommodated within reasonable custom field counts are stored as text notes with a warning flag.

Bullhorn stores resume files, parsed documents, and uploaded communications as separate attachment objects accessible only via the REST API. Bullhorn's standard CSV export does not include attachments. We retrieve originals via Bullhorn's file reference URLs and upload them to Recruit CRM's document storage, linking each file to the corresponding Candidate or Job record. If the customer's Bullhorn edition excludes API access, we flag the attachment gap explicitly and recommend the customer export files manually before the migration window.

Bullhorn CandidateList represents a candidate's submission to a specific job, storing status within the recruitment pipeline (e.g., submitted, phone screen, interview, offer). These map to Recruit CRM's Application or submission records linking Candidate to Job. The candidate-job association, submission date, and pipeline status transfer. Bullhorn's CandidateList-specific fields (interview date, feedback notes) migrate as custom fields on the Recruit CRM application record.

Bullhorn Users map to Recruit CRM Users by email match. Bullhorn User records carry name, email, role, department, and active/inactive status. We resolve owners by email at migration time; any Bullhorn User without a matching Recruit CRM User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrated records (Candidates, Jobs, Tasks) is updated to the resolved Recruit CRM User ID.