ERP cutover process flow (rehearsal to hypercare)
Editable ERP cutover process flow for SAP, Oracle, Dynamics 365 or NetSuite go-lives: mock cutover, legacy freeze, data load, reconciliation sign-off, go/no-go decision, rollback and hypercare exit.
What the ERP cutover process flow (rehearsal to hypercare) process is
A cutover plan is usually a spreadsheet of several hundred tasks, and it should be: the detail matters. What the spreadsheet does not show well is the shape of the weekend: the gates where work stops until someone signs, and the paths that run when a gate fails. Those are what the steering committee needs to understand before go-live, and what the team needs to have rehearsed.
This template draws that shape. A mock cutover that can fail and loop back. A reconciliation the business has to sign. A go/no-go decision with criteria agreed in advance, and a rollback path that ends in a postponed go-live rather than a scramble. Then hypercare with exit criteria, so it ends on evidence rather than on a date.
It works for any ERP: SAP S/4HANA, Oracle Fusion, Dynamics 365, NetSuite or a smaller system. Rename the lanes to your project roles, keep the detailed runbook in your project plan, and use this flow to explain and approve the gates.
What this flowchart covers
In this template
- The cutover runbook baseline and one or more mock cutovers with timing and defect targets
- Freezing transactions and master data in the legacy system
- Extracting final balances and open items, loading master data and transactions, and the technical cutover of interfaces and jobs
- Business reconciliation of the loaded data, with a reload path when breaks are found
- The go/no-go decision, the rollback plan, opening the new system and hypercare exit criteria
When to use this template
- You are planning go-live for an ERP implementation and need the steering committee to approve the gates
- The cutover plan exists as a task list and nobody can explain the decision points
- A previous go-live had no agreed rollback criteria and you want them defined in advance
- You are running a phased rollout and need a repeatable cutover pattern for each country or site
How it works
Rename the lanes to your project roles
Map lanes to the cutover manager, business key users, the data migration team, technical teams and the steering committee or go-live board.
Write your go/no-go criteria
Put the agreed criteria in the decision's note: reconciliation signed, no open severity-1 defects, support staffed, rollback still possible.
Set the rehearsal targets
Write the timing and defect targets on the mock cutover decision, and plan at least two rehearsals for a large go-live.
Link the detailed runbook
Attach or link the task-level runbook to the relevant steps so the flow stays readable and the detail stays in one place.
Approve the plan
Send the flow for approval to the program sponsor and process owners; the approved version is your record of what was agreed.
Frequently asked questions
What is an ERP cutover plan?
It is the detailed plan for moving from the legacy system to the new ERP: freezing the old system, loading final data, switching interfaces and users, and confirming the new system is correct before people start working in it. It includes owners, timings, dependencies, sign-off points and a rollback plan.
What should go/no-go criteria include?
Typical criteria are: data reconciliation signed off by the business, no open severity-1 defects and an agreed list of known severity-2 issues, users trained, support and hypercare staffed, interfaces tested end to end, and confirmation that rollback is still possible within the cutover window.
How many mock cutovers should we run?
At least one full rehearsal using production-like data and the real runbook, and usually two or three for a large implementation. Each rehearsal should be timed and measured against targets, and the runbook updated before the next one.
When does hypercare end?
When agreed exit criteria are met, not on a fixed date. Common criteria are ticket volume trending down, no open severity-1 issues, and the first month-end close completed in the new system.
Where this process fits
In most operations this process follows Enterprise Software Implementation Process.
Comes before
- Enterprise Software Implementation Process — Enterprise software implementation template covering discovery, requirements, design, configuration, integration, data migration, testing, UAT, go-live, hypercare and handover.
- SAP ECC to S/4HANA migration process flow — Editable SAP ECC to S/4HANA migration process flow: Readiness Check, custom code analysis, fit-to-standard, the brownfield, greenfield or selective data transition decision, testing and the conversion cutover.
- Dynamics AX 2012 to Dynamics 365 upgrade process flow — Editable Dynamics AX 2012 to Dynamics 365 Finance and SCM upgrade process flow: Lifecycle Services analysis, the upgrade or reimplement decision, code to extensions, data upgrade, UAT and go-live.