Migrate from cvviz to Zoho Recruit

CVViZ Job records map to Zoho Recruit Job Opening. We carry title, description, department, employment type, location, and the active/inactive status flag. CVViZ job board distribution settings (LinkedIn, Google for Jobs, Facebook) migrate as metadata only; the customer must republish postings in Zoho Recruit job board distribution module after migration. Any jobs exceeding the destination Zoho Recruit plan active-job limit are flagged as archived during scoping and activated post-migration upon plan upgrade.

CVViZ Candidate records map directly to Zoho Recruit Candidate. We carry first name, last name (required in Zoho Recruit; CVViZ records without a last name receive a 'not provided' placeholder per Zoho's import requirement), email, phone, social profiles (LinkedIn, GitHub, Stack Overflow URLs), employment history, and current status. Last Name is mandatory in Zoho Recruit import; records without a value must specify 'not provided' or similar before import begins.

CVViZ Application records (linking a Candidate to a Job with a current pipeline stage and timestamp) map to Zoho Recruit Job Application. We preserve stage history with timestamps, source attribution (referral, job board, direct), and any offer or rejection records. The Job Application sits as a child record under both the Candidate and the Job Opening in Zoho Recruit's relational structure.

CVViZ pipeline stages are fully organization-specific with no universal schema. We capture the complete stage map (names, order, probability percentages) during pre-migration schema review, then map each named stage to a corresponding Zoho Recruit Hiring Pipeline stage value. Any CVViZ stages with no Zoho equivalent are flagged for manual configuration before the final import run. Stage transitions and associated notes migrate as Application history records.

CVViZ stores parsed resume fields alongside raw PDF/DOCX files. We extract the binary file and attach it to the corresponding Candidate record in Zoho Recruit. Parsed structured fields (skills, education, certifications) migrate to equivalent Zoho Recruit Candidate custom fields. If the destination lacks a resume parser, candidates land with the raw file unparsed and the structured fields populated from our pre-parse transform.

CVViZ Talent Pool maintains passive candidates not tied to a specific job requisition. We migrate Talent Pool entries as Zoho Recruit Candidate records with a custom field or status value (e.g., lifecycle_stage = 'Passive') that identifies their talent pool origin. Source attribution (where the passive candidate was first sourced) migrates to a Zoho Recruit custom field.

CVViZ pre-screening questions and candidate responses store as key-value pairs per Job or Application. We map these to Zoho Recruit custom fields on the Job Opening (for company-wide questions) or on the Job Application (for position-specific questions). Unstructured or free-text responses that do not map cleanly to Zoho's field types are flagged for manual review during scoping.

CVViZ AI ranking scores derive from proprietary NLP against the job description and historical hiring data. We carry the numeric score value as a Zoho Recruit custom field on the Candidate record. The destination ATS will not recalculate or update this score; it remains a static snapshot from the migration date. We recommend setting expectations with the customer that Zoho Recruit's Zia matching will re-rank candidates over time.

CVViZ custom fields on Jobs migrate to Zoho Recruit custom fields on Job Opening. We carry field names, data types (text, number, date, picklist, checkbox), and values. The destination Zoho Recruit org must have identically named custom fields created before migration; we document the required schema and provide the field creation checklist.

CVViZ custom fields on Candidates migrate to Zoho Recruit custom fields on Candidate. Same approach as Job custom fields: field names, data types, and values carry forward. Picklist fields on CVViZ must have matching picklist values defined in Zoho Recruit before import; mismatches are flagged in the mapping document.

CVViZ Users map to Zoho Recruit Users. We resolve by email match. Any CVViZ User without a matching Zoho Recruit account goes to a reconciliation queue; the customer provisions missing users in Zoho Recruit before migration of record assignments proceeds. Role assignments migrate to Zoho Recruit Profiles and Roles based on the closest equivalent permission set.

CVViZ rule-based automations for email triggers, notifications, and stage transitions are platform-specific and do not map cleanly to Zoho Recruit Blueprint or workflow rules. We document the complete rule logic including trigger event, conditions, actions, and order of execution. The customer rebuilds these in Zoho Recruit's Blueprint editor post-migration. This inventory is delivered as a written deliverable, not migrated as code.

CVViZ job board posting configurations (LinkedIn, Google for Jobs, Facebook, Stack Overflow, GitHub) store as metadata flags on Job records. We document which boards each job was distributed to. The customer must reconnect and republish job postings in Zoho Recruit's job distribution module; posting credentials and job board API keys do not transfer between platforms.

CVViZ captures LinkedIn, GitHub, Stack Overflow, Twitter, and Facebook profile URLs on Candidate records. We map these to corresponding Zoho Recruit custom fields on the Candidate module. Zoho Recruit does not have native social profile parsing; profile URLs land as static links rather than enriched contact data.