Small Manufacturer MRP Go-Live Cutover Checklist
Most small plants go live on a new MRP over a weekend or a quiet week, and the risk sits in the data and the people, not the software. This checklist covers master data, opening balances, training and the fallback plan so cutover day is boring.
0 of 32 items complete
9 critical items still open - these are the highest-risk gaps.
Master data
Opening balances
People and training
Process and tooling
Cutover and fallback
Do not set a go-live date until all critical items are ticked. Review the list at a go/no-go meeting two days before cutover.
Want your cutover plan reviewed?
Optional: an ERP migration specialist checks your plan for gaps.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Assign each group to an owner: engineering for BOMs, the warehouse lead for balances, finance for costs, the plant manager for people. Review it weekly during the project, then hold a go/no-go meeting two days before cutover. Items marked critical block the date. Keep the printed list on the wall and tick items with a name and a date.
- One owner per group
- Weekly review before cutover
- Critical items block the date
- Record the decision in writing
Opening balances done right
Count stock close to the freeze and load it by location and lot. Load only open quantities on sales and purchase orders, never history. Decide how work in progress is handled: finish the jobs on the old system, or reopen them with remaining operations. Reconcile the opening stock value with the ledger, because a mismatch on day one becomes a variance every month afterwards.
People, not just data
Train each person on their own tasks using real parts, not a demo company. Name a super user for every shift, because the first questions come at 6 a.m. Plan a short daily meeting for two weeks to clear issues quickly. Expect productivity to dip in the first week and tell customers about possible delays in advance.
Common mistakes
Loading dirty data to hit a date, skipping the final count, loading every historic order, training in a sandbox with fake parts, and having no rollback line. Also common is leaving the old system writable, so two sources of truth appear. Decide the point of no return and communicate it.
Frequently Asked Questions
How long before go-live should I count inventory?
Count as close to the freeze as practical, ideally within 48 hours, and stop movements between the count and the load or log them to apply afterward. A count weeks earlier forces large corrections after go-live and undermines trust in the new system on day one.
Should I migrate historical orders?
Usually not. Load open orders and keep history in the old system or an export for reference. History adds migration cost and risk for little daily value. Migrate summary figures if reporting needs them, such as annual usage per part for planning.
What is a sensible go-live window?
Choose a quiet week away from month end, a major shipment or a customer audit. Many small plants cut over on a weekend and run the first week with extra support staff. Avoid going live in the last week of the quarter if finance depends on clean numbers.
When should we roll back?
Define criteria in advance, such as being unable to ship orders for a full day or stock errors that cannot be resolved by the daily meeting. Rollback is only practical in the first days, before new transactions pile up, so decide early and keep the old system intact.
If you want help planning data migration and cutover for an ERP or MRP, Netray can review your plan.
Related Tools
Small Manufacturer MRP Vendor Demo Question Checklist
Questions to ask in every cloud MRP demo so you compare vendors on your real process, not their sample data.
ERP Migration & SelectionSmall Manufacturer MRP Readiness Assessment
Score your readiness for MRPeasy, Katana, Odoo, ERPNext or a similar system, and see what to fix before you buy.
Other ERPsERPNext DocType Reference for Manufacturing
Lookup table of ERPNext manufacturing, stock, buying and selling DocTypes with what each stores and where it links.
Developer ToolsOdoo XML-RPC BOM Export Python Script Generator
Fill in your Odoo URL, database and filters to get a ready Python script that exports BOMs and component lines to a CSV file.
More ERP Migration & Selection tools
See all- Small Manufacturer ERP ROI and Payback Calculator
- 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