# ERP Go-Live Cutover Plan Worksheet

> Source: https://netray.co/tools/eu-erp-cutover-plan-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Hour-by-hour go-live cutover task list with owners, durations, dependencies and rollback checkpoints, ready to run a weekend cutover.

## Category

erp-migration

## Region

Europe

## Industry

Discrete Manufacturing

## Audience

- ERP project manager
- Cutover lead
- IT manager

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Seq

**Key:** seq

**Type:** number

#### Phase

**Key:** phase

**Type:** select

**Options:**

- Freeze
- Extract
- Load
- Reconcile
- Interfaces
- Go / no-go
- Release
- Hypercare

#### Task

**Key:** task

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Planned start

**Key:** start

**Type:** text

**Help:** Day and time, for example Sat 08:00

#### Duration (h)

**Key:** hours

**Type:** number

#### Depends on seq

**Key:** depends

**Type:** text

#### Rollback point

**Key:** rollback

**Type:** select

**Options:**

- Yes
- No

#### Status

**Key:** status

**Type:** select

**Options:**

- Planned
- Running
- Done
- Failed

**Rows:**

#### Freeze

**Seq:** 1

**Task:** Stop order entry and goods movements in legacy ERP

**Owner:** Operations manager

**Start:** Fri 18:00

**Hours:** 1

**Rollback:** Yes

**Status:** Planned

#### Extract

**Seq:** 2

**Task:** Final extract of open orders, stock and open items

**Owner:** Data migration lead

**Start:** Fri 19:00

**Hours:** 4

**Depends:** 1

**Rollback:** Yes

**Status:** Planned

#### Load

**Seq:** 3

**Task:** Load stock and open orders into production system

**Owner:** Technical consultant

**Start:** Sat 00:00

**Hours:** 6

**Depends:** 2

**Rollback:** No

**Status:** Planned

#### Reconcile

**Seq:** 4

**Task:** Reconcile stock quantities and values with legacy

**Owner:** Finance controller

**Start:** Sat 06:00

**Hours:** 5

**Depends:** 3

**Rollback:** No

**Status:** Planned

#### Interfaces

**Seq:** 5

**Task:** Switch EDI, carrier and bank interfaces to new system

**Owner:** IT integration lead

**Start:** Sat 11:00

**Hours:** 3

**Depends:** 4

**Rollback:** No

**Status:** Planned

#### Go / no-go

**Seq:** 6

**Task:** Go-live decision meeting

**Owner:** Steering committee

**Start:** Sat 14:00

**Hours:** 1

**Depends:** 5

**Rollback:** No

**Status:** Planned

**Totals:**

#### Total task hours

**Key:** hours

**Agg:** sum

**Format:** hours

#### Number of tasks

**Key:** seq

**Agg:** count

**Format:** integer

**Summary:**

#### Average task duration

**Key:** avg_task

**Expr:** if(gt(count,0), sum_hours / count, 0)

**Format:** hours

**Notes:** Sum of hours is task effort, not elapsed time, since tasks may run in parallel. Check the critical path separately from the dependency column.

## Content

**Intro:** A cutover plan is the runbook for the weekend when the old ERP stops and the new one starts. It lists every task, who does it, when it starts, how long it takes and where you can still go back. This worksheet captures that in a form you can edit during rehearsals.

**Sections:**

#### How to use it

**Body:** Build the plan during the first mock cutover and refine it with each rehearsal. Number tasks in execution order, assign a named owner, write the planned start and the realistic duration from the rehearsal timings and record dependencies. Mark the steps after which you can still revert to the legacy system. During the real cutover, update the status as tasks finish so the committee sees progress against the plan.

**Bullets:**

- Use measured durations from rehearsals, not estimates
- One named owner per task and a named deputy
- Mark clear rollback points before the point of no return
- Include communication tasks to users, customers and suppliers

#### Typical cutover phases

**Body:** A manufacturing cutover generally runs through a freeze of transactions, final extract, load, technical checks, reconciliation of stock and open items against the legacy system, interface switching for EDI, banking and carriers, a go or no-go decision and release to users, followed by hypercare. Allow a buffer of at least a third of the planned elapsed time for the unexpected.

#### Go / no-go criteria

**Body:** Define the criteria before the weekend: reconciliation differences within agreed tolerance, interfaces tested with real messages, key users able to log in with correct roles, critical reports available and support staffing confirmed for the first two weeks. If criteria are not met by the decision time, the plan should say whether you roll back or extend.

#### Common mistakes

**Body:** Plans fail when durations come from optimism instead of rehearsal, when one person owns too many tasks, or when interfaces are left until after the decision. Another frequent gap is no plan for what shop floor staff do while the system is unavailable. Prepare paper forms and a catch-up procedure for the freeze period.

**Cta:** If your cutover involves moving from SyteLine or another ERP we support, we can review the plan for gaps before the first rehearsal. Optional.

**Faq:**

#### How many mock cutovers should we run?

**Answer:** At least two full rehearsals are typical, and three for complex multi-plant or heavily regulated environments. The first finds technical problems, the second proves durations and the third proves the fixes and the team's coordination.

#### When should the cutover happen?

**Answer:** Choose a period with low volume and not close to a financial period end or year end if possible. Many manufacturers pick a weekend after month close, or a plant shutdown, to allow reconciliation without live pressure.

#### What is a point of no return?

**Answer:** The step after which going back to the old system would lose or corrupt data, for example after new transactions have been posted in the new ERP. The plan should state it clearly and the go or no-go decision should happen before it.

#### Do I need a command centre?

**Answer:** For larger projects, yes. A single room or video bridge with the cutover lead, technical lead, business owners and vendor representative reduces handoff delays. For small projects, a shared channel and scheduled checkpoint calls often suffice.

## Search terms

erp cutover plan template, go live cutover checklist excel, erp go live plan template, cutover runbook template, erp cutover schedule, data migration cutover plan

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json