When to use a data migration template
Data migrations look simple on paper: move records from one system to another. In practice, the data is messier than anyone expected, fields do not match one to one, and the business needs the old system to keep working until the last moment. Migrations that go wrong lose records, break reports and damage trust in the new system. A template makes the process careful and repeatable.
Use it when replacing a CRM, ERP, project tool or database, moving from spreadsheets to a system, or merging data after an acquisition.
How the template is structured
- Assess. List every source, profile data quality and agree what moves, what is archived and what is deleted.
- Map. Map fields between systems, define validation rules and plan security for sensitive data.
- Cleanse. Remove duplicates and fix missing and invalid values before migrating, not after.
- Test. Run trial migrations into a test environment, validate them and repeat until they pass.
- Migrate. Freeze changes, run the production migration and keep the rollback ready.
- Validate. Run the agreed checks, get business sign-off and archive or retire the source.
The Sensitive data label marks tasks that involve personal or confidential data, so access and handling rules are applied.
How to use it in Worklenz
- Create a project for the migration and link the client if it is client work.
- Add the phases and tasks above and attach the field mapping and validation rules to their tasks.
- Add a task per data source in the assess and map phases if there are several.
- Set the cut-over date and work back from it.
- Track time on the Pro plan and above to improve estimates for future migrations.
Making migration work visible and billable
Data cleansing is the part of a migration that most often grows beyond the estimate. Time tracking shows how much time goes into each phase, so you can raise extra cleansing with the client early. On the Business plan, project finance compares the budget with the cost of logged time.
Example: moving a sales team to a new CRM
A consultancy is moving a sales team’s data from spreadsheets and an old CRM into a new CRM. Profiling finds 12 percent duplicate contacts and inconsistent country names. The team agrees merge rules with the sales director, maps fields and standardises formats.
The first trial migration fails validation because of a date format issue; the second passes. On cut-over day, the sales team stops editing the old system at noon, the migration runs in the afternoon, and the sales director checks twenty key accounts before signing off. The old system is kept read-only for a month, then archived.
Deciding what not to migrate
Every migration is a chance to leave old data behind. Records that have not been touched in years, closed accounts, duplicate files and test data all make the new system slower and harder to use. Agree retention rules with the business and with whoever owns compliance: what must be kept and for how long, what can be archived in a cheaper place and what can be deleted. Migrating less data also makes testing faster and reduces the risk of errors during cut-over.
Who should be involved
A migration lead owns the plan. Data engineers or technical consultants handle mapping, scripts and validation. A business data owner decides cleansing rules and signs off results. Security or compliance reviews the handling of personal data.
Common data migration mistakes
The first mistake is skipping data profiling, so problems appear during cut-over. The second is migrating dirty data and promising to clean it later. The third is retiring the old system before validation is complete. This template puts profiling, cleansing and validation before each irreversible step.
Tips for safer migrations
- Profile before you promise a date. Data quality decides the timeline.
- Clean before you move. Cleaning in the new system is harder.
- Run at least one full trial. Samples hide problems that full volumes reveal.
- Keep the rollback until sign-off. Do not retire the source too early.
Related: the IT project template and the security assessment template.





