Migrate from Rival Recruit to Recruit CRM & ATS

Rival Recruit Candidate records map to Recruit CRM Candidate records with full contact information, work history, source attribution, and stage status. The candidate_id, email address, and phone number serve as the dedupe key during import. Stage status from Rival maps to the corresponding Recruit CRM pipeline stage value. Resume attachments are extracted separately from the record metadata and reattached as candidate documents in Recruit CRM.

Rival Recruit Position records (job requisitions with title, department, location, hiring manager, and open/closed status) map to Recruit CRM Job records. The position hierarchy and any configured approval workflow status migrate as job metadata. Active positions (open and in-progress) are flagged for priority cutover sequencing.

Rival Recruit pipeline stage values map to Recruit CRM pipeline stage values based on a configuration table generated during schema discovery. We preserve the stage probability and stage name from Rival if they exist as custom fields, and configure the Recruit CRM Master Pipeline with corresponding stage values before candidate records import.

Rival Recruit Employee records (personal info, job title, department, manager, start date, employment status, effective-dated employment changes) map to Recruit CRM Contact records. Effective-dated history is preserved as notes or custom date fields depending on the customer's record cleanup preferences. The Employee record type is distinct from Candidate in Rival and maps to a separate Contact classification in Recruit CRM.

Rival Recruit Onboarding Records are tied to new hires via the Onboard Web Service Guide (v2020.2.1) which documents a subset of onboarding endpoints. Active onboarding journeys are mapped to the candidate record in Recruit CRM under the onboarding section. We flag any onboarding records using undocumented endpoints and handle them via bulk export where API coverage is insufficient. Onboarding workflow step definitions are not migrated as automation code; they are delivered as a written blueprint for the customer's admin to rebuild in Recruit CRM's pipeline automation builder.

Rival Recruit documents (resumes, cover letters, offer letters, compliance documents) stored against candidate and employee records are extracted as binary files separately from metadata. We maintain a document-to-record lookup table and reattach each file to the corresponding candidate or job record in Recruit CRM at import time. File type, upload date, and associated custom fields are preserved as document metadata.

Rival Recruit interview events (date, time, interviewer, candidate, position) are mapped to Recruit CRM Event records linked to the candidate and job. Interview scorecards configured in Rival Recruit do not have a native Recruit CRM equivalent; scorecard data is extracted as a structured note and attached to the candidate record for admin reference.

Rival Recruit custom fields on Candidate objects are customer-specific and discovered via API schema audit before mapping. We pre-create matching custom fields in Recruit CRM before candidate records import, preserving field types (text, number, date, picklist, checkbox) and any conditional visibility rules. Custom field data migrates into the corresponding Recruit CRM custom fields on import.

Rival Recruit custom fields on Position objects are enumerated during pre-migration schema discovery and matched to custom fields created in Recruit CRM on the Job record. We configure Recruit CRM custom fields to match the source field type and any picklist values before position records import. Empty or inactive custom fields in Rival Recruit are excluded from the mapping.

Rival Recruit users (name, email, role, team assignment) map to Recruit CRM users. We resolve users by email match. Any Rival Recruit user without a matching Recruit CRM user is placed in a reconciliation queue for the customer to provision before record import resumes, because Owner assignment on candidate and job records requires a resolved user reference.

Tags applied to candidates in Rival Recruit for segmentation and sourcing campaigns are extracted as a flat lookup table (candidate_id to tag value). Tags are re-applied as native Recruit CRM tags on the candidate record at import time. If the customer uses a large number of tags (over 200 distinct values), we discuss consolidation options during scoping to avoid tag proliferation in Recruit CRM.