Migrate from BrightMove to Recruit CRM & ATS

BrightMove Candidates map directly to Recruit CRM Candidates. We extract the full candidate record including resume content, contact information, status history, and custom fields. Custom field types (text, dropdown, date, checkbox) migrate with type preservation. Dropdown fields require value mapping where the BrightMove option set differs from Recruit CRM's existing picklist. Resume files are extracted separately, validated for integrity, and attached to the candidate record post-import using Recruit CRM's document attachment API.

BrightMove Job Orders map to Recruit CRM Jobs. The job title, description, requirements, department, and client association transfer directly. Pipeline stages require mapping because BrightMove allows tenant-specific custom stages while Recruit CRM uses standard stage names at the job level with customization available per role. We extract BrightMove's complete stage taxonomy during discovery and map each to the Recruit CRM equivalent before any job data moves.

BrightMove Placements map to Recruit CRM Placements. Each placement records the hired candidate, start date, compensation details, and client association. We preserve the linkage to the originating job order by resolving the job reference during migration. If BrightMove stores placement status changes or placement-specific notes, these migrate as placement activity records in Recruit CRM.

BrightMove Client Contacts map to Recruit CRM Contacts. The contact name, email, phone, company, and role transfer directly. Custom fields on contacts migrate with type preservation and value mapping for dropdown fields. We determine whether each contact in BrightMove represents a client contact or a candidate contact by examining the contact type field, and route accordingly to Recruit CRM's contact model.

BrightMove activity logs and notes attached to candidates and jobs map to Recruit CRM's activity timeline. Activity types vary by BrightMove tenant configuration; we extract all available activity types and map them to Recruit CRM's activity categories (call, email, meeting, note). Historical timestamps are preserved to maintain the candidate's activity timeline in chronological order. Activity notes migrate as text content attached to the corresponding activity record.

Resume files and attached documents stored per BrightMove candidate are extracted during migration, validated for file integrity, and reattached to the corresponding candidate record in Recruit CRM. We handle common resume formats (PDF, DOC, DOCX) and preserve the original filename. Document metadata (upload date, file type, size) migrates as record attributes in Recruit CRM's attachment model.

BrightMove custom fields on candidates (text, dropdown, date, checkbox types) require pre-migration configuration in Recruit CRM. We create matching custom field definitions in Recruit CRM before any candidate data loads, using the same field label and data type. Dropdown fields require value set alignment; any BrightMove option values without a Recruit CRM equivalent are flagged for the customer to resolve before migration completes.

BrightMove custom fields on job orders migrate to Recruit CRM job custom fields. We extract the full custom field taxonomy during discovery, create matching definitions in Recruit CRM, and map values during job import. Job-level custom fields that reference candidate fields or other jobs require relationship validation during migration.

BrightMove user accounts representing recruiters and hiring managers map to Recruit CRM users. We resolve each BrightMove user by email match against the destination Recruit CRM user table. Team assignments and role permissions migrate where Recruit CRM's permission model supports equivalent role definitions. Users without a matching Recruit CRM account go to a reconciliation queue for the customer's admin to provision before migration resumes.

BrightMove tags on candidates and jobs provide categorization that transfers to Recruit CRM's tag model. We extract all distinct tag values from BrightMove candidates and jobs, create matching tags in Recruit CRM, and apply them during candidate and job import. Tag naming conventions differ between systems; we flag any semantic mismatches for the customer to review.