Migrate from Wizehire to Zoho Recruit

Wizehire Jobs (with title, description, status, location, department, and pipeline stages) map directly to Zoho Recruit Job Openings. The job status (open/closed/paused) maps to Zoho Recruit's Opening Status field. We extract Wizehire job board distribution flags to set Zoho Recruit's Social Posting and job board channel fields. WizeHire's custom pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected or account-customized labels) map to Zoho Recruit's Candidate Status picklist values configured per Job Opening.

Wizehire Candidate records (name, email, phone, resume, application date) map to Zoho Recruit Candidates. The critical mapping step is deduplication: when the same person applied to multiple WizeHire job postings, WizeHire creates separate Candidate records. We identify duplicates by email address match, consolidate into a single Zoho Recruit Candidate profile, and attach all applications to that one record. Zoho Recruit requires Last Name as a mandatory field; we flag any WizeHire candidates with missing last names for the customer to supply before import.

WizeHire Applications link Candidates to Jobs and store stage progression with timestamps (Applied, Screening, Interview, Offer, Hired, Rejected). We preserve each stage transition date for audit trail. Applications in Zoho Recruit are tied to the unified Candidate record (post-deduplication) and the Job Opening. The application status from WizeHire maps to the corresponding Zoho Recruit Candidate Status value on the Application.

WizeHire stores DISC+ personality profile results (Dominance, Influence, Steadiness, Conscientiousness dimensions) as structured data per candidate. Zoho Recruit does not have a native DISC+ field. We export the DISC+ scores and dimension values and create custom fields on the Zoho Recruit Candidate module (disc_dominance__c, disc_influence__c, disc_steadiness__c, disc_conscientiousness__c) before migration. The customer configures these as single-line or numeric fields depending on whether they want raw scores or percentage values retained.

WizeHire hiring manager scorecards with custom evaluation criteria and per-candidate scores map to Zoho Recruit Interview Feedback Forms. We export scorecard template criteria and the individual scores assigned per Application. Zoho Recruit's Interview Feedback Form is a structured form object; we create feedback form templates that match WizeHire's criteria structure and populate them with the historical score data during application migration.

WizeHire custom pre-screening questions per Job map to Zoho Recruit custom fields on the Job Opening or Candidate module. We export the question text and candidate responses. Zoho Recruit supports up to 50 custom fields per module on Standard and 300 on Enterprise. For migrations exceeding these limits, we prioritize the most business-critical questions and document remaining questions for manual entry or Zoho Recruit form-based capture post-migration.

WizeHire background check results (pass/fail flag and provider name from Checkr or similar integrations) map to custom fields on the Zoho Recruit Candidate record. Zoho Recruit does not natively process background checks but can store the result as a field. We export the flag and provider name, map them to bg_check_status__c and bg_check_provider__c custom fields, and note that the customer may need to configure Checkr integration separately in Zoho Recruit if they continue using that provider.

WizeHire's 100+ industry-tested job templates are exported as structured text records with template name, category, and body content. Zoho Recruit does not have a native job template library equivalent to WizeHire's, but we export templates as a configuration dataset that the customer can use to rapidly populate new Job Openings. These are handled as data records, not as a native template feature, and we include a template index so the customer can match templates to job categories during Zoho Recruit setup.

WizeHire interview guides (questions and evaluation criteria attached to Jobs) are exported as structured text. Zoho Recruit does not have a native interview guide object. We attach interview guide content to the corresponding Job Opening as an HTML-formatted Note or as a PDF attachment in the Document Library, preserving the structured sections (interview stage, questions, evaluation rubric). The customer rebuilds any automated interview scheduling workflows in Zoho Recruit's calendar integration post-migration.

WizeHire hiring team notes (text entries with author and timestamp) attached to Candidate profiles map to Zoho Recruit Notes on the Candidate record. We preserve the note body, author name, and creation timestamp. Zoho Recruit Notes are module-scoped and appear on the Candidate's activity timeline.

WizeHire tags (user-applied labels for candidate filtering) map to Zoho Recruit Tags on the Candidate record. Tags are stored as a comma-separated list per candidate in WizeHire; we parse and import them as individual Tag records in Zoho Recruit's tag management. Tag-based filtering is preserved for the customer's existing segmentation logic.

WizeHire user accounts (hiring managers, admins) with roles and names are exported and mapped to Zoho Recruit Users. We match by email address. Zoho Recruit requires at least two Users in the account before migration can begin; if the customer has only one, we flag this during scoping. Users with existing separate Zoho Recruit accounts cannot be imported until those accounts are closed, which is a Zoho Recruit platform constraint we verify during the pre-migration audit.

WizeHire's customizable pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected or account-customized) are exported as stage names and their sort order. Zoho Recruit's candidate status values are configurable per Job Opening. We map the WizeHire stage names and order to Zoho Recruit's Candidate Status picklist and apply them to each Job Opening during migration so that historical pipeline progression is preserved in the correct order.