This guide explains how to migrate data from a previous ATS or CRM to Manatal. It covers the available migration options, the migration process, and the types of data that can be transferred from supported systems.
Choosing Your Migration Method
Manatal offers two ways to bring your data into your Manatal account:
| Self-Data Import | Manatal Executed Migration | |
|---|---|---|
| Data size | Small | Large and complex |
| Who does the work | You | Manatal's migration team |
| Technical requirement | Comfortable preparing CSV or JSON files | Exporting Data from your Legacy System |
| Full historical migration | Partial | Yes |
| Best for | Quick, focused imports | Complete legacy ATS migrations |
Self-Data Import
If you want to move quickly and don't want to wait for our migration team, the Self-Data Import tool allows you to upload data directly into Manatal on your own schedule.
Use the Self-Data Import when:
- You have a limited number of records to import
- You are comfortable preparing structured CSV or JSON files
Ready to get started? Check out our step-by-step instructions in the Self-Data Import guide.
Manatal Executed Migration
A Manatal Executed Migration is our fully supported service. Our dedicated Data Migration Team handles the heavy lifting, including the extraction, mapping, and final upload of your data.
Eligibility Requirements
Before starting your migration, you will need to confirm your eligibility with your Manatal Point of Contact.
Your Point of Contact will verify:
- Your subscription plan includes migration support
- Your legacy system is on our supported systems list (or qualifies for a custom migration)
To check your eligibility, contact your Dedicated Customer Success Point of Contact or email sales@manatal.com.
Before You Start
A clean, complete export from your previous system is the single biggest factor in a smooth migration. Before you begin, prepare both platforms:
In your previous system:
- Wrap up open activities: Finalize any in-progress updates in your old ATS before exporting, so the data you send is current and complete. Once your export is taken, any changes made in the old system afterward will not be captured.
- Export your full dataset: Download all of your data, making sure to include candidate attachments (resumes, CVs, etc.) if your legacy system allows it.
- Note your data cut-off point. The export is a snapshot in time. The date you generate it becomes your cut-off; activity in your old system after that date won't be migrated.
In your Manatal account:
- Your Manatal account has been created.
- Your users have been invited.
You do not need to configure pipeline stages, custom fields, or other settings in advance.
What We Need From You
To keep your migration on schedule, we'll need you to be available and responsive at a few key points. Delays on these steps will extend your timeline.
| We'll ask you to | Why it matters |
|---|---|
| Provide your exported data | Nothing can begin until the migration team has your data |
| Confirm mapping (stage and user mapping) | We map your old pipeline stages and user accounts to Manatal. We'll share these for your sign-off, and we can't proceed until they're confirmed |
| Review and approve the preview | You verify the imported data in a test environment before it goes live |
Migration Support and Assistance
Throughout the import process, your dedicated Customer Success Point of Contact and Data Migration Team will be available to answer your questions and guide you.
Migration process
| Step | Who | What happens |
|---|---|---|
| 1 | You | Export your data from your legacy system |
| 2 | You | Contact your dedicated Customer Success Point of Contact to request a Manatal executed data migration |
| 3 | You | Provide the exported data from your legacy system to Manatal’s Data Migration Team. |
| 4 | Data Migration Team | Extracts your data and maps it to Manatal's data structure |
| 5 | Data Migration Team | Uploads your data into a test environment so you can review everything before it goes live |
| 6 | You & Data Migration Team | Our team shares a preview of the imported data and mapping files for your review. You may also be asked to provide or confirm mapping details, such as stage and user mapping. |
| 7 | You | Review and confirm the mapping is correct within 5 working days. |
| 8 | Data Migration Team | Imports the approved data into your live Manatal account. |
| 9 | You | Review and confirm the imported data is correct within 14 working days |
Supported Standard Systems
Manatal currently supports 14 standard systems for Manatal Executed Migration. Standard systems have pre-built mapping templates, which means faster processing and a more predictable outcome.
If you don't see your system on this list, contact your dedicated Customer Success Point of Contact to clarify eligibility. We may still be able to migrate your data through a custom migration process.
| ATS System | Support Contact | Migration Details |
|---|---|---|
| Bullhorn | Bullhorn Support Portal | Bullhorn to Manatal Migration Guide |
| CATS | CATS Help Center | CATS to Manatal Migration Guide |
| Ceipal | Ceipal Support | Ceipal to Manatal Migration Guide |
| Crelate | Crelate Support | Crelate to Manatal Migration Guide |
| FreshTeam | FreshTeam Help Center | FreshTeam to Manatal Migration Guide |
| JazzHR | JazzHR Help Center | JazzHR to Manatal Migration Guide |
| JobAdder | JobAdder Help Center | JobAdder to Manatal Migration Guide |
| Lever | Lever Support | Lever to Manatal Migration Guide |
| Loxo | Loxo Support | Loxo to Manatal Migration Guide |
| Teamtailor | Teamtailor Help Center | Teamtailor to Manatal Migration Guide |
| Trakstar | Trakstar Support | Trakstar to Manatal Migration Guide |
| Vincere | Vincere Customer Support | Vincere to Manatal Migration Guide |
| Workable | Workable Support | Workable to Manatal Migration Guide |
| Zoho Recruit | Zoho Recruit Support | Zoho Recruit to Manatal Migration Guide |
What We Import
The following data is commonly imported during a Manatal Executed Migration. Exact fields and availability vary by system - refer to your system's migration guide for details:
- Organizations - name, address, industry, website, and general company information
- Candidates - name, contact details, current role, work history, education, and skills
- Jobs - title, description, location, status, and salary information
- Contacts - name, email, phone, and linked organization
- Matches- pipeline stage, and key dates
- Attachments - resumes, CVs, and supporting documents
- Notes - recruiter notes, comments, and activity history
- Custom Fields - Coordinate with the migration team to define which additional custom fields need to be included in the import scope.
What we do not import
The following data is not imported regardless of which ATS system you are migrating from:
- Deleted or archived records
- Internal system tracking fields and audit logs
- Interview scheduling data and calendar events
- Email correspondence and message threads
- Configurations
- User permission settings and access levels
Migration Term Glossary
Different ATS systems use different names for the same concepts. This table shows how your system's terminology maps to Manatal.
| ATS System | Organizations | Candidates | Jobs | Contacts | Matches |
|---|---|---|---|---|---|
| Bullhorn | ClientCorporation | Candidate | JobOpening | Contact | JobResponse |
| CATS | Organization | Candidate | Position | Contact | Submission |
| Ceipal | Client | Candidate | Job | Contact | Application |
| Crelate | Account | Contact | Job | Contact | WorkflowItem |
| FreshTeam | Company | Candidate | Job | Contact | Application |
| JazzHR | Department | Candidate | Job | Contact | Application |
| JobAdder | Company | Candidate | Job Order | Contact | Application |
| Lever | Posting Team | Contact | Posting | Contact | Opportunity |
| Loxo | Organization | Candidate | Job | Contact | Application |
| Team Tailor | Company | Candidate | Job | Contact | Application |
| Trakstar | Opening Team | Candidate | Opening | Contact | Application |
| Vincere | Organization | Candidate | Job | Contact | Application |
| Workable | Company | Candidate | Job | Contact | Application |
| Zoho Recruit | Client | Candidate | Job Opening | Contact | Job Application |
FAQ
1. What is my data cut-off date?
- Your export is a snapshot taken at a single point in time. The moment you generate it from your previous system, that becomes your cut-off date. Any activity in your previous system after that point (new candidates, status changes, notes) won't be included. For this reason, we recommend wrapping up activity in your old system right before you export.
2. What happens if I want to make a change after I’ve already confirmed the mapping file?
- Once you provide written consent to proceed with the migration, no changes can be made to the mapping. This is to avoid inconsistencies and ensure data integrity throughout the migration. We recommend reviewing the mapping carefully with all necessary stakeholders before confirming.
3. If I forget to share some of the data initially, can I send it later?
- We encourage you to share all data in one complete package at the beginning of the process. If additional data is sent later, it may require a rework of the mapping and could impact timelines. In most cases, a second migration process will be scoped separately.
4. What if my system isn't on the supported list?
- Contact your dedicated Customer Success Point of Contact. We may still be able to migrate your data through a custom migration process.
5. How long will my migration take?
- Most migrations commonly take between 2 to 4 weeks from when we receive your data. The biggest factors are the size and complexity of your data and how quickly mapping and preview are confirmed on your side.
The final timeline will be confirmed by the Manatal Data Migration team that is applicable to your migration.
6. How much time should I expect to dedicate as a client during the entire migration process?
-
Most of the effort required from your side will be in the early stages - specifically during data sharing, mapping review, and mapping approval. The actual migration and post-migration activities are handled by our team. We recommend setting aside time for:
- Data gathering and formatting
- Reviewing the mapping file and providing timely approval
- A post-migration review within 14 working days