Home/Migrations/ATS migration
Migrations

ATS migration that keeps every candidate, note and placement.

Switching from Bullhorn to Loxo, Lever to Ashby, or merging two databases after an acquisition? Remqa's engineers move your candidates, resumes, notes and pipelines, clean up duplicates on the way and switch your recruiters over without losing a day.

In short

Remqa migrates ATS and recruiting CRM data between Bullhorn, Loxo, Recruit CRM, Greenhouse, Lever, Ashby and similar systems. Candidates, resumes, notes, submissions, jobs and placements are moved with history intact, duplicates are merged, and recruiters verify real records before cutover.

  • Resumes and files stay linked to the right candidate
  • Duplicates are matched on email, phone, name and profile links
  • Recruiters keep working during the test run
  • The old ATS stays read-only until sign-off

Why ATS migrations are harder than they look

A recruiting database is years of relationships. The value is in the notes, the past submissions, the placement history and the resumes, not just the names. Standard import tools tend to bring over the contact record and leave the history behind. Recruiters then spend months searching two systems.

What we migrate

  • Candidates and contacts: profiles, contact details, tags, sources and owners
  • Resumes and files: every attachment linked to the right candidate, with parsed text where the new system supports it
  • History: notes, emails, call logs, submissions, interviews and placements with original dates
  • Jobs and clients: companies, client contacts, jobs and pipelines with stage mapping
  • Hygiene: duplicate candidates merged, bounced emails flagged, inconsistent titles and locations normalised

Systems we work with

Bullhorn, Loxo, Recruit CRM, Greenhouse, Lever, Ashby, Workable, JobAdder, Crelate, Vincere, Zoho Recruit and spreadsheets. If your system has an API or a full data export, we can work with it.

How an ATS migration runs

1

Map. Every object, field, owner, stage and file is mapped from old to new. You sign off on the map before anything moves.

2

Test run. A full trial migration into a sandbox or a copy of the new system, so problems show up before go-live, not after.

3

Verify. Record counts reconciled, relationships checked, and spot checks on real records with your team.

4

Cut over. A planned switch with a short freeze window, then a final delta sync for anything that changed during the test run.

5

Keep the old system read-only. Nothing is deleted until you are happy with the new one.

Where AI helps

Recruiting data is messy. We use AI to match duplicate candidates that differ by an email or a nickname, normalise job titles and locations, and map custom fields and stages between systems. Engineers review the rules, and your team spot-checks real candidates before cutover.

Doing the groundwork yourself? Our ATS migration checklist walks through what to export, what to clean and what to test.

After the move

A new ATS is a good moment to stop the copy and paste between tools. Once your data is in one clean place, our AI recruiting agents can run sourcing, outreach, screening and scheduling on top of it.

FAQ

Common questions.

Can you migrate out of Bullhorn?

Yes. We work from Bullhorn's API or a full data export, depending on what your contract and plan allow, and move candidates, notes, files, jobs and placements.

Will resumes and attachments come across?

Yes. Files are migrated and linked to the same candidate or contact in the new system, and we verify file counts before cutover.

How do you handle duplicate candidates?

We match on email, phone, name and profile links, review uncertain matches with your team and merge before import so the new system starts clean.

Do recruiters lose time during the switch?

Very little. Recruiters keep working in the old system during the test run, then there is a short freeze and a final sync at cutover.

What happens to the old ATS?

It stays read-only until you sign off. Nothing is deleted until you say so.

Talk to an engineer

Tell us what you are moving.

In 30 minutes we look at your current system, where you want to go and what could go wrong. You leave with a plan, whether or not you work with us.

Book a free migration call
30 minutesFree, with an engineer
Your stackWe look at what you run today
Straight answerIncluding when we're not the fit