Migrate from BrightMove to Crelate

BrightMove Candidate records map to Crelate Person. We preserve name fields, contact information (email, phone, address), work history, skills, and source attribution. Resume files are extracted as binary attachments and re-linked to the corresponding Person record in Crelate's Files section. Status history migrates as Crelate Activity entries if the history depth is within scope.

BrightMove Job Order records map to Crelate Job Order. The job title, description, requirements, department, and location transfer directly. BrightMove's configurable pipeline stages require the most attention: we extract the full stage taxonomy during discovery, configure matching stages in Crelate's stage system before migration, and preserve stage order and any stage-specific sub-statuses in a custom field on each Job Order record.

BrightMove Placement records map directly to Crelate Placement. We preserve start date, compensation details, placement status, and the linkage to the originating Job Order and placed Candidate. If the BrightMove placement references a Client Contact, we ensure that contact exists in Crelate before placement records load.

BrightMove activity logs attached to Candidates and Jobs map to Crelate Activity records. Calls become Tasks with TaskSubtype=Call; scheduled interactions become Events with start and end times; notes become Activity entries with full text preserved. Activity type taxonomy varies by BrightMove tenant configuration, so we extract the full activity type list during discovery and map each type to the nearest Crelate Activity subtype.

Resume files and attachments stored per Candidate in BrightMove are extracted during migration, file integrity is validated, and files are loaded into Crelate's Files section linked to the corresponding Person record. We preserve original file names and MIME types. File metadata beyond name and type (such as upload timestamp from BrightMove) migrates to a custom field on the Crelate File record.

BrightMove custom fields exist on Candidates, Jobs, and Placements. Crelate custom fields are restricted to Person (Contact), Company, and Opportunity. We audit every BrightMove custom field during discovery and categorize each as: (a) directly migratable to a Crelate custom field on Person or Company, (b) remapped to Crelate notes or tags, or (c) flagged for post-migration manual recreation on Job Orders if no equivalent exists. Dropdown (picklist) fields require value mapping where the option set differs between systems.

BrightMove recruiter and hiring manager user accounts map to Crelate Users. We reconcile by email address. Any BrightMove User without a matching Crelate User goes to a reconciliation queue, and the customer's admin provisions the missing account before record migration resumes. Team assignments and role metadata migrate as Crelate Team records where the destination plan supports team-based permissions.

BrightMove tags on Candidates and Jobs map to Crelate Labels on the corresponding Person or Job Order. Tag naming conventions differ between systems, so we preserve the original BrightMove tag name and apply it as a Crelate Label, noting any naming differences for the customer's admin to normalize post-migration if desired.

BrightMove Client Contacts map to Crelate Person records when they represent individual contacts, or to Crelate Company records when they represent organizations. We use the contact's company affiliation and role fields to determine the appropriate Crelate entity type, creating a Company record first when the contact is associated with an organization, then linking the Person to that Company.

BrightMove's back office module ($499/month add-on) stores invoicing and timesheet data in a separate schema with its own structure. Crelate has no equivalent back office module. We scope whether this data must migrate. If yes, we design a Crelate custom object to receive the relevant fields (invoice number, amount, date, status, client reference, candidate reference, hours) and preserve the linkage to the related Placement. If no, we deliver a structured CSV export of back office data for the customer's records.

BrightMove's tenant-specific pipeline stages are not standardized and must be extracted in full during discovery. We map each BrightMove stage to a Crelate Stage entry, preserving stage order, probability percentage, and any stage-specific statuses. Crelate stage configuration happens before any Job Order data loads, ensuring the stage taxonomy is complete and validated before migration begins.

BrightMove placement records include compensation split information (recruiter fee percentage, client fee, candidate rate) that migrates to custom fields on the Crelate Placement record. We verify field type compatibility: percentage fields migrate as numeric fields, and monetary fields migrate as currency fields. Fee split rules tied to BrightMove back office billing are scoped with the invoice data migration decision above.