UAT and the Go-Live Checklist: Testing Odoo Before You Switch
Short answer: User acceptance testing (UAT) is where real users run real business scenarios in the new system before it goes live, to catch what a developer's own testing would miss. A rushed or skipped UAT is one of the most common reasons go-live week turns chaotic.
What should UAT actually cover?
- End-to-end scenarios, not single screens: a full sales order from quotation to payment, not just "can I open the form."
- Edge cases that happen in real business, like a partial delivery, a returned item, or a multi-currency invoice.
- Reports and documents users rely on daily, checked for correct data and layout, not just that they generate.
- Permissions: can each role actually do what their job requires, and nothing more.
A practical go-live week checklist
- Opening balances migrated and reconciled against the old system.
- Critical integrations (bank, e-invoicing, payment gateway) tested with real transactions, not just a demo.
- Users trained on their specific tasks, not a general system overview.
- A rollback or fallback plan agreed, in case something critical fails on day one.
- Support contacts and escalation path shared with everyone before, not during, the first crisis.
Why does skipping UAT cost more later?
An issue caught in UAT costs an afternoon to fix. The same issue discovered during live operation, with real customer data and real deadlines, costs days and damages trust in the new system right when people are still deciding whether they like it. UAT is not a formality; it is the cheapest point in the whole project to find problems.
| Aspect | Found in UAT | Found after go-live |
|---|---|---|
| Time to fix | An afternoon | Days |
| Data involved | Test scenarios | Real customer data and real deadlines |
| Effect on users | Confidence that the system was checked | Damaged trust while people are still deciding whether they like it |
Frequently asked questions
Who should do UAT, the project team or actual end users?
Actual end users, ideally the people who will use the system daily, since they notice what a project manager might not.
How long should UAT take?
It depends on scope, but rushing it to meet a date is a common mistake; a realistic UAT period should be planned from the start, not squeezed at the end.
What happens if UAT finds a major issue close to the planned go-live date?
The honest answer is usually to delay rather than go live with a known critical issue; a short delay is cheaper than a bad first week.
Go live with confidence, not crossed fingers
ExtraMile runs structured UAT and go-live planning for every Odoo implementation.
Ask about go-live planning or message us on WhatsApp: Egypt · Gulf
This article was drafted with AI assistance and reviewed and edited by the ExtraMile implementation team.