Migrate your Wizehire data
SMB-focused ATS platform with AI recruiting tools, DISC+ assessments, and hiring coach support. Small businesses use it to post, evaluate, and hire candidates across 100+ job boards from a single dashboard.
In its favor
Why people choose Wizehire
The signal that keeps Wizehire on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Extremely low barrier to entry for first-time hirers — the interface is simple enough that owners with no recruiting background can post a job and collect applicants within the same session.
Job board distribution to 100+ sites means a single posting reaches far more candidates than posting to Indeed alone, which is the primary reason customers cite for switching from Indeed for Employers.
Integrated DISC+ assessments give small businesses a structured, objective way to evaluate candidate personality fit without purchasing a separate assessment tool.
Built-in hiring coaches provide human support that larger ATS platforms lack — customers value having a named expert to guide job ad writing and candidate filtering.
Monthly pricing at $249 is significantly cheaper than enterprise ATS platforms, making it accessible for businesses with fewer than 50 employees who need professional-grade hiring tools.
Does not have the technology enhancements of traditional ATS systems — enterprise users switching from tools like Greenhouse or Lever find it feels limited, clunky, and lacking in configurability.
Interview request tools are not very customizable — teams that need structured, branded interview workflows outgrow what WizeHire offers out of the box.
Candidate applications are not linked across multiple jobs — the same person applying to two different roles creates two separate candidate records with no shared profile to consolidate them.
Messaging and candidate communication features are unreliable — users report that in-app messaging sometimes fails to deliver, creating gaps in candidate conversation history.
Job board placement is not premium by default — getting featured placement on job boards requires paying an additional fee on top of the subscription, which surprises customers who expected inclusive distribution.
Reasons to switch
Why people leave Wizehire
The recurring reasons buyers give for replacing Wizehire. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Wizehire 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
Wizehire pricing overview
WizeHire uses a flat monthly subscription model ranging from $249 to $449 per month depending on the tier. There is no per-seat or per-hire pricing, but premium job board placement and background checks are billed as add-ons. The subscription continues even when all job postings are closed.
Quickstart
Tier 1 of 2
$249/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Wizehire's schedule — see our quote-based pricing →
What gets migrated
Wizehire object support
Object-by-object support for Wizehire migrations. Per-pair details surface during scoping.
Jobs
Fully supportedJobs are the primary object in WizeHire's data model. Each Job has a title, description, status (open/closed/paused), location, department, and a set of pipeline stages. We export all Jobs and map their stage labels to the destination system's pipeline structure.
Candidates
Fully supportedCandidate profiles include name, email, phone, resume, and application date. Multiple applications by the same person to different jobs appear as separate records in WizeHire. We export all Candidate profiles and flag duplicates for customer review during migration.
Applications
Fully supportedApplications link Candidates to Jobs and store status (Applied, Screening, Interview, Offer, Hired, Rejected). We preserve the application status and timestamp at each stage transition for audit trail purposes.
DISC+ Assessments
Mapping requiredWizeHire stores DISC+ personality profile results per candidate as structured data. We export these as a custom object tied to the Candidate. Not all destination systems have a DISC+ field, so we map the raw scores to a custom candidate property or note field.
Scorecards
Mapping requiredHiring managers create scorecards with custom criteria to evaluate candidates. Scorecard templates and individual candidate scores are stored. We export scorecard values per application and map them to the destination's evaluation fields if supported.
Screening Questions
Mapping requiredEach Job can have custom pre-screening questions. Candidate responses are stored per application. We export question text and answers. Mapping to the destination's custom question schema requires field-level configuration.
Background Checks
Mapping requiredBackground check results are stored as flags on the Candidate or Application object. WizeHire integrates with third-party background check providers. We export the pass/fail flag and provider name; full report content depends on what the provider exposes via API.
Job Templates
Mapping requiredWizeHire provides 100+ industry-tested job templates. These are organizational assets stored per account. We export templates as text/structure records and handle them as configuration data in the migration package.
Interview Guides
Mapping requiredInterview guides are attached to Jobs and outline questions and evaluation criteria. We export them as structured text per Job. The destination system may not have a native interview guide object, so we map them to a custom field or a notes section.
Hiring Pipeline Stages
Mapping requiredWizeHire uses a default pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) that can be customized per account. We export the stage names and order and map them to the destination pipeline, flagging any non-standard stages that need manual recreation.
Candidate Notes
Mapping requiredHiring team members leave notes on candidate profiles. These are stored as text entries with author and timestamp. We export notes and map them to the destination's candidate note/comment object.
Candidate Tags
Mapping requiredUsers can tag or filter candidates by attributes. Tags are stored as a list per candidate. We export tags and map them to the destination system's label or tag field.
User/Team Members
Mapping requiredWizeHire user accounts (hiring managers, admins) have roles and names. We export user records to map them to owner assignments on Jobs and Candidates in the destination system.
| Object | Support | Notes |
|---|---|---|
| Jobs | Fully supported | Jobs are the primary object in WizeHire's data model. Each Job has a title, description, status (open/closed/paused), location, department, and a set of pipeline stages. We export all Jobs and map their stage labels to the destination system's pipeline structure. |
| Candidates | Fully supported | Candidate profiles include name, email, phone, resume, and application date. Multiple applications by the same person to different jobs appear as separate records in WizeHire. We export all Candidate profiles and flag duplicates for customer review during migration. |
| Applications | Fully supported | Applications link Candidates to Jobs and store status (Applied, Screening, Interview, Offer, Hired, Rejected). We preserve the application status and timestamp at each stage transition for audit trail purposes. |
| DISC+ Assessments | Mapping required | WizeHire stores DISC+ personality profile results per candidate as structured data. We export these as a custom object tied to the Candidate. Not all destination systems have a DISC+ field, so we map the raw scores to a custom candidate property or note field. |
| Scorecards | Mapping required | Hiring managers create scorecards with custom criteria to evaluate candidates. Scorecard templates and individual candidate scores are stored. We export scorecard values per application and map them to the destination's evaluation fields if supported. |
| Screening Questions | Mapping required | Each Job can have custom pre-screening questions. Candidate responses are stored per application. We export question text and answers. Mapping to the destination's custom question schema requires field-level configuration. |
| Background Checks | Mapping required | Background check results are stored as flags on the Candidate or Application object. WizeHire integrates with third-party background check providers. We export the pass/fail flag and provider name; full report content depends on what the provider exposes via API. |
| Job Templates | Mapping required | WizeHire provides 100+ industry-tested job templates. These are organizational assets stored per account. We export templates as text/structure records and handle them as configuration data in the migration package. |
| Interview Guides | Mapping required | Interview guides are attached to Jobs and outline questions and evaluation criteria. We export them as structured text per Job. The destination system may not have a native interview guide object, so we map them to a custom field or a notes section. |
| Hiring Pipeline Stages | Mapping required | WizeHire uses a default pipeline (Applied, Screening, Interview, Offer, Hired, Rejected) that can be customized per account. We export the stage names and order and map them to the destination pipeline, flagging any non-standard stages that need manual recreation. |
| Candidate Notes | Mapping required | Hiring team members leave notes on candidate profiles. These are stored as text entries with author and timestamp. We export notes and map them to the destination's candidate note/comment object. |
| Candidate Tags | Mapping required | Users can tag or filter candidates by attributes. Tags are stored as a list per candidate. We export tags and map them to the destination system's label or tag field. |
| User/Team Members | Mapping required | WizeHire user accounts (hiring managers, admins) have roles and names. We export user records to map them to owner assignments on Jobs and Candidates in the destination system. |
Gotchas
What to watch for in Wizehire migrations
Issues we've hit on past Wizehire migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Billing does not stop when all jobs are closed
No documented public bulk API
Candidate duplication across multiple job postings
| Severity | Issue |
|---|---|
| High | Billing does not stop when all jobs are closed |
| High | No documented public bulk API |
| Medium | Candidate duplication across multiple job postings |
Leaving Wizehire?
Where Wizehire customers move next
5 destinations Wizehire can migrate to.
How a Wizehire migration works
Four steps, Wizehire-specific
Connect
Not publicly documented as a developer-facing API. Pre-built integrations are configured through the partner connectors (LinkedIn Recruiter System Connect, ADP Marketplace, Checkr, Payscale, HelloSign). into Wizehire. Scopes limited to read-only on the data we move.
Map
We translate Wizehire-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Wizehire quirks before production.
Migrate
Full migration with Wizehire rate-limit handling. Rollback available throughout.
FAQ
Wizehire migration FAQ
Answers to the questions buyers ask most during Wizehire migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Wizehire 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 Wizehire.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Wizehire setup and destination — written quote back within a business day.