Outgrowing Excel? How a Small HR Team Moves Candidate Tracking Into a Hiring System
A spreadsheet works for five candidates and breaks at fifty. The signs that a small HR team has outgrown Excel, how to choose between an ATS, a no-code base and an HR suite, and a step-by-step migration you can pilot on one open role.
Ece Badak • Oct 17, 2026 • 6 min read

Almost every small HR team starts tracking candidates in a spreadsheet. It is free, everyone knows how to use it, and for the first few roles it works.
Then the company grows. Three people share one file, candidates arrive by email, WhatsApp and three job boards, hiring managers ask for updates in chat, and the spreadsheet becomes the place where information goes to be out of date.
This guide is for a one- to five-person HR team that is ready to move on. It covers the signs you have outgrown the spreadsheet, how to choose what comes next, and how to move without stopping hiring for a month.
Signs you have outgrown the spreadsheet
You do not need a system because a blog said so. You need one when the spreadsheet starts costing you candidates or hours. Common signs:
- Two people edit the file at once, and someone's changes disappear.
- Candidates fall through the gaps. A good applicant waited two weeks because nobody owned the next step.
- Hiring managers cannot see their own candidates without asking HR.
- CVs live somewhere else, in inboxes and download folders, not next to the candidate's row.
- You cannot answer simple questions, such as how long hiring takes, or where candidates come from, without an afternoon of work.
- Data protection is a worry. You are not sure who has a copy of which CV, or when you should delete it.
If three or more of these sound familiar, the spreadsheet is already more expensive than a tool.
Your three options
| Option | Good for | Watch out for |
|---|---|---|
| Applicant tracking system (ATS) | Teams that hire every month and want job posts, applications, pipelines and interviews in one place | Big ATS products can be more than a small team needs. Look for one built for your size. |
| No-code database (for example Airtable or Notion) | Teams that hire rarely and like building their own tools | You build and maintain everything yourself, including permissions and data deletion. |
| HR suite with a recruiting module | Companies that already use the suite for payroll and HR records | Recruiting modules are often basic, with limited screening and interview features. |
For most small teams that hire regularly, an ATS or an all-in-one hiring tool is the right step. A no-code base is a reasonable middle step if you hire a few people a year.
Step 1: Clean the spreadsheet before you move it
Do not move a mess into a new system. Before the migration:
- Decide which candidates to move. Usually: everyone in an active process, plus past candidates you would contact again and have permission to keep.
- Delete what you should not keep. Under GDPR and similar laws, you should not keep candidate data longer than you need it or without a legal basis. A migration is the right moment to delete old rows.
- Remove duplicates and fix obvious errors such as phone numbers in the email column.
Step 2: Map your columns to the new system
Most spreadsheets have similar columns. Map each one before you import:
| Spreadsheet column | New system field |
|---|---|
| Name, email, phone | Candidate profile |
| Role applied for | Job or pipeline |
| Status ("called", "2nd int", "offer?") | Pipeline stage |
| Source ("LinkedIn", "referral") | Source |
| Notes | Notes or activity history |
| CV link or file name | Attached CV |
| Interviewer, date | Interview record |
The status column needs the most work. Spreadsheet statuses grow organically, and a file often has fifteen of them. Agree on five to seven pipeline stages first, for example: Applied, Screened, First interview, Team interview, Offer, Hired, Rejected. Then map every old status to one of them.
Step 3: Decide who sees what
A spreadsheet shared with the whole company is a data protection risk. In the new system, set access before you invite anyone:
- HR: all roles and candidates.
- Hiring managers: only their own roles.
- Interviewers: only the candidates they interview, and only what they need.
Step 4: Pilot on one open role
Do not move everything at once. Pick one open role with a cooperative hiring manager and run it entirely in the new system for two to three weeks:
- Post the job, or point applicants to the new system's apply page.
- Upload the CVs you already have for that role.
- Move candidates through the stages you agreed.
- Run interviews and collect feedback in the system, not in chat.
- At the end, ask the hiring manager and the team what was easier and what was harder.
Fix what the pilot shows, then move the other roles.
Step 5: Switch off the spreadsheet
The most common migration failure is running both for months. People keep updating the spreadsheet "just in case", and the new system is always half wrong.
Pick a date. After that date, the spreadsheet is read-only, and then it is archived and deleted according to your retention rules.
What to look for in a tool for a small team
- Fast setup. You should be able to post your first job the same day.
- Bulk CV upload, because you will start with a folder of CVs.
- Screening help. When one post brings 200 applicants, a small team cannot read every CV carefully.
- Hiring manager access that is simple enough that managers actually use it.
- Interview notes and feedback in the same place as the candidate.
- Clear data handling: where data is stored, how to delete it and who can see it.
Where Firstview fits
Firstview is recruiting software for small businesses and in-house HR teams. It covers the ATS basics, so you can run job posts, applications, the hiring pipeline and interviews in one place without a separate ATS. On top of that:
- Bulk upload: upload CVs as PDF, DOCX or TXT, or one merged PDF that Firstview splits into candidates. Duplicates are skipped.
- CV screening with reasons: every CV is read against the role's criteria, with a reason for each one, so a two-person team does not have to read 200 CVs line by line. A person always decides.
- AI first interviews: candidates take a live voice interview whenever they are ready, so first rounds do not wait for your calendar.
- Hiring managers see only their own roles, get their pending actions and add a team score in one thread.
It works the same for one HR person or a full talent team.


