ERP

How to Build an ERP Cutover Plan and Checklist in 2026 (Hour-by-Hour Runbook for Government)

Build an ERP cutover plan your city or county can run: freeze dates, go/no-go criteria, rollback triggers, an hour-by-hour runbook and a full 2026 checklist.

Chris Rodney 17 min read
On this page
  1. Key takeaways
  2. What is an ERP cutover plan?
  3. How to build an ERP cutover plan in 7 steps (2026)
  4. How to set go/no-go criteria and run the decision
  5. How to write an ERP rollback plan
  6. Sample hour-by-hour ERP cutover runbook
  7. The complete ERP cutover checklist for 2026
  8. How to hand off from cutover to hypercare
  9. FAQ
  10. Treat cutover as a decision, not a weekend

An ERP cutover plan is the hour-by-hour runbook that moves your city, county or district off the legacy system and onto the new ERP. It sets the freeze dates, sequences every conversion and validation task with a named owner, defines written go/no-go criteria, and says exactly when and how you roll back if something breaks.

Many troubled go-lives don’t fall apart on cutover weekend; they fall apart days earlier, at a go/no-go meeting treated as a formality. Birmingham City Council in the UK is the textbook case.

KCT plans and runs cutovers for public agencies as both an ERP advisor and an implementer. Below you’ll get a 7-step method, go/no-go criteria, rollback triggers, a sample hour-by-hour runbook and a full ERP cutover checklist, all on this page.

Key takeaways

Start cutover planning months ahead and rehearse it more than once. KCT rule of thumb: at least two full mock cutovers.

Freeze in layers: configuration, master data, then transactions, each with its own date.

Write go/no-go criteria and name the decision owner before testing ends.

Define rollback triggers and a point of no return before cutover weekend.

Cutover is done when the first payroll, AP run and bank reconciliation tie out, not when the system opens.

What is an ERP cutover plan?

An ERP cutover plan is the time-sequenced task list for switching from your legacy system to the new ERP. It covers the data freeze, conversion loads, reconciliation, go/no-go checkpoints and rollback, and every task has an owner, a backup, a verification step and a sign-off.

Microsoft’s Dynamics 365 implementation guide describes cutover as the short window when you can’t use your old system or your new one. Teams call it the “cutover weekend” because the window is usually less than 48 hours.

The same guide separates the cutover strategy (when, who, communication and roles) from the cutover plan (the detailed task list with timing, owners, verification, sign-off and rollback).

Cutover vs go-live vs hypercare

These three phases run back to back.

Swipe to see all columns →

PhaseWhat happensEnds when
CutoverLegacy freezes, data is extracted, loaded and reconciled, interfaces are switched, go/no-go checkpoints runThe sponsor gives the final “go” and the new system opens to users
Go-liveThe new ERP becomes the system of record and staff start posting live transactionsThe first business day closes with transactions flowing
HypercareA command center triages issues, monitors the first payrolls, AP runs and month-end, and stabilizes the systemIssue volume drops to normal support levels and the first close is done

We’ll cover cutover through the first business day. The hypercare handoff section near the end points you to our guide on the command center, severity levels and the First 30 days post go-live.

Why a public sector ERP cutover is harder

A public-sector ERP cutover carries constraints a private company rarely faces. Opening balances land fund by fund. Open POs and encumbrances must carry over cleanly, or departments lose budget authority on day one.

Pay dates are often tied to labor agreements and can’t slip. Utility billing cycles keep running mid-conversion. And the same lean finance team that runs the city is also running the cutover. For fund-by-fund opening balances, see how to survive your first month-end close on a new ERP.

Your first action: name one cutover lead from the agency and one from the vendor. They own the plan.

How to build an ERP cutover plan in 7 steps (2026)

You build an ERP cutover plan by locking the window, assigning every task, freezing in layers, proving conversions, rehearsing, and writing go/no-go and rollback rules early.

1

Pick the cutover window around your fiscal calendar.

2

Build the task list with owners, durations and dependencies.

3

Set your freeze dates for configuration, master data and transactions.

4

Plan conversions and validation, including opening balances.

5

Rehearse with at least two mock cutovers.

6

Write go/no-go criteria and name the decision owner.

7

Write the rollback plan and mark the point of no return.

Step 1: Pick the cutover window around your fiscal calendar

Choose a window that avoids year-end, budget adoption, fixed payrolls and peak billing cycles.

Microsoft’s guidance warns against cutting over when you have to close the books or report results, and says to account for holidays. The Washington State Auditor made a similar point in its August 2024 One Washington performance audit, flagging training scheduled during year-end reconciliation as a risk.

Put pay dates, check runs, billing cycles and council dates on one calendar, then pick a primary and backup weekend. KCT rule of thumb: start detailed cutover planning during build, at least 3 to 4 months before go-live.

Step 2: Build the cutover runbook task list with owners, durations and dependencies

Every task gets an owner, a backup, a start time, a duration, a predecessor, a verification step and a sign-off. A task with no owner won’t get done at 2 a.m. on a Saturday.

Those columns mirror Microsoft’s cutover guidance. Owners are named people, never a department, and durations come from mock timings.

Step 3: Set your data freeze and change freeze dates

Freeze in layers, not all at once. Each layer protects the data that the next load depends on.

Configuration freeze
No new pay rules, workflows or security roles.
Master data freeze
Vendors, employees, customers and GL accounts stop changing, or changes get dual-keyed.
Transaction cutoffs
Last check run, last PO, last cash receipt, last meter read.
Legacy read-only
The moment legacy stops accepting entries and becomes inquiry only.

The Washington State Auditor’s data transfer leading practices include planning to isolate affected systems and backed-up data before the transfer. Our guide to ERP parallel testing also recommends freezing pay rule and configuration changes after the final parallel run.

Publish the freeze calendar to every department, plus a one-page emergency change process: who approves a change, and how it gets entered in both systems.

Step 4: Plan the data migration cutover and validation, including opening balances

Sequence loads in dependency order (configuration, master data, open items, balances) and reconcile after each one.

The Washington auditor’s leading practices call for testing data before and after the transfer. Nevada shows what happens when that work gets squeezed: its independent verification and validation (IV&V) contractor reported in December 2024 that resources for testing conversions, integrations and reports were not scheduled well enough before go-live. Late technical work left 36 interfaces waiting for agency validation that month.

For every load, define control totals and a signer:

Record counts, legacy vs new

GL balances by fund

Open PO and encumbrance totals by department

AP open items by vendor

AR and utility balances by customer class

Step 5: Rehearse with at least two mock cutovers (dress rehearsals)

A mock cutover runs the real plan with production-like data, the real people and the real clock.

Microsoft’s guidance says to practice the cutover several times, keeping each rehearsal as close to the real event as possible: same data, tools, people and timing. At the City of Oxnard, KCT split the go-lives into Finance, then HCM, then EPL (enterprise permitting and licensing), and each cutover was proofed and rehearsed before it landed.

Time every task; the final mock’s durations become your runbook. KCT rule of thumb: run the final mock within a few weeks of go-live, and add nothing new to scope after it.

Step 6: Write go/no-go criteria and name the decision owner

Write the criteria, get them signed, and name one executive who makes the call. The go/no-go section below has a criteria table you can adapt.

Step 7: Write the rollback plan and mark the point of no return

Decide in advance what triggers a rollback, how you’d do it and the last moment you still can. The rollback section below lists sample triggers.

How to set go/no-go criteria and run the decision

A go/no-go is a scheduled meeting where a named executive approves or stops go-live against criteria written weeks earlier. “Go with known issues” is fine only when every issue has a written workaround and an owner.

Birmingham shows the cost of skipping that discipline. According to Grant Thornton’s public interest report, as reported by The Register, emails between the integrator and the program director from 29 to 31 March 2022 showed council testers couldn’t fully test bank reconciliation. Bank file loading and key consolidation reports were failing. Reports to the steering committee still rated cash management “Green.”

The council went live on Oracle on 11 April 2022. Auditors concluded the program was unlikely to have approved go-live had testing information been presented more clearly. The council now faces a potential bill of about £130 million to complete its ERP replacement, against an initial estimate of around £20 million.

In Washington State, the State Auditor reported that as of July 2024, One Washington hadn’t finalized its contingency plans or go/no-go criteria, and called that a project risk. The state’s project page now shows a Core Financials go-live range of October 2027 through October 2028.

Now a “no” that worked. In a May 2020 audit, Gainesville, Florida’s City Auditor noted that at the go/no-go checkpoint, the city moved its March 23, 2020 go-live to April 20, 2020 to allow more time to integrate with Gainesville Regional Utilities’ (GRU) SAP system. That’s a go/no-go doing its job.

Go/no-go criteria table

Thresholds below are KCT rules of thumb, not an industry standard. Adjust them to your project.

Swipe to see all columns →

AreaGo criterionOwner
TestingZero open Severity 1 defects; every open Severity 2 has a signed workaroundTest lead
Parallel payrollExit memo signed; variances explained (see Step 3 for the parallel testing guide)Payroll manager
Data conversionControl totals tie by fund in the final mockFinance director
InterfacesBank, positive pay, benefits and billing interfaces tested end to endIT lead
SecurityRoles assigned and tested for every go-live userSecurity admin
TrainingGo-live roles trained before the cutover weekendTraining lead
RehearsalFinal mock finished inside the planned windowCutover lead
SupportCommand center staffed with names and shiftsPMO
CommunicationsFreeze and go-live notices sent to departments, vendors and council liaisonCommunications lead
RollbackRollback steps written, backups verified, point of no return on the runbookCutover lead

Who is in the room and who decides

The executive sponsor decides. In the room: finance, payroll, IT, go-live department leads, the vendor or SI project manager and any independent advisor.

Ask vendors to put caveats in the headline of their status report, not the appendix.

When to hold go/no-go meetings

KCT rule of thumb: a preliminary go/no-go about two weeks out, a final one before cutover weekend starts, and checkpoints during the cutover, such as right after load reconciliation. Get the criteria signed before the last test cycle starts.

Many agencies run cutover with the same lean finance team that keeps the city running, and nobody independent checks the go/no-go evidence. KCT’s Full-spectrum ERP Implementation team builds and runs cutover runbooks, mock cutovers and go-live command centers alongside your staff and your vendor.

How to write an ERP rollback plan

An ERP rollback plan defines the triggers that stop the cutover, the point of no return, the steps to restore legacy as the system of record, and who makes the call. Nobody writes a good rollback plan at 3 a.m.

Microsoft’s guidance lists a rollback plan as a core cutover component. Gainesville’s auditor cited COBIT 2019 control BAI07.01, which expects a fallback or back-up plan (2020 audit).

Nevada’s December 2024 IV&V report recorded that lacking a contingency plan for the Financial MVP was an accepted risk, and that contingency plans should have been robust.

Rollback triggers

Write triggers as yes/no tests anyone can check:

Conversion control totals don’t tie within the agreed tolerance by the reconciliation checkpoint.

Payroll can’t be produced and validated for the next pay date.

The bank file or positive pay file fails the bank’s test.

A critical interface (bank, benefits, billing) is down with no workaround.

The cutover is running more than a set number of hours behind the checkpoint. KCT rule of thumb: set this at 4 to 6 hours for a weekend cutover.

The point of no return

Once live transactions post in the new system (a payroll, a check run, a batch of utility bills), rolling back stops being a restore. It becomes re-keying everything in legacy.

Put it on the runbook as a named line item, right after the final go/no-go.

Plan B that isn’t a full rollback

Not every problem needs a full rollback:

Delay one module
Go live with finance and hold HCM, the same split-go-live logic KCT used at Oxnard.
Manual workaround
Run a process by hand for a short, defined period with a named owner.
Legacy read-only
Keep legacy open for inquiry so staff can look up history while issues get fixed.

Rehearse the rollback at least once in a mock.

Sample hour-by-hour ERP cutover runbook

A cutover runbook lists every task in clock order with an owner and a checkpoint. Below is an illustrative KCT runbook for a weekend finance and payroll go-live. Replace every time with actual durations from your final mock.

Swipe to see all columns →

WhenTaskOwnerCheckpoint
Friday 12:00Legacy transaction cutoff: last AP entries, receipts and PO changesFinance directorCutoff notice confirmed by departments
Friday 17:00Legacy set to read-only; final full backups takenIT leadBackup verified and logged
Friday 18:00Final extracts from legacy; record counts capturedConversion leadExtract counts recorded
Friday 20:00 to Saturday 06:00Load master data: vendors, employees, customers, GL accountsVendor/SI technical leadCounts match extracts
Saturday 08:00Load open items, encumbrances and opening balances by fundConversion leadLoad logs clean
Saturday 12:00Reconciliation checkpoint 1: control totals by fund, AP, AR, encumbrancesFinance directorGo/no-go checkpoint: continue or trigger rollback
Saturday 14:00Switch interfaces; test bank and positive pay filesIT leadBank confirms test file accepted
Saturday 18:00Security and role smoke test with real user accountsSecurity adminSample users log in and complete key tasks
Sunday 09:00Business validation by departments: sample transactions, reports, payroll previewDepartment leadsEach department signs off
Sunday 14:00Final go/no-go meetingExecutive sponsorSigned go decision
Sunday 16:00Point of no return: open the new system to usersCutover leadGo-live notice sent
Monday 07:00 (first business day)Command center opens; first-day issue triagePMOFirst daily status report

The window where neither system takes entries runs just under 48 hours. That lines up with Microsoft’s description of a cutover weekend. Send a short status update at every checkpoint to the sponsor, department leads and your council liaison.

The complete ERP cutover checklist for 2026

This ERP cutover checklist groups every task by phase, from 12 weeks out through the first week live, and doubles as your ERP go-live checklist. Use the table as a cutover plan template inside your own project tracker. Timeframes are KCT rules of thumb; adjust them to your go-live date.

Swipe to see all columns →

PhaseChecklist itemOwnerDone
8 to 12 weeks outCutover strategy approved: window, roles, decision ownerExecutive sponsor
8 to 12 weeks outPrimary and backup cutover dates checked against pay dates, billing cycles, close and council calendarCutover lead
8 to 12 weeks outCommunications plan drafted for staff, vendors, banks, residents and councilCommunications lead
4 to 8 weeks outFull task list built with owners, backups, durations and predecessorsCutover lead
4 to 8 weeks outControl totals defined and signers named for every loadConversion lead
4 to 8 weeks outMock cutover 1 run with production-like data and timedCutover lead
4 to 8 weeks outFreeze calendar published to departmentsPMO
4 to 8 weeks outRollback plan drafted with triggers and point of no returnCutover lead
2 to 4 weeks outMock cutover 2 run inside the planned window, rollback steps rehearsedCutover lead
2 to 4 weeks outGo/no-go criteria signed by the executive sponsorExecutive sponsor
2 to 4 weeks outParallel payroll exit memo signedPayroll manager
2 to 4 weeks outEnd-user training complete for go-live rolesTraining lead
2 to 4 weeks outSecurity roles assigned and tested for all go-live usersSecurity admin
2 to 4 weeks outCommand center roster and severity definitions publishedPMO
Final weekConfiguration freeze in effectIT lead
Final weekMaster data freeze in effect; dual-key log startedFinance director
Final weekTransaction cutoff dates confirmed with every departmentCommunications lead
Cutover weekendLegacy set to read-only and backed upIT lead
Cutover weekendMaster data, open items, encumbrances and balances loadedVendor/SI technical lead
Cutover weekendReconciliation checkpoint passed and signedFinance director
Cutover weekendInterfaces switched; bank and positive pay test files acceptedIT lead
Cutover weekendDepartment business validation signedDepartment leads
Cutover weekendFinal go/no-go decision signed; point of no return passedExecutive sponsor
First business day and first weekCommand center open with daily status reportPMO
First business day and first weekFirst payroll pre-checked against prior periodPayroll manager
First business day and first weekFirst AP check run reviewed before releaseFinance director
First business day and first weekDaily bank reconciliation completedTreasury

Before mock 1, put a name in every Owner cell.

How to hand off from cutover to hypercare

Cutover ends when the first payroll, the first AP run and the bank reconciliation tie out, not when users can log in. Keep your cutover team on the hook until then.

Nevada’s IV&V contractor reported that production support volume after Phase 1A go-live was unplanned, pulling resources from later phases, including payroll. Staff post go-live support as part of the cutover plan.

Give the first payrolls extra checking and prove accuracy pay period by pay period.

Then hand off to hypercare. Our guide to the first 90 days after ERP go-live covers the command center, severity levels and the First 30 days post go-live.

FAQ

What is a cutover plan in ERP implementation?

A cutover plan is the runbook that takes you from the legacy freeze to the first business day on the new ERP. Every task in it carries an owner, a checkpoint and a sign-off.

What is the difference between cutover and go-live?

Cutover is the short window when legacy is frozen and data moves across; go-live is the moment the new ERP becomes the system of record. Hypercare support then follows go-live.

How long does an ERP cutover take?

An ERP cutover window is usually less than 48 hours, according to Microsoft’s implementation guidance, hence the name cutover weekend. Planning and rehearsal take months, and your final mock timings should set the real window.

Who makes the go/no-go decision?

The executive sponsor makes the go/no-go decision, based on written criteria signed weeks earlier. Finance, payroll, IT, department leads, the vendor project manager and any independent advisor present the evidence.

What is a mock cutover?

A mock cutover is a full rehearsal of the ERP cutover plan with production-like data, the real people and the real clock. Teams time every task, find missing steps and test the rollback; KCT rule of thumb: run at least two.

What should an ERP rollback plan include?

An ERP rollback plan should include written triggers, a point of no return, steps to restore legacy as the system of record, verified backups and the person who calls it. Add partial options, such as delaying one module or a short manual workaround.

What is a data freeze in ERP cutover?

A data freeze is the point after which certain data stops changing so it converts accurately during cutover. Freeze configuration first, then master data, then transactions, and finally set legacy to read-only.

Do you need outside help for an ERP cutover?

Outside help for an ERP cutover depends on how many modules, departments and stakeholders the go-live touches, and your team’s cutover experience. Start with an assessment of your plan and readiness; KCT can support at any point, from planning through the first business day.

Treat cutover as a decision, not a weekend

A good ERP cutover is a chain of decisions made weeks earlier: the window, the freezes, the control totals, the criteria and the point of no return.

If your go-live date is set, write your go/no-go criteria and rollback triggers this month, then rehearse until the timings stop surprising you.

If you’d like a team that’s run this before, KCT’s Full-spectrum ERP Implementation service plans and runs cutovers with your staff and your vendor. If your go-live is already scheduled, start with an ERP health check or talk to our team.

Ready when you are

Let's talk before it slips.