Migrate from Jobvite to Zoho Recruit

Jobvite Jobs map directly to Zoho Recruit Jobs. We extract title, description, requirements, department, location, and job status (open, closed, archived, draft) from the Jobvite Jobs API. Active Posting status translates to Zoho Recruit's Published/Unpublished state. Non-standard job types (contract, part-time, internship) map to Zoho Recruit's Job Type picklist values, with any custom types requiring field-level configuration before import.

Jobvite Candidates map to Zoho Recruit Candidates as the primary person record. We preserve name, email, phone, address, work history, education, skills, and the original application source attribution. Jobvite's SMS consent field (Yes/No/Unknown) maps to a custom Candidate field sms_consent_status__c that we create in Zoho Recruit during schema setup; records with Unknown status are flagged for re-collection before text outreach sequences activate.

Jobvite Applications link a Candidate to a Job at a specific Pipeline Stage and include stage history, rejection reasons, advancement dates, and interviewer assignments. Zoho Recruit consolidates application history within the Candidate record's activity timeline. We create a Candidate history entry for each stage transition, preserving the original stage name from Jobvite and the timestamp of each advancement or rejection.

Jobvite Pipeline Stages are configurable per Job, which means different jobs may have different stage sequences. Zoho Recruit uses shared pipeline templates with stages that apply across jobs or are scoped per pipeline. We extract every distinct stage sequence from Jobvite during discovery, identify the most common pattern, configure a Zoho pipeline template to match, and flag any non-standard stage sequences that require a separate pipeline template in Zoho Recruit.

Jobvite custom field definitions (label, type, picklist values) are exported from the schema API and mapped to Zoho Recruit custom fields created during schema setup. Picklist-type custom fields from Jobvite map to Zoho Recruit picklist or multi-select picklist depending on the original cardinality. Boolean custom fields map to Zoho Recruit checkboxes. Date and datetime fields map with timezone normalization applied.

Jobvite Users include Recruiters, Hiring Managers, and Interviewers with role-based permissions. We resolve active users by email match against Zoho Recruit Users. Any Jobvite User without a matching Zoho Recruit account is flagged in the reconciliation queue; Zoho Recruit's own documentation states that users with pre-existing Zoho Recruit accounts cannot be migrated and must close the separate account before migration proceeds.

Jobvite Offers are tied to an Application and include compensation details, start date, and approval status. We migrate offer records as Zoho Recruit Offers with compensation, proposed start date, and status. Approval history from Jobvite migrates as an Offer history log entry rather than a live workflow record, since Zoho Recruit's approval routing requires Blueprint configuration that happens post-migration.

Jobvite Onboarding records exist only if the customer holds an active Onboarding add-on license. If active, we export onboarding task lists, new hire paperwork status, I-9/E-Verify records, and assigned onboarding task assignments. Zoho Recruit does not have a native onboarding module; onboarding data is migrated as a written inventory delivered to the customer's HR admin for rebuild in their chosen onboarding tool or manual process.

Jobvite structured interview scorecards and hiring team ratings migrate as Zoho Recruit Interview Feedback records attached to the Candidate. We preserve interviewer name, score values, and written feedback. The scoring rubric (1-5 scale, thumbs up/down, structured rubric) is mapped to Zoho Recruit's rating format, and any non-standard rubric types are flagged for review.

Jobvite attachments on Candidates and Applications (resumes, cover letters, portfolio files, signed offer documents) are exported as binary blobs alongside metadata (filename, upload date, attached-by user). We import attachments to Zoho Recruit Candidates using the API's file upload endpoint, preserving the original filename and linking each attachment to the correct Candidate record via the candidate_id lookup.

Talemetry Lists stored in Jobvite's separate data partition map to Zoho Recruit Candidate Lists. Talemetry-specific export endpoints are used for this layer because these Lists are not accessible through Jobvite's standard Candidate API. We map the list membership (candidate IDs) and list metadata (name, description, creation date) to Zoho Recruit Lists, flagging any lists that exceed Zoho Recruit's list membership limits at the customer's target tier.

Talemetry Campaigns and source tracking data are mapped to Candidate source fields in Zoho Recruit. Campaign names and source attribution are stored as custom fields on the Candidate record. We flag any source values affected by the Indeed-Glassdoor merger (post-acquisition, Glassdoor applications appear as Indeed source in Jobvite) so the customer can decide whether to normalize source attribution in Zoho Recruit or preserve the post-merger state.

Jobvite collaborative hiring notes from the hiring team migrate as Zoho Recruit Notes attached to the Candidate. We preserve note content, author, and creation timestamp. Notes are imported as Zoho Recruit Notes with the note body and author attribution intact.

Jobvite Employee records (from the Onboarding or Evolve Suite modules) are not migrated as transactional records. These exist in a separate Employee data layer that is distinct from the recruiting ATS objects. If the customer holds an active Evolve Suite license for internal mobility, we deliver an inventory of Employee records and their skills/experience profiles as a structured CSV for manual import or HRIS integration setup.