ATS vs spreadsheet: when is it time to switch?
The signs your recruitment spreadsheet is breaking, what staying on it quietly costs you, and a practical way to switch to an ATS without losing pace.
On this page
Switch from spreadsheet to ATS when tracking breaks before recruiting does: duplicate candidates, missed follow-ups, no answer to “where did we leave this person”, and GDPR deletion requests you cannot execute cleanly. For most recruiters that happens somewhere between five and ten active roles, or the first time two people share the file.
What breaks first in a recruitment spreadsheet?
The status column. It is accurate the day you build it and drifts from reality within a week, because every update is a manual chore performed after the real work. Once you stop trusting the status column, you re-check everything against your inbox, which means the sheet is now decoration.
Then duplicates: the same candidate enters twice through different routes, and you only learn this after a double submission. Then attachments: CVs live in mail threads, downloads and a folder called “CVs new”, with no link to the row. Then versions: the file becomes Candidates_FINAL_v3, and a second person editing it ends the system entirely. Reporting never breaks because it never existed; a client asking “where are we” triggers twenty minutes of rebuilding.
The failures arrive in that order at almost every desk, which makes them a useful early-warning sequence.
What are the signs it is time to switch?
- You discovered a duplicate candidate after submitting them.
- A promised follow-up surfaced weeks late, and it cost you goodwill or a placement.
- You answer status questions from your inbox, not the sheet.
- CVs are findable only by scrolling email.
- A second person needs access: a collaborator, a virtual assistant, a client.
- A GDPR deletion or access request would take an afternoon and still feel incomplete.
- You rebuild the same client overview by hand every week.
- Posting one job means logging in to several boards, one at a time.
Three or more and the spreadsheet is costing more than it saves. One or two, and you may genuinely be fine; we make the honest case for staying manual in do I need an ATS as an independent recruiter.
What does staying on a spreadsheet actually cost?
- Hours: retyping CVs, updating statuses, hunting attachments, rebuilding overviews. It is unbilled work that grows with every active role.
- Placements: a dropped follow-up is sometimes a dropped fee, and a year of decent ATS pricing costs less than one fee at almost any desk. That arithmetic, not features, is the real business case.
- Compliance: spreadsheets multiply copies, which makes retention limits and deletion requests genuinely hard to execute. Our guide to candidate data retention covers what you are actually required to do with old CVs.
- Reputation: slow or duplicate outreach reads as disinterest to candidates and disorganisation to clients.
Against that: a spreadsheet is free, instant and fully yours. Below roughly five active roles it remains a perfectly defensible choice. The mistake is not starting with a spreadsheet; it is staying six months past the point where it broke.
How do you switch without losing momentum?
- Export and clean. One CSV, obvious duplicates merged, dead rows dropped.
- Import with a safety net. Recruitifly’s migration runs a dry run first and supports rollback, so you see what will be created before anything is. Spreadsheet imports count as migrations too, not just ATS-to-ATS moves.
- Start live roles in the new system first. History can follow in a second pass.
- Make the spreadsheet read-only for a month. An archive, not an exit ramp.
- Switch on retention rules on day one, so the compliance debt stops growing the moment you move.
Choosing where to switch to is its own exercise: vendor questions, trial structure, exit checks. We keep the full list in how to choose an ATS: the checklist, built to be worked through in an afternoon.
On cost: this move does not require a big contract. Recruitifly’s solo tier is EUR 70 per month with unlimited jobs and migration tooling included; all tiers are public on the pricing page.
Recruitifly is in private beta. If your sheet is showing three or more of the signs above, talk to us and join the beta; bring the spreadsheet and we will show you what the dry-run import makes of it.
Frequently asked questions
How many active roles can a spreadsheet handle?
In practice about five concurrent searches, less if application volume is high. The constraint is not storage, it is maintenance: every status change, follow-up and duplicate check is manual work, and the first week you skip that work the sheet stops being trustworthy, which is when candidates start falling through.
Can I import my spreadsheet into an ATS?
Yes, this is a standard path. Export to CSV, clean obvious duplicates, and map your columns to the system's fields. Recruitifly's migration tooling runs a dry run first, shows you exactly what will be created, and supports rollback, so a messy first import does not pollute your new database.
Is it risky to keep candidate data in Excel under GDPR?
It raises your risk, because compliance is entirely manual. Copies multiply across downloads, email attachments and backups, so honouring a deletion request completely is hard, and proving retention limits is harder. If you stay on a spreadsheet, keep one master file, record consent and dates, and calendar a deletion routine.
Should I switch to an ATS mid-search or wait until it is quiet?
Move between searches if you can, but do not wait for a mythical quiet month. The practical approach is to start live roles in the new system, keep the spreadsheet read-only as an archive, and import historical candidates in a second pass. That keeps momentum while the switch happens.
Recruitifly Editorial
Editorial
Related reading
Adding LLM screening to your ATS without creating duplicate records
Layer LLM screening over your ATS without splitting your candidate data: one source of truth, stable ID sync, scores written back as fields, not copies.
Sourcing with adjacent job titles and skills
Searching one job title misses most of the market. A worked SRE example plus a repeatable method for mapping adjacent titles and skills for any role.
AI Act candidate disclosure: notice template
What to tell applicants when automated screening is used, under the EU AI Act and GDPR Articles 13, 14 and 22, plus a copy-paste disclosure notice template.
Want to see how this looks on your own data?
No hard promises. Just a straight conversation about exports, stages, and your current stack.
Contact us