Free, no sign-up to start: the plan opens as a live, editable Gantt chart. 18 tasks across 5 phases, about 5 weeks from start to finish with the parallel work shown.
What's in the template
| Phase | Task | Owner | Duration | Starts | Depends on |
|---|---|---|---|---|---|
| Prepare | Cutover strategy and scope | Cutover manager | 3 days | Day 1 | Nothing (starts first) |
| Prepare | Cutover runbook (hour by hour) | Cutover manager | 4 days | Day 4 | Cutover strategy and scope |
| Prepare | Rollback plan | Technical lead | 2 days | Day 4 | Cutover strategy and scope |
| Prepare | User communication plan | Change manager | 2 days | Day 4 | Cutover strategy and scope |
| Rehearse | Mock cutover 1 | Technical lead | 3 days | Day 8 | Cutover runbook (hour by hour), Rollback plan |
| Rehearse | Fix issues from mock cutover 1 | Technical lead | 4 days | Day 11 | Mock cutover 1 |
| Rehearse | Mock cutover 2 (timed dress rehearsal) | Technical lead | 2 days | Day 15 | Fix issues from mock cutover 1 |
| Rehearse | End-user training | Change manager | 5 days | Day 6 | User communication plan |
| Readiness | Change freeze begins | Milestone | Day 17 | Mock cutover 2 (timed dress rehearsal) | |
| Readiness | Data reconciliation sign-off | Data lead | 2 days | Day 17 | Mock cutover 2 (timed dress rehearsal) |
| Readiness | Go/no-go decision | Milestone | Day 19 | Data reconciliation sign-off, End-user training, Change freeze begins | |
| Cutover | Final data extract and load | Data lead | 2 days | Day 19 | Go/no-go decision |
| Cutover | Smoke tests and business validation | Technical lead | 1 day | Day 21 | Final data extract and load |
| Cutover | Go-live | Milestone | Day 22 | Smoke tests and business validation | |
| Hypercare | Hypercare support | Support team | 10 days | Day 22 | Go-live |
| Hypercare | Daily issue triage | Cutover manager | 10 days | Day 22 | Go-live |
| Hypercare | Decommission legacy system | Technical lead | 3 days | Day 32 | Hypercare support |
| Hypercare | Close cutover and lessons learned | Cutover manager | 1 day | Day 32 | Hypercare support, Daily issue triage |
Durations are examples to replace with your own estimates, not benchmarks. Some work runs in parallel, so the plan takes 34 days instead of the 54 it would take one task at a time. The 12 darker bars are the critical path: a day lost on any of them moves the finish date.
About this cutover plan
A cutover is the move from the old system to the new one: freeze changes, load the final data, switch users over and, if it goes wrong, roll back. It is short, it happens once, and it usually happens over a weekend, which is why it needs more rehearsal than any other part of an implementation.
This template covers the five weeks around a go-live. It starts with the cutover strategy, the hour-by-hour runbook and the rollback plan, runs two mock cutovers with a fix window between them, and ends with a go/no-go decision, the final data load, go-live, two weeks of hypercare and decommissioning the old system. Communication and end-user training run alongside. Every task has an owning role, and the go-live and go/no-go are milestones.
The chart is the days-level plan. The minute-by-minute steps for the cutover weekend belong in the runbook itself, which is one of the tasks here; most teams keep it as a spreadsheet so each step can be ticked off as it runs.
Who it's for: Implementation leads, IT project managers and system integrators planning the go-live of an ERP, CRM, finance or other business system.
How to use it
- Use this template. Click Use this template. The plan opens in the editor with prepare, rehearse, readiness, cutover and hypercare as lanes, owners on every task and the go/no-go and go-live as milestones. No sign-up is needed.
- Set the go-live and work backwards. Put your real start date on the first task and check where go-live lands. If it is later than the business date, look at the critical path (the runbook and the two mock cutovers) before cutting anything else.
- Write the runbook alongside. Use the runbook task to build the hour-by-hour checklist for the cutover weekend: each step, its owner, its expected duration and its rollback point. Time it during the second mock cutover.
- Hold the go/no-go and share the plan. Agree the go/no-go criteria in advance (data reconciled, training done, no open critical defects) and share a read-only link with the steering group so everyone knows when the decision is.
Why two mock cutovers
The first mock cutover finds the problems: a data load that fails on real volumes, a step missing from the runbook, a permission nobody set up. The fix window after it is where those get solved. The second mock is a dress rehearsal run against the clock, following the runbook exactly, to prove the cutover fits in the window you have and that the rollback plan works.
That sequence (runbook, mock 1, fixes, mock 2) is the critical path of this plan, together with the data reconciliation, the final load and hypercare. If the first mock goes badly and the fixes take longer than four days, go-live moves, and the chart shows by how much. Teams that skip the second rehearsal usually find out on the cutover weekend how long the data load really takes.
The go/no-go decision
Go/no-go is a milestone with three inputs here: the data reconciliation is signed off, end-user training is finished and the change freeze is in place. Training and the freeze have slack; reconciliation does not. Write the criteria down when you write the cutover strategy, not on the day, so the decision is about evidence rather than mood.
A no-go is not a failure. It is the reason the rollback plan and the communication plan exist. If you decide not to go, the plan should already say what users are told and when the next window is.
Planning tips
- Freeze changes to both the old and the new system before the final data load, and put the freeze on the chart so nobody schedules a release into it.
- Give every runbook step an owner and a rollback point. Knowing where you can still turn back is as important as knowing the next step.
- Time the second mock cutover and compare it with the window you have. If it does not fit with room to spare, change the plan now.
- Staff hypercare before go-live. The first two weeks after cutover need named people on support, not whoever is free.
- Leave decommissioning on the plan. Running the old system in parallel for longer than planned costs money and confuses users.
Frequently asked questions
- What is a cutover plan?
- It is the plan for moving from an old system to a new one: the preparation, rehearsals, go/no-go decision, final data migration, go-live and the support period after it. This template puts those on one Gantt chart with owners and links.
- What is the difference between a cutover plan and a runbook?
- The cutover plan covers the weeks around go-live at the level of days. The runbook is the hour-by-hour checklist for the cutover itself: each step, who does it, how long it should take and where you can roll back. Writing the runbook is one of the tasks in this plan.
- How long is hypercare after go-live?
- It depends on the system and the organisation; this example uses ten days. Plan it as a task with named people and an end date, and agree what has to be true (for example, no open critical issues) before support moves to the normal service desk.
- Can I use this cutover plan in Excel?
- Yes. Download CSV gives you every task with its owner, start date, end date, phase and dependencies, which opens in Excel or Google Sheets. The milestones have a duration of 0 days.
- Is this cutover plan template free?
- Yes. Opening and editing it in the browser is free with no sign-up, and the CSV download on this page is free. A free account keeps one saved project.
Related templates and guides
- Implementation Plan Gantt chart template
- ERP Implementation Plan Gantt chart template
- Data Migration Plan Gantt chart template
- SaaS Customer Implementation Gantt chart template
- Change Management Plan 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.