Migrate from Rival to Crelate

Rival Employee records map to Crelate Candidate profiles. Core fields (name, email, phone, job title, department, hire date) migrate directly. The employee's current job title in Rival becomes the Candidate's target title; department becomes a custom Candidate field or tag. We resolve the mapping against Crelate's Candidate object schema during discovery.

Rival's department and reporting-line relationships are stored as a related node graph. Crelate does not have a native org hierarchy object; departments and reporting relationships must be decomposed into flat structures. Department names migrate as tags on Candidate records; reporting relationships (manager-employee) migrate as a custom Manager field pointing to the manager's Candidate record or as a tag. This decomposition adds a discovery step to understand the full graph before flattening.

Rival stores compensation with effective dates, meaning one Employee record can have multiple compensation rows over time. Crelate Candidate records store compensation as current-state fields. We extract the most recent compensation record (by effective_date descending) and write it as the Candidate's salary field. Full historical compensation rows are mapped to a custom multi-line text or notes field so the effective-date sequence is preserved for audit rather than lost entirely.

Rival PTO balances are current-state values with no direct Crelate ATS equivalent. Crelate is a recruiting platform, not an HRMS. PTO balance data cannot be meaningfully represented in Crelate's candidate model. We extract the balance snapshot at migration time and deliver it as a structured CSV for the customer's admin to either ignore or import into a separate HR system post-migration.

Rival benefits data (plan names, coverage tiers, enrollment dates) is mapped as structured records per Employee to Crelate Candidate custom fields. Plan names and tier information migrate as text fields on the Candidate. Carrier-specific IDs are flagged as non-mappable because Crelate does not have a native benefits carrier integration and these IDs are destination-system-specific.

Job titles and department assignments are standard flat fields in Rival and migrate directly to Crelate Candidate fields. Department names are written as tags on the Candidate to support Crelate's filtering and reporting by department. Job title migrates as the Candidate's primary professional title field.

Location data (office addresses, remote designations) is a flat field on Rival Employee records. It migrates directly to Crelate Candidate's address and location fields with minimal transformation. Remote or hybrid designations migrate as a custom Candidate field or tag.

Rival custom fields are customer-defined with no public schema registry. We discover the live schema by coordinating with the customer's Rival administrator during scoping, then build a per-migration field-mapping table before executing any writes. Each discovered custom field is typed (text, date, number, picklist) and mapped to an equivalent Crelate custom Candidate field. This discovery step adds time to the project timeline and is not required when migrating from platforms with published schemas.

Rival's user and role model (admin, manager, employee role types) maps to Crelate Users by email match. Role names differ across platforms and require explicit mapping during scoping. Crelate's permission model is role-based with configurable access levels. We flag any Rival roles without a direct Crelate equivalent for the customer's admin to resolve post-migration.

Employee documents (offer letters, contracts, ID scans) are stored as binary blobs in Rival's document management module with no documented export endpoint. We cannot guarantee document fidelity in a self-serve migration and do not include binary files in the migration scope. We deliver a document inventory CSV mapping filenames and associated Employee IDs to facilitate manual re-upload in Crelate post-migration.

If Rival contains active job orders from its recruiting module, these map to Crelate Job Order records. Job title, description, requirements, status, and assigned recruiter migrate directly. We discover whether the Rival instance contains active job orders during scoping since not all Rival deployments use the recruiting module.

Candidate submissions and application history from Rival's recruiting module map to Crelate Submission or Application records linked to the corresponding Candidate and Job Order. Submission status, submission date, and source information migrate. Any submission notes or feedback fields map to Crelate activity or notes on the Submission record.