Moving business records into a new ERP is more than an import exercise. Staff need to know when the old system stops being authoritative, how opening balances are checked and what happens if the first working day exposes a problem. A cutover rehearsal lets a business test those decisions before the real move.
A rehearsal that exposes a real migration problem
Consider a company moving customer invoices and stock records into a new ERP. The test import accepts every file, but finance finds two customer accounts with the same name and different balances. Operations finds that one product is counted in cartons in the old system and individual units in the new one. Technically successful imports have therefore produced records that are not ready for daily use. The rehearsal should stop those exceptions from becoming opening-day disputes. Keep a decision log, assign the customer issue to finance and the unit issue to the responsible inventory owner, and rerun the affected checks after the corrections are agreed.
Choose a complete business cycle
Select a small but representative set of customers, products, opening balances and transactions. Include an adjustment, an incomplete record and an approval that has not finished. A rehearsal built entirely from clean demonstration records will miss the exceptions staff meet in practice. Define the expected result before importing anything.
Give each record an accountable owner
Finance should approve the balances it will use, while the relevant operating team checks its customer, supplier or stock records. Record who can accept an exception and who must resolve it. The implementation team can run an import, but it should not silently decide what an unexplained balance means for the business.
Rehearse the sequence and elapsed time
Write the order of exports, cleaning, imports, checks and access changes. Run those steps against a test environment and record where the team has to stop for clarification. Include time to review the results. A migration that completes technically overnight may still require substantial business review before staff can transact.
Define a usable recovery decision
Agree who decides whether to continue, pause or return to the previous process. Specify which records must be preserved and how new transactions will be handled if the move is paused. Test the recovery procedure in the rehearsal environment. A document saying that backups exist is not the same as a demonstrated recovery process.
Turn the rehearsal into a go-live checklist
Record failed checks, responsible owners and the evidence required to close each issue. Repeat only the affected steps when practical, then obtain the agreed sign-off. Include first-day support, staff communication and a route for reporting problems. Ask the implementation provider to price rehearsal and validation explicitly in the project scope.
A quick reference for your team
| Check | Evidence before approval |
|---|---|
| Customers and suppliers | Duplicates reviewed; stable references mapped |
| Opening balances | Totals reconciled and signed off by responsible staff |
| Stock units | Units and pack conversions confirmed |
| Open transactions | Outstanding invoices, orders and approvals accounted for |
| Recovery | A rehearsed decision and recovery process |
What should the implementation quotation include?
Ask for discovery, record mapping, trial imports, reconciliation support, training, cutover assistance and post-launch support to be separated. Confirm what your team must supply and who decides whether an exception is acceptable. A proposal that only describes software installation does not tell you who will check the business records. The right scope depends on the systems and workflows being moved, so use representative anonymised data before accepting an estimate.
Frequently asked questions
Must the entire business migrate at once?
Not necessarily. A phased move may be suitable, but it needs clear rules for which system owns each record during the transition.
Who should approve the imported totals?
The business owners of those records, supported by the implementation team. Approval should identify the checks completed and any unresolved exceptions.
Discuss your requirements
Discuss your ERP migration, source systems and cutover requirements with ZamaCore. Visit ZamaCore.