Migrate from Recright to Bullhorn ATS & CRM

Recright Candidate records (name, email, application date, status, and custom properties) map directly to Bullhorn Candidate. The Bullhorn Candidate object receives all standard fields including firstName, lastName, email, phone, and status. We resolve the dedupe key by email match and set the Candidate status field to correspond with the Recright application status. Any Recright custom candidate properties migrate to Bullhorn custom fields on the Candidate entity via Admin > Field Mappings, using unused customText, customDate, or customFloat slots.

Recright Positions (defining the job opening with associated interview templates and publication settings) map to Bullhorn Job records. The Recright position title becomes the Job title; description fields map to the Bullhorn description; published status in Recright maps to a Bullhorn job status value. We create Bullhorn Job records before Candidate records so that the Job reference is satisfied at Candidate insert. If the Recright position references multiple interview stages, we create corresponding Bullhorn JobSubmissions or custom fields to preserve pipeline structure.

Recright Pre-recorded Interviews are the core data object: a Candidate's video response to a structured Interview Question. We export interview metadata (question text, response duration, completion timestamp, watch count per question) as structured fields on the Bullhorn Candidate record or as a custom Interview Responses custom object. The video blob itself cannot be downloaded programmatically from Recright; we flag this as a separate manual transfer action and coordinate an SFTP share or encrypted drive delivery. Bullhorn does not natively support video embedding on Candidate records, so video links are stored as Bullhorn Note records with the Recright interview URL as the Note body or as a Document/Attachment upload.

Recright Interview Guides (Prepare module) with ranked questions, time limits, and scoring rubrics do not have a direct Bullhorn equivalent. Bullhorn does not expose a native structured interview template object. We create a Bullhorn Custom Object named Recright_Interview_Guide__c with fields for guide name, question text, intended order, time limit, and scoring rubric. We document the original Recright guide structure in the migration validation report so the customer's Bullhorn admin can rebuild guides as Bullhorn Automation triggers or manual checklist fields per Job if preferred.

Recright Assessment Scores (numerical or qualitative scores assigned by team members per question and per reviewer) map to Bullhorn custom fields on the Candidate record. We create customNumber or customFloat fields for each distinct reviewer-question combination or aggregate the scores into customSummary fields per section. We preserve the reviewer name and timestamp as custom fields or as a JSON blob in a customText long-text field. If the number of unique reviewer-question combinations exceeds available custom fields, we create a child Custom Object (Assessment_Score__c) with lookup to Candidate to handle the one-to-many relationship.

Recright Interview Questions (text prompts, time limits, recording settings, tied to specific Interview Guides) export as structured data that we map to Bullhorn custom fields on the Interview Guide custom object or as question-text entries in a Questions__c child object. We preserve the question order, required time limit per question, and whether the question allows multiple attempts. Bullhorn's lack of a native question bank or rubric object means this structure requires custom object configuration before migration.

Recright team members (name, email, role, and access permissions per position) map to Bullhorn User records by email match. Bullhorn roles and permissions are assigned using Bullhorn's standard permission sets and teampacements. We reconcile any Recright role (Interviewer, Hiring Manager, Admin) to the nearest Bullhorn equivalent. Owners without a matching Bullhorn User are held in a reconciliation queue for the customer's Bullhorn admin to provision before Candidate import resumes.

If the customer has added custom fields to candidate records in Recright, we map these as Bullhorn custom fields on the Candidate entity via Admin > Field Mappings. We match Recright field names and data types (text, number, date, picklist) to Bullhorn customText, customFloat, customDate, or customDropdown fields. Bullhorn has a finite number of custom field slots per entity; we audit available slots during scoping and flag if the customer's Recright custom field count exceeds available Bullhorn slots, in which case we create a child Custom Object to absorb overflow fields.

Recright position publication status (Draft, Published, Closed) maps to Bullhorn Job status (Open, Interview, Offer, etc.). We capture the original Recright status in a custom field original_position_status__c for audit and reporting continuity. If the Recright position has a scheduled publish date, we store that in a Bullhorn custom field and advise the customer's Bullhorn admin to set up a Bullhorn Automation or Flow reminder for activation.

Recright tracks how many times each team member watches a candidate's video response. This watch history has no Bullhorn native equivalent. We store the watch count per reviewer as a customInterview_watch_count__c field or as a JSON list in a long-text custom field on the Candidate record. If granular per-reviewer watch history is required, we create a child Custom Object (Interview_Watch__c) linked to Candidate with fields for reviewer User, interview reference, and watch_count.

Recright captures application metadata including source (referral, job board, direct), application date, and any UTM or tracking parameters. These map to Bullhorn custom fields on the Candidate record. Candidate source maps to a Bullhorn customDropdown field; application date maps to a customDate field. We preserve any original URL or UTM parameters in a customText field for marketing attribution continuity if the customer later runs campaign analytics.

Recright tracks the completion status of each Pre-recorded Interview (Not Started, In Progress, Completed) and records timestamps for each stage transition. We map Recright interview completion status to Bullhorn Candidate status values and store the completion timestamp in customDate fields (interview_started_date__c, interview_completed_date__c). The completed_by_reviewer timestamp maps to Bullhorn customDate fields for audit trail. Bullhorn's Candidate status is a picklist that the customer's admin configures; we coordinate the status value mapping during schema design.