Exit criteria
Leave hypercare when all of these are true, not when the calendar says so:
- No S1 or S2 issue has been open for more than 24 hours in the last five consecutive business days.
- Superusers resolve 80% or more of queries without the partner, for five consecutive business days.
- The first month-end close is completed in Odoo, and finance has confirmed the numbers.
- If payroll is live, the first full pay run was processed and approved without consultant help.
- All in-scope daily transactions are in Odoo, with no parallel Tally or Excel records for the same data.
- A BAU support arrangement is signed and every user knows how to raise an issue.
Business-as-usual support
After hypercare, support moves to a steady model:
- L1 stays in-house: superusers, with time protected in their role.
- An internal Odoo lead (for mid-sized companies and up) owns configuration changes, user management and the improvement backlog.
- The partner provides L3 under an AMC or retainer with a written SLA, and a clear definition of what's a bug (covered) versus a change (quoted).
- A change-control routine: small monthly releases tested on a staging copy first, never direct changes to production.
Measure the benefits you promised
The business case promised numbers: a shorter close, lower inventory, faster collections, less admin time. Now measure them, against the baseline you recorded before the project:
| KPI | Baseline | At 3 months | At 6 months | At 12 months |
|---|---|---|---|---|
| Month-end close (days) | 12 | |||
| Stock accuracy (count vs system) | unknown | |||
| Inventory value (৳) | ||||
| DSO (days) | 45 | |||
| VAT return preparation (hours) |
Expect the ramp we used in the ROI calculator: labour and procurement benefits first, inventory and collections from month 7, and production and waste later. If a benefit isn't showing up on schedule, find out why. It's usually a process that's being run around the system, not through it.
The 3-month and 6-month reviews
Hold a structured review at three and six months with the sponsor and process owners:
- What are we still doing outside Odoo, and why?
- Which reports do managers actually use, and which do they rebuild in Excel?
- Which open S3/S4 items and change requests matter now?
- Are the benefits on track against the business case?
- What's phase 2 (payroll, quality, maintenance, a second site)?
A mature implementation isn't the one with the most modules. It's the one where management takes decisions from Odoo's numbers without checking them against a spreadsheet first.
Keep it healthy
- Access review every quarter. Deactivate leavers the day they leave, and remove access nobody needs anymore.
- Backups tested, not just taken. Restore to a test database twice a year.
- Compliance updates. Every June's budget changes rates and forms. Plan a configuration check each July. Compliance Watch lists the changes and what to update.
- Refresher training for new joiners and whenever processes change.
- Upgrade planning. Keep customisations few and documented so each Odoo version upgrade stays affordable.
Exercise (15 minutes). Fill in the baseline column of the KPI table for your company today. If you can't, that's the first task: without a baseline, you'll never be able to show the ERP paid off.
Key takeaways
- Exit hypercare on criteria: stability, L1 capability, a clean first close, full adoption.
- BAU means in-house L1, an internal Odoo lead, partner L3 under SLA, and change control.
- Measure benefits against the baseline at 3, 6 and 12 months.
- Review access, backups and compliance on a fixed rhythm.
You've finished the course
Well done. Put it to work with the free tools: check your readiness, build your business case, and download the UAT, migration, training and hypercare templates. If you'd like an experienced second opinion on your go-live plan, get in touch.