Migrate from SnapHire to Recruit CRM & ATS

SnapHire Candidate records map to Recruit CRM Contact. Name, email, phone, address, and application history transfer directly. Candidate status (active, archived, rejected) maps to Recruit CRM's Contact status field. Historical stage movements are preserved as a stage_history custom text field or as a dated timeline note on the Contact record for auditability.

SnapHire Job records (title, department, location, description, pipeline assignment) map to Recruit CRM Job Requisition. The job pipeline in SnapHire becomes a Recruit CRM pipeline with corresponding stage values. We extract the job's associated pipeline and stage configuration during discovery and build matching stage values in Recruit CRM before job records are loaded.

SnapHire custom candidate data fields (validation rules, multi-choice dropdowns, checkboxes) map to Recruit CRM's associated_fields endpoint — POST /v1/candidates/associated-field/{candidate}/{job}. Each associated field in Recruit CRM requires a pre-existing field_id, so we create the destination field schema in Recruit CRM first, extract the field IDs, then map SnapHire custom field values during ingestion. Multi-choice values require explicit option mapping if the option sets differ between platforms.

SnapHire hiring-stage workflows (stage progressions with configurable actions at each stage) do not migrate as code. We document the existing SnapHire workflow stages and actions in a written inventory. Each SnapHire workflow maps to a Recruit CRM pipeline configuration with matching stage names and probabilities. The customer's admin rebuilds any conditional logic or automated actions in Recruit CRM post-migration.

SnapHire's Candidate Match feature generates match scores between talent community candidates and job profiles. The matched candidate records and their static scores transfer as custom fields on the candidate Contact record. The matching algorithm itself is SnapHire-native and cannot be replicated. Recruit CRM's AI-powered candidate matching regenerates match scores post-migration based on its own scoring model.

Each candidate's SnapHire stage movement history (stage name, entry date, exit date, action taken) is preserved as a structured custom field or as dated Activity notes in Recruit CRM. We extract the stage_history object from SnapHire's candidate export and populate it as a multi-line text field (or equivalent) in Recruit CRM to maintain auditability of the full hiring journey.

SnapHire rejection reasons are configured per-organization as freeform or predefined lists. We extract the full rejection reason taxonomy during discovery and map each reason to a Recruit CRM custom picklist field on the Contact or to a candidate status value. Any reason not covered by the destination taxonomy is flagged for manual assignment post-migration.

SnapHire job-specific categories used for reporting do not have a direct equivalent in Recruit CRM. We map them to Recruit CRM Tags on the Job Requisition, or to a custom multi-select field if the customer requires category-level pipeline reporting. The mapping choice is made during scoping based on how the customer uses categories for analytics.

Candidate and job attachments — resumes, cover letters, assessment files — transfer as binary blobs. We download from SnapHire (as available via CSV export or portal download) and re-upload to Recruit CRM linked to the corresponding Contact or Job record. File naming conventions are preserved to aid recruiter recognition post-migration.

SnapHire Owners referenced on Candidate, Job, and Workflow records map to Recruit CRM Users by email match. We extract all distinct owner references, match against Recruit CRM's user list, and flag any SnapHire owners without a matching Recruit CRM User for the customer's admin to provision before record import begins.

SnapHire's onboarding automation is designed exclusively for intelliHR (Humanforce) integration — pushing new hire data to downstream HR systems. This configuration does not transfer to Recruit CRM, which has no native intelliHR push. We extract the onboarding workflow configuration and deliver it as a written document so the customer's admin can rebuild the workflow logic in Recruit CRM or a separate onboarding tool post-cutover.

SnapHire application records (linking a Candidate to a Job with an application date and status) map to Recruit CRM's candidate-to-job association. We resolve the candidate Contact ID and job Requisition ID at migration time and create the association using Recruit CRM's candidate-job linking endpoints or through the bulk import with explicit lookup resolution.