Data migration
Move the database without stopping the desk
Migrations fail on the day the old system is switched off, which is why ours is two stages with a parallel run in between. A dedicated migration specialist is assigned to your project and works with your team from the first sample export to go-live.
How it runs
- A dedicated migration specialist assigned to your project
- A two-stage process that keeps the business trading
- Zero-downtime implementation approach
- Comprehensive data validation at every stage
- Full technical support throughout the process
Systems we have migrated from
Our migration specialists analyse, map and import data from a wide range of file formats and source systems. We have run migrations from small databases up to enterprise systems, so most of what you are moving off is something we have seen before.
Not on the list? Send us a sample export — the assessment in stage one exists precisely to answer that question before anyone commits.
Stage one — the full migration
Stage one typically begins a month before you switch away from your current provider; the exact timeline depends on the volume and complexity of the data. For large databases we recommend at least a week of running both systems in parallel.
Provide sample data and CRM access
Client provides sample or full data exported from their current system, and optionally access to their current CRM.
Pre-migration assessment
Assess the sample data provided, estimate migration times and create the project plan.
Project sign-off
Sign off the project plan and pay the data migration invoice.
Data analysis and mapping scripts
Perform thorough data analysis and create the migration scripts.
Master data import
Import master data and compare with the source CRM.
Sample data import
Import 100 records for each module and compare with the source CRM.
Sample validation
Validate the sample data imported and sign off.
Import full data
Import and validate the full data set and compare with the source CRM.
Data validation
Validate the data imported and sign off.
Parallel run
Run both systems side by side. The client validates thoroughly and works with the migration team to fix anything that surfaces.
Stage two — the delta
Everything that changed in the old system during the parallel run, brought across on the day you go live. This is the stage that makes the switch a non-event.
Provide full or delta export
Client provides the final delta export from their current system, and optionally access to their current CRM.
Import and validation
Import new records, update existing ones, validate and ensure complete synchronisation.
Go live
Client begins using Recruitly as their primary system, with full support from the implementation team.
What comes across
Unless agreed otherwise before the project begins, the migration covers the following record types — including the documents attached to them.
Master data
Core system configuration and reference data.
Activity records
Notes, emails and all conversation history.
Contacts and companies
Including all associated documents and attachments.
Candidate profiles
CVs, branded CVs and all candidate documentation.
Job records
All job details and associated documents.
Pipeline information
Complete job pipeline and workflow structures.
Placement data
Historical and active placement records.
Start with a sample export
The pre-migration assessment tells you the shape of the job before anyone commits to a date. Bring an export from your current system and we will tell you what moves cleanly and what needs mapping.