# Acumatica Go-Live Cutover Checklist for Manufacturers

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

## Short answer

A cutover checklist covering data, inventory, open orders, security, integrations and rollback before and after an Acumatica go-live.

## Category

erp-migration

## Erp

Acumatica

## Industry

Manufacturing

## Audience

- Project manager
- ERP consultant
- Controller

## Tool

**Kind:** checklist

**Groups:**

#### Data and balances

**Items:**

**Text:** Chart of accounts, subaccounts and ledgers approved by the controller

**Critical:** true

Customers and vendors cleaned, de-duplicated and loaded

Stock items, item classes and units of measure loaded and spot checked

**Text:** Opening trial balance loaded and agreed to the legacy system

**Critical:** true

**Text:** Open AR and AP documents loaded and agreed to control accounts

**Critical:** true

Open sales orders and purchase orders loaded with correct dates and quantities

Bills of material and routings loaded and verified for active products

#### Inventory and shop floor

**Items:**

**Text:** Physical inventory counted at freeze, by warehouse and location

**Critical:** true

**Text:** Inventory valuation reconciled to the general ledger

**Critical:** true

Lot and serial numbers loaded where tracked

Work in process quantities and values calculated and entered

Standard or average costs approved for the costing method in use

Production orders open at cutover reviewed and either closed or recreated

#### Security and access

**Items:**

**Text:** Roles mapped to screens and approved by process owners

**Critical:** true

Segregation of duties reviewed for payments and journal entries

Default accounts and posting rules tested for each transaction type

Integration users created with least privilege

Admin account passwords stored in a vault

#### Integrations and reports

**Items:**

**Text:** Banking, tax and payment connections tested end to end

**Critical:** true

EDI, ecommerce and shipping connections tested with real samples

Generic inquiries and reports used daily rebuilt and signed off

Scheduled processes and automation schedules configured

Email templates and document layouts approved

#### Cutover, training and rollback

**Items:**

**Text:** Cutover runbook with owners, times and dependencies agreed

**Critical:** true

Legacy system set to read only after the final extract

End user training completed with role based exercises

**Text:** Rollback criteria and decision time agreed in writing

**Critical:** true

Hypercare roster and issue triage routine in place for the first month

First period close plan with extra review of inventory and WIP

**Scoring Note:** Every critical item must be complete before cutover. If more than a quarter of the remaining items are open one week before the date, reconsider the go-live date.

## Content

**Intro:** A manufacturing go-live fails on inventory, open orders and security more often than on the software itself. This checklist groups the cutover tasks so nothing is left to memory on the weekend.

**Sections:**

#### How to use the checklist

**Body:** Assign an owner to each group and walk through the list at the go/no-go meeting. Tick items as they are verified, not just started. Export the list to PDF or Excel to attach to the project record. Items marked critical are the ones that, when missed, produce wrong financials or stop shipments on day one.

#### Why these areas

**Body:** Balances must tie out because the first close will expose any gap. Inventory and WIP are the largest judgement areas in a manufacturer, and they drive cost of goods sold. Security matters because the new system is often more open than the old one. Integrations decide whether orders, payments and shipments flow without manual rework.

**Bullets:**

- Tie every opening balance to a source report
- Freeze inventory movement during the count
- Rehearse the cutover at least once

#### Common mistakes

**Body:** Teams skip a full dress rehearsal, load open orders with stale dates, forget unit of measure conversions, or leave the legacy system writable. Another frequent miss is no rollback criteria, which turns a problem into an argument. Decide the rules before the pressure begins.

**Cta:** If you want an outside reviewer for your cutover plan, we can look at the runbook and data checks with your team.

**Faq:**

#### How long before go-live should we freeze data?

**Answer:** Plan a defined freeze window just long enough to extract, load and reconcile. For many small manufacturers this is a weekend or a month-end boundary, rehearsed beforehand.

#### Should we load history?

**Answer:** Usually load balances and open transactions, and keep history in an archive or reporting copy. Loading full history adds time and risk without much operational benefit.

#### When is a rollback appropriate?

**Answer:** When agreed criteria are missed, such as balances that do not reconcile or shipping blocked. Define the criteria and the decision time before cutover.

#### Does this apply to other ERPs?

**Answer:** Most of it does. Replace the Acumatica specifics, such as screens and roles, with your system's equivalents.

## Search terms

acumatica go live checklist, acumatica cutover plan, erp go live checklist manufacturing, acumatica implementation checklist, erp cutover checklist, acumatica data migration checklist

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