ERP Cutover Plan Worksheet
A cutover plan is the minute-by-minute order of work between the last legacy transaction and the first live one. This worksheet lets you list each task, its owner and a buffer, and shows whether the total fits the freeze window.
| Seq | Phase | Task | Owner | Planned duration (min) | Buffer % (%) | Duration with buffer | Planned start | Status | |
|---|---|---|---|---|---|---|---|---|---|
33 min | |||||||||
225 min | |||||||||
468 min | |||||||||
288 min | |||||||||
150 min | |||||||||
30 min | |||||||||
69 min |
Total effort assumes tasks run one after another. Tasks that can run in parallel shorten the elapsed window, so mark them in the task text and compare your critical path against the freeze window the business agreed.
Cutover reconciliation review
Share your reconciliation approach and we will suggest queries and checks that cut the time spent validating loaded data.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Replace the example rows with your own tasks in the sequence they must run. Give every row a single owner, an honest duration taken from your last mock load, and a buffer. Use the phase column to group tasks into freeze, extract, load, reconcile, validate, go/no-go and open. The summary shows total effort with buffer in hours. Compare that number to the freeze window your business signed off, such as a Friday evening to Monday morning shutdown. Export to Excel to share the runbook with the cutover team.
Where durations come from
Never estimate cutover durations from memory. Time each task during mock loads: at least two full dress rehearsals are normal on manufacturing projects. Record extract time, load time per object and reconciliation time. Then set the buffer based on how stable the timings were. A load that varied from 90 to 140 minutes between mocks deserves a 30 to 40 percent buffer, while a scripted reconcile query that always takes 10 minutes needs very little.
- Use actual timings from mock loads, not vendor estimates
- Add a larger buffer to steps that depend on third parties or manual work
- Include time for reconciliation, which is often longer than the load
- Keep a decision point for go/no-go and a rollback trigger time
Reading the result
If effort with buffer is below the freeze window and most tasks are sequential, you have headroom. If it exceeds the window, look for parallel work, remove tasks that can be done earlier such as loading static master data before the freeze, or reduce the number of open transactions by cleaning up before cutover. Also state your rollback point: the latest time at which you can still return to the legacy system without losing business data.
Common mistakes
Teams commonly leave out reconciliation and smoke testing, skip rehearsing the rollback, and plan cutover tasks without naming who is awake at three in the morning. Another is forgetting interfaces: EDI, shop floor devices, banking files and tax connections all need switching and verifying. Add them as rows so they are owned and timed like everything else.
Frequently Asked Questions
How long does an ERP cutover take?
For a single plant, cutover typically fits in a weekend of 36 to 60 hours including reconciliation and smoke tests. Larger or multi-site cutovers take longer and are often split into waves. The measured timings from your mock loads should decide, not a general rule.
How many mock cutovers should we run?
Two or three full rehearsals is common. The first finds data problems, the second validates fixes and timings, and the last is a dress rehearsal run to the real schedule with the real team.
What is a freeze window?
It is the period when users stop entering transactions in the legacy system so a consistent snapshot can be moved. The business has to agree the window because shipments, receipts and production reporting are interrupted.
What should the rollback plan include?
A defined trigger, a point of no return time, the steps to reopen the legacy system, and how transactions entered in the new system will be handled. Rehearse it at least once on paper with the whole team.
If reconciliation takes more of your window than the load itself, we can show how AI-assisted queries over legacy and new ERP data can speed the comparison, on your own infrastructure if needed.
Related Tools
ERP Implementation Project Plan Template
Generate a structured ERP implementation project plan with scope, phases, governance, milestones and risks, ready to export as PDF or Word.
ERP Migration & SelectionERP Data Migration Plan Template
Generate a data migration plan covering scope, data owners, cleansing, mock loads, reconciliation and sign-off for your ERP project.
ERP Migration & SelectionERP Go-Live Readiness Assessment
A ten-question scored assessment of your ERP go-live readiness, with a verdict and recommended actions before your go/no-go meeting.
ERP Migration & SelectionERP Hypercare Issue Log Worksheet
A hypercare issue log with severity, owner, hours open, SLA and a breach flag calculated per row.
ERP Migration & SelectionERP Cutover Weekend Readiness Checklist
Confirm every prerequisite is genuinely complete before the ERP cutover weekend, covering data validation, sequencing, day one operations, rollback triggers, and hypercare staffing.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment