.webp?dpl=dpl_32JWLLCSmASCFQ1e2y2kZ2GA1AJw)
Switch from JazzHR
Switching from JazzHR to Yardstick
Getting your data out
Getting your data out of JazzHR
The exact steps to get your candidates, jobs, and applications out of JazzHR — including what your plan gates and what needs a support ticket. Every step links to JazzHR’s own documentation.
- 1
Export your candidate records to CSV yourself. In JazzHR, go to Reports and run “Candidate Record Raw Data Download” — it exports every candidate in the account with 50+ fields (name, contact details, job title, source, and the rest) as a CSV. Large accounts get the file emailed once it finishes generating. Source
Self-serve
- 2
Need a single candidate? Open their profile, scroll below the resume, and use “Export Candidate” to download that person as CSV or PDF. Source
Self-serve
- 3
For resumes, attachments, and the full data set (candidates, contact info, parsed resumes, source, EEOC data, jobs, and pipelines), request a full data export from your JazzHR account or support rep — the self-serve CSV covers fields, not files. Source
Support request · plan-dependent
Watch the deadlines
- The full resume-and-attachment export is a support request JazzHR handles by plan and service level, and it can take a few weeks — start it before you begin cancelling, not after. Source
What survives the move
The pipeline moves — people, roles, and the history connecting them.
Yardstick imports the three things every ATS actually holds: your candidates, the jobs they were attached to, and the applications that record who stood where in which role. Applying the import also creates the job postings and starter interview plans that give each role a working home — so you land in a system that’s ready to run interviews, not an empty shell.
Your JazzHR candidate CSV maps straight into the dry run as candidates, jobs, and applications; the resumes and attachments come across once JazzHR's support export lands, and your agent converts either one to the importer's structured rows.
Hand it to your agent
Your coding agent can run the whole move.
The importer is part of Yardstick’s public API and the yardstick CLI, available on every account. So instead of working the exports by hand, you can hand them to a coding agent (Claude Code, Codex, or similar): it converts each export into structured rows, runs the dry run, and brings you a row-by-row preview of exactly what will be created. You read it and approve; the agent applies it — and the apply writes exactly what the preview showed, nothing more.
That’s the same division of labor Yardstick is built on everywhere: agents prepare the work, and humans approve it. An import never emails a candidate, never merges people, and never deletes anything.
The right fit
Who should move — and who shouldn’t.
If JazzHR still fits how your team hires, there's no reason to move. Teams switch to Yardstick when they've outgrown JazzHR's interview depth — they want structured, job-specific interview plans and scorecards, AI decision briefs under human approval, and an ATS a coding agent can operate. One practical note: JazzHR cancellation isn't self-serve — it's a request handled by a rep over email, and JazzHR offers a paid “hibernation” plan to keep your data after you leave — so pull your export while your account is active, before you start that conversation.
FAQ
Common questions about leaving JazzHR.
How do I export my candidates from JazzHR?
JazzHR has a self-serve report — Reports → Candidate Record Raw Data Download — that exports every candidate with 50+ fields to CSV (emailed to you if the file is large). You can also export a single candidate to CSV or PDF from their profile. These give you field data; resumes and attachments come through a separate support request.
Can I get my resumes and attachments out of JazzHR?
Not through the self-serve CSV — that's field data only. Resumes, attachments, and the full data set (including EEOC data, jobs, and pipelines) come through a full data export you request from JazzHR support, which JazzHR gates by plan and service level and which can take a few weeks. Start it early.
Can an AI agent migrate my JazzHR data to Yardstick?
Yes. Yardstick's importer is part of its public API and the yardstick CLI on every account, so a coding agent can convert your JazzHR exports into structured rows, run the dry-run, and show you the preview. You approve it; the agent applies it. The agent does the work; the approval stays with you.
Do I have to cancel JazzHR before I export my data?
No — and you shouldn't. Export while your account is active: run the self-serve CSV and start the support request for resumes first. JazzHR cancellation is request-based (handled by a rep over email), so keep the account live until your data is safely out.
Bring your JazzHR pipeline with you.
Create your account and dry-run your first import — see the row-by-row preview of exactly what will be created before anything is written.
Want the full picture first? See how importing into Yardstick works.