Blog

The spreadsheet-to-ATS migration guide (without losing your mind)

Still hiring from a spreadsheet? Here's how to switch to an ATS in under an hour: what to bring, what to leave behind, and how to set up your first pipeline.

Your spreadsheet started as a quick fix. A few columns for candidate names, emails, and interview dates. Maybe a color-coding system for pipeline stages. It worked fine when you had two open roles and ten applicants.

Now you have seven open roles, three hiring managers asking for updates, and a sheet with 47 columns that takes four seconds to load. You know you need a real tool. But the idea of migrating everything feels like a weekend project you'll never get to.

Here's the truth: most teams move from a spreadsheet to a working ATS pipeline in under an hour. The trick is knowing what to bring, what to leave behind, and what to set up first.

Signs your spreadsheet has hit its limit

You don't need a consultant to tell you when your spreadsheet stops working. You already know. But here are the signs, so you can stop pretending it's fine.

You've built a color-coding system. Green for "active," yellow for "waiting on feedback," red for "rejected," blue for... something you defined three months ago and forgot. Your spreadsheet now has a legend row at the top, and you're the only person who understands it.

You Ctrl+F for candidate names. When your hiring manager asks "where are we with that backend engineer from last week?" you open the sheet, hit Ctrl+F, type a partial name, and scroll through twelve matches. This takes 30 seconds when it should take zero.

You forgot to reply to someone. Not because you don't care. Because the email thread lives in Gmail, the candidate status lives in the sheet, and nothing connects the two. You found the missed reply three days later. The candidate had already accepted another offer.

Scheduling lives somewhere else entirely. Your sheet tracks who needs an interview. Your calendar tracks when. Your email tracks the back-and-forth to find a time. Three tools, zero connection between them. Every interview takes five to eight emails to book.

Multiple people edit the same file. Two recruiters. One sheet. Someone overwrites a status update. Someone else sorts a column and breaks the formulas. You spend 15 minutes figuring out what changed and who changed it.

If three or more of these sound familiar, you're past the spreadsheet's useful life. Not because spreadsheets are bad tools. They're fine tools for many jobs. Hiring pipeline management at scale isn't one of them.

What to bring with you

Moving to an ATS doesn't mean recreating your spreadsheet inside a new tool. Most of what's in your sheet right now is either outdated, redundant, or a workaround for features you didn't have.

Here's what's worth bringing:

Active candidates. Anyone currently in your pipeline: people you're screening, interviewing, or about to make an offer to. These are the records that matter on day one.

Your talent pool contacts. Strong candidates who didn't get the role but you'd consider for future positions. If you've been keeping a "maybe later" tab, this is the content worth preserving.

Your pipeline stage names. You've already figured out what stages your hiring process needs. Applied, Phone Screen, Technical Interview, Final Round, Offer. Whatever your version looks like, bring that structure with you. It's earned knowledge.

Email templates you reuse. That rejection email you spent an hour wordsmithing. The interview confirmation template. The "we're still deciding" message. These save time in any tool.

Here's what to leave behind:

Old candidate data. Those 200 rows from 2024 that you'll "maybe reference someday"? You won't. Start clean. If you need historical data later, your spreadsheet isn't going anywhere.

Formula hacks that simulate automation. The VLOOKUP that calculates days-in-stage. The conditional formula that flags overdue follow-ups. These were clever solutions to missing features. Your ATS handles this natively.

Conditional formatting that's become your UI. If your spreadsheet relies on 15 formatting rules to be usable, that's a sign the tool isn't the right one for the job. You don't need to recreate that visual system. A proper pipeline view replaces it.

What to set up first

The biggest mistake teams make when switching to an ATS: trying to configure everything before they start using it. You don't need the perfect setup on day one. You need a working setup.

Here's the priority order for your first session:

1. Build your pipeline stages. Keep it simple. Five stages cover most hiring processes: Applied, Screen, Interview, Offer, Hired. You can add stages later as your hiring process matures. Don't spend 45 minutes debating whether "Technical Assessment" deserves its own stage. It can wait.

2. Import your active candidates. Export your spreadsheet to CSV. Map your columns to the ATS fields (name, email, current stage, position). Import. This is the single highest-value action because it means you're working from the new tool immediately, not running two systems in parallel.

3. Connect your email. This is the feature that changes everything. When your email lives inside the ATS, every message you send or receive is attached to the candidate's profile. No more switching between Gmail and your spreadsheet. No more missed replies.

4. Connect your calendar. Link your Google Calendar so interviews show up in both places. Set up your availability rules so candidates can book time through a scheduling link instead of a five-email chain.

5. Set up one automation. Start with something small: auto-send a confirmation email when someone applies, or notify a hiring manager when a candidate reaches the interview stage. One automation on day one shows you how the system works without overwhelming you.

6. Build your careers page. This is optional for day one but high-impact. A branded careers page where candidates can browse open roles and apply directly feeds candidates into your pipeline automatically. No more forwarding resumes from your inbox. If you want to go deeper on this, read the guide to careers pages that convert.

The 30-minute migration

Here's what this looks like in practice, using Bringboard as the example.

Minutes 0-5: Export and clean your spreadsheet. Open your Google Sheet or Excel file. Delete the columns you don't need (those formula hacks, the color-coding legend row, the "notes to self" column). Keep: name, email, phone, current stage, position, and any custom fields you care about. Export to CSV.

Minutes 5-10: Create your pipeline. In Bringboard, create a position for each open role. Set up your stages. If you're unsure, start with the default five-stage pipeline and customize later. Drag to reorder. Done.

Minutes 10-15: Import candidates. Upload your CSV. Map each column to the corresponding field. Bringboard shows you a preview before importing, so you can catch mismatches. Hit import. Your candidates land in the right positions at the right stages.

Minutes 15-20: Connect email and calendar. Add your email sending domain so messages come from your address, not a generic no-reply. Connect Google Calendar for scheduling. Set your availability windows.

Minutes 20-25: Send your first email from the tool. Pick a candidate who needs a follow-up. Open their profile. Write the email (or pick a template). Send it. The message now lives on their timeline, visible to your whole team. No more forwarding threads.

Minutes 25-30: Set up your first automation. Go to automations. Create a rule: when a candidate moves to "Interview," send a calendar booking link. Save it. You've eliminated the most time-consuming part of your old workflow.

That's it. Thirty minutes, and your hiring runs from a real tool.

What changes on day two

The first morning after migration feels different. Here's what you'll notice.

No more Ctrl+F. Search by name, email, position, or stage. Results in under a second. Your hiring manager asks about a candidate, and you pull up their full profile, including every email, note, and interview, in one click.

Email history lives on the candidate. Open any candidate profile and see every message exchanged, who sent it, and when. No more digging through Gmail threads to figure out where a conversation left off.

Scheduling takes one message, not five. Send a booking link. The candidate picks a time from your available slots. The interview shows up on both calendars with a video meeting link attached. The entire process that used to take 48 hours of back-and-forth now takes one email and one click.

Your careers page is live. Candidates find your open roles, read descriptions, and apply through a form that feeds directly into your pipeline. No more "send your resume to careers@" and manually creating rows.

Your hiring manager can check the pipeline themselves. Instead of pinging you for a status update, they open Bringboard and see exactly where every candidate stands. Fewer Slack messages. Fewer "quick check-in" meetings about hiring.

The learning curve is real but short. Most teams report feeling comfortable within two to three days. By the end of the first week, the spreadsheet feels like a relic.

The right time to switch

The best time to move from a spreadsheet to an ATS was before you needed to. Before you lost that candidate to a slow process. Before the sheet broke during a critical hiring push.

The second best time is now, while you have a manageable number of open roles. Migration at five open positions takes 30 minutes. Migration at 25 open positions takes a full afternoon and a lot more cleanup.

You don't need an enterprise platform to make this switch. Most growing teams are better served by a right-sized tool that matches how they hire today, not a system built for 10,000-employee companies.

Bringboard is free during beta. No implementation timeline. No onboarding calls. No feature gates. Sign up, import your candidates, and start hiring from a real tool today.

Start your free migration →

Ava Stavros

Head of Content at Bringboard

Recruited for three startups before any of them had an ATS. Spent too many hours wrangling spreadsheets, chasing scheduling emails, and explaining to founders why "just post it on LinkedIn" isn't a hiring strategy. Now writes about what growing teams get wrong about hiring, and how to fix it without buying software built for Fortune 500 companies.

Keep readingAll posts →