Cloud MRP Go-Live Cutover Plan Template
Go-live day fails when inventory balances, open orders and people are not ready at the same moment. This template gives you a one-page cutover plan with freeze, count, load and rollback decision so that Monday starts cleanly.
Fill in
Cloud MRP Go-Live Cutover Plan Template
Cutover Plan
Company: Northfield Fabrication LLC New system: Cloud MRP (vendor to be inserted) Cutover lead: Dana Whitfield
Data freeze: 2027-01-29 Physical count: 2027-01-30 Go-live: 2027-02-01
Scope of data to load
Item master, BOMs, routings, vendors, customers, open sales orders, open purchase orders, opening stock by bin and lot.
Cutover steps
| # | Step | Owner | Due | Done |
|---|---|---|---|---|
| 1 | Announce freeze: no new part numbers or BOM changes | |||
| 2 | Close or receive all open purchase receipts in the old system | |||
| 3 | Complete physical count by bin | |||
| 4 | Reconcile count to old system and adjust | |||
| 5 | Load opening inventory with lot numbers and cost | |||
| 6 | Load open sales orders and open POs | |||
| 7 | Run MRP once and review suggestions with the planner | |||
| 8 | Verify opening inventory value against the general ledger | |||
| 9 | Go-live briefing and floor tablets or scanners ready | |||
| 10 | Post first receipt, first job issue and first shipment |
Rollback criteria
Rollback decision time: Monday 12:00, if receiving and shipping cannot be posted
Roll back if inventory value differs from the ledger by more than the agreed tolerance, if receiving or shipping cannot be posted, or if MRP produces clearly wrong suggestions for top items. Keep the old system read-only and available for two weeks after go-live.
Approvals
Starting point. Agree the inventory value tolerance with your accountant and confirm period-end timing so the opening balance matches the books.
Cutover readiness check
Share your plan and we will review risks in data loads and balances. Optional.
Optional. The tool and every export work without this. No spam.
How to use it
Fill the dates and the scope of data to load, then export and print. Assign an owner and due date for each step. Hold a 30 minute walkthrough with everyone listed, because most cutover problems come from steps nobody thought they owned. Keep the printed plan at the cutover lead's desk and tick steps off in real time.
Why the order matters
Freeze stops the data moving while you load it. The physical count then sets the true opening balances; loading book balances carries old errors into the new system. Open purchase orders and sales orders should load only after inventory so receipts and shipments can match. Running MRP once before opening the floor shows whether BOM or lead time data was loaded wrongly.
- Freeze, count, reconcile, load
- Match opening value to the ledger
- Run MRP before the floor starts
- Keep the old system read-only for two weeks
Rollback thinking
A rollback plan is not pessimism. Write down in advance what failure looks like and at what time you decide. For many small plants, the realistic fallback is to continue in spreadsheets for another few days while data is corrected. The key is that the decision time and criteria are agreed before stress begins.
Common mistakes
Going live without a physical count, loading lot-controlled items without lot numbers, and scheduling go-live on a month-end when accounting is also closing. Also train people on the exact transactions they use in the first week, not the whole system.
Frequently Asked Questions
Do I need a full physical count before go-live?
It is the safest way to set opening balances, especially for lot or serial controlled items. Plants with strong cycle counting may count only high-value or fast-moving items, but should document the decision.
When should I choose the go-live date?
After a quiet period, and not on a month-end or a heavy shipping week. Many plants choose the first working day of a month so the opening balance aligns with the ledger.
Should I run both systems in parallel?
A short parallel run of one or two jobs is useful. Running everything twice for weeks creates double entry and frustration. Pick a clear switch date and keep the old system read-only.
Who should be cutover lead?
Someone with authority over planning, purchasing and the shop floor, usually the operations manager. The lead must be free of other tasks during cutover week.
Netray can compare your opening balances to ERP or spreadsheet extracts and flag mismatches before cutover.
Related Tools
Cloud MRP Implementation Project Plan Worksheet
Editable task list with owner, start date, days, hours and rate that totals your internal and consultant effort for a cloud MRP rollout.
Engineering & PLMCloud MRP BOM Data Cleanup Worksheet
Clean each BOM line with unit of measure, scrap allowance and cost before loading data into MRPeasy, Katana, Odoo, ERPNext or Fishbowl.
Supply Chain & InventorySmall Plant Min Max Reorder Point Worksheet
Compute reorder point, maximum level and suggested order quantity per item so you can load clean planning parameters into your cloud MRP.
ERP Migration & SelectionSmall Manufacturer ERP Requirements Document Template
A fill-in requirements document you can send to MRPeasy, Katana, Odoo, ERPNext or Fishbowl resellers so every vendor quotes the same scope.
More ERP Migration & Selection tools
See all- Small Manufacturer ERP Cost Calculator
- Spreadsheet to MRP Migration Checklist
- Cloud MRP Vendor Demo Script Template
- Cloud MRP Vendor Quote Comparison Worksheet
- ERP TCO Comparison Calculator (5-Year)
- ERP Migration Risk Assessment
- Data Migration Effort Calculator
- ERP Selection Scorecard for Manufacturers
- ERP Go-Live Readiness Checklist