Migrate from Snaphunt to Recruit CRM & ATS

Snaphunt Job postings map directly to Recruit CRM Job records. Fields transfer including title, description, location, remote status, and requirements. Any custom fields on Snaphunt Jobs are identified during the audit phase and mapped to Recruit CRM custom fields, which are created before import. Job status (Active, Paused, Closed) maps to the Recruit CRM job status field. Note that Snaphunt's Flexpert managed-service jobs and Snaphyre pre-vetted talent postings are platform-bound services and do not migrate as data records.

Snaphunt Candidate profiles map to Recruit CRM Candidates with full contact information, skills, work history, and psychometric profile scores. AI-generated match scores from Snaphunt transfer as a custom numeric field on the Candidate record. Video resume URLs transfer as a text note on the Candidate so the customer can decide whether to re-upload manually. Email and phone are mapped by field name. Candidates without a linked Job (sourced but not applied) migrate as standalone Candidates.

The Snaphunt Application record links a Candidate to a Job with a status, source, and timestamp. We map these directly to Recruit CRM Applications with the Candidate-Job lookup resolved at migration time. Source attribution (direct, referral, job board) and the current pipeline stage at time of export are preserved. Applications in Snaphunt that are archived rather than deleted are flagged for explicit customer decision on whether to include.

Snaphunt psychometric and skills assessment results store as structured numeric scores and free-text summaries. Numeric scores transfer to Recruit CRM custom fields on the Candidate record. Narrative summaries are preserved as text notes attached to the Candidate. We inspect the Snaphunt export schema during the audit phase to identify all assessment score fields and map them individually. Assessment metadata (assessment name, date taken, provider) migrates as a structured note block.

Snaphunt video resume files are hosted media referenced by URL in the candidate profile. The video files themselves are not downloadable via any export mechanism. We document each video resume URL and attach it as a note on the corresponding Recruit CRM Candidate record. The customer must decide whether to request candidates to resubmit videos to Recruit CRM or to manually re-upload if the videos are accessible. We provide a written inventory of all candidates with video URLs for the customer to action.

Snaphunt interview records include scheduled date, interviewer name, interview type, and outcome notes. We map these to Recruit CRM Interview records or Tasks depending on the destination configuration. Calendar invite links associated with Snaphunt interviews do not export and are documented as a gap in the migration scope. Interview outcome notes and feedback text transfer as text blocks. If no Interview object exists in the destination configuration, we fall back to Task records with a custom interview type flag.

Snaphunt's default pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) map to Recruit CRM pipeline stage values via a configurable mapping table. We inspect the Snaphunt export to detect any non-standard or custom pipeline stages specific to the account and map them to Recruit CRM equivalents. Stage ordering is preserved. Probability percentages associated with stages in Snaphunt transfer as a configuration step in Recruit CRM.

Snaphunt team member accounts include name, email, and role. We export the user list and map by email match to Recruit CRM User records. Permissions and access levels in Snaphunt are not fully exportable; we document the Snaphunt role assignments so the customer's Recruit CRM admin can configure equivalent permissions. If a Snaphunt user no longer has an active account, we flag for admin decision on whether to provision a corresponding inactive Recruit CRM User.

Snaphunt accounts with custom fields on Candidates or Jobs are inspected during the audit phase. Each detected custom field is created in Recruit CRM with an equivalent field type (text, number, picklist, date, or checkbox). Fields that cannot be detected in the export schema before extraction are flagged as manual-recovery items and assigned to a catch-all text property for post-migration review. Recruit CRM's custom field configuration is available in Settings for the admin team.

Snaphunt employer brand assets (logos, banners, branded job page templates) are platform-bound and not accessible via any export mechanism. These are explicitly excluded from migration scope. We document the existing brand assets during discovery by reviewing the Snaphunt employer profile with the customer's team, producing a reference list for the design team to manually recreate in Recruit CRM.