ERP Migration & SelectionFree templatePDF, Excel, Word exportAcumatica

ERP Cutover Weekend Plan Template for Acumatica and Sage Projects

Cutover is a few hours where mistakes are expensive. A written runbook with owners, times, validation checks and a rollback rule keeps a weekend go-live calm and auditable.

Fill in

Live preview
Download:

ERP Cutover Weekend Plan Template (Acumatica and Sage)

Cutover Plan: Northfield Fabrication Inc.

Moving from Sage 100 2021 to Acumatica Manufacturing Edition Cutover lead: A. Moreno Legacy freeze: Friday 2027-06-25 17:00 Go-live: Monday 2027-06-28 06:00 Rollback decision deadline: Sunday 2027-06-27 18:00

Cutover schedule

StepTaskOwnerStartDurationDone
1Announce freeze, stop new transactions in legacyCutover lead
2Close open shipments, receipts and shop ordersOperations
3Final backup of legacy databaseIT
4Extract final master and open transaction dataData lead
5Load masters, then open orders, then balancesPartner
6Run validation checksFinance and Operations
7Go/no-go meetingSteering group
8Open system to users, confirm accessIT

Validation checks

Trial balance agrees to legacy within 0.00; AR and AP aging totals match; inventory quantity and value by warehouse match; open sales and purchase order counts match

Go/no-go criteria

CriterionRequired resultStatus
Trial balance proofZero variance
Subledger agreementAR, AP and inventory agree
Critical interfacesTested and running
User accessRoles confirmed for all named users
Open ordersCounts and values agree
SupportHypercare staffed

Rollback plan

If go/no-go criteria are not met by Sunday 2027-06-27 18:00, operations continue on Sage 100 2021. Transactions entered in the new system during validation are discarded. The legacy backup taken in step 3 is retained read-only. The steering group sets a new cutover date.

Hypercare

Partner consultant on site for the first 5 business days; daily 8:30 stand-up; issue log reviewed twice daily

Approvals

Steering group chair / Date
Finance lead / Date
Operations lead / Date
Cutover lead / Date

Adapt the schedule to your site calendar, shipping cutoffs and month end timing. Avoid cutting over during a fiscal period close unless the plan explicitly handles it.

Automate cutover validation queries

Ask how comparison queries between old and new ERP can be generated and run read-only.

Optional. The tool and every export work without this. No spam.

How to use it

Fill in the systems, freeze and go-live times and the rollback deadline, then expand the schedule table with real durations from your test loads. Each step needs one owner. The validation checks and go/no-go criteria should be agreed before the weekend, not decided during it. Export to PDF, print copies for the war room and tick steps off as they complete.

  • Use timings from your rehearsal, not estimates
  • Name a decision maker for go/no-go
  • Set the rollback deadline before you start
  • Keep the legacy backup untouched

Sequence of a typical cutover

The common order is freeze legacy, close in-flight transactions, back up, extract, load masters, load open orders and balances, validate, then decide. Masters must go first because transactions refer to them. Financial opening balances usually load last, once inventory and subledger values are known, so that control accounts reconcile. Interfaces and integrations are switched over after validation.

Go/no-go criteria

Use objective, numeric criteria. A trial balance variance of zero, subledgers that agree to control accounts, matching inventory quantity and value by warehouse, and counts of open orders are standard. Include a qualitative item for user access and for critical interfaces such as shipping or EDI. If a criterion fails, the plan should state who may waive it and how it is recorded.

Common mistakes

Teams skip a timed rehearsal, so the real load takes twice as long as planned. They also forget physical processes such as stopping receipts at the dock or reconciling work in process. Another frequent issue is leaving rollback undefined, so the decision gets made under pressure at 3 am.

Frequently Asked Questions

How long should a cutover take?

For an SMB manufacturer, final extract, load and validation often fit in a weekend, but it depends on data volume and the number of sites. Run at least one full timed rehearsal and plan the real cutover from that duration with a buffer.

Should we run both systems in parallel?

Full parallel operation doubles the workload and is rare outside finance. Many companies run a parallel financial close for the first period only. Decide this with your controller and auditors.

What is hypercare?

Hypercare is the first days or weeks after go-live with extra support: consultants on site or on call, a daily issue stand-up and fast fix turnaround. Define its length and staffing in advance.

Can I use this for non-Sage or non-Acumatica moves?

Yes. Replace the system names. The structure of freeze, load, validate, decide and rollback applies to any ERP replacement.

If you want help building validation queries across the old and new ERP so the comparison is automatic, we can scope that with you.