Moving off YC's Work at a Startup ATS

Getting your data out of Work at a Startup

What YC and the vendors it connects with document about moving candidates out, checked on November 18, 2026. Each step links to the page it comes from.

  1. 1

    Start from what YC publishes. Its recruiting tools page describes job postings, pre-defined stages and team invites, and says nothing about exporting your data. The Work at a Startup integrations page needs a YC login, so the full list of connected tools is not public.

  2. 2

    If you move to Ashby, its guide has you paste an Ashby API key into Work at a Startup, then export candidates one at a time from their Work at a Startup profile with the Export button, choosing the job. They arrive in Ashby at the New Lead stage. The guide describes no bulk export.

  3. 3

    If you move to Dover, its guide connects from the Work at a Startup integrations page. Jobs sync and new applicants import on their own, but candidates who were already in a Work at a Startup job before the sync do not appear in Dover. Single candidates can be sent across from the Work at a Startup inbox with Export to ATS.

  4. 4

    If you move to Gem, its guide has you paste a Gem access key under Settings, then Integrations, in Work at a Startup and map each Work at a Startup job to a Gem job. New applicants then appear in Gem at Application Review, and interested prospects can be exported to a Gem job.

  5. 5

    For any other ATS, one route we have not run end to end is Bookface MCP, if YC has turned it on for your account. YC's hosted MCP server gives an AI agent Work at a Startup tools to list applicants by job, read each candidate's profile and internal notes, read whole pipelines, list jobs, and read a job's applicants with their answers and resume links.

Watch the deadlines

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.

If YC has turned on Bookface MCP for your account, your AI agent can read each job, its applicants and their pipeline stage, and turn them into rows for candidates, jobs and applications for the dry run. We have not run this route end to end. Keep your own copy of anything the import does not take, such as internal notes and resumes, so that history stays with your team.

Your AI 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 your AI 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.

Which ATSs connect to Work at a Startup

On November 18, 2026, the Work at a Startup integration guides we found were Ashby's, Dover's and Gem's; YC's full list needs a YC login. Ashby moves candidates one at a time from their profile. Dover syncs jobs and new applicants, but not candidates who applied before you connected. Gem brings new applicants into mapped Gem jobs. Yardstick has no Work at a Startup integration. One route, which we have not run end to end: if YC has turned on Bookface MCP for your account, your AI agent can read your candidates through it, turn them into rows for candidates, jobs and applications, and run Yardstick's dry run, so you see what will be created before anything is written.

Who should move — and who shouldn’t.

If Work at a Startup still covers your hiring, there is no reason to move. If you have hired a recruiter who needs more than a job board's pipeline, teams like yours move to Yardstick when they want an AI-designed interview guide and scorecard for every role, a bill that follows the number of open roles, and an ATS their AI agent can operate. Your first 3 Jobs are free, and the free plan does not expire. After your third Job, Core is $49 a month plus $29 per open role, billed monthly.

Common questions about leaving Work at a Startup.

Which ATS should a YC startup move to after the Work at a Startup ATS?

It depends on how you want candidates to travel. The Work at a Startup integration guides we found on November 18, 2026 are Ashby's, Dover's and Gem's, so candidates can move across from inside Work at a Startup. An ATS without a Work at a Startup integration, including Yardstick, means taking candidates out yourself, because YC documents no file export. For Yardstick, one route we have not run end to end: if YC has turned on Bookface MCP for your account, your AI agent reads your candidates through it and runs a preview-first import that a person on your team approves.

Can I export my candidates from Work at a Startup to a CSV?

YC's public pages describe no CSV or file export, as of November 18, 2026. The documented ways out are the Export button for a connected ATS (one candidate at a time in Ashby's and Dover's guides) and YC's Bookface MCP, which, if YC has turned it on for your account, lets an AI agent read applicants, notes, pipelines and jobs. If YC adds an export, it will be on its own pages, so check there first.

How do I move from Work at a Startup to Yardstick?

Yardstick has no Work at a Startup integration. One route, which we have not run end to end: if YC has turned on Bookface MCP for your account, connect your AI agent to it and to Yardstick. The agent can read your jobs, applicants and stages, turn them into import rows, and run Yardstick's dry run. You read the preview and approve it before anything is written.

What does Yardstick cost after a free ATS?

Your first 3 Jobs are free, and the free plan does not expire. After your third Job, Core is $49 a month plus $29 per open role, billed monthly. Closed or archived Jobs are not billed.

Bring your Work at a Startup 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.