Migrate from BrightMove to Zoho Recruit

BrightMove Candidates map directly to Zoho Recruit Candidates. We extract resume data, contact information, status history, and all custom fields. Zoho Recruit requires a Last Name value on every Candidate import — any BrightMove candidate without a surname is flagged and assigned a placeholder value 'Not Provided' during the transform phase. Email, phone, address, skills, and source fields migrate to equivalent Zoho Candidate fields. Tags from BrightMove become Zoho Recruit Tags applied via the tag association API.

BrightMove Job Orders (title, description, requirements, department, location, status) map to Zoho Recruit Job Openings. The most critical mapping work is the pipeline stage. BrightMove allows organizations to configure custom pipeline stages that vary by tenant — we extract the full stage taxonomy during discovery and map each BrightMove stage to the nearest Zoho Recruit stage equivalent (Open, Phone Screen, Interview, Offer, Hired, Closed) preserving the original order. Any custom stages that have no Zoho equivalent are created as custom stage values in Zoho Recruit before migration.

BrightMove Placements record a hired candidate with start date, compensation details, and client association. Zoho Recruit does not have a standalone Placement object — the placement relationship is expressed by associating the Candidate record to the Job Opening with a status of 'Hired' and recording the start date and compensation in custom fields on the Candidate or Job Opening. We extract placement start_date, compensation_package, and client_name from BrightMove and create the Candidate-Job Opening association in Zoho Recruit with those values stored as custom fields. Note: BrightMove placement billing data (invoicing, AR/AP) lives in the BrightMove back office module and does not map to any Zoho Recruit ATS object; it belongs in Zoho Books if accounting continuity is required, a scope addressed separately.

BrightMove Contacts are client-facing recruiter or hiring-manager contacts associated with client companies. Zoho Recruit separates client company records (Clients module) from individual Contact records (Contacts module, often used as a sub-module of Clients). We map BrightMove Contact name, email, phone, and role to the Zoho Recruit Contact fields, and map the associated client company to a Zoho Recruit Client record. Custom fields on BrightMove Contacts are mapped to Zoho custom fields on the Contact or Client module based on field type.

BrightMove stores activity logs and notes against candidates and job orders. Activity types vary by tenant configuration. We extract all available activities — calls, interviews, status updates, internal notes — and map them to Zoho Recruit Activity records. Zoho Recruit's activity stream supports date, description, activity type, and linked candidate or job opening. We preserve activity timestamps and assign the activity to the migrated candidate or job opening using Zoho's lookup relationship. Large note volumes use batch inserts via the Zoho Recruit API.

Resume files and attached documents stored per BrightMove candidate are extracted during migration, validated for file integrity, and uploaded as Zoho Recruit Candidate attachments. We preserve the original filename and file type. If a candidate's resume was parsed into structured fields in BrightMove (name, email, phone extracted from the resume), those parsed fields map to the corresponding Zoho Recruit Candidate fields separately from the attachment.

BrightMove allows custom fields on Candidates using types including text, dropdown, date, and checkbox. Zoho Recruit supports equivalent custom field types in all paid editions. We map text fields to Zoho Single Line or Multi Line fields, date fields to Zoho Date fields, checkboxes to Zoho Checkbox fields, and dropdowns to Zoho Picklist fields. For dropdown fields, we extract the BrightMove picklist option values and create matching Zoho Picklist values during the schema pre-creation phase. The Standard Edition of Zoho Recruit does not support Lookup fields — if BrightMove custom fields include lookup relationships, the destination must be on Standard edition or above.

BrightMove Job Orders support custom fields to capture department-specific requirements, compensation ranges, or clearance levels. These map to Zoho Recruit Job Opening custom fields using the same type-mapping logic as candidate custom fields. Department and classification custom fields on BrightMove job orders often require value normalization before mapping to Zoho picklists.

BrightMove User accounts (recruiters and hiring managers) are mapped to Zoho Recruit User records. We resolve by email address. Users who already have an active Zoho Recruit account cannot be imported — Zoho requires closing the separate account first per the Zoho Recruit Data Migration documentation (help.zoho.com/portal/en/kb/recruit/essentials/data-management/data-migration). We flag any BrightMove user with a matching existing Zoho Recruit account and escalate to the customer's admin for resolution before the migration phase begins.

Tags applied to BrightMove candidates and job orders are extracted and applied as Zoho Recruit Tags. Tag naming conventions may differ between systems, so we map the BrightMove tag name to the Zoho tag name using an exact-match lookup table built during discovery. Tags used for candidate segmentation or job order categorization carry over for use in Zoho Recruit's filtering and reporting.

BrightMove's back office module ($499+/mo) stores invoicing, AR/AP, and payroll data for staffing firms. Zoho Recruit is an ATS, not an accounting platform — none of these objects have a Zoho Recruit equivalent. If the customer needs accounting continuity, we scope a separate data extraction of BrightMove back office records into CSV for import into Zoho Books. This is a distinct engagement from the ATS migration and is priced separately. We disclose this boundary clearly during scoping to prevent scope creep.

BrightMove's built-in job board distribution (Indeed, ZipRecruiter, and other integrations) is a platform configuration, not a data record. These integrations do not migrate. We deliver a written job board reconnection checklist that identifies every BrightMove-connected job board account, the credentials needed, and the Zoho Recruit job board integration setup steps for each. The customer's admin executes the reconnection post-migration; we do not configure third-party job board accounts on behalf of the customer.