Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 14 tasks across 4 phases, about 10 weeks if every task runs in sequence.
What's in the template
| Phase | Task | Duration | Starts | Depends on |
|---|---|---|---|---|
| Assess | Source inventory and owners | 5 days | Day 1 | Nothing (starts first) |
| Assess | Data mapping and transformation rules | 10 days | Day 6 | Source inventory and owners |
| Assess | Data quality assessment | 5 days | Day 16 | Data mapping and transformation rules |
| Build | Data cleansing | 10 days | Day 21 | Data quality assessment |
| Build | Migration scripts | 10 days | Day 31 | Data cleansing |
| Build | Rollback plan | 2 days | Day 41 | Migration scripts |
| Rehearse | First test load | 2 days | Day 43 | Rollback plan |
| Rehearse | Validation and reconciliation | 5 days | Day 45 | First test load |
| Rehearse | Second test load | 2 days | Day 50 | Validation and reconciliation |
| Rehearse | Sign-off from data owners | 2 days | Day 52 | Second test load |
| Cutover | Freeze changes in source | 1 day | Day 54 | Sign-off from data owners |
| Cutover | Production migration | 2 days | Day 55 | Freeze changes in source |
| Cutover | Post-migration validation | 2 days | Day 57 | Production migration |
| Cutover | Decommission old system | 14 days | Day 59 | Post-migration validation |
Durations are examples to replace with your own estimates, not benchmarks. Every task waits for the one before it, so the whole chain is the critical path until you overlap work that can run in parallel.
About this data migration plan
Migrations go smoothly when they are rehearsed. This plan includes two test loads with validation between them, a written rollback plan, and decommissioning of the old system once the new one is trusted.
It suits moving a database, CRM or file store to a new platform.
Who it's for: Data engineers, IT managers and systems administrators.
How to use it
- Open the plan. Click Use this template.
- Add your systems. Rename rows to your source and target systems and assign data owners.
- Mark the freeze and cutover. Turn them into milestones so stakeholders see the window.
- Share with owners. Send a read-only link to every data owner.
Planning tips
- Reconcile row counts and totals after every test load.
- Write the rollback plan before the first production load, not during it.
- Keep the old system read-only for a while before decommissioning it.
Frequently asked questions
- What are the steps in a data migration?
- Inventory, mapping, quality assessment, cleansing, scripting, test loads with validation, sign-off, freeze, production load, validation and decommissioning.
- How many test loads should I run?
- At least one full rehearsal. This template plans two so fixes from the first can be verified.
- Is there an ERP template?
- Yes, see the ERP implementation template.
Related templates and guides
- Cutover Plan Gantt chart template
- ERP Implementation Plan Gantt chart template
- Software Sprint Plan Gantt chart template
- Compliance Audit Preparation Plan Gantt chart template
- API Integration Project Gantt chart template
- Sprint planning on a Gantt chart
- Microsoft Project alternative
- Free Gantt chart maker, no sign-up
- Critical path calculator
- Free timeline templates
- All Gantt chart templates
- Gantt chart examples
- How to make a Gantt chart
- Excel Gantt chart template
The free plan saves one project. Downloads from the editor (PDF, CSV) and more projects are on Solo, $12/month.