ERP Cutover Plan Template: Every Task, Owner and Contract Seat From Freeze to First Invoice
Twenty-six tasks with an hour, an owner and a rollback note, as an Excel file you can fill in today.
Free Excel file for a work email. Or read the whole plan on this page.
Every task is marked for rollback
- Tail kept
- Clipped
- One way
An ERP cutover plan lists every task from data freeze to first invoice, including final loads, reconciliations, the go or no-go call, the rollback trigger and first transactions, each with an owner marked partner, employee or contract seat.
Last updated: October 24, 2026
Cutover is the weekend everybody pretends is normal. It isn’t. You’re moving a company’s money, stock and customers from one system to another, and somebody in accounts receivable still expects an invoice to go out on Tuesday, whether or not the new system has been told what a customer is.
A good plan fits on one sheet. Every task has an hour, an owner, a person who signs it off and a note on what you’d have to undo if the call goes wrong, and that note should name the backup you’d restore from instead of just saying undo it. That last column is the one most plans skip. It’s also the one you’ll want at three in the morning.
I built this one for the stretch after the ERP implementation checklist runs out, about four weeks before the date, when the project lead and the controller are staring at a calendar. It works the same on NetSuite, SAP S/4HANA, Oracle Fusion Cloud ERP or Dynamics 365, because only the names of the load tools change. The owners are marked partner, employee or contract seat, and the seats are the people KORE1 places on contract inside the IT staffing services it has run since 2005.
Download the ERP Cutover Plan Template
One work email and the Excel file is yours. It carries the same 26 tasks as the plan below, with the planned time of every task worked out from your cut date and every blank shaded.
The runbook sheet
Twenty-six tasks in five phases, each with an hour offset. Type the cut date once and every planned time fills itself in.
Owner and sign-off columns
Pick partner, employee or contract seat from a drop-down, then add the person, the signer and the rollback note.
Go or no-go and seats
Seven criteria, the signatures and four rollback triggers on one sheet, and the four contract seats with KORE1 bill rates beside your hours on another.
Where should we send it?
Work email, please. We use your details to respond to this request. See our privacy policy.
Your template is ready
Download it, set your cut date and send the plan to your project lead.
Download the Excel File ↓Next
Short a seat or two? Tell us the cutover date, the seats, the hours and the metro and a KORE1 recruiter sends bill rates for your req. The 2026 Contract Rate Card has all 1,365 cells.
What Does an ERP Cutover Plan Include?
Twenty-six tasks in five phases, in the order they run. Hours count from H0, the cut, when the new system opens for business. The line down the left edge of each task shows whether rolling back is still cheap.
KORE1 · ERP cutover plan
ERP Cutover Plan, Freeze to First Invoice
Who owns the task
- Employee Your own staff.
- Partner Your implementation partner.
- Contract seat A contractor you bring on for the window.
If you roll back after the task
- Tail kept The old system is still the system of record. Rolling back means reopening it and lifting the freeze.
- Clipped Live work sits in the new system. Rolling back means restoring the old one from backup and replaying every entry since the cut.
- One way Something has left the building. Rolling back can’t recall it. You credit, reverse or correct.
| Hour | Task | Owner | Signs off | If you roll back after it |
|---|---|---|---|---|
AFreezeH-96 to H-60 · 5 tasksStop the data and the settings from moving while you prepare. | ||||
| H-96A1 | Start the master data freezeNo new customers, vendors or items in the old system without the controller’s initials. | EmployeeController | Controller | Tail keptLift the freeze. Nothing downstream has moved. |
| H-96A2 | Freeze configuration and integrationsFrom here every change in the new system goes through the change log, even the ones that look harmless. | PartnerImplementation lead | Partner lead and IT lead | Tail keptLift the freeze. Parked changes wait their turn. |
| H-84A3 | Back up both systems and test a restoreA backup you haven’t restored is a hope. Prove the way back before you need it. | Contract seatERP consultant | IT lead | Tail keptKeep both backups. Every later rollback leans on them. |
| H-72A4 | Reset the plan from your last rehearsalSwap every guess for the minutes the last mock cutover really took, then add a buffer. | Contract seatProject manager | Partner lead | Tail keptRevert the plan file. No system was touched. |
| H-60A5 | Check production access for named usersRoles, single sign-on, multi-factor and approval routing, tested with real accounts for day one. | Contract seatHelp desk | IT lead | Tail keptReset the roles. Minutes, not hours. |
BFinal loads and reconciliationsH-48 to H-10 · 9 tasksLoad the last data, then prove it ties before anyone is asked to trust it. | ||||
| H-48B1 | Put the old system in read-onlyLast postings go in, period cutoffs are taken, and nobody types into the old system after this. | EmployeeIT administrator | Controller | Tail keptSwitch it back to read and write. |
| H-44B2 | Extract the final data from the old systemMasters first, then open items, then balances, each with a row count and a control total. | Contract seatData analyst | Partner data lead | Tail keptDelete the extract and run it again. |
| H-36B3 | Load the masters and check the countsCustomers, vendors, items, price lists and the chart of accounts map. Counts and totals must match. | Contract seatData analyst | Partner data lead | Tail keptPurge by load ID and reload. |
| H-30B4 | Load the open transactionsOpen receivables and payables, open orders and purchase orders, and stock by location and lot. | Contract seatERP consultant | Controller and operations lead | Tail keptPurge by load ID before anything posts. |
| H-24B5 | Post the opening balancesThe trial balance goes into the new ledger as one journal, with the old system’s totals beside it. | EmployeeGeneral ledger accountant | Controller | Tail keptReverse by journal, or wipe and reload while the old system is still live. |
| H-20B6 | Reconcile the moneyTrial balance, receivables, payables and inventory value, each tied to the old system with every variance named. | Contract seatData analyst | Controller | Tail keptA failed tie-out is a no-go, not a rollback. |
| H-16B7 | Reconcile the operationsStock counts by location, open order and purchase order counts, and a spot check of price lists. | EmployeeOperations lead | Partner lead | Tail keptA failed count is a no-go. Recount before the call. |
| H-12B8 | Point the integrations at production, heldEDI, ecommerce, payments, bank feeds and payroll, each tested with one real message that waits for release. | PartnerIntegration lead | IT lead | Tail keptRepoint to test. Held messages stay held. |
| H-10B9 | Triage every open defectEach gets a severity, a workaround and an owner. Nothing goes into the call as a mystery. | Contract seatProject manager | Partner lead | Tail keptDefect log only. Nothing to undo. |
CGo or no-go and the cutH-4 to H0 · 4 tasksMake the call while rollback is still cheap, then open the doors. | ||||
| H-4C1 | Hold the go or no-go callSeven criteria, read out loud. Any one that fails makes it a no-go. | EmployeeExecutive sponsor | Controller, operations lead and partner lead | Tail keptA no-go costs a rescheduled weekend. Needs A3 and B1. |
| H-2C2 | Name the rollback caller and the triggerWrite down who can call it, who backs them up and the numbers that make the call for them. | PartnerImplementation lead | Executive sponsor | Tail keptLast clean rollback. Reopen the old system and lift the freeze. |
| H-1C3 | Lock the old system and release the integrationsThe old system stays readable for lookups. Held messages start to flow. | EmployeeIT administrator | Executive sponsor | ClippedPast here, rollback means restoring from A3 and replaying every entry. |
| H0C4 | Open the new system to usersSingle sign-on on, announcement out, command center live. This is H0, the cut. | PartnerImplementation lead | Executive sponsor | ClippedRestore from A3 and replay everything entered since H0. |
DFirst transactionsH+1 to H+24 · 5 tasksProve the money and the stock move the way they should, inside the first day. | ||||
| H+1D1 | Run the five smoke transactionsA sales order to an invoice draft, a purchase order to a bill, a payment, a journal and a stock transfer. | EmployeePower users | Process owners | ClippedRestore from A3, then replay these and what followed. |
| H+2D2 | Release the held messages and watch the queuesCheck the error queues every thirty minutes. Replay failures from the source systems. | Contract seatERP consultant | IT lead | ClippedReplay from the source systems. Needs C3. |
| H+4D3 | Stand up the floorThe command center takes tickets, and a floor walker sits in each department. | Contract seatHelp desk | Partner lead | ClippedStaffing only. The rollback is the data, not the desk. |
| H+8D4 | Reconcile day oneNew transactions against their source documents, stock movements and cash, signed before anyone sleeps. | Contract seatData analyst | Controller | ClippedCorrect by journal. A full rollback needs A3 and a replay. |
| H+24D5 | Hold the day-one reviewDefects, workarounds, blocked users and the stop-loss rule, read out and decided. | EmployeeExecutive sponsor | Partner lead and controller | ClippedThe last easy rollback call. Restore from A3 and replay. |
EFirst invoice and hand-offH+36 to H+96 · 3 tasksSend the first bill, then give every open item an owner and a date. | ||||
| H+36E1 | Run the first billing batchDraft invoices checked line by line against orders before one is released. | EmployeeBilling lead | Controller | ClippedDelete the drafts. Nothing has left the building. |
| H+48E2 | Send the first customer invoiceTax, terms and remit-to all checked. This is the first thing a customer sees. | EmployeeBilling lead | Controller | One wayA sent invoice can only be credited, never recalled. |
| H+96E3 | Close the runbook and hand offOpen items go to the hypercare list with a name and a date, and the support roster is confirmed. | PartnerImplementation lead | Executive sponsor | One wayHand-off record. Open items now live on the hypercare list. |
Tally
- 10 employee tasks
- 5 partner tasks
- 11 contract seat tasks
- 16 tail kept
- 8 clipped
- 2 one way
Hours are starting points, not KORE1 terms. Move them to match your rehearsal timings. This is a template, not legal, audit or validation advice. Have your controller and your auditor review it before the cut, and on a validated system your quality lead too.
The seat rates further down are KORE1 bill rates, and all four cells are observed. Where KORE1 has fewer than five placements in a cell, the index models the rate from BLS Occupational Employment and Wage Statistics, May 2025, with a 24% employer burden and the bill range KORE1 observes. The full method is public.
When Do You Call Go or No-Go, and What Triggers Rollback?
The go or no-go call is a short vote. Four people sign before H-4, the executive sponsor, the controller, the operations lead and the partner’s cutover lead, and each of them signs a line they could read aloud to an auditor. If any one of the seven things below is false, the answer is no-go. That isn’t a failure. It’s the plan working.
On a validated system your quality lead signs too, before the call and not after it. Foretopia’s change control puts client quality approval ahead of the change for the same reason.
Go only if all seven are true
- Every final load ties to the old system within [$ tolerance], and each variance has a name next to it.
- The last rehearsal finished inside the window, with at least [8] hours to spare.
- No severity 1 defect is open, and each severity 2 has a workaround someone has tried.
- Each integration passed one real test message in production, held and not released.
- A sample of [10] users per department signed in with the right role.
- The roster has a backup for every seat, contract seats included, and everyone has the bridge number.
- Rollback was rehearsed and timed, and the caller has a name.
Roll back after the cut if any one happens
- More than [25] integration messages fail in [2] hours and can’t be replayed.
- The ledger won’t tie to receivables, payables or stock after [2] correction passes.
- Warehouse or finance can’t ship or invoice by [H+8].
- A load error turns up in masters that live transactions already use.
Called by [name], on the recommendation of [partner lead]. Backup [name].
After H0 the math changes. Rolling back now means restoring the old system from the A3 backup and replaying every entry made since the cut, so the trigger has to be a number you picked in advance, with a name next to it. In this plan the last clean rollback is C2, the first clipped step is C3 and the first one-way step is E2, the first invoice that leaves the building.
Pick the numbers when you’re calm. Nobody picks good numbers at 3 a.m. NIST’s contingency planning guide makes the same point about backups, which is to test the restore and not just the copy.
4 weeks
the release phase in a 2026 Foretopia NetSuite plan, three of them hypercare
26
tasks in this plan, in five phases, each with one owner and one signer
$91
an hour, the median bill rate for an ERP consultant (n=15, multi-state)
$115
an hour, the median bill rate for a data analyst (n=11, primarily Southern California)
Rates are KORE1 bill rates for placements started 2023 to 2026, the records behind the Contract Rate Index 2026-Q4. The four-week figure is a Foretopia delivery benchmark from a 2026 NetSuite project plan for a mid-market pharma manufacturer.
Who Staffs Cutover Weekend?
Eleven of the 26 tasks sit with contract seats, and four roles cover them. Here’s what each one costs by the hour, from KORE1 placements.
| Seat | KORE1 cell | Low | Median | High | 60 hours at the median |
|---|---|---|---|---|---|
| ERP consultantRuns A3, B4 and D2 | ERP / NetSuite / Salesforce consultant, multi-staten=15 | $73 | $91 | $123 | $5,460 |
| Data analystRuns B2, B3, B6 and D4 | Data analyst / BI developer, primarily Southern Californian=11 | $69 | $115 | $116 | $6,900 |
| Help deskRuns A5 and D3 | Help desk / IT support technician, primarily Southern Californian=39 | $41 | $49 | $55 | $2,940 |
| Project managerRuns A4 and B9 | IT project / program manager, primarily Southern Californian=21 | $105 | $116 | $124 | $6,960 |
Reference rates are the 25th percentile, median and 75th percentile of KORE1 bill rates in each cell of the KORE1 Contract Rate Index 2026-Q4, effective October 16, 2026. Cells come from KORE1 W2 contract placements started 2023 to 2026, with five or more in each.
Four seats at 60 hours each and the medians come to $22,260 for a cutover week. The 60 hours is an assumption, so use your own. Weekend and overnight hours can trigger overtime for W2 contractors, and the rules come from the U.S. Department of Labor and your state, so check both before you promise anyone a Saturday night shift or a Sunday double. Hours are yours to change.
Send the cutover date, the seats, the hours and the metro, or say remote. Or browse the 2026 Contract Rate Card.
What Does Each Cutover Seat Own?
Each seat owns whole tasks, so nobody guesses whose job it is.
Contract seat · 3 tasks
ERP consultant
Takes the backups, loads the open transactions and watches the integration queues after the cut. Owns A3, B4 and D2.
ERP consultant hourly rates 2026Contract seat · 4 tasks
Data analyst
Extracts the final data, loads the masters and reconciles the money, then ties out day one. Owns B2, B3, B6 and D4.
Data analyst contract bill rates 2026Contract seat · 2 tasks
Help desk
Tests production access before the cut and runs the floor after it. Owns A5 and D3.
Help desk contract bill rates 2026Contract seat · 2 tasks
Project manager
Keeps the plan honest with rehearsal timings and runs the defect triage. Owns A4 and B9.
Project manager contract bill rates 2026
Eleven tasks sit with seats and ten with your own people. That’s about right. Contractors carry the loads and the watching, and your employees keep the decisions, because only they can say yes to money leaving the building or to a customer hearing about a problem.
If the seats aren’t hired yet, how fast a contractor can start is the question to ask first. Once they start, the contractor onboarding checklist covers accounts and access, and the contractor ramp plan template covers the first thirty days.
What Breaks If Cutover Slips?
The first thing to break is the budget. Four seats at the medians above cost $22,260 for one 60-hour week, so a week of slip with the whole team on the clock is a five-figure line that buys you nothing.
The second is the data, and it goes stale the minute the freeze lifts. Here’s the short list of what else moves.
- Rehearsal timings expire. The load that fit the window last month may not fit it now.
- Nobody can add a customer, a vendor or an item while the freeze holds, and sales finds that out around day three.
- Balances loaded on Friday are wrong by Wednesday. Reload, tie out, sign again.
- The calendar bites. A slip that crosses month-end close, or one of NetSuite’s two yearly releases, can turn a lost week into a lost month, because nobody wants to load balances while the books are still open.
- And the seats? A contractor who sits idle for a week may be on another contract by the next one.
“Focus… where companies are still investing and where they simply can’t afford to have projects fail or go unfinished.”
Devin Hornick, KORE1 partner
Slip once and you re-plan. Slip twice and you re-staff. If the date is already moving, read what breaks if the project doesn’t finish and look at ERP project rescue staffing.
Where Does Cutover End and Hypercare Start?
Cutover ends when the first invoice leaves the new system and the runbook is closed. Hypercare starts at that hand-off, with a support roster, a defect list that has owners and a daily call.
In a 2026 NetSuite plan for a mid-market pharma manufacturer, Foretopia scheduled the release phase at four weeks, three of them hypercare, which left about one week for cutover itself and sits close to the eight days this plan covers from H-96 to H+96.
Cutover is done when
- The five smoke transactions passed (D1).
- The controller signed the day-one reconciliation (D4).
- The first customer invoice went out right (E2).
Hand the open items to the hypercare list with a name and a date on each. If you need people for those three weeks, go-live and hypercare staffing covers the seats and ERP program team staffing covers the team around them. For the week itself, see how many contractors a NetSuite go-live needs.
Common Questions
What should an ERP cutover plan include?
An ERP cutover plan should include every task from data freeze to first invoice, each with an hour offset, an owner, a sign-off and a rollback note. The essentials are the freeze, final loads, reconciliations, the go or no-go call, the rollback trigger and the first transactions. This template has 26 tasks in five phases.
How long does an ERP cutover take?
About a week from freeze to first invoice. In a 2026 NetSuite plan Foretopia scheduled the whole release phase at four weeks, three of them hypercare, so cutover itself got roughly one. Rehearsal timings beat any rule of thumb, so reset the hours after your last mock run.
What’s the difference between a cutover plan and a go-live checklist?
Short version, a checklist says what must be true before you open the new system, and a plan says who does what, when, and how to undo it. You need both. The go or no-go call in this template is the point where the checklist gets signed.
Who makes the go or no-go call?
The executive sponsor, on the partner lead’s recommendation. The controller and the operations lead sign first, so four signatures land before H-4, and on a validated system the quality lead signs too, which is why that name goes on the roster before the weekend and not on a Saturday night. If any single criterion fails, the call is no-go.
Can you roll back after go-live?
Yes, until something leaves the building. After the cut, rolling back means restoring the old system from backup and replaying every entry since, and a sent invoice can only be credited, so the cheapest rollback is the one you call before the cut. Pick your triggers and your caller before H-4.
Hit Me Up With Your Cutover Date
Tell us the date, the seats you’re missing and whether the work is on site or remote. A KORE1 recruiter takes it from there.
Send Us the Cutover Date →Not yet? Download the template first.
