Migrate from Recright to Recruit CRM & ATS

Recright Candidate records (name, email, application date, status, and metadata) map directly to Recruit CRM Candidate records. We extract all standard candidate fields 1:1 and map them to Recruit CRM's Candidate object, preserving the original application date and source attribution. Custom candidate properties (if configured in Recright) migrate as Recruit CRM custom fields, with data type mapping confirmed during scoping. Email address serves as the primary dedupe key during import.

Recright Positions define the job opening and hold associated interview templates, candidate pools, and publication settings. We map Positions to Recruit CRM Job records, preserving job title, description, department, location, and opening date. Position-specific interview guides are linked to the corresponding Job as an assessment template during migration. If a Recright Position has multiple active candidates, all are associated with the migrated Job record.

Recright's core object: a Candidate's video response to a structured Interview Question. We export interview metadata including question text, response duration, completion timestamp, and watch count. The video blob itself cannot be downloaded via API; we flag this in scoping, coordinate a separate secure file transfer (SFTP, encrypted drive, or Recright-assisted download), and determine whether Recruit CRM supports video file attachments on candidate records. If native video attachment is unsupported, we store a secure link reference in a custom field.

Recright's Prepare module lets teams build structured interview guides with ranked questions, time limits, and scoring rubrics. We map these to Recruit CRM Assessment Templates or Custom Objects, preserving question text, intended ranking order, and scoring rubric weights. Where Recruit CRM's template structure does not support the full ranking or weighting model from Recright, we flatten the guide into a question bank with a custom field indicating the original order and weight, and we document the remapping in the migration validation report.

Team members assign numerical or qualitative scores to candidate responses within Recright's assessment interface. We extract scores per question and per reviewer, mapping them to Recruit CRM custom score fields on the Candidate record. The reviewer attribution (which team member scored) migrates as a text or reference field. If the scoring scale in Recright does not map to a standard numeric range in Recruit CRM, we normalize values and document the transformation in the mapping spec.

Interview Questions in Recright are tied to specific Interview Guides and include text prompts, time limits, and recording settings. We export these as structured fields and map to equivalent question or text block fields within the Recruit CRM Assessment Template or as custom fields on the Candidate record. The time limit and recording-setting metadata migrate as custom fields with integer or boolean values respectively.

Recright supports multi-user teams with role-based access per Position. We extract team member names, email addresses, and role assignments, then map them to Recruit CRM User records by email match. Recright's per-Position role scoping does not have a direct Recruit CRM equivalent, so we assign the closest User role (Admin, Recruiter, or Standard User) and document the original permission matrix for the customer's admin to rebuild in Recruit CRM's role and access settings.

If customers have added custom fields to candidate records in Recright, we handle these as custom properties during migration. We map field names and data types to Recruit CRM's custom field schema, matching text fields to text, numeric values to number, dates to date, and multi-select values to multi-select picklist where supported. Field-level mapping is confirmed during scoping, and any Recright custom property without a Recruit CRM equivalent is documented as a candidate note with a tag indicating the original source field name.

The original application submission timestamp from Recright migrates as a custom date field on the Recruit CRM Candidate record, preserving historical application timing for reporting and audit purposes. We use this field for pipeline velocity reporting rather than the Recruit CRM record creation date.

Recright candidate statuses (Applied, In Review, Shortlisted, Rejected, Offer, Hired) map to the equivalent Recruit CRM pipeline stage. We extract the full status history per candidate and apply the most recent status as the initial pipeline stage in Recruit CRM, with earlier statuses recorded as a custom note or activity log for audit completeness.