Odoo upgrades · Silver Partner
Odoo upgrades without the drama
Odoo releases a new version every year and officially supports the three most recent, which means every Odoo site has a countdown running whether anyone is watching it or not. Upgrades are also where the platform's best improvements arrive. This page covers how we run them for Australian businesses, from single-version hops to rescues of sites stranded three versions back.
The part most people get wrong
Odoo's upgrade service is free for every Enterprise subscriber; you do not need a partner to convert your database. What the free service does not do is the part that hurts: testing and migrating your custom modules, checking your integrations still work, cleaning years of accumulated data, and timing the cutover so it doesn't land on BAS week. That is the work you are buying from a partner, and any partner who implies the database conversion itself is their secret sauce is telling you something about themselves.
Why upgrade at all
Three honest reasons. Support: outside the three-version window you are on your own for fixes. Features: recent versions have brought real gains in accounting, inventory and usability, and our Odoo v20 roadmap guide covers what is coming next. Cost of waiting: each version skipped makes the eventual jump harder, because custom code drifts further from the current framework. A v15 site upgrading today has a materially bigger project than it would have had one version at a time.
How we run an upgrade
The process is unglamorous on purpose. We audit your customisations and integrations, run a test upgrade on a staging copy, fix what breaks there rather than in production, have your team test their real workflows on staging, then schedule the production cutover for a quiet window with a rollback plan. Australian localisation gets checked explicitly: our guide to what changed in the AU localisation shows why that step is not optional.
Stranded on an old version?
Sites two or more versions behind, often with a departed developer's custom code, are a speciality we didn't plan on but do a lot of. The playbook changes: sometimes stepping through versions, sometimes reimplementing cleanly on the current version and migrating data, which is occasionally cheaper than dragging a decade of custom code forward. We will price both paths so the decision is yours. If the site was built by someone else, that is fine; most of our upgrade work starts that way. And if the problem is bigger than the version, our ERP rescue service is the right front door.
FAQ
Frequently asked questions
How much does an Odoo upgrade cost in Australia?
A lightly customised single-version upgrade typically lands in the low five figures; heavily customised or multi-version sites cost more, and a scoped audit gives you the number before you commit. The database conversion itself is free from Odoo for Enterprise subscribers; the cost is testing, custom code and cutover.
How long does an Odoo upgrade take?
Most single-version upgrades run 3 to 8 weeks end to end, with production downtime measured in hours over a weekend. Multi-version jumps and heavy customisation extend the testing phase, not usually the downtime.
Can we skip versions, say v15 straight to v19?
Yes, the upgrade service supports jumping versions. Custom modules still have to be rewritten for the target framework, which is where multi-version jumps earn their reputation. Occasionally a clean reimplementation beats the jump, and we will tell you when.
Do you upgrade sites you didn't build?
Constantly. We start with a customisation audit so nobody is surprised mid-project, and you get documentation of what your system actually contains, which is often the first time anyone has had it.
Not sure how far behind you are?
Tell us your version and what's custom, and we will give you a straight read on the size of the jump, from our Brisbane team of certified Odoo Silver Partner consultants.
Book before the support window decides your timeline for you.