Migrate from SnapHire to Zoho Recruit

SnapHire candidate records map directly to Zoho Recruit's Candidates module. We map first name, last name, email, phone, and address fields 1:1. The Last Name field is mandatory in Zoho Recruit — any SnapHire candidate records without a last name value are flagged during scoping, and we supply a transformation to insert a placeholder value ('Not Provided') to prevent import rejection. Candidate status from SnapHire maps to the Zoho Recruit Candidate Status picklist; we resolve any non-matching values against the destination picklist during the field mapping phase.

SnapHire Job records map to Zoho Recruit Job Openings. We map job title, department, location, employment type, and job description fields directly. The job's associated pipeline (hiring stage sequence) in SnapHire maps to Zoho Recruit's Hiring Process on the Job Opening record. Active versus closed status in SnapHire determines the Job Opening status in Zoho Recruit. We flag any SnapHire jobs with expired or filled status for the customer's admin to verify before import.

SnapHire Workflows configure hiring stages and stage-specific actions per job pipeline. These do not migrate as code to Zoho Recruit Blueprint because the automation models are structurally different. We extract the full SnapHire workflow configuration — stage names, stage order, required actions at each stage, and rejection reasons — and produce a written Blueprint design document that the customer's admin uses to rebuild the hiring process in Zoho Recruit. Workflow automation actions (email triggers, task assignments, status updates) are documented separately as workflow rule recommendations.

SnapHire Categories are user-defined job taxonomy labels used for reporting. We map them to Zoho Recruit Tags on the Job Opening record. Tags in Zoho Recruit are flat, single-select or multi-select text labels that support filtering and grouping. If the customer uses Categories for cross-job reporting, we recommend Zoho Recruit's Department and Function fields as structural equivalents and Tags as supplemental labels. We flag any Categories with names exceeding Zoho's tag character limit (50 characters) for truncation during transformation.

SnapHire supports custom candidate data fields with validation rules and multi-choice options (dropdowns, checkboxes). These fields vary per-organization with no documented schema export. During scoping, we request a full custom field inventory from the customer and map each field individually to a Zoho Recruit custom field. Single-select fields map to Zoho Recruit Picklist; multi-select fields map to Multi-Select Picklist; free-text fields map to Single-Line or Multi-Line Text depending on expected length. Standard tier caps custom fields at 50 per module; Enterprise extends this to 300. We verify field count against the destination plan during discovery.

SnapHire's Candidate Match feature generates algorithm-based match scores between talent community candidates and job profiles. This is a SnapHire-native matching algorithm that has no direct equivalent in Zoho Recruit. We preserve the matched candidate records and their snapshot match scores as static data in a custom candidate field (e.g., snaphire_match_score__c). The talent community structure itself — how passive candidates are organized and matched — cannot be replicated in Zoho Recruit. If the customer requires passive candidate matching post-migration, Zoho Recruit's Zia AI provides resume-to-job semantic matching from the Professional tier, though the workflow and candidate pool organization differ from SnapHire's Candidate Match.

Candidate and job attachments (resumes, cover letters, assessment files, portfolio items) migrate as binary blobs. We download files from SnapHire and associate them with the corresponding candidate or job record in Zoho Recruit using Zoho's file attachment API or CSV-based upload with base64-encoded content. Resume files associated with candidates migrate as the candidate's primary resume attachment, which Zoho Recruit's resume parsing then extracts into structured candidate fields automatically on import. File size limits (Zoho caps individual attachments at 20 MB) are enforced during the transform phase.

SnapHire records every stage movement a candidate passes through with timestamps and stage names. We preserve this as a Zoho Recruit Candidate Timeline or Activity history field. Stage changes migrate as Task records with a custom Activity Type (e.g., 'Stage Transition') and the stage name stored in a custom field. For Zoho Recruit Standard and above, we use the candidate's Activity History section to preserve auditability. We flag any SnapHire rejection reason associated with a stage exit for explicit mapping to Zoho Recruit's rejection picklist.

SnapHire rejection reasons are configured per-organization and may be freeform text or a predefined picklist. We extract the full rejection reason taxonomy from SnapHire and map it to Zoho Recruit's Candidate Status picklist (Rejected sub-status) or a custom picklist field depending on the destination plan tier. Freeform rejection reasons in SnapHire without a structured picklist require the customer to define a Zoho-compatible taxonomy during scoping, which we document in the mapping specification.

SnapHire user records associated with candidate assignments, job ownership, and workflow actions map to Zoho Recruit Users. We resolve SnapHire users by email address against Zoho Recruit's user list. Any SnapHire user who does not have a corresponding Zoho Recruit account is added to a reconciliation queue for the customer's admin to provision before the production migration begins, per Zoho's requirement that users exist in the destination system before data can reference them.

SnapHire's native onboarding automation is designed to integrate specifically with intelliHR (Humanforce), creating person and job records when a candidate is marked Hired. This integration has no equivalent in Zoho Recruit. We extract the full onboarding workflow configuration — trigger conditions, field mappings, and downstream actions — and deliver it as a written blueprint for the customer's admin to rebuild using Zoho Recruit Blueprint or Zoho People if the customer adopts the broader Zoho HCM suite. The actual automation cannot be migrated as code.

SnapHire tracks the candidate source (job board, referral, direct application) on each candidate application record. We map the source value to Zoho Recruit's Source picklist on the candidate record. Sources that do not map to a Zoho Recruit default picklist value are added as new picklist options during the schema configuration phase, before the candidate import begins.