Migrate from SnapHire to Bullhorn ATS & CRM

SnapHire Candidate records (name, contact details, stage progression, application history) map directly to Bullhorn Candidate. We preserve the full hiring stage history as a note or custom text area on the Bullhorn Candidate record for audit continuity. Candidate status from SnapHire maps to Bullhorn Candidate status using an explicit value-mapping table built during scoping.

SnapHire Job records (title, department, location, description, pipeline association) map to Bullhorn JobOrder. The JobOrder's status field maps from SnapHire job status, and we preserve the job's assigned categories as Bullhorn JobOrder categories or custom fields depending on the Bullhorn edition. Job attachments migrate as ContentDocumentLink records attached to the JobOrder.

SnapHire custom candidate data fields vary per-organization and are extracted during the SnapHire Client Success coordination phase. Multi-choice dropdowns and checkboxes require explicit value mapping to Bullhorn equivalent picklists or Custom Object fields. Bullhorn ATS edition supports 2 Custom Objects with 55 fields each; Bullhorn Front Office Growth/Enterprise supports 10. We pre-create the destination schema before migration and match field types to the closest Bullhorn field type.

The SnapHire Candidate Match feature generates match scores between talent community candidates and job profiles. These scores are preserved as a static custom field on the Bullhorn Candidate record during migration. The matching algorithm logic itself is SnapHire-native and cannot be replicated in Bullhorn. We document the matched candidate list with their scores for the customer's Bullhorn admin to evaluate using Bullhorn Search & Match if that module is licensed.

SnapHire workflows define hiring stage progressions and configurable actions per stage. Bullhorn does not have a direct equivalent at the object level. We document the existing SnapHire workflow configuration (stages, actions, triggers, assignment rules) as a written specification and recommend Bullhorn Automation or manual pipeline stage configuration as the rebuild path post-cutover.

SnapHire job categories are user-defined labels used for reporting. They have no direct Bullhorn equivalent at the object level. We map them to Bullhorn JobOrder categories or tag them using Bullhorn's tagging model depending on the Bullhorn edition. The customer chooses the preferred approach during scoping, and we flag any categories that cannot map directly.

Candidate resumes, cover letters, and assessment files stored as attachments in SnapHire are downloaded as binary blobs and re-uploaded to Bullhorn as ContentDocument records linked via ContentDocumentLink to the Candidate record. We preserve the original filename and any SnapHire metadata (upload date, source) in the ContentDocument description field.

Job-level attachments (job descriptions, requirements documents, company briefs) migrate to Bullhorn JobOrder as ContentDocument records attached via ContentDocumentLink. We maintain the association to the correct JobOrder during import using the Bullhorn JobOrder ID resolved during the job migration phase.

SnapHire records each Candidate's movement through hiring stages with timestamps and optional rejection reasons. We preserve this as a formatted Note or custom text area on the Bullhorn Candidate record, maintaining the chronological order and including the original stage name, date, and any rejection reason recorded in SnapHire.

SnapHire rejection reasons are configured per-organization as freeform text or predefined lists. We extract the full rejection reason taxonomy from SnapHire during discovery and map each reason to either a Bullhorn custom Candidate field or a Candidate status value, depending on which approach the customer prefers. Unmapped reasons are preserved as text for manual review post-cutover.

SnapHire onboarding workflows push new hire data to intelliHR (Humanforce) to create employee records. This integration does not exist in Bullhorn. We extract the onboarding configuration (trigger, field mappings, downstream destination) as a written specification for the customer's Bullhorn admin to rebuild using Bullhorn Onboarding or a third-party integration if applicable.

SnapHire Owners map to Bullhorn User records by email match. We extract every distinct owner referenced on Candidate, Job, and attachment records and match against the Bullhorn destination User table. Owners without a matching Bullhorn User are placed in a reconciliation queue for the customer's admin to provision before record import resumes.