Switching to Yardstick
Your candidates, jobs, and applications come with you — and you see exactly what the import will do before it does anything.
Leaving an ATS usually means a services project: export requests, spreadsheet archaeology, weeks of back-and-forth, and quiet data loss along the way. Yardstick's importer works differently. You export from your current system, run a dry run, and read a row-by-row preview of exactly what will be created. Nothing is written until you approve that preview — and if you'd rather not do any of it by hand, your coding agent can run the whole migration for you.
What comes with you
Every ATS holds the same three things you actually care about: the people, the roles, and the history connecting them. The import covers all three.
The people in your pipeline, past and present. Once they're in, past candidates can be organized into talent pools so their history keeps working for you.
The roles they were attached to.
Which candidate was in which stage of which job.
When an import is applied, Yardstick creates the people, jobs, and applications from your export, plus 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 you still have to wire up. That's the scope: it's the pipeline itself that moves — not your old system's notes, attachments, or interview history.
Two ways to run the move
The importer is part of Yardstick's public API and the yardstick CLI — the same surfaces agents already use to operate Yardstick, available on every account. So instead of working through the CSVs yourself, you can hand your exports to a coding agent (Claude Code, Codex, or similar) and ask it to move you in. The agent converts each CSV into structured rows, drives the dry run through the CLI or API, and brings you the preview. You read it and approve; the agent applies it.
That's the same division of labor Yardstick is built on everywhere: agents prepare the work, and humans approve it.
Coming from Greenhouse? Its export arrives as a .zip archive, and the importer has a dedicated path for it — your agent uploads the archive and previews it directly, no CSV wrangling required.
Built to be predictable
Migration is where trust in a new system starts, so the importer is built to be predictable in the ways that matter.
The apply step is pinned to the exact preview you approved. If the preview changes, the apply doesn't run.
The only automatic match is an exact candidate email in your own account. Anything fuzzy — a near-duplicate person, an uncertain stage mapping — waits for your explicit decision.
Imports are idempotent: replaying an apply doesn't duplicate your data.
An import creates records. It never emails a candidate, never merges people, never deletes anything.
What you're switching to
It's what your hiring runs on afterward. Yardstick is a structured-interview ATS: job-specific interview plans, consistent interviews, scorecards on every candidate, and AI decision briefs drafted from interview evidence with the hiring team making the calls. And it's built for agents as well as humans — the same API and CLI that import your data let your agent inspect pipelines, prepare actions, and draft updates, always under your approval.
Pricing follows the same no-drama principle as the import: pay-as-you-go for active hiring — no seats, no lock-in.
Weighing a specific move? See how Yardstick compares to Greenhouse, Workable, and Ashby.
FAQ
Candidates, jobs, and applications — the people in your pipeline, the roles they belong to, and where each person stands in each role. Applying an import also creates job postings and starter interview plans for the imported roles.
Yes. The importer is part of Yardstick's public API and the yardstick CLI on every account, so a coding agent can convert your ATS 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.
The importer auto-matches only on an exact candidate email already in your account. Every fuzzy match — a similar name, an unclear pipeline stage — is surfaced in the dry-run preview for you to decide explicitly. Nothing is merged behind your back.
No — you need an export. If you can download CSVs from your current ATS, you (or your agent) can dry-run an import and read the preview before applying it.
The work scales with your export, not with a vendor's services queue. As soon as you have your export, you (or your agent) can dry-run the import and read the preview; applying it writes exactly what the preview showed. There's no engagement to schedule and nobody to wait on.
No. An import creates records from your export. It never contacts candidates, never merges existing people, and never deletes anything.
.webp?dpl=dpl_72As55GvZTNYQn4FeTD38sqLSYSu)