Migrate from Snaphunt to BambooHR

Snaphunt Job postings (title, description, location, remote status, requirements) map directly to BambooHR Job Openings. BambooHR's applicant tracking stores job postings with department, location, and employment status. We extract the full job record from Snaphunt CSV and create corresponding Job Openings via the BambooHR API. Any custom job fields from Snaphunt migrate as BambooHR custom fields on the Job Opening.

Snaphunt Candidates (contact info, skills, work history, psychometric profile) map to BambooHR Employee records for hired candidates or Applicant records for those still in pipeline. We use email as the dedupe key. BambooHR requires Employee records to include hire date, department, and job title; for Candidates not yet hired, we create Applicant records. Any Snaphunt custom candidate fields migrate as BambooHR custom fields on the corresponding record type.

Snaphunt Applications link a Candidate to a Job with a status, source attribution, and timestamp. We map these to BambooHR Applications associated with the corresponding Job Opening. Pipeline stage (Applied, Screening, Interview, Offer, Hired, Rejected) maps to BambooHR application status. Source attribution (referral, job board, direct) migrates as a text field since BambooHR stores application source as part of its standard tracking.

Snaphunt psychometric and skills assessment scores (numeric) migrate to BambooHR custom numeric fields on the Employee or Applicant record. Narrative assessment summaries migrate as custom text fields. BambooHR does not have a native assessment module, so structured scores require pre-creation of custom fields before migration. We create the field schema during the discovery phase and validate with the customer before import.

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 exportable via standard platform exports. We preserve the video URL in a BambooHR custom text field (e.g., video_resume_url__c) on the Applicant record. The customer decides whether to re-upload videos to a shared drive or document management system, or notify candidates to resubmit.

Snaphunt interview records (scheduled date, interviewer, type, outcome notes) map to interview notes in BambooHR's applicant tracking. BambooHR stores interviews as part of the application timeline rather than as standalone objects. We migrate structured interview data (date, interviewer name, type) as notes attached to the Application. Calendar invite links from Snaphunt do not transfer; we document the original interview scheduling data for manual re-creation.

Snaphunt pipeline stages (Applied, Screening, Interview, Offer, Hired, Rejected) map to BambooHR application status values. We configure the status workflow during schema design, mapping each Snaphunt stage to an equivalent BambooHR status. The customer reviews and approves the stage mapping before migration to ensure alignment with their hiring process.

Snaphunt team member accounts (name, email, role) map to BambooHR Employee records. BambooHR uses Employee records as the user base for its platform access. We resolve team members by email match. Any Snaphunt role information (Recruiter, Hiring Manager, Interviewer) migrates as a custom text field or maps to BambooHR's permission groups if applicable.

Snaphunt accounts using custom fields on Candidates are identified during the audit phase. We extract all visible custom fields from the CSV export and create equivalent custom fields in BambooHR. Custom field types are mapped: text to text, numeric to numeric, date to date, and picklist to dropdown. Fields not visible in the standard export are flagged as manual-review items.

Snaphunt employer branding assets (company logos, banners, branded job page templates) are platform-bound and cannot be extracted. We document the existing brand assets during discovery as a reference list for the customer's design team to recreate in BambooHR's employee-facing branding settings. This is a manual task outside the migration scope.