Trial migrations belong in the build
If the first full data load happens the week before go-live, every problem it reveals becomes an emergency. Load trial datasets during the build instead: customers, vendors, products and balances, cleaned of duplicates, in a staging environment your team can check.
Each trial should end with a reconciliation sheet and a list of decisions for your team, such as which flagged duplicates to merge and which inactive records to archive.
Reconcile what matters on day one
- Opening balances, agreed with finance line by line.
- Open sales and purchase orders, with quantities still to deliver or receive.
- Stock on hand by location, ideally confirmed by a physical count.
- Customer and vendor balances, matched to statements.
Test with the people who will use it
Staff meeting the system for the first time on go-live day is one of the most common causes of a bad first month. User acceptance testing should run real scenarios, role by role, and end with a signed test matrix and recorded training your team can return to.
The go or no-go checklist
- Signed test matrix with no open critical findings.
- Final reconciliation sheet signed by finance.
- Integrations tested end to end, with error handling and a runbook.
- Scanners, printers and other hardware checked on site.
- A data-entry freeze on the old system at an agreed time.
- A named person on your side and ours for the first days after cutover.
After the weekend
Go-live is not the finish line. The team that built the system should stay on it through the first month-end close, fixing issues the day they surface. That is what our four weeks of hypercare are for.