Migrate from BrightMove to BambooHR

BrightMove Candidates map to either BambooHR Employees (if the candidate was placed and is now an active employee) or to BambooHR Applicants in the Hiring module (if the candidate is still in the recruiting pipeline). We extract the candidate's employment status from BrightMove Placement records to determine the split: any Candidate with a corresponding Placement becomes an Employee, and all other Candidates become Applicants in BambooHR Hiring. The original BrightMove candidate ID is preserved in a custom field brightmove_candidate_id__c for audit traceability.

BrightMove Job Orders map to BambooHR Job postings. Job title, description, requirements, department, and location transfer directly. Pipeline stages from BrightMove's customizable workflow stages require configuration in BambooHR: each BrightMove stage becomes an Application Status value in BambooHR's Hiring settings. We extract the full stage taxonomy during discovery and configure BambooHR Hiring statuses to match the stage order before migration begins.

BrightMove Placements represent hired candidates with start dates, compensation, and client associations. Placements map directly to BambooHR Employee records as the primary employment record. Compensation details (salary, pay rate, commission) migrate to BambooHR payRate and custom compensation fields. The linkage to the originating BrightMove Job Order is preserved by cross-referencing the brightmove_job_id__c field on the Employee record.

BrightMove Contacts represent client-side recruiters and hiring managers. These map to BambooHR Employee records if the contact is a user in BambooHR, or to BambooHR Company records if the contact represents an external organization. We extract contact type flags from BrightMove custom fields during discovery to determine the appropriate mapping. Any contact associated with a BrightMove Placement/client assignment migrates to the corresponding BambooHR Company record.

BrightMove allows custom fields on Candidates, Jobs, and Placements. Custom field types (text, dropdown, date, checkbox, numeric) are extracted and mapped to BambooHR Employee or Job custom fields using BambooHR's field ID model. Dropdown fields require explicit value-mapping because BrightMove option labels may differ from the BambooHR options we configure. We retrieve the full BambooHR field taxonomy via GET /v1/meta/fields during scoping and map each BrightMove field to the corresponding BambooHR numeric field ID.

Resume files and candidate attachments stored in BrightMove are extracted during migration, validated for file integrity, and attached to the corresponding BambooHR Employee record as files. We use the Employee's brightmove_candidate_id__c or brightmove_placement_id__c as the matching key to attach files to the correct record. File type and original filename are preserved.

BrightMove activity logs and notes against Candidates and Placements migrate to BambooHR Employee Notes. Activity type classification (interview, call, email, status update) maps to BambooHR note categories. Timestamps and user attribution migrate as metadata on the note. We extract all available activity history and attach it to the corresponding Employee record based on the candidate-to-employee mapping.

BrightMove User accounts representing recruiters and hiring managers map to BambooHR Employee records by email address. We resolve each BrightMove user referenced on Candidate, Job, or Placement records and match by email against the BambooHR Employee table. Any BrightMove user without a matching BambooHR Employee goes to a reconciliation queue for the customer's admin to provision before record import completes.

BrightMove tags on Candidates and Jobs are extracted and applied as labels in BambooHR. We preserve the original BrightMove tag names and attach them to the corresponding Employee or Job record. The customer chooses whether tags migrate as BambooHR Topics (for cross-object classification) or as custom label fields during scoping.

BrightMove's back office module handles staffing billing, timesheets, and AR/AP automation. BambooHR does not have a staffing-billing equivalent. We scope this as a selective export during discovery: if the customer needs historical invoicing or timesheet data, we extract it as a CSV and deliver it for manual import or external storage. Back office data does not migrate into BambooHR as a native module because no equivalent object model exists.