Migrate from Snaphunt to Bullhorn ATS & CRM

Snaphunt candidate profiles map directly to Bullhorn Candidate records. Contact information (name, email, phone, address) maps to the corresponding Bullhorn Candidate fields. Snaphunt's AI-generated match scores and psychometric profile scores migrate to Bullhorn custom numeric fields (customObject1s or customObject2s depending on Bullhorn edition). We preserve the original Snaphunt candidate ID in a text field for reconciliation. Any custom fields on the Snaphunt profile that are not in the standard export schema are flagged during audit and mapped to Bullhorn custom Candidate fields.

Snaphunt video resume files are hosted on Snaphunt's media infrastructure and referenced by URL in the candidate profile. The video files themselves are not downloadable via any export mechanism. We preserve the video URL in a Bullhorn custom Candidate text field (e.g., snaphunt_video_resume_url__c) and flag each affected candidate record in the migration manifest so the customer's Bullhorn admin can decide whether to notify candidates to resubmit or re-upload videos manually.

Snaphunt stores psychometric and skills assessment results as structured numeric scores and narrative summaries. Numeric scores map directly to Bullhorn custom numeric fields on the Candidate record. Narrative summaries are preserved as text blocks and mapped to a custom text area field. The assessment type label (e.g., personality, cognitive, skills) is retained as a picklist value on the same custom object.

Snaphunt job postings (title, description, location, remote status, requirements) map to Bullhorn JobOrder records. The Snaphunt job status (Active, Draft, Closed) maps to Bullhorn JobOrder status. Remote/hybrid designation migrates to the Bullhorn JobOrder isRemote field. Any Snaphunt custom job fields are mapped to Bullhorn custom JobOrder fields or the JobOrder customObject.

Snaphunt applications link a Candidate to a Job with a status, source, and timestamp. We map applications to Bullhorn JobSubmission (the standard Bullhorn ATS application record) with CandidateID and JobOrderID lookups resolved at migration time. The Snaphunt application source (referral, job board, direct) migrates to the JobSubmission source field. Pipeline stage at time of export (Applied, Screening, Interview, Offer, Hired, Rejected) maps to the corresponding JobSubmission status.

Snaphunt's six pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) are configurable per account. We map these to Bullhorn JobSubmission status values and optionally create a Bullhorn Sales Process per Snaphunt pipeline if the customer uses multiple pipelines. Stage names and order are preserved from the Snaphunt export. Bullhorn's pipeline customization requires admin access; we document the mapping in the migration manifest.

Snaphunt employer brand assets (logos, banners, branded job page templates) are platform-bound and cannot be extracted in a reusable format. We document the existing brand assets during discovery with screenshots and asset references so the customer's design team can recreate them in Bullhorn Careers Page Builder. This is a manual-recreation item, not a data migration item.

Snaphunt team member accounts (name, email, role) map to Bullhorn User records. We extract the full user list from Snaphunt's export and map recruiter and hiring manager assignments to Bullhorn User lookups on JobOrder and JobSubmission. Permissions and access levels are not fully exported from Snaphunt, so we flag the permission gap in the handoff document and recommend the Bullhorn admin rebuilds access roles post-migration.

Snaphunt accounts that use custom fields on candidate profiles export those fields in the extended CSV schema. We extract all visible custom fields during the audit phase and create matching custom fields in Bullhorn (Candidate entity) before migration. Bullhorn ATS edition limits custom Candidate fields; Bullhorn ATS allows 2 custom objects per entity while Bullhorn Front Office Growth/Enterprise allows 10 custom objects with 55 fields each. We confirm the customer's Bullhorn edition during discovery.

Snaphunt interview records (scheduled date, interviewer, type, outcome notes) are exported as structured data. We map interview records to Bullhorn Note entities attached to the corresponding JobSubmission, preserving the interviewer name, interview date, type, and outcome notes. Calendar invite links are not preserved from Snaphunt exports.

Snaphunt skill tags and competencies stored on candidate profiles migrate to Bullhorn Candidate skills fields. Bullhorn does not have a native structured skills object by default; we map skills to a Bullhorn custom Candidate text field (skills__c) as comma-separated values, or to a custom picklist if the Bullhorn admin has configured a skills vocabulary.

Snaphunt employer accounts (if used as client records) map to Bullhorn ClientCorporation. The Snaphunt company name, website, industry, and address fields map to the corresponding Bullhorn ClientCorporation fields. If Snaphunt is used purely as a candidate-sourcing platform with no client accounts, this mapping is skipped.