Migrate from RecruitBPM to Recruit CRM & ATS

RecruitBPM Candidate records map directly to Recruit CRM Candidate records. We carry forward contact details, resume data, skills, employment history, source attribution, and status. Custom fields on Candidate are extracted during scoping and mapped to Recruit CRM custom fields, with any unmappable fields flagged and documented. Candidate owner assignment (recruiter) migrates via email lookup against Recruit CRM user records.

RecruitBPM Client records (organizations or companies that the agency places talent into) map to Recruit CRM Company records. We carry forward company name, industry, location, contact details, relationship notes, and client-specific custom fields. Client-to-Company mapping is a 1:1 transform with no dependency on other objects.

RecruitBPM Job Orders map to Recruit CRM Jobs. Each Job Order carries client linkage, requirements, compensation, location, and pipeline stage. We preserve the stage progression and create the corresponding pipeline in Recruit CRM before Job import begins. Closed and active Job Orders both migrate; historical Job Orders are preserved as read-only or closed records depending on Recruit CRM's supported status states.

RecruitBPM Placement records (confirmed hires) map to Recruit CRM Placement records. We carry forward start date, compensation, placement fee, and links to the Candidate and Client. Placement records serve as historical billing and performance reference, so no records are excluded from migration scope unless the customer explicitly requests archiving.

RecruitBPM Talent Pools (segregated candidate collections by skill, location, or certification) map to Recruit CRM Lists or Tags depending on the customer's intended usage. Pool membership and engagement history are preserved as list membership records tied to Candidate IDs. We define the List or Tag strategy during scoping based on how the customer uses pools.

RecruitBPM customizable pipeline stages (which vary by agency configuration) map to Recruit CRM Job Stage values. We extract the full stage definition set during scoping, including stage names, order, and any probability or milestone flags, and configure the corresponding stages in Recruit CRM before Job import.

RecruitBPM activity records (calls, emails, SMS, voicemails, notes) tied to Candidates and Clients map to Recruit CRM Activity records. The activity type taxonomy differs between platforms, so we normalize common types (call, email, SMS) and map proprietary types to the closest Recruit CRM equivalent. Activity timestamp and owner assignment are preserved. Note content migrates as structured activity entries with text preserved.

RecruitBPM interview records (scheduled time, interviewer, format, outcome notes) map to Recruit CRM Interview records or Activity records depending on the destination's current schema. Video interview format flags are preserved where supported. Interview-to-Candidate linkage is maintained via candidate ID lookup at migration time.

RecruitBPM platform users who own records and drive workflows map to Recruit CRM User records. User email, name, and role migrate directly. Owner assignment on individual records is preserved by matching on email. Recruit CRM permission sets and team structures do not exist in RecruitBPM and must be configured manually post-migration; we document the RecruitBPM permission structure as a reference for the customer.

Resume files, contracts, and other attachments stored in RecruitBPM migrate as binary files to Recruit CRM's file storage. We verify file format compatibility and flag any formats that are unsupported at the destination. File-to-record linkage (which attachment belongs to which Candidate or Job) is preserved via the parent record ID mapping.

RecruitBPM supports customizable fields across Candidates, Clients, and Job Orders with schemas that vary by tenant. We extract the complete field definition set during scoping, identify Recruit CRM equivalents (including custom fields where no standard field exists), and create the destination schema before data import. Any custom fields that cannot map cleanly are flagged with the original field name, data type, sample values, and recommended Recruit CRM field action.