Migrate from Recright to Zoho Recruit

Recright Candidate records (name, email, application date, status, metadata) map directly to Zoho Recruit Candidate. Recright's First Name and Last Name split is preserved; Zoho Recruit requires Last Name as a mandatory field, so candidates without a Last Name are flagged during scoping and set to 'Not Provided' or a customer-specified placeholder. Custom Candidate Properties migrate to Zoho Recruit custom fields (created during schema setup), mapping data types (text, date, picklist) to their Zoho equivalents.

Recright Positions define the job opening and hold associated interview templates, candidate pools, and publication settings. These map to Zoho Recruit Job Opening records. Position status (active, paused, closed) migrates to Zoho Recruit Opening Status. Active position count limits vary by Zoho Recruit tier (1 for Free, 10 per recruiter for Standard, 20 per recruiter for Enterprise), so we verify the customer's target tier during scoping.

Recright's Prepare module stores structured interview guides with ranked questions, time limits, and scoring rubrics. Zoho Recruit does not have a native structured guide template object. We map these to a Zoho Recruit Custom Module (named 'Interview Guides') with fields for Guide Name, Question Text, Question Order, Time Limit, and Scoring Rubric. Score weighting from Recright migrates as a decimal custom field. If the customer prefers, we flatten the guide into a question bank plus a Zoho Recruit Assessment with questions entered manually.

Recright Interview Questions (tied to specific guides, with text prompts, time limits, and recording settings) map to individual records within the Interview Guides Custom Module or to Assessment questions. We preserve the question text, time limit, and order within the guide. Whether questions go into the Custom Module or the native Assessment module is decided during scoping based on the customer's intended review workflow in Zoho Recruit.

Recright Pre-recorded Interviews (a Candidate's video response to a structured Interview Question) export as metadata: question text, response duration, completion timestamp, and watch count. Video blob files are not programmatically accessible. We create a Zoho Recruit Interview record linked to the Candidate, storing the Recright metadata in custom fields (recright_interview_id, response_duration_seconds, completion_timestamp, watch_count). Video files are coordinated separately (see Gotchas). The Interview record links to the Job Opening and the mapped Interview Guide Custom Module record.

Recright Assessment Scores (numerical or qualitative scores per question and per reviewer) map to custom numeric or picklist fields on the Interview record or the Interview Guide Custom Module, depending on whether the customer prefers per-question or per-reviewer aggregation. We preserve the raw score value, the max score for normalization, the reviewer's name, and the review timestamp. Scores are not aggregated into a Zoho Recruit native score field because Zoho Recruit's Assessment module does not expose per-question reviewer scoring in the same data model.

Recright multi-user team members (name, email, role per position) map to Zoho Recruit User records. We extract distinct team members across all positions, match by email against the Zoho Recruit User table, and flag any Recright team member without a corresponding Zoho User in a reconciliation queue for the customer's admin to provision. Zoho Recruit requires at least two users to run the migration wizard; we verify this during scoping.

Recright Position publication settings (job board distribution, career site status, job posting URLs) do not have a direct Zoho Recruit equivalent. We document the publication settings as a text field on the Job Opening record and recommend the customer republish openings from Zoho Recruit's native job posting tools (which support free job postings on Standard and Enterprise tiers) as part of their go-live checklist.

Recright custom fields added to candidate records map to Zoho Recruit custom fields on the Candidate object. We extract the field name, data type, and values during CSV analysis, create matching custom fields in Zoho Recruit during schema setup, and migrate values during the Candidate import phase. Picklist values in Recright map to Zoho Recruit picklist or multi-select picklist fields with values created in the destination before import.

Recright video interview files (MP4/webm blobs) cannot be downloaded via any documented API. We flag this as a separate workstream during scoping. If the customer has Recright support provide a secure download of video files, we store them as Zoho Recruit Attachments on the mapped Interview record, noting that Zoho Recruit's attachment storage has per-organization limits. Alternatively, we document the video file location as a custom text field with a link to a secure shared drive (SFTP, encrypted cloud storage, or Recright-assisted download) so the videos remain accessible to hiring teams.

Recright candidate statuses (applied, screening, interview, offer, hired, rejected) map to Zoho Recruit Candidate Status values. We extract the full status taxonomy from the customer's Recright account, create matching picklist values in Zoho Recruit during schema setup, and preserve the status history as activity notes or a custom field if the customer requires an audit trail of status transitions.

Recright tracks watch count per interview response (how many times a reviewer has viewed a video). We preserve this as a custom integer field recright_watch_count on the Interview record. This is informational metadata that Zoho Recruit does not natively track.