All articles

Switching ATS without losing your database: a migration checklist

How to move an agency from spreadsheets or an old applicant tracking system to a new one, in the right order, without losing candidates, history or the team's trust.

By Kevin Thibaut 7 min read

Most agencies do not change their ATS because they found a better one. They change because the current setup has become painful: a database nobody trusts, emails scattered across personal inboxes, a pipeline that lives half in the tool and half in a spreadsheet. The fear that stops them is always the same. “What if we lose everything in the move?”

You will not, if you do it in the right order. This checklist is the order we recommend, whether they are coming from spreadsheets or from another applicant tracking system.

Before you export anything

Decide what you actually want to keep

A migration is the best chance you will get to clean up. Before exporting, agree as a team on what is worth bringing across:

  • Candidates you have been in touch with recently, or who are in an active process.
  • Clients and contacts, with the jobs that are open or on hold.
  • Notes and history for candidates you are likely to work with again.

Then look at what you should not bring. Profiles nobody has touched in years, with no consent or legitimate reason to keep them, are a GDPR liability rather than an asset. If you have a retention policy, apply it now. If you do not have one, this is the moment to write it.

List every place data lives today

The ATS is rarely the only source. Make a list:

  • The ATS or spreadsheet itself
  • CV folders on a shared drive or in email attachments
  • Personal inboxes with candidate conversations
  • LinkedIn, where a lot of the real relationship history sits
  • Notes in documents, notebooks or a separate CRM

Anything not on the list will be left behind.

Exporting and cleaning

Export in the most complete format you can get

Ask your current vendor for a full export: candidates, contacts, jobs, pipeline stages, notes, and the original CV files. A CSV of names and emails without the documents is not a backup. If the vendor charges for exports or limits them, find out early, before you are under time pressure.

Remove duplicates before import, not after

The same candidate often exists two or three times: once from an application, once from a LinkedIn import, once typed in by hand. Merge duplicates on email address and phone number before you import. Many ATS, Digger included, flag likely duplicates on import, but starting clean is always faster.

Map your pipeline stages

Write down the stages you use today and how they translate to the new tool. This is also a good time to simplify. Many agencies find that a pipeline with fifteen stages is really six stages and a lot of exceptions.

Running the switch

Start with a sample

Import a small, representative set first: a few hundred candidates, two or three open jobs, one client. Check that names, documents, notes and stages came across correctly. Fix the mapping, then import the rest. With Digger, the 30-day free trial is the right place to do this test with your real data.

Connect email, calendar and LinkedIn on day one

The new ATS only stays accurate if conversations flow into it automatically. Connect each recruiter’s mailbox and calendar, and install any browser extension for LinkedIn, before the team starts working in the tool. Otherwise the old habits come straight back.

Pick a cut-over date and stick to it

Running two systems in parallel for weeks is how data ends up split between them. Choose a date. Before it, the old system is the reference. After it, every new candidate, note and message goes into the new one, and the old system becomes read-only.

Train on real work, not on a demo

An hour of training on a demo account is forgotten by Friday. Instead, have each recruiter move one of their own open jobs into the new tool with someone who knows it sitting next to them. They learn the parts they will use every day, on candidates they care about.

After the move

Check what the team is not using

After two weeks, look at what is and is not happening in the new tool. If one recruiter is not logging calls, or notes are still going into a spreadsheet, ask why. It is usually a small friction that can be fixed, not resistance to change.

Keep the old export, then delete it

Keep a secure copy of the final export from the old system for as long as your retention policy allows, in case something turns out to be missing. Then delete it. A forgotten export on a shared drive is exactly the kind of copy that causes GDPR trouble later.

Close the old account properly

Make sure the old vendor deletes your data at the end of the contract, and ask for written confirmation. Under your data processing agreement, they should.

The short version

  1. Decide what to keep, and what to let go of.
  2. List every place data lives today.
  3. Export everything, including the original files.
  4. Remove duplicates and map your stages.
  5. Import a sample, check it, then import the rest.
  6. Connect email, calendar and LinkedIn from the first day.
  7. Cut over on a fixed date.
  8. Train on real jobs.
  9. Review after two weeks, then clean up the old data.

If you are considering Digger, our comparison pages cover how it differs from the ATS agencies most often move from, and you can book a call to talk through your migration with the team.

Try it on your next open role

Import your CVs, open a job and see ranked, explained candidates in the first hour.

Start free trial

30-day free trial. Cancel anytime.