“ERP go-live checklist” and “ERP go-live readiness checklist” are some of the most searched ERP terms, and for good reason. In manufacturing, go-live is when shipments, production orders and supplier receipts start depending on the new system on the same day. This checklist is written for plants, not for an office-only rollout, and it ends with the hypercare plan, because the first 90 days decide whether the program is remembered as a success.
- Readiness is proved with evidence: completed mock cutovers, reconciled data, end-to-end tests that include plant-floor systems, and trained people at every shift.
- The go/no-go decision should be made against criteria agreed weeks in advance, not in the meeting.
- Plants need a fallback for every critical process: shipping, receiving, production reporting and labeling.
- Hypercare is a staffing plan. Name who owns each module, interface and plant for the first 90 days, and overlap them with the build team.
1. Data readiness
- At least two full mock conversions completed, with load errors trending to zero.
- Item master, bills of material, routings and costs reconciled and signed off by plant engineering and finance.
- Open sales orders, purchase orders, production orders and on-hand inventory reconciled to the legacy system by value and quantity.
- Customer and supplier masters, including EDI trading partner setups, validated.
- A named data owner for each object who signs the final reconciliation.
2. Integrations and plant-floor systems
- Every interface (MES, WMS, EDI, labeling, quality, scales, carriers, banks) tested end to end with production-like volumes.
- Error handling and monitoring in place, with a named owner for each interface after go-live.
- Label templates and printers tested in every plant and warehouse.
- Shop-floor devices, scanners and terminals provisioned, with user IDs and security roles working.
- Fallback procedures written for shipping, receiving and production reporting if an interface fails.
3. Testing
- Integration and user acceptance testing completed for order-to-cash, procure-to-pay, plan-to-produce and record-to-report, with critical defects closed.
- Month-end close rehearsed on converted data.
- Performance tested for peak periods such as month-end and shipping cutoffs.
- Security roles tested with real users, not administrator accounts.
4. Cutover plan
- Hour-by-hour cutover runbook rehearsed at least once in a dress rehearsal.
- Production and shipping freeze windows agreed with plant and customer service leaders, and customers informed where needed.
- Inventory counts scheduled and owners assigned.
- Rollback criteria and the point of no return defined.
5. People and training
- Role-based training completed for every shift, including weekend and night crews.
- Super-users named and trained in each plant and department, and released from part of their day job for the first weeks.
- Updated work instructions at the point of use on the shop floor.
- A command center with clear escalation paths and on-site support in each plant for the first two weeks.
The go/no-go questions
Agree the criteria in advance and answer them with evidence:
- Can we ship to our top customers on day one, including EDI and labels?
- Can every plant report production and consume inventory accurately?
- Are converted balances reconciled and signed off by finance?
- Are open critical defects zero, with workarounds documented for the rest?
- Is the hypercare team named, scheduled and in place?
If the honest answer to “can we ship on day one?” is “probably,” the answer to go-live is not yet.
Hypercare: the first 90 days
Hypercare is the period after go-live when the project team stays on to stabilize the system. In manufacturing, most of the serious problems appear in the first two to six weeks: inventory that does not match, costs that roll up incorrectly, interfaces that fail at volume, and the first month-end close. Plan it as a staffing exercise:
- Keep the people who built it. Overlap the functional leads and integration developers with the support team for at least the first close.
- Cover each plant. Put on-site support in plants for the first two weeks, then shift to a support desk with plant escalation.
- Track a short list of measures daily: orders shipped on time, production reported, interface errors, inventory adjustments and open tickets by severity.
- Define the exit. Agree in advance what has to be true to hand over to steady-state support.
Our article on why ERP transformations fail after go-live goes deeper on staffing the stabilization period. Maxary places functional leads, integration support and plant-floor specialists for cutover and hypercare. See what we staff.
Frequently asked questions
What should an ERP go-live checklist include?
Data readiness and reconciliation, integration and plant-floor system testing, completed user acceptance testing, a rehearsed cutover plan with rollback criteria, trained users on every shift, and a staffed hypercare plan.
What is ERP hypercare?
Hypercare is the period right after go-live, typically 30 to 90 days, when the implementation team stays in place to fix issues quickly and stabilize the system before handing over to steady-state support.
How long should hypercare last for a manufacturer?
Long enough to cover at least the first month-end close and the first full production and shipping cycles in every plant. For most manufacturers that is 60 to 90 days, with on-site plant support in the first two weeks.
Who decides go or no-go?
A steering committee with business, finance, operations and IT leaders, against criteria agreed weeks in advance and supported by evidence from mock cutovers and testing.