Migrate from Snaphunt to Zoho Recruit

Snaphunt Job postings (title, description, location, remote status, requirements) map directly to Zoho Recruit Job Opening records. We extract full job records from Snaphunt's CSV export and map them to Zoho Recruit's standard Job Opening fields: Title, Description, Skills Required, Location, and Remote/Onsite designation. Any Snaphunt job with multiple locations or multi-region remote designations is split into separate Job Opening records in Zoho Recruit. Custom fields on Snaphunt Jobs are created in Zoho Recruit during the pre-migration schema phase, with field type matching (text, picklist, multi-select) determined during the audit.

Snaphunt Candidate profiles (contact information, skills, work history, psychometric profile, video resume URL) map to Zoho Recruit Candidates. We map structured fields directly: name, email, phone, skills, and current employer. The psychometric profile summary from Snaphunt is preserved as a text block in a Zoho Recruit custom Notes field labeled Psychometric_Profile_Snaphunt__c. Video resume URLs are preserved as text in a custom URL field labeled Video_Resume_URL_Snaphunt__c and flagged for manual re-upload if the customer chooses to use Zoho Meet video interviews post-migration. Zoho Recruit requires a Last Name field on every Candidate; any Snaphunt Candidate without a surname is mapped to a Last Name of 'Not_Provided' and flagged for manual review.

Each Snaphunt Application links a Candidate to a Job with a status, source attribution, and timestamp. We map this to Zoho Recruit by matching the Candidate email (primary key) and Job Opening title-plus-location (secondary key) to create the association. The Snaphunt application status (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Zoho Recruit's pipeline stage values. Source attribution from Snaphunt (direct, referral, job board) migrates to the Source field on the Zoho Recruit Candidate record.

Snaphunt tracks candidates through standard stages (Applied, Screening, Interview, Offer, Hired, Rejected). We map these stages directly to Zoho Recruit pipeline stages, configuring Zoho Recruit's Hiring Pipeline stages to match the Snaphunt stage names and order. Stage probability percentages from Snaphunt are preserved in a Zoho Recruit custom field for reporting. If Snaphunt includes custom stage names (specific to the customer's account), we configure Zoho Recruit pipeline stages to match during the pre-migration configuration phase. Workflow Rules in Zoho Recruit for stage-change automation are documented separately and handed to the customer for manual rebuild.

Snaphunt psychometric and skills assessment results are stored as numeric scores and narrative summaries. Numeric scores map directly to custom Number fields on a Zoho Recruit custom module called Snaphunt_Assessments__c, linked to the Candidate via a Lookup relationship. Free-text assessment summaries are preserved as Text Area fields. If Zoho Recruit's built-in Assessment module is active in the customer's edition, we map scores into the standard Assessment fields; otherwise we use the custom module approach. Skills assessment scores are mapped to Zoho Recruit Skills fields on the Candidate record where field types align.

Video resumes are hosted media files referenced by URL in the Snaphunt candidate profile. The video files themselves are not exportable via Snaphunt's standard platform exports. We extract the video URL from each candidate record and preserve it in a Zoho Recruit custom URL field labeled Video_Resume_Link__c on the Candidate record. This allows recruiters to click through to the original Snaphunt-hosted video if the Snaphunt account remains active, or to manually re-upload the video file to Zoho Recruit's document storage or a linked Zoho Meet interview session. Video file download from Snaphunt's media infrastructure is not in scope; we document the URL and flag affected candidates for customer action.

Snaphunt Interview records include scheduled date, interviewer name, interview type, and outcome notes. We map these to Zoho Recruit Interview records with Start Date/Time, End Date/Time, Interview Type, and Interviewer fields. Calendar invite links associated with Snaphunt interviews do not export as transferable links; we document the original calendar context in a Notes field on the Zoho Recruit Interview record. If the interviewer name maps to a Zoho Recruit User (matched by email), we set the Owner field; otherwise the interviewer name is stored as free text and flagged for manual assignment in Zoho Recruit.

Snaphunt team member accounts include name, email, and role. We export the user list and map it to Zoho Recruit Users by email address. A Zoho Recruit User account must not already exist in the customer's Zoho Recruit organization before import; users with pre-existing Zoho Recruit accounts must close those accounts before they can be imported under the company's Recruit account. Role and permissions from Snaphunt are documented in a written inventory for the customer's Zoho Recruit admin to reconfigure in Zoho Recruit's Roles and Profiles settings. We flag any Snaphunt user without a Zoho Recruit counterpart as a manual provisioning item before the production migration phase.

Some Snaphunt accounts include custom fields on candidate profiles that are not part of the standard export schema. We inspect the full candidate export during the audit phase and identify all non-standard columns. Each identified custom field is pre-created in Zoho Recruit with the appropriate field type (Text, Picklist, Multi-Select, Number, Date, Checkbox) before the Candidate import begins. Zoho Recruit's custom field limits by edition are checked at scoping: Standard allows 50 custom fields per module, Enterprise allows 300 per module. If the customer's Snaphunt custom field count exceeds the target Zoho Recruit edition limit, we flag the overflow fields for customer decision on field prioritization or edition upgrade.

Snaphunt employer branding assets (company logos, banners, branded job page templates) are platform-bound and cannot be extracted in a reusable format. We exclude brand assets from the migration and document them during discovery as a reference list for the customer's design team to manually recreate in Zoho Recruit's Careers Page builder and Job Opening branding settings. Zoho Recruit's branding customization includes logo upload, color theme, and custom careers site templates; we provide the documented Snaphunt brand assets as a recreate brief for the customer's marketing or brand team.

Snaphunt internal notes and comments attached to Candidates or Applications are exported as text blocks and mapped to Zoho Recruit Notes linked to the corresponding Candidate record via ContentDocumentLink. We preserve the original note timestamp and author name. If the Snaphunt note author maps to a Zoho Recruit User (via email match), we set the Created By field; otherwise the author name is embedded in the note body. Rich text formatting from Snaphunt notes is converted to plain text to avoid import errors in Zoho Recruit's Note field.

Snaphunt candidate attachments (resume files, portfolio documents) referenced in the candidate profile are not bulk-downloadable via Snaphunt's standard export. We extract the attachment file names and URLs from the Snaphunt export and preserve them as text entries in a Zoho Recruit custom field labeled Original_Attachment_Filenames__c. Recruiters are advised to download remaining attachments from Snaphunt before account closure and re-upload them to the Zoho Recruit Candidate record or Document Library. We provide a checklist of flagged candidates with attachment references as part of the migration handoff package.