Go-live is where months of work meet the first Monday morning. Companies that treat it as one day often struggle; those that plan it as a week, with owners and checks, usually have a calm first month. This checklist assumes you have completed testing as described in acceptance testing and moved data as in the data migration guide.
Seven days before
- Confirm the go-live date with department heads, and avoid month-end, VAT filing days and major holidays.
- Announce the data freeze: no new master data in the old system after a stated time.
- Print quick-reference cards for the five most common tasks of each role.
- Check that every user can log in, has the right role and has completed training.
- Confirm hardware: printers, label printers, scanners, tablets and internet backup.
The cutover day
- Take a full backup of the old system and keep it read-only.
- Load final balances: bank, customers, suppliers, stock quantities and values, fixed assets, open orders and leave balances.
- Reconcile totals with the old system: trial balance, receivables and payables listings, stock valuation. Differences must be explained, not ignored.
- Create a test transaction in each main flow, such as a sale, a purchase, a payment and a stock transfer.
- Sign-off by finance and operations before opening the system to all users.
The first five working days
| Day | Focus | Daily check |
|---|---|---|
| 1 | Sales, purchasing and receiving | Count of documents created, errors logged, stuck users |
| 2 | Invoices, receipts and payments | Cash and bank balances against actuals |
| 3 | Stock movements and counts | Spot-count five fast items against the system |
| 4 | Reports and approvals | Do managers see the numbers they expect? |
| 5 | Review and fix list | Prioritised list with owners and dates |
Support rota
Name a first-line support person in each department and a second line from the implementation team, with phone and WhatsApp contacts on the wall. Keep a shared log of every issue with time, user, description and status. Hold a ten-minute meeting each morning to review the log, decide priorities and tell users what changed.
Rollback rules
Decide in advance what would make you stop and return to the old system, for example totals that cannot be reconciled or an inability to invoice for two days. Write the criteria and the person who decides. You may never use them, but having them reduces panic when something goes wrong.
After the first week
Run the first month-end close carefully, review the improvement list and schedule refresher training. Adoption continues after go-live; read ERP user adoption and training. For the full project plan see the ERP implementation checklist. Talk to us about a managed go-live.
