Migrate from SnapHire to BambooHR

SnapHire Candidate records map to BambooHR Applicants attached to a corresponding Job Opening. We map candidate name, email, phone, stage status, rejection reason, and application date. Candidate Match scores transfer as static custom fields (numeric value and match percentage) on the Applicant record since BambooHR has no equivalent matching algorithm. Stage history migrates as a text timeline field on the Applicant for audit purposes.

SnapHire Job records (title, department, location, description, pipeline) map to BambooHR Job Openings. Job pipeline assignment in SnapHire maps to BambooHR's job status field and hiring pipeline configuration. Open and closed dates transfer as Start Date and Target Hire Date fields in BambooHR.

SnapHire custom candidate data fields (dropdowns, checkboxes, text inputs, validation rules) vary per-organization and require individual field-level mapping. Multi-choice options map to BambooHR dropdown or multiselect custom fields with explicit value mapping. Any custom field without a BambooHR equivalent is flagged during scoping and either maps to a free-text field or is marked for admin review. This mapping work scales with custom field count and can be the longest single configuration task for field-heavy SnapHire instances.

The Candidate Match feature generates match scores between talent community candidates and job profiles using a SnapHire-native algorithm. We preserve the matched candidate records and their numeric scores as static custom fields on the Applicant record in BambooHR. The matching logic itself cannot be replicated because it has no direct equivalent in BambooHR's ATS. Hiring teams should configure BambooHR's applicant sourcing and talent pooling features post-cutover if passive candidate matching is a recruiting priority.

Candidate and job attachments download from SnapHire as binary files and re-upload to BambooHR as Applicant attachments with the same filename and association. Resume files map to the BambooHR Resume field on the Applicant; cover letters and assessments map as general attachments linked to the Applicant record. File integrity is verified by comparing file hash post-upload.

Each candidate's stage movement history (stage name, entry date, exit date, action taken) transfers as a structured text or JSON custom field in BambooHR preserving the timeline. BambooHR does not have a native stage history audit object for applicants, so the history is stored as a custom field rather than as native activity records. We flag this gap during scoping so the customer's admin knows that stage history is visible on the Applicant record but not in a separate audit log.

SnapHire rejection reasons are per-organization freeform or predefined lists. These map to a custom dropdown field in BambooHR with explicit value mapping from SnapHire's reason taxonomy to BambooHR's allowed values. Any SnapHire reason without a matching BambooHR option is mapped to an 'Other' bucket and flagged for admin review.

SnapHire Workflows define hiring stage progressions and actions per job. We do not migrate workflows as executable automation. We deliver a written inventory of every active SnapHire Workflow with its trigger conditions, stage progression sequence, and configured actions. This document allows the customer's BambooHR admin to configure equivalent hiring pipelines and stage actions in BambooHR's ATS setup area. Workflow configuration is the customer's rebuild responsibility post-cutover.

SnapHire's onboarding automation pushes new hire data to intelliHR (Humanforce) when a candidate is marked Hired. For migrations to BambooHR, which has its own native onboarding module, we extract the existing automation configuration (trigger, field mappings, push targets) as documentation. The customer's HR admin rebuilds the onboarding sequence using BambooHR's new hire packet, onboarding checklist, and e-signature features post-cutover. We do not build the onboarding automation inside the migration scope.

SnapHire Categories are user-defined labels used for reporting pipeline metrics by job type. These map to BambooHR Job Opening tags or department assignments depending on their intended use. We map them to the closest equivalent and flag any category that does not have a clean BambooHR equivalent for the customer's admin to resolve.