# ERP Go-Live Cutover Runbook Template for Acumatica and Sage

> Source: https://netray.co/tools/acumatica-sage-go-live-cutover-runbook-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Fill-in cutover runbook with freeze, extraction, load, validation, go or no-go and rollback steps, ready to export as a document.

## Category

erp-migration

## Erp

Acumatica

## Industry

SMB Manufacturing

## Audience

- Project manager
- ERP consultant
- IT manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Source system

**Key:** source

**Type:** text

**Default:** Sage 100

#### Target system

**Key:** target

**Type:** text

**Default:** Acumatica

#### Cutover lead

**Key:** lead

**Type:** text

**Default:** Project manager

#### Freeze start

**Key:** freeze

**Type:** date

**Default:** 2026-11-13

#### Go-live date

**Key:** golive

**Type:** date

**Default:** 2026-11-16

#### Go or no-go decision time

**Key:** decision

**Type:** text

**Default:** Sunday 18:00

#### Rollback plan

**Key:** rollback

**Type:** textarea

**Default:** Reopen the source system in read-write mode, notify users, and resume processing there until the issue is resolved.

**Blocks:**

#### Cutover Runbook

**Body:** Company: {{company}}
Source system: {{source}}
Target system: {{target}}
Cutover lead: {{lead}}
Freeze start: {{freeze}}
Go-live: {{golive}}

#### Schedule

**Table:**

**Columns:**

- Step
- Task
- Owner
- Start
- Done

**Rows:**

**0:** 1

**1:** Announce freeze; block new transactions in {{source}}

**2:** {{lead}}

**3:** {{freeze}}

**0:** 2

**1:** Final backup of {{source}} and verify restore

**2:** IT

**0:** 3

**1:** Extract master data, open orders, open balances

**2:** Data lead

**0:** 4

**1:** Load into {{target}} in dependency order

**2:** Data lead

**0:** 5

**1:** Reconcile trial balance, AR, AP, inventory valuation

**2:** Controller

**0:** 6

**1:** Run business smoke tests: order, receipt, ship, invoice

**2:** Key users

**0:** 7

**1:** Go or no-go decision at {{decision}}

**2:** Steering group

**3:** {{decision}}

**0:** 8

**1:** Open {{target}} to users and enable integrations

**2:** IT

**3:** {{golive}}

#### Go or No-Go Criteria

**Body:** Proceed only if the trial balance matches the source, open AR and AP agree to the control totals, inventory quantity and value are reconciled, and critical business transactions pass the smoke test.

#### Rollback Plan

**Body:** {{rollback}}

#### Approvals

**Signatures:**

- Cutover lead
- Controller
- Operations manager
- Executive sponsor

**Notes:** A starting template. Adapt the steps, owners and timings to your project plan, and rehearse the runbook at least twice before the real cutover.

## Content

**Intro:** A go-live succeeds or fails on the runbook. This template gives you a time-ordered cutover plan covering freeze, backup, extract, load, reconciliation, smoke tests, a formal go or no-go decision and a rollback path, which you can export and adapt for any ERP move.

**Sections:**

#### How to use it

**Body:** Fill in the company, source and target systems, key dates and decision time, then edit the generated task list to match your plan. Assign a named owner to every step and record the actual start and finish times during rehearsals. Print the final version for the cutover room so everyone works from the same document.

#### Why these steps

**Body:** The sequence follows the dependencies of a typical ERP cutover: stop change in the old system, take a verified backup, extract and load master data before open items, reconcile finance and inventory to control totals, then test real transactions before deciding. Reconciliation against control totals is the objective evidence the steering group needs to say go.

**Bullets:**

- Agree go or no-go criteria before the weekend, not during it.
- Test the rollback; a plan never exercised is a hope.
- Keep a communication log for users, suppliers and customers.

#### Common mistakes

**Body:** Skipping rehearsals, leaving integrations and EDI partners out of the plan, and not freezing changes to prices and master data in the source are common. Another is declaring success before the first end-of-day and first invoice run. Plan hypercare for the first weeks and keep the runbook current as defects are found.

**Cta:** Netray can help automate reconciliations and data loads so the cutover steps are repeatable.

**Faq:**

#### How many rehearsals do I need?

**Answer:** At least two full rehearsals with production-like data, with the second run following the final runbook to confirm timings. More are justified for complex manufacturing data.

#### Who makes the go or no-go call?

**Answer:** The steering group or executive sponsor, using criteria agreed in advance and evidence from reconciliations and smoke tests, not the project team alone.

#### Does it work for any ERP?

**Answer:** Yes. The structure is generic. The source and target fields let you adapt it for Sage 300, Sage X3, Acumatica or other systems.

#### What about rollback?

**Answer:** Define the point of no return, the trigger conditions and the steps in advance. After users have entered significant transactions in the new system, rollback becomes much harder.

## Search terms

erp cutover plan template, go live runbook template, erp go live checklist, acumatica go live plan, sage 300 go live plan, cutover weekend schedule template

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