Migrate from BrightMove to Bullhorn ATS & CRM

BrightMove Candidate records map directly to Bullhorn Candidate. We extract name, email, phone, address, resume content, status history, source information, and custom fields. The BrightMove candidateID becomes a custom reference field; the Bullhorn Candidate entityId is used for subsequent lookups. Resume files are extracted as binary attachments and reattached to the Bullhorn Candidate record as ContentDocument records.

BrightMove Job Order records map to Bullhorn JobOrder. We extract title, description, requirements, department, location, pay rate, bill rate, and the full pipeline stage configuration. Custom stages from BrightMove are mapped to Bullhorn JobOrder status values, preserving stage order. If BrightMove uses custom status values not present in Bullhorn, we add them as user-defined status values during the mapping phase.

BrightMove Placement records map to Bullhorn Placement with a direct 1:1 relationship. We extract start date, end date, pay rate, bill rate, overtime eligibility, and the client association. The placement links to the migrated Candidate (via candidateID-to-entityId lookup), the migrated JobOrder, and the ClientCorporation. Compensation fields migrate as custom decimal fields if the standard Placement object does not cover the full structure.

BrightMove Contact records split into Bullhorn ClientCorporation (the company entity) and ClientContact (the individual). BrightMove contacts that share a company association are grouped under a single ClientCorporation, and the individual contact details map to ClientContact records linked via the corporation. We extract name, email, phone, title, company, and any custom fields on the contact.

BrightMove activity logs and notes against candidates and jobs migrate to Bullhorn Note records. Activity type varies by tenant configuration; we extract all available activity text, timestamp, and owner information. Notes attach to the Bullhorn Candidate or JobOrder via ContentDocumentLink. If BrightMove activities include call disposition or outcome data, we preserve these in custom fields on the Note or as separate Task records.

Resume files and attached documents from BrightMove are extracted as binary files, validated for integrity, and uploaded to Bullhorn as ContentDocument records linked to the corresponding Candidate via ContentDocumentLink. We preserve the original filename and file type metadata. Bulk document migration requires chunked processing to stay within Bullhorn's API rate limits.

BrightMove custom fields on candidates, jobs, and placements are mapped to Bullhorn custom fields. We extract the custom field type (text, dropdown, date, checkbox, numeric) and create equivalent Bullhorn custom fields before migration. Dropdown fields require value mapping where the BrightMove option set does not match the Bullhorn picklist; we document any mismatches for the customer's admin to resolve before migration.

BrightMove user accounts representing recruiters and hiring managers map to Bullhorn User records. We match by email address and preserve team assignments, user type (internal recruiter, external recruiter, hiring manager), and the userID reference for activity and placement assignment lookups. Any BrightMove user without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import continues.

BrightMove tags on candidates and jobs are extracted and applied as Bullhorn Tags. Bullhorn supports tagging on Candidate, JobOrder, and Placement records. We preserve the tag name and note that tag naming conventions may differ between systems; we do a string-normalization pass before applying tags to avoid duplicates caused by case differences or trailing whitespace.

BrightMove's configurable job pipeline stages map to Bullhorn JobOrder status values. We extract the full stage taxonomy during discovery, including stage order, stage-specific statuses, and any conditional stage transitions. Bullhorn status values are configured per corporation, so multi-division BrightMove accounts may require multiple status configurations in Bullhorn.

BrightMove tracks candidate submissions across multiple job orders as part of its candidate history. We extract submission records and create Bullhorn CandidateJobOrder entries that represent each time a candidate was submitted to a job. This preserves the submission date, submission status, and the submitting recruiter.

BrightMove maintains a status pipeline for candidates (e.g., Applied, Screening, Interview, Offer, Hired). We extract the full status history with timestamps and map each BrightMove status to the corresponding Bullhorn Candidate status. Status history is preserved as custom date and picklist fields on the Candidate record for reporting continuity.