# ERP Cutover Plan Worksheet

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

## Short answer

Build a task-by-task ERP cutover runbook with owners, durations and a buffer, and calculate the total cutover window.

## Category

erp-migration

## Audience

- Project manager
- Cutover manager
- ERP administrator

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Seq

**Key:** seq

**Type:** number

#### Phase

**Key:** phase

**Type:** select

**Options:**

- Freeze
- Extract
- Load
- Reconcile
- Validate
- Go/No-go
- Open

#### Task

**Key:** task

**Type:** text

#### Owner

**Key:** owner

**Type:** text

#### Planned duration (min)

**Key:** dur

**Type:** number

**Format:** minutes

#### Buffer %

**Key:** buffer

**Type:** number

**Unit:** %

#### Duration with buffer

**Key:** adj

**Type:** number

**Expr:** dur * (1 + buffer / 100)

**Format:** minutes

#### Planned start

**Key:** start

**Type:** date

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- In progress
- Done
- Blocked

**Rows:**

#### Freeze

**Seq:** 1

**Task:** Legacy system transaction freeze announced and enforced

**Owner:** Cutover manager

**Dur:** 30

**Buffer:** 10

**Start:** 2027-05-28

**Status:** Not started

#### Extract

**Seq:** 2

**Task:** Final extract of open POs, open sales orders and on-hand inventory

**Owner:** Data lead

**Dur:** 180

**Buffer:** 25

**Start:** 2027-05-28

**Status:** Not started

#### Load

**Seq:** 3

**Task:** Load balances and open transactions into production

**Owner:** Technical lead

**Dur:** 360

**Buffer:** 30

**Start:** 2027-05-29

**Status:** Not started

#### Reconcile

**Seq:** 4

**Task:** Reconcile inventory value and GL trial balance to legacy

**Owner:** Finance lead

**Dur:** 240

**Buffer:** 20

**Start:** 2027-05-29

**Status:** Not started

#### Validate

**Seq:** 5

**Task:** Smoke test: create PO, receive, issue to job, ship order

**Owner:** Key users

**Dur:** 120

**Buffer:** 25

**Start:** 2027-05-30

**Status:** Not started

#### Go/No-go

**Seq:** 6

**Task:** Go/no-go decision with steering committee

**Owner:** Project manager

**Dur:** 30

**Buffer:** 0

**Start:** 2027-05-30

**Status:** Not started

#### Open

**Seq:** 7

**Task:** Open system to users, confirm integrations running

**Owner:** IT lead

**Dur:** 60

**Buffer:** 15

**Start:** 2027-05-31

**Status:** Not started

**Totals:**

#### Planned minutes

**Key:** dur

**Agg:** sum

**Format:** minutes

#### Minutes with buffer

**Key:** adj

**Agg:** sum

**Format:** minutes

**Summary:**

#### Planned cutover effort (hours)

**Key:** hours_plan

**Expr:** sum_dur / 60

**Format:** hours

#### Cutover effort with buffer (hours)

**Key:** hours_buf

**Expr:** sum_adj / 60

**Format:** hours

**Primary:** true

#### Buffer held (hours)

**Key:** buffer_hours

**Expr:** (sum_adj - sum_dur) / 60

**Format:** hours

**Notes:** Total effort assumes tasks run one after another. Tasks that can run in parallel shorten the elapsed window, so mark them in the task text and compare your critical path against the freeze window the business agreed.

## Content

**Intro:** A cutover plan is the minute-by-minute order of work between the last legacy transaction and the first live one. This worksheet lets you list each task, its owner and a buffer, and shows whether the total fits the freeze window.

**Sections:**

#### How to use the worksheet

**Body:** Replace the example rows with your own tasks in the sequence they must run. Give every row a single owner, an honest duration taken from your last mock load, and a buffer. Use the phase column to group tasks into freeze, extract, load, reconcile, validate, go/no-go and open. The summary shows total effort with buffer in hours. Compare that number to the freeze window your business signed off, such as a Friday evening to Monday morning shutdown. Export to Excel to share the runbook with the cutover team.

#### Where durations come from

**Body:** Never estimate cutover durations from memory. Time each task during mock loads: at least two full dress rehearsals are normal on manufacturing projects. Record extract time, load time per object and reconciliation time. Then set the buffer based on how stable the timings were. A load that varied from 90 to 140 minutes between mocks deserves a 30 to 40 percent buffer, while a scripted reconcile query that always takes 10 minutes needs very little.

**Bullets:**

- Use actual timings from mock loads, not vendor estimates
- Add a larger buffer to steps that depend on third parties or manual work
- Include time for reconciliation, which is often longer than the load
- Keep a decision point for go/no-go and a rollback trigger time

#### Reading the result

**Body:** If effort with buffer is below the freeze window and most tasks are sequential, you have headroom. If it exceeds the window, look for parallel work, remove tasks that can be done earlier such as loading static master data before the freeze, or reduce the number of open transactions by cleaning up before cutover. Also state your rollback point: the latest time at which you can still return to the legacy system without losing business data.

#### Common mistakes

**Body:** Teams commonly leave out reconciliation and smoke testing, skip rehearsing the rollback, and plan cutover tasks without naming who is awake at three in the morning. Another is forgetting interfaces: EDI, shop floor devices, banking files and tax connections all need switching and verifying. Add them as rows so they are owned and timed like everything else.

**Cta:** If reconciliation takes more of your window than the load itself, we can show how AI-assisted queries over legacy and new ERP data can speed the comparison, on your own infrastructure if needed.

**Faq:**

#### How long does an ERP cutover take?

**Answer:** For a single plant, cutover typically fits in a weekend of 36 to 60 hours including reconciliation and smoke tests. Larger or multi-site cutovers take longer and are often split into waves. The measured timings from your mock loads should decide, not a general rule.

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

**Answer:** Two or three full rehearsals is common. The first finds data problems, the second validates fixes and timings, and the last is a dress rehearsal run to the real schedule with the real team.

#### What is a freeze window?

**Answer:** It is the period when users stop entering transactions in the legacy system so a consistent snapshot can be moved. The business has to agree the window because shipments, receipts and production reporting are interrupted.

#### What should the rollback plan include?

**Answer:** A defined trigger, a point of no return time, the steps to reopen the legacy system, and how transactions entered in the new system will be handled. Rehearse it at least once on paper with the whole team.

## Search terms

erp cutover plan worksheet, erp cutover plan template excel, erp cutover checklist, erp go live cutover plan, cutover runbook template, erp cutover timeline, erp data cutover schedule, cutover weekend plan

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