Go-live is a decision, not a date. Use this checklist to confirm data, testing, users, cutover and support are ready before you switch to the new ERP.
An ERP is ready to go live when migrated data has been reconciled and signed off, user acceptance testing is complete with no open critical issues, users are trained and have accounts with the right roles, the cutover plan has been rehearsed, VAT, invoice and payroll outputs have been checked, integrations are tested, and a support team is in place for the first weeks. Agree go or no-go criteria in advance and decide against them, not against the date.
Most go-live problems were visible beforehand: data that never reconciled, tests that were skipped, or users who were trained weeks earlier and forgot.
A readiness review brings these issues out while there is still time to fix them or move the date. It also gives the steering committee a clear basis for the decision.
Use this list alongside your implementation checklist and plan support with post-go-live hypercare.

Problems that readiness checks catch.
Opening balances or stock values that do not match the old system.
Known issues waved through to meet the date.
Users who cannot post or approve on day one.
Each area needs a named owner and a sign-off.
Masters cleaned, opening balances, stock and open items reconciled and signed off.
End-to-end user acceptance tests passed, with no open critical defects.
Accounts created, roles and approvals tested, training completed.
Bank, payroll, e-commerce, e-invoicing and other links tested.
Hour-by-hour plan rehearsed, with freeze dates and rollback steps.
Hypercare team, issue log and escalation contacts in place.
An example. Agree your own thresholds with the steering committee.
| Go if | No-go if | Evidence | Owner | |
|---|---|---|---|---|
| Data migration | Balances reconcile to the penny | Unexplained differences | Signed reconciliation | Finance lead |
| Testing | No open critical defects | Critical defects open | Test log | Project manager |
| Training | All key users trained | Key roles untrained | Attendance records | Process owners |
| Integrations | All live links tested | Bank or payroll untested | Test results | IT lead |
| Compliance | VAT and invoice outputs checked | Invoice layout not approved | Sample outputs | Finance lead |
A typical run-up for a mid-sized company.
Durations are typical ranges; your plan is agreed after discovery.
Check every area and agree actions.
Run the full cutover with real timings.
Refresh training close to go-live.
Decide against the agreed criteria.
Load final data, switch on and support users closely.
Outputs to confirm before the first live transaction.
Approved invoice and credit note layouts with AED VAT and TRNs.
Tax codes mapped so the first VAT return can be prepared from the new system.
A parallel payroll run and a tested WPS salary file, if payroll is included.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
The outcomes to aim for.
Balances match the old system.
Work continues from day one.
Issues found before go-live.
Criteria agreed in advance.
More guides and services connected to this topic.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertAt the start of a month or quarter, away from VAT return deadlines, payroll runs and year-end close.
A short parallel run for payroll or key reports can help. Running everything twice for months usually causes confusion.
Move the date. A short delay costs far less than going live with unreconciled data or untested processes.
The steering committee, based on criteria agreed in advance and evidence from each area owner.
Usually two to six weeks, covering at least one month-end close.
Yes. We run independent readiness reviews for projects with any implementation partner.
Related Solutions
Talk to us about your departments, branches and approval rules, and we will map a phased rollout.
Sharjah Media City (Shams), Sharjah, UAETeam in Dubai, serving all seven emirates