.webp?dpl=dpl_32JWLLCSmASCFQ1e2y2kZ2GA1AJw)
Switch from Recruitee
Switching from Recruitee to Yardstick
Getting your data out
Getting your data out of Recruitee
The exact steps to get your candidates, jobs, and applications out of Recruitee — including what your plan gates and what needs a support ticket. Every step links to Recruitee’s own documentation.
- 1
Export your candidates' essential fields yourself. In the Candidates tab, use the three-dots (⋯) menu at the top right to export to CSV — the file downloads immediately. Source
Self-serve · essential fields
- 2
Jobs don't have a CSV export. The only no-code jobs export is an XML feed of your published jobs (at your-company.recruitee.com/api/offers.xml) — it covers public job data, not unpublished roles or internal fields. Source
Published jobs only (XML)
- 3
For the complete record — attachments, CVs, notes, and all fields across every candidate — there's no bulk self-serve export. It routes through Recruitee's open API, which in Recruitee's own words “may require advanced technical knowledge, or a dedicated developer.” The only self-serve alternative is printing candidate profiles to PDF one at a time. Source
API · developer or agent
Watch the deadlines
- Recruitee has applied a documented 5% list-price increase at contract renewal in consecutive years (effective January 1, 2025 and again January 1, 2026), calculated on the list price before discounts — so your renewal is a natural moment to reassess and to move your data. 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 Recruitee candidate CSV covers the essential fields and maps straight into the dry run as candidates, jobs, and applications; the full record — attachments and notes — comes through the API, which is exactly the developer-shaped work your coding agent can do for you.
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 Recruitee still fits how your team hires, there's no reason to move. Teams switch to Yardstick when they've felt the annual renewal increases and want deeper structured interviews — job-specific plans and scorecards, AI decision briefs under human approval — and an ATS a coding agent can operate. The practical wrinkle is that Recruitee's complete export needs a developer; if you don't have one spare, that's precisely the migration a coding agent can run for you, preview and all.
FAQ
Common questions about leaving Recruitee.
How do I export my candidates from Recruitee?
From the Candidates tab, use the three-dots (⋯) menu at the top right to export a CSV of your candidates' essential fields — it downloads immediately. That CSV is fields only; the complete record (attachments, notes, all fields) comes through Recruitee's open API, and jobs export only as an XML feed of published roles.
Can I get my resumes, attachments, and notes out of Recruitee?
Not through a bulk self-serve export — the essential-fields CSV doesn't include them. The complete record routes through Recruitee's open API, which Recruitee says may require a developer, or you can print candidate profiles to PDF one at a time. A coding agent can run the API export for you.
Can an AI agent migrate my Recruitee data to Yardstick?
Yes — and Recruitee is a clear case for it, because Recruitee itself says a full export may require a developer. Yardstick's importer is part of its public API and the yardstick CLI on every account, so a coding agent can call Recruitee's API, convert the export into structured rows, run the dry-run, and show you the preview. You approve it; the agent applies it.
Why do teams leave Recruitee?
A common trigger is cost: Recruitee moved to employee-count-based pricing in 2024 and has applied a documented 5% list-price increase at renewal in consecutive years. Renewal is a natural moment to reassess — and since the complete export needs developer work, planning the move early (or handing it to an agent) makes the switch smoother.
Bring your Recruitee 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.