Migrate your SnapHire data
New Zealand-origin ATS platform with configurable workflows and a strong talent community matching feature. Built for HR teams managing mid-to-large recruitment pipelines who need flexibility over out-of-the-box simplicity.
In its favor
Why people choose SnapHire
The signal that keeps SnapHire on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Established New Zealand vendor (founded 2003) with 20+ years serving customers in NZ, Australia and the US — local-market credibility for AU/NZ buyers concerned about data residency and APAC support hours.
App-store extensibility — additional capabilities are made available at no extra cost via SnapHire's own app store, giving customers a wider feature footprint than the headline tiers suggest.
Personal, thorough customer support — multiple reviewers single out 'superbly personal' support as a primary retention reason, contrasting with larger global ATS vendors.
End-to-end coverage: applicant tracking, contact management, custom career websites, job posting, social-media integration, candidate database with resume parsing and onboarding all in one platform.
Custom-quote commercial model (rather than rigid tiers) lets SnapHire bundle the right module mix for the customer's actual hiring volume and recruiter headcount.
Reporting is criticised by reviewers as 'klunky' and not easily grasped for day-to-day users — analytics depth lags modern ATS competitors.
Lacks some advanced automation features (e.g., AI-driven candidate matching beyond Candidate Match) that are now standard in newer cloud ATS platforms.
Custom-quote-only pricing makes self-serve evaluation and budget benchmarking hard — third-party estimates suggest from ~$1,500/month but the actual rate is opaque.
Larger enterprises and high-volume hiring teams report outgrowing SnapHire's customisation ceiling and migrate to platforms with deeper workflow scripting and BI.
App-store ecosystem is smaller than global competitors (Workday, Greenhouse, iCIMS), limiting third-party connectors for niche assessment tools or vertical CRMs.
Reasons to switch
Why people leave SnapHire
The recurring reasons buyers give for replacing SnapHire. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where SnapHire fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
SnapHire pricing overview
SnapHire does not publish pricing publicly on its website or in the research data. Pricing appears to be quote-based, tiered by organization size and feature access. Prospective customers must contact SnapHire directly for a proposal.
SnapHire (custom-quote)
Tier 1 of 1
Custom (sales-led — third-party estimates from ~$1,500/month)
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on SnapHire's schedule — see our quote-based pricing →
What gets migrated
SnapHire object support
Object-by-object support for SnapHire migrations. Per-pair details surface during scoping.
Candidates
Fully supportedStandard candidate records with name, contact details, application history, and stage progression. We map candidate status and stage history 1:1 into the destination ATS, preserving the full application timeline.
Jobs
Fully supportedJob records contain title, department, location, description, and associated pipeline. We transfer job records and their metadata directly. Workflows attached to jobs require workflow-level mapping at scoping.
Workflows
Mapping requiredSnapHire uses SnapHire workflow functionality to manage hiring stages and actions. Workflows are structured as stage progressions with configurable actions at each stage. We map these to destination pipeline stages, noting that custom workflow logic (e.g., automated triggers) may need manual reconfiguration post-migration.
Categories
Mapping requiredJob-specific categories are used primarily for reporting. Categories are user-defined and may not map directly to tags or labels in the destination ATS. We map them to the closest equivalent and flag any reporting dependencies.
Custom Candidate Data Fields
Mapping requiredSnapHire supports custom candidate data field validation and multi-choice dropdown/checkbox options. Custom fields vary per-customer and require field-level mapping. We extract the full custom field schema during discovery and map each to a destination field or flag it as a custom property.
Candidate Match (Talent Community)
Mapping requiredCandidate Match automatically suggests talent community candidates matching job profiles. This is a SnapHire-native feature with no direct equivalent in most destination ATSs. We preserve the matched candidate records and their match scores as custom fields on the candidate record.
Attachments
Fully supportedCandidate and job attachments (resumes, cover letters, assessment files) are transferred as binary blobs. We download and re-upload with the same association in the destination system.
Hiring Stage History
Fully supportedEach candidate's stage movement history is recorded in SnapHire. We preserve this as a timeline or stage-history field in the destination system, maintaining auditability of the hiring process.
Rejection Reasons
Mapping requiredRejection reasons are configured per-organization in SnapHire. These are freeform or predefined lists that need explicit mapping to the destination ATS rejection reason taxonomy.
Onboarding Workflows
Mapping requiredSnapHire supports onboarding workflows that push new hire data to downstream HR systems. When migrating away, we extract the onboarding configuration for reference. The actual onboarding automation cannot be transferred as-is and must be rebuilt in the destination system.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | Standard candidate records with name, contact details, application history, and stage progression. We map candidate status and stage history 1:1 into the destination ATS, preserving the full application timeline. |
| Jobs | Fully supported | Job records contain title, department, location, description, and associated pipeline. We transfer job records and their metadata directly. Workflows attached to jobs require workflow-level mapping at scoping. |
| Workflows | Mapping required | SnapHire uses SnapHire workflow functionality to manage hiring stages and actions. Workflows are structured as stage progressions with configurable actions at each stage. We map these to destination pipeline stages, noting that custom workflow logic (e.g., automated triggers) may need manual reconfiguration post-migration. |
| Categories | Mapping required | Job-specific categories are used primarily for reporting. Categories are user-defined and may not map directly to tags or labels in the destination ATS. We map them to the closest equivalent and flag any reporting dependencies. |
| Custom Candidate Data Fields | Mapping required | SnapHire supports custom candidate data field validation and multi-choice dropdown/checkbox options. Custom fields vary per-customer and require field-level mapping. We extract the full custom field schema during discovery and map each to a destination field or flag it as a custom property. |
| Candidate Match (Talent Community) | Mapping required | Candidate Match automatically suggests talent community candidates matching job profiles. This is a SnapHire-native feature with no direct equivalent in most destination ATSs. We preserve the matched candidate records and their match scores as custom fields on the candidate record. |
| Attachments | Fully supported | Candidate and job attachments (resumes, cover letters, assessment files) are transferred as binary blobs. We download and re-upload with the same association in the destination system. |
| Hiring Stage History | Fully supported | Each candidate's stage movement history is recorded in SnapHire. We preserve this as a timeline or stage-history field in the destination system, maintaining auditability of the hiring process. |
| Rejection Reasons | Mapping required | Rejection reasons are configured per-organization in SnapHire. These are freeform or predefined lists that need explicit mapping to the destination ATS rejection reason taxonomy. |
| Onboarding Workflows | Mapping required | SnapHire supports onboarding workflows that push new hire data to downstream HR systems. When migrating away, we extract the onboarding configuration for reference. The actual onboarding automation cannot be transferred as-is and must be rebuilt in the destination system. |
Gotchas
What to watch for in SnapHire migrations
Issues we've hit on past SnapHire migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
SnapHire Bullhorn export can take 2–3 weeks
Custom data fields vary per-organization
Candidate Match scores are not transferable as logic
No public API documentation for bulk export
Onboarding workflows push to intelliHR only
| Severity | Issue |
|---|---|
| High | SnapHire Bullhorn export can take 2–3 weeks |
| Medium | Custom data fields vary per-organization |
| Medium | Candidate Match scores are not transferable as logic |
| Medium | No public API documentation for bulk export |
| Low | Onboarding workflows push to intelliHR only |
Leaving SnapHire?
Where SnapHire customers move next
5 destinations SnapHire can migrate to.
How a SnapHire migration works
Four steps, SnapHire-specific
Connect
Not publicly documented into SnapHire. Scopes limited to read-only on the data we move.
Map
We translate SnapHire-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate SnapHire quirks before production.
Migrate
Full migration with SnapHire rate-limit handling. Rollback available throughout.
FAQ
SnapHire migration FAQ
Answers to the questions buyers ask most during SnapHire migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your SnapHire migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate SnapHire.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your SnapHire setup and destination — written quote back within a business day.