The last seven days are about control, not surprises
Go-live week is the stage where every open issue is either resolved, parked with a clear owner, or ruled out as low risk. By this point, the system should already have been configured, tested and signed off. The focus now shifts to making sure people, data and processes are ready for the first live day.
For a small or medium business, this week often exposes the things that were easy to miss earlier. A payment approval step that takes too long. A report that does not match the old format. A user who can log in but has not yet practised their actual daily tasks. The aim is not perfection, it is readiness with a proper backup plan.
- Confirm the go-live date and cut-off time for old-system entries
- Freeze any non-essential process changes for the week
- Assign one person to each key function, such as sales, stock, finance and support
- Make sure data backups are taken before the final migration
What should be finished before the switch
Before a new system launches, the business should know exactly what is moving across and what stays behind. That includes master data, opening balances, supplier records, customer details and any live transactions that must be carried over. If the data is messy, the new system will carry that mess forward.
A proper pre-launch checklist also covers user access, device readiness and business rules. If staff will be working through load-shedding or from a site with weak connectivity, confirm how they will access the system and what happens if power or internet drops during the first day.
- Validate customer and supplier records for duplicates, missing VAT numbers and old contacts
- Check stock quantities, units of measure and item codes
- Confirm roles and permissions for each user group
- Test printers, scanners and any integrated devices on site
- Review month-end, payroll or dispatch timing if the launch falls near a cycle close
In Durban or Gqeberha, coastal humidity can affect hardware rooms and equipment storage, so it is worth checking that devices and cabling are stored properly. In Johannesburg and Pretoria, offices often need a clean handover plan for high-volume teams that cannot afford delays at 8 am on Monday morning.
The support room should be ready before users arrive
During go-live week, the support structure matters as much as the software itself. Staff need to know who to call, what to record and how to escalate issues. A support room can be a physical boardroom, a shared call log or a virtual team channel, but the rule is the same: every issue must be logged and owned.
It helps to keep the first-day support team small and practical. Too many voices create confusion. One person should handle operational queries, one should watch data and transactions, and one should track any technical issue that needs fixing or rollback. That way the business is not guessing who is doing what.
- Keep a live issue register with time, user, module and status
- Use simple priority levels: urgent, same-day, next-day
- Agree when a problem should be escalated to management
- Prepare short scripts for common questions from users
- Keep system access details and backup contacts in one secure place
Training should focus on real work, not theory
In the final week, training should be short, practical and tied to daily tasks. A finance clerk does not need a generic overview if they are about to process journals, match invoices and run payments. A stores team needs to know how to receive goods, move stock and correct errors without breaking the workflow.
Good adoption depends on repetition. People remember better when they do the same transaction three or four times under supervision. That is why the last week should include guided practice, quick refreshers and a simple cheat sheet that staff can keep at hand. A five-minute reminder on a screen can save an hour of confusion later.
For a manufacturing client in the East Rand, for example, go-live week might include a morning rehearsal of receiving raw materials, a midday test of production issue slips and a close-of-day check on stock valuation. For a professional services firm in Cape Town, it could mean testing timesheets, project billing and approval flows before the first live invoice run.
The first live day needs a clean handover plan
Live day is not the end of the project, it is the start of business-as-usual support. The handover should spell out what happens in the first hour, what gets checked at lunchtime and what must be reviewed before close of business. If the team is spread across Centurion, Johannesburg and Durban, the timing of check-ins matters even more.
Management should expect a few minor issues. A report may need a filter changed. A user may forget a step. A stock balance may need a correction after the first receipt. These are normal if they are handled quickly and documented properly. The important thing is to keep operations moving while the team works through the early fixes.
- Check opening balances against signed-off migration reports
- Verify that first transactions are posting correctly
- Review any failed integrations before the end of the day
- Confirm that critical reports are available for management
- Record lessons learned while they are still fresh
What good go-live support looks like after launch
After the first week, support should move from intensive oversight to steady control. That usually means daily check-ins at first, then twice-weekly reviews, then normal support retainer or internal ownership once the process settles. The point is not to hover forever, but to make sure the business is stable.
At this stage, the team should also watch for hidden process gaps. Maybe approvals are taking too long in one department. Maybe a report is technically correct but not useful for decision-making. Maybe staff are bypassing a step because it adds no value. These are the practical lessons that turn a system launch into a working business change.
For South African SMEs, a successful go-live is often measured by small things: invoices going out on time, stock being counted properly, managers seeing the right numbers and staff not having to work around the system. That is where the real value shows up.
