Acumatica Go-Live Cutover Checklist for Manufacturers
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.
0 of 29 items complete
9 critical items still open - these are the highest-risk gaps.
Data and balances
Inventory and shop floor
Security and access
Integrations and reports
Cutover, training and rollback
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.
Cutover plan review
Optional: have an expert read through your cutover runbook.
Optional. The tool and every export work without this. No spam.
How to use the checklist
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
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.
- Tie every opening balance to a source report
- Freeze inventory movement during the count
- Rehearse the cutover at least once
Common mistakes
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.
Frequently Asked Questions
How long before go-live should we freeze data?
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?
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?
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?
Most of it does. Replace the Acumatica specifics, such as screens and roles, with your system's equivalents.
If you want an outside reviewer for your cutover plan, we can look at the runbook and data checks with your team.
Related Tools
Acumatica Screen ID Reference
Look up common Acumatica screen IDs and names for role setup, generic inquiries, import scenarios and support tickets.
Developer ToolsAcumatica OData Generic Inquiry URL Builder
Generate the OData URL for an Acumatica generic inquiry, with $filter, $select, $orderby and $top, ready for Excel, Power BI or a script.
ERP Migration & SelectionSage 300 vs Acumatica Manufacturing Fit Assessment
Score how well your current Sage system supports your manufacturing process and see whether it is time to evaluate alternatives.
More ERP Migration & Selection tools
See all- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist
- ERP Change Management Readiness Assessment
- ERP Integration Complexity Calculator
- Cloud vs On-Premise ERP Cost Calculator
- ERP Upgrade vs Replace Assessment