Migrate from Rival Recruit to Crelate

Rival Recruit Candidate records map 1:1 to Crelate Person records. Standard fields (name, email, phone, address, source, status, stage) migrate directly. Pipeline stage history from Rival's candidate_activity log is preserved as a Crelate Activity note with timestamps for audit continuity. Rival's source attribution field maps to Crelate Tags or a custom Source field depending on the customer's tag strategy chosen during scoping. Custom fields on Candidate are discovered via API before migration and mapped explicitly—no assumptions are made because every Rival customer has a different custom field configuration.

Rival Recruit Position records map to Crelate Job records. Fields including job title, department, hiring manager (mapped to Owner), location, open/closed status, and posting date migrate directly. Rival's pipeline stage names on Position are preserved as Crelate Pipeline stage labels via the Crelate field mapping interface. Positions with a linked hiring manager require that the hiring manager email resolves to an existing Crelate User or is placed in a User reconciliation queue for admin provisioning before Position import.

Rival Recruit stores resumes, cover letters, offer letters, and compliance documents as binary attachments against Candidate and Employee records. We extract the binary file separately from the metadata (filename, MIME type, upload timestamp) and remap each attachment to the corresponding Crelate record by matching the parent record ID during migration. Files are uploaded to Crelate's document attachment endpoints and linked via the Crelate attachment relationship. Any documents exceeding Crelate's attachment size limits are flagged for manual upload with a reference list delivered post-migration.

Rival Recruit Employee records (personal info, job title, department, manager, start date, employment status) map to Crelate Employee records if the destination workspace has the Employee module enabled, or to Person records tagged as Employees if not. Effective-dated employment changes are preserved as historical entries in Crelate's activity log to maintain the record's change history. Manager relationships in Rival are resolved by email lookup to the destination User record.

Rival platform Users (name, email, role, team assignment) map to Crelate Users. We match by email address and resolve Role and Team from Rival's permission set. Any Rival User without a matching Crelate User account is placed in a provisioning queue; the customer's admin creates the corresponding Crelate accounts before the User phase of migration so that Owner assignment on Candidate and Position records is satisfied at import time.

Rival Recruit tags applied to Candidates for segmentation and sourcing campaigns are extracted as a flat lookup table keyed by Candidate ID. We reapply tags as native Crelate Tags on the migrated Person records. If the customer uses a high volume of tags with overlapping naming conventions, we deduplicate during transform and deliver a tag consolidation map alongside the migration report.

Custom fields on Rival Recruit Candidate records are discovered via the API schema audit before migration. Each discovered custom field is mapped to a Crelate custom field of matching type (text, number, date, picklist, checkbox). Crelate's field mapping UI supports mapping form responses and custom fields to Person properties, tags, or tag categories. We generate the complete custom field mapping table as part of the migration deliverable and configure Crelate custom fields in the destination workspace before data import begins.

Custom fields on Rival Recruit Position records are discovered via API schema audit and mapped to Crelate Job custom fields. Field types are matched (string to text, integer to number, date to date, picklist to picklist). Job-level custom fields in Crelate are created before Position migration so that incoming records are accepted without validation errors.

Rival Recruit Interview events (date, time, interviewer, candidate, position) are extracted and mapped to Crelate Activity records. The interviewer assignment resolves by email against the Crelate User table. Interview scorecards and rating fields from Rival are preserved as Crelate Activity notes or custom Activity fields if configured. Interview invitations and calendar links do not migrate; the customer's admin rebuilds the interview scheduling workflow in Crelate.

Rival Workflow onboarding journeys (steps, assignees, conditions, new hire status) are exported as a written JSON blueprint inventory. Crelate does not include a native onboarding journey builder in its ATS/CRM module. Active onboarding journeys with pending start dates are flagged as high-priority records for the customer's admin to re-create manually in their chosen onboarding tool or to re-enter directly in Crelate's activity log. This is a configuration gap, not a data loss—we document what exists so nothing is forgotten.

Rival Workflow definitions (onboarding, offboarding, internal mobility journeys) are exported as JSON blueprints with step owners, conditions, and automation triggers documented. Crelate's automation triggers support pipeline-based task creation and email sequencing but are structurally different from Rival's journey builder. We deliver a written workflow inventory with each step, assignee, and condition mapped to a recommended Crelate automation equivalent. The customer's admin rebuilds these in Crelate's workflow editor post-migration.

Rival Recruit branded career site content, job board distribution settings, employee testimonial pages, and job posting templates are configurable assets rather than transactional records. We export the site configuration as a structured JSON export and a written page-by-page content inventory. Crelate's Careers Page editor is a separate tool with its own content management model; the customer's marketing or recruiting team rebuilds the career site using the exported content inventory as a content source guide. This is not data that can be programmatically mapped between platforms.