Mon – Sat: 9:00 AM – 7:00 PM IST
Implementation

ERP cutover planning

The hours between stopping the old system and starting the new one — planned to the task, and rehearsed at least twice.

In short

Cutover is the transition from legacy to live: final balances extracted, data loaded, systems switched, users let in. It is a sequenced plan with owners and timings for every task, a go/no-go decision point, and a rollback position. The work is not technically difficult; it is unforgiving of anything that was not rehearsed.

Why It Matters

Why this matters in practice

Cutover concentrates all the project's risk into a short window, usually a weekend, with the business unable to transact while it runs. Everything that has been approximate during the project — a load that takes longer than expected, a reconciliation that does not tie — becomes a problem with a clock attached. This is why rehearsal, not planning, is the control.

Every task sequenced, timed and owned
Rehearsed at least twice before the real event
A defined go/no-go decision with named decision-makers
A rollback position that is real, not theoretical
How It Works

How it works in practice

1

Freeze and finalise

Legacy transactions stop at a declared point. Outstanding documents are completed or carried deliberately.

2

Extract and load

Closing balances, open orders, open payables and receivables, stock positions. Timed from rehearsal, not estimated.

3

Reconcile

Loaded balances tied back to legacy before anyone is let in. This is the step that most often overruns.

4

Go/no-go

Against criteria agreed in advance, by named people. Deciding under pressure without criteria produces optimism.

5

Open and support

Users in, hypercare team visible, and a daily issue triage for the first weeks.

Worked example

A worked example: a runbook that found its own problem

A business schedules cutover over a long weekend: freeze Friday evening, migrate Saturday, verify Sunday, open Monday morning. The runbook has 140 tasks with owners and durations.

The dress rehearsal two weeks earlier produces the useful finding. The sequence works, but the total elapsed time is 41 hours against a 58-hour window — leaving far less contingency than the plan assumed, because three tasks took roughly twice their estimate. More importantly, the final reconciliation could not start until a load that finished at 2am, meaning the verification team would be checking financial control totals in the middle of the night.

Two changes follow, and neither would have been visible without rehearsing. The load sequence is reordered so reconciliation can begin on completed objects while later ones are still loading. And a formal go/no-go is added at the point where remaining work exceeds remaining window, with the rollback decision made there rather than at 6am Monday with nobody senior awake. Rehearsal's value is less in proving the plan works than in finding where it does not.

Key terms

The vocabulary, briefly

Term What it means
Runbook The hour-by-hour task list for cutover, with owners, durations and dependencies.
Go/no-go A decision point with defined criteria, taken before committing to the next stage.
Rollback The plan for returning to the legacy system, which must be tested rather than assumed.
Freeze The period when legacy changes stop, so the final extract is stable.
Dress rehearsal A full timed practice of the runbook, in a realistic environment.
What Goes Wrong

Common mistakes worth avoiding

Never rehearsing fully

A partial rehearsal validates the parts you were already confident about.

No rollback criteria

If the decision to abandon is made emotionally at 3am, it will be made badly. Define the triggers beforehand.

Reconciliation left till last

If balances do not tie, you need time to investigate — not fifteen minutes before opening.

Hypercare understaffed

Week one generates more questions than any other period of the project.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Rehearsal elapsed vs window Contingency, measured rather than assumed. Below about 30% is uncomfortable.
Tasks exceeding estimate Where the plan is optimistic, identified before it matters.
Reconciliation completion time Whether verification can finish before the business needs the system.
Rollback tested Yes or no. An untested rollback plan is a document rather than an option.
FAQ

Questions we are asked about this

Big-bang is shorter and riskier; phased spreads risk but requires the two systems to coexist and reconcile, which is its own work. Multi-site businesses often phase by site; single-site ones usually go big-bang.
Derived from rehearsal timings plus contingency, not chosen first. A typical mid-sized ERP cutover runs over a long weekend, with reconciliation as the largest block.
Long enough for the rehearsed elapsed time plus meaningful contingency — thirty to fifty percent is a reasonable target. The window is determined by what the business can tolerate being without the system, so establish that first and then find out whether the migration fits. Discovering the mismatch during cutover is the worst possible sequence, and it is common when the window is assumed rather than tested.
Full parallel running — every transaction entered twice — is extremely expensive and error-prone, and it tends to collapse within days under its own weight. A read-only legacy system for lookup and reference is cheap and genuinely useful. Parallel running of a specific high-risk process, such as payroll, for one cycle is often worth it. Blanket parallel operation sounds prudent and rarely survives contact with the workload.
Criteria agreed and written down before cutover begins: reconciliation failures above a defined threshold, critical functionality unavailable, or elapsed time exceeding the point from which recovery is still possible. The last is the one teams forget — there is a moment after which rolling back is no longer feasible, and it should be identified in advance and treated as a hard go/no-go rather than discovered by passing it.
A named owner for every runbook task, a single decision-maker empowered to call go/no-go without convening a meeting, technical staff for migration and verification, business users for reconciliation and acceptance, and a communication owner keeping everyone else informed. Every one of those roles needs a named backup, because cutover weekends have a reliable habit of coinciding with someone's emergency.
Related

Where to read next

ERP implementation phases

Read more

What is UAT?

Read more

ERP data migration

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.