Manufacturing ERP Cutover: Rehearsal and Recovery Checklist

A manufacturing ERP cutover needs a defined transaction boundary, a rehearsed migration sequence, reconciled operating records and a named go/no-go decision owner. A backup alone does not explain how the factory will handle a receipt or job update while systems are changing.

Choose an operating window with the people who own stores, production, quality, purchasing and accounts. Define which activities pause, which may continue and where any permitted interim records are captured. Do not promise zero downtime before the sequence has been tested.

Define the last-entry boundary

Identify the final accepted transaction in the old process, the export time and the first transaction permitted in the new process. State how the team handles late paperwork, receipts in transit, open jobs, outside material and quality holds.

Rehearse with representative data

Microsoft's cutover guidance describes planning and rehearsing the transition. Time the sequence your team will actually perform: stop or bound entry, export, migrate, validate, reconcile, grant the intended access and enter the first accepted transaction.

Include a partial delivery, a held lot, an open production job and a correction. Record elapsed time and who is available at each step. A rehearsal that imports a clean sample but omits reconciliation will understate the operating window needed.

Trace a delivery that crosses the boundary

In this illustrative example, a PO is for 60 parts. Before cutover, 35 have been received and accepted; 25 remain due. Preserve the receipt history and remaining commitment so the next 25-piece delivery is posted once in the new process.

Check that 35 + 25 reconciles to 60 without importing the old receipt again as a new movement. If some of the 35 are on inspection hold instead, preserve that status separately; a received quantity does not by itself establish usable stock. The numbers demonstrate the check and are not a customer case study.

Set go/no-go criteria before the window begins

Assign one decision authority and named reviewers. Record go, hold or recover with the evidence, time and conditions. A new discrepancy after go-live may require correction in the new system rather than restoring a backup that would erase later valid work.

Reconcile the first operating shifts

Track issues by affected record, operating impact, owner and next review. Keep the interim log until every entry has a corresponding posted record or an approved disposition. Reconcile transfers to accounting and other systems with their source IDs.

For earlier readiness gates, use the ERP implementation checklist. The timeline guide helps plan dependencies before setting the window. Ask the Optiwise implementation team to document the cutover and recovery responsibilities in your agreed release plan.

Questions from manufacturing teams

Can ERP cutover guarantee no factory downtime?

No general guarantee follows from a checklist. Define the operating window and test the actual migration, validation and first-entry sequence with representative records.

What happens to transactions created during cutover?

Use an approved boundary and a controlled interim log where activity is permitted. Reconcile every interim record to its eventual posting so it is neither lost nor entered twice.

Should we restore the backup whenever an issue appears?

Use the agreed recovery criteria and decision owner. A bulk restore can remove valid new transactions, so assess current records and reconcile the affected work before choosing recovery.