Migrate from Snaphunt to Crelate

Snaphunt Job postings map directly to Crelate Job records. We extract title, description, location, remote status, requirements, and posting date from the Snaphunt export. Any custom fields on Jobs detected in the export are mapped to Crelate custom fields, which we pre-create before import. The Job status (Active, Paused, Closed) maps to Crelate Job status. Snaphunt does not support multi-pipeline job boards, so there is no equivalent to Crelate's Record Type concept at the Job level.

Snaphunt Candidate profiles map to Crelate Contact records. We extract full profile fields including name, email, phone, skills, work history, location, and timezone. Psychometric profile scores and AI-generated match scores are preserved in custom fields on the Contact record. Video resume URLs are stored in a custom field crelate_video_resume_url__c and flagged for manual re-upload. The Snaphunt candidate status (Active, Hired, Archived) maps to Crelate's contact status.

Snaphunt Applications link a Candidate to a Job with a status, source, and timestamp. We map each Application to a Crelate Job Application record tied to the migrated Contact and Job. The Snaphunt pipeline stage (Applied, Screening, Interview, Offer, Hired, Rejected) maps to Crelate's application stage values. Source attribution (referral, job board, direct) migrates to the Crelate application source field.

Snaphunt psychometric and skills assessment results are stored as structured scores and free-text summaries. Numeric scores migrate to custom numeric fields on the Crelate Contact record (e.g., assessment_overall_score__c). Narrative summaries and evaluator notes migrate to a long-text custom field (assessment_summary__c) on the Contact. We inspect the Snaphunt export schema during the audit phase to identify all assessment fields present.

Snaphunt video resume files are hosted on Snaphunt's media infrastructure and referenced by URL in the candidate profile. The platform does not provide a bulk download of video files, and the URLs are not directly importable into Crelate's document storage. We preserve every video resume URL in a custom field crelate_video_resume_url__c on the Contact record and generate a manual-recovery checklist listing each affected candidate with their original video URL for the customer's team to re-upload individually.

Snaphunt tracks candidates through defined pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected). We map these stages directly to Crelate's application stage configuration. The customer chooses whether to adopt Crelate's default stage names or recreate the Snaphunt stage names during the configuration phase. Stage timestamps (when a candidate entered each stage) migrate as Activity records attached to the Contact and Job Application.

Snaphunt interview records include scheduled date, interviewer, interview type, and outcome notes. We map these to Crelate Activity records of type Interview with the date, interviewer name, and notes preserved. Crelate supports Event records for calendar-linked scheduling, but Snaphunt interview calendar invite links do not export. We document the original interview scheduling context in the activity notes so the Crelate admin can recreate calendar events if needed.

Snaphunt team member accounts include name, email, and role. We export the user list and map them to Crelate User records. Owner assignments on Jobs, Applications, and Activities resolve by email match to the Crelate User. Permissions and access levels are not fully exportable from Snaphunt; we document the Snaphunt role assignments (Admin, Recruiter, Hiring Manager) for the Crelate admin to configure equivalent permissions post-migration.

Some Snaphunt accounts include custom fields on candidate profiles that are not visible in the standard export schema. We inspect the full candidate export during the audit phase and flag any non-standard fields. These map to Crelate custom fields on the Contact object, which we pre-create with the appropriate field type (text, number, date, picklist, checkbox) before the main migration. If a custom field cannot be detected before export, we create a catch-all long-text field candidate_notes__c and place the unrecognized data there.

Company branding assets configured in Snaphunt including logos, banners, and branded job page templates are platform-bound and not accessible via export. We document the existing brand assets during discovery (logo URLs, banner descriptions, template copy) so the customer's design team has a reference list to recreate manually in Crelate's employer branding settings.

If the Snaphunt export includes company records associated with candidates (employer history, client companies), these map to Crelate Company records. The Snaphunt company name, website, industry, and size fields map to the corresponding Crelate Company fields. Company records are imported before Contact records to satisfy the Company-Contact relationship if the customer's Crelate configuration requires it.

Archived or inactive candidate records in Snaphunt migrate to Crelate Contact records with an Inactive status flag. This preserves the historical record for compliance and audit purposes without cluttering the active candidate pipeline. The customer specifies during scoping whether archived records should migrate in full or be excluded from the active migration scope.