Loading…
Loading…
The final checks that turn go-live from a nervous leap into a calm, confident switch-on.
24 checks · 6 sections
Go-live should feel like flipping a switch, not jumping off a cliff. The difference is preparation: everything tested, data reconciled, people trained, and a clear plan for the day itself and the days after. Run through this checklist before you set a date — the more you can tick, the calmer go-live morning will be.
Functional testing is complete
Every configured process has been run end-to-end and behaves as expected.
User acceptance testing is signed off
Real users tested with real scenarios and formally agreed it's fit for purpose.
Key business scenarios are verified
Your highest-volume and highest-risk flows — sales, purchase, invoicing — all work.
Known issues are logged and triaged
Anything outstanding is documented, with a call made on fix-before vs fix-after.
Master data is migrated and checked
Customers, suppliers, items and accounts are loaded, clean and spot-verified.
Opening balances are in and reconciled
Trial balance, stock and outstanding AR/AP match your old system to the rupee.
The reconciliation numbers tie out
Someone from finance has confirmed the totals agree — not just 'looks about right'.
A cut-off point is agreed
You know the exact date/time the old system stops and the new one becomes the record.
Training is complete
Every user has been trained on the tasks they'll actually do day one.
Roles and permissions are set
People can see and do what they need — and nothing they shouldn't.
Department champions are briefed
Your internal go-to people know the plan and can support their teams.
Quick reference guides are handy
Short how-to notes for common tasks reduce the day-1 flood of questions.
The go-live date is agreed
A date everyone owns — ideally after a period-end, avoiding your busiest week.
The cutover sequence is written down
The ordered list of steps from 'stop old system' to 'new system live'.
Who does what is clear
Every cutover task has a named owner and a time slot — no assumptions.
Everyone is told the plan
Staff, and where relevant customers and suppliers, know what changes and when.
Hypercare support is on standby
Your implementation team is available and responsive for the first days/weeks.
A rollback or parallel-run plan exists
You've decided how to run both systems (or step back) if something goes wrong.
An issue log is set up
One place to capture problems, owners and status — so nothing gets lost in chat.
Escalation contacts are known
Everyone knows who to call for a blocker, and how fast to expect a response.
First live transactions are verified
A real sales order, purchase and payment are posted and checked start to finish.
GST and e-invoice are working
A live invoice generates the correct GST, IRN/e-invoice and e-way bill where needed.
Daily health checks are running
Someone confirms backups, integrations and key reports each day of hypercare.
A review after the first close is booked
Sit down after month-end to fix rough edges and plan the next improvements.
Tip: print this page (Ctrl/Cmd + P) to use it as a working checklist.
You're ready when testing and UAT are signed off, opening balances reconcile to your old system, users are trained, roles and permissions are set, and you have a written cutover plan plus support on standby. If any of those are shaky, it's usually better to hold the date than to go live on hope — a short delay is far cheaper than a messy launch.
A parallel run means processing the same transactions in both your old system and the new ERP for a short period, then comparing the results. It builds confidence that the new system is accurate before you fully retire the old one. It's extra effort, so many businesses use a lighter version — reconciling opening balances and closely watching the first weeks — rather than a full dual entry.
The first days and weeks — often called hypercare — are when questions and edge cases surface. You want your implementation partner responsive, an internal champion in each department, an issue log to capture problems, and clear escalation contacts. In India, pay special attention that GST, e-invoicing and e-way bills are generating correctly on the very first live invoices.
Get a clear plan, an honest timeline, and a fixed scope. Talk to a real expert today — whether or not you work with us.
Kochi (Kadavanthra & Infopark) · Thiruvananthapuram · across India & overseas · In business since 2011