The Odoo Version Upgrade Guide: A Practical Checklist Before You Migrate
This one’s for businesses already on Odoo, not businesses moving to it. Odoo ships a new major version every year, and older versions eventually stop receiving security and bug-fix support. At some point, upgrading isn’t optional — the only question is whether it’s planned or forced.
Here’s a practical checklist for what to look at before you commit to an upgrade date.
1. Check what’s actually custom
Standard Odoo features upgrade cleanly, because Odoo maintains the upgrade path for them. Custom modules and heavily modified views don’t get that guarantee — someone has to check that each one still works on the new version, and fix what doesn’t.
Before you plan a date, get an honest inventory of what’s custom in your instance: custom modules, modified standard views, and third-party apps from the marketplace. That list is what actually drives the cost and timeline of the upgrade, not the Odoo version jump itself.
2. Know which integrations are at risk
If Odoo talks to anything else — a payment gateway, a shipping provider, a government e-invoicing API, an accounting export — check each one specifically. API changes between major versions are usually well documented by Odoo, but third-party integrations built on top of them aren’t automatically covered.
3. Don’t skip the staging test
Never upgrade a production database directly. Odoo’s upgrade process (whether self-managed or via Odoo’s own upgrade service) should always run against a copy of your data first — a staging environment you can break, test, and throw away without consequence.
Test the actual daily workflows your team uses, not just whether the system boots. Create a sales order, post an invoice, run a stock move, generate the reports someone checks every week. That’s where upgrade issues actually show up, not on the login screen.
4. Plan around your accounting close, not around convenience
Upgrading mid-way through an open fiscal period or in the middle of month-end closing is how avoidable stress gets added to an already technical process. Pick a cutover date that lines up with a natural close in your accounting calendar.
5. Budget time for user re-training, not just technical work
Odoo’s UI does shift between versions — sometimes subtly, sometimes not. Build in a short internal walkthrough for staff before go-live, especially for anyone who relies on a specific screen or report that may have moved or changed slightly.
6. Have a rollback plan, not just a go-live plan
Know, in advance, what “this isn’t working, revert to the old version” actually looks like — and how long you’re willing to run degraded before pulling that trigger. Deciding this under pressure, mid-cutover, is how a bad day becomes a bad week.
Where Zenithonsoft fits
Migration guidance and version-upgrade support are part of our Professional and Managed tiers for the industry solutions we build, and it’s also something we handle directly for existing Odoo customers as part of Odoo Advisory. If you’re not sure whether now is the right time to upgrade, or what your specific customizations will cost to carry forward, book a free discovery call — we’ll look at your actual instance before giving you a number.