Migrate from Recright to Crelate

Recright Positions define the job opening and hold associated interview templates, candidate pools, and publication settings. We map Position Name to Crelate Job Name, Position status to Job Status, and publication dates to Crelate date fields. Position-level interview templates are handled separately (see Interview Guide mapping). If the Recright Position has an assigned team member, we map that as the Job Owner in Crelate by resolving the team member email against Crelate User records. Positions without an active candidate pool are migrated as draft Jobs for the customer to review before publishing.

Recright Candidate records include full name, email address, application date, status, and any metadata fields. We extract all candidate fields 1:1 and map them to Crelate Person/Contact records. The candidate's application timestamp from Recright is stored as a custom date field in Crelate since the native Created Date field reflects the Crelate import time, not the original application date. Candidate status (applied, screened, rejected, hired) maps to a custom picklist field that we create during schema setup, preserving the original Recright status labels for audit continuity.

Each Candidate's structured video response to an interview question in Recright carries metadata: question text, response duration, completion timestamp, and reviewer watch count. We map these to Crelate Activity records (Tasks) linked to the Person record, with question text stored in the Task Body field and duration stored in a custom field. The video file itself cannot be downloaded from Recright via API — we create a custom field containing the Recright recording URL or a placeholder noting the file is pending secure transfer. Crelate does not natively support video attachments on Person records without a third-party integration; we flag this limitation in the migration validation report and advise the customer to configure a video hosting integration before cutover.

Recright's Prepare module stores structured interview guides with ranked questions, time limits per question, and weighted scoring rubrics. Crelate does not have a native interview guide template object, so we create a Custom Object in Crelate (API name: Interview_Guide__c) with fields for Guide Name, Question Text, Question Order, Time Limit (seconds), Maximum Score, and Scoring Weight. Each guide becomes one Custom Object record; each question within the guide becomes a child record linked via lookup. We document the intended question order and weighting in a JSON metadata file delivered alongside the migration, so the customer's admin can rebuild the ordered scoring workflow in Crelate's custom form builder if desired.

Team members assign numerical or qualitative scores to candidate responses within Recright's assessment interface. We extract scores per question and per reviewer, mapping to custom numeric fields on the Person record in Crelate (score_reviewer_1__c, score_reviewer_2__c, etc.) and cross-referencing against the Interview Guide Custom Object to link each score to its parent question. Total aggregate scores and individual reviewer ratings are stored as separate fields for audit. Qualitative reviewer comments are stored as Note records linked to the Person. Crelate's field mapping feature allows these custom scores to map to Contact fields directly from activity forms, but during migration we write them as static custom fields to preserve the historical record.

Recright Interview Questions are tied to specific Interview Guides and include text prompts, time limits, and recording settings. We export each question as a child record of the Interview Guide Custom Object, preserving the question text as Question_Text__c, the time limit in seconds as Time_Limit__c, and any recording instructions as Instructions__c. The question order is preserved via a Position field (Integer) that maintains the original sequence. Questions with conditional branching (asked only if a previous answer met a threshold) are flagged in the notes field as branching_not_supported__c and are documented for the customer admin to rebuild in Crelate's conditional form logic.

Recright supports multi-user teams with role-based access per Position. We extract team member names, email addresses, and role labels from Recright. Email addresses are used as the lookup key in Crelate — we match against the Crelate User table by email. Team members without matching Crelate Users go to a reconciliation queue for the customer's admin to provision before record import. Recright role labels (Admin, Interviewer, Viewer) map to Crelate User Roles that the admin configures during Crelate setup. Owner assignment on Candidate records resolves to the matched Crelate User.

If the customer has added custom fields to Candidate records in Recright (beyond the standard name, email, and status fields), we handle these as custom properties during migration. We create equivalent custom fields in Crelate's Contact schema using the same field label, map the data type (text, number, date, picklist) to the nearest Crelate field type, and migrate values directly. Multi-select picklist values from Recright map to Crelate multi-select picklist fields. Date fields preserve the original timestamp. We flag any Recright custom field type that has no direct Crelate equivalent (for example, a file attachment field) in the migration validation report and document the recommended replacement approach.

Recright stores application metadata including the job applied to, application source (referral, job board, direct), and UTM or attribution data if configured. We map the job applied to to the Crelate Job lookup on the Person record. Application source is stored as a custom picklist field on the Contact. UTM and attribution data is stored as custom text fields for reporting continuity. Tasks are created in Crelate to represent application submissions, with the Task Subject set to Application Received and the Activity Date set to the original application timestamp.

If Recright tracks status changes over time (applied to screened to rejected, for example), we preserve this as a series of Task records in Crelate linked to the Person. Each status change becomes a Task with Subject containing the old and new status and Activity Date set to the timestamp of the change. This gives the customer's recruiting team a visible status history timeline in Crelate without relying on Recright's proprietary history view. If Recright does not expose status change timestamps in the CSV export, we flag this gap and advise the customer that only the current status will migrate.

Recright Positions may have job board distribution settings or internal posting configurations. We map these to Crelate's Job Portal settings and job board integration fields (Indeed, LinkedIn, Monster, Google for Jobs) which are available from the Business tier. If the customer used Recright's integration with a specific job board, we document the integration name in the migration notes and advise the customer to reconfigure the equivalent integration in Crelate during the post-migration setup phase.

Recright supports tagging candidates and positions with custom labels for segmentation. We map these labels to Crelate Tags, which are supported for Person, Job, and other record types via the Crelate API. Tags are stored in the tags object with keys corresponding to tag category names. If a Recright tag has no equivalent category in Crelate, we create the category on first import. Tags used for candidate segmentation or pipeline grouping migrate as-is for immediate filtering capability.