Migrate from Rival to Recruit CRM & ATS

Rival Employee records map to Recruit CRM Candidate records. Core fields (name, email, phone, title, department, hire date) migrate directly. We resolve the mapping from Rival's employee field schema to Recruit CRM's candidate object fields during discovery by coordinating with the Rival administrator to extract the live field list. Any Rival custom fields on employee records are mapped individually and written to Recruit CRM's custom candidate fields.

Rival's department and reporting-line relationships migrate as Recruit CRM organizational units. We extract the node graph (manager IDs, department IDs, hierarchy depth) and re-attach candidates to the correct department assignments in Recruit CRM. If Recruit CRM does not support nested hierarchies natively, we denormalize the reporting chain into flat department assignments and preserve the manager relationship as a custom field on the candidate record.

Rival location data (office addresses, remote designations) stored as flat fields on employee records migrates to Recruit CRM's candidate address and location fields. Remote or work-from-home designations migrate as a custom picklist value to preserve the original classification.

Rival job title and department assignments on employee records map to Recruit CRM Job Orders and candidate skill tags. We extract unique job title strings from Rival employee records, deduplicate them, and create Recruit CRM Job Order records for each distinct role. Candidate records receive skill tags aligned to their Rival job title and department for searchability in the destination system.

Rival salary and compensation records with effective dates migrate as structured custom fields on the corresponding Recruit CRM Candidate record. We preserve the effective_date sequence by writing the most recent compensation row to the primary compensation field and storing historical rows as a JSON blob in a custom notes field. Compensation carrier IDs and plan-specific identifiers may not map 1:1 and are flagged for manual verification post-migration.

Rival PTO balance snapshots migrate as opening balance values in Recruit CRM custom fields on the candidate record. Ongoing accruals are not carried forward; the customer's Recruit CRM administrator sets accrual rates post-migration. We flag this as a manual post-migration step during scoping.

Rival benefits enrollment data (plan names, coverage tiers, enrollment dates) migrates as structured custom fields per candidate in Recruit CRM. Carrier-specific enrollment IDs are preserved in a custom field but flagged as non-guaranteed 1:1 mappings because benefit carrier identifiers vary across platforms.

Rival user accounts (admin, manager, employee role types) map to Recruit CRM user accounts. Role names and permission sets differ across platforms and require explicit mapping during scoping. We extract distinct user records from Rival, match by email to Recruit CRM users, and flag any roles without a direct Recruit CRM equivalent for the administrator to configure post-migration.

Rival employee documents (offer letters, contracts, ID scans) are stored as binary blobs with no documented export API. We cannot guarantee document fidelity in an automated migration. We flag document-heavy migrations during scoping, extract document filenames and associated employee IDs, and provide a mapping table for manual re-upload to Recruit CRM candidate records post-migration. This is a manual step that adds to the project timeline.

Rival custom fields are customer-defined and discovered only through coordinated access with the Rival administrator. We extract the live schema during scoping, build a per-migration field-mapping table, then pre-create equivalent custom fields in Recruit CRM before executing any candidate record writes. This discovery step adds one to two weeks to the project timeline and is required because Rival has no published schema registry.