Data migration
Plan your ATS data migration with the Leonar team
The fear of losing everything keeps a lot of agencies on a tool they no longer like. A planned data migration takes the guesswork out of switching. You prepare your exports, the Leonar team confirms what can be carried over, and nothing is fixed before we have seen a real file. This page tells you what to bring to that discussion.
Trusted by 400+ recruiting teams and agencies
Used by 300+ high-growth recruiting teams and agencies globally
What "data migration" really means when you switch ATS
A data migration moves your working memory from one tool to another. Your contacts, your client companies, your open deals, your CVs, and where possible your notes and your history. The real question is not the technical transfer. It is knowing what actually arrives on the other side.
Two paths exist in Leonar, and they do not fit every situation the same way. You can import your files yourself, self-service. Or you can hand the migration to our team, who work from your exports. Most agencies switching tools want both: import the simple records right away, and have the rest taken over.
The rest of this page separates clearly who does what, what you can expect, and what still has to be confirmed. The goal: that you can request a migration discussion already knowing what to bring. If you want to tidy your records first, our guide on how to clean your recruiting CRM saves time before the export.
Your migration plan in three clear responsibilities
A migration goes well when each side knows what it carries. Here is the split, in the order it happens.
1
You You supply the exports
You run the export from your current tool while you still have access. You gather a CSV file for your contacts, companies and deals, and your CVs as PDF, DOC or DOCX. That is the raw material of the migration, and it stays yours.
2
Leonar team The team confirms feasibility and scope
On the migration call, we look at a real export, source by source. Contacts come in through column mapping, CVs are reviewed before saving. For notes, attachments and pipeline history, we confirm what can be carried over instead of promising it in advance.
3
You You validate a sample, if you want one
This step is optional. If you want extra reassurance, we can agree a sample once we have looked at your exports together. You check how a contact, a CV and its available history land, then confirm the scope before any full migration runs. Nothing is prepared on a blanket promise.
This split describes a service discussion, not an automatic promise. No scope, no timeline and no volume are fixed before we have looked at a real export together.
What you import yourself, what the team takes over
Self-service imports cover the essentials right away. The assisted migration handles the volume and the cases that need confirming. The table below keeps a file import from being mistaken for a complete connector.
| Your data | Self-service | With assisted migration |
|---|---|---|
| Contacts, companies and deals | CSV import with column mapping | Carried over by the team from your exports |
| CVs (PDF, DOC, DOCX) | Batches of 20, reviewed before saving | Carried over by the team, sample on request |
| Notes, attachments, pipeline history | Not carried by a plain file import | Confirmed source by source on the call |
| Team-assisted takeover | You import yourself, at your own pace | Migration is included with an annual subscription, quote otherwise |
CSV import accepts CSV files for your contacts, companies and deals. CV import reads up to 20 files at a time and you review them before saving. Later, your contacts and project pipelines can also come back out in CSV, Excel or JSON, depending on the record type. The operational detail of the switch lives in our ATS migration checklist.
A concrete example: the attachments and history of a legacy ATS
Illustrative example
Take an agency leaving a legacy ATS. Its CVs sit in one place, its interview write-ups and pipeline history in another. This is a common setup, and it is exactly where the question "does everything come across?" is decided.
Contacts and companies export to CSV without trouble, and CVs reload in batches. Attachments and history, though, depend on how that specific tool stored them. You cannot guess it from a website page. You check it on a real export.
That is precisely the second step of the plan: the team confirms what is carried over source by source. If it helps, you can then agree an optional sample and validate it before the full migration. This example is illustrative. It describes no named tool and does not promise that attachments or history come across in every case.
Migration is included with an annual subscription
Data migration is included with an annual subscription; otherwise, we provide a quote. The quote is decided after the migration call, once the scope is confirmed on a real export. We attach no timeline, no volume and no connector to this offer until we have seen your files. The software itself keeps its public per-user pricing.
Common questions about data migration
How much does data migration cost?
Data migration is included with an annual subscription; otherwise, we provide a quote. The quote depends on your source and on the scope confirmed during the migration call. We do not set a price or a volume before looking at a real export.
Does all my data transfer automatically?
No, and nobody should promise that before seeing your files. Contacts, companies and deals come in through CSV import with column mapping. CVs load in batches of 20 PDF, DOC or DOCX files, reviewed before saving. For notes, attachments and pipeline history, what can be carried over is confirmed source by source during the migration call.
Does Leonar connect directly to my old tool?
Migration starts from your own exports, not from a connector wired into your old tool. You pull the files out of your current tool, then the Leonar team takes over your data from those exports. You stay in control of what you hand over.
Can I import my data myself without a call?
Yes. CSV import (contacts, companies, deals) with column mapping and CV import in batches of 20 are self-service in Leonar. The team-assisted takeover is there when you want to hand off a larger volume or confirm a precise scope before you switch.
How do I request a migration discussion?
Book a demo and say you are preparing a tool change. We look together at your current tool, the exports available and a realistic scope. When it helps, we agree on a sample you can validate before any full takeover.
Read before you switch tools
-
-
MigrationHow to Clean Your Recruiting CRM
-
Ready to plan your migration before you switch tools?
Book a demo, say you are preparing a migration, and leave with a realistic scope. If it helps, you can agree an optional sample to validate before you switch.
What you find after the migration
ATS for recruiting agencies
The base that carries your candidate pipelines once your data is migrated.
Recruiting CRM for agencies
Candidates and clients in one workspace, ready the moment migration ends.
Running an agency? See the whole picture on our recruiting agency software page.