If you are running Odoo 16 or earlier, you have probably already heard about the 25% legacy surcharge Odoo began applying to Enterprise subscriptions in April 2026. It changes the cost calculation for anyone sitting on an older version but it does not automatically mean you should upgrade right now.
The right answer depends on your specific situation. Here is a structured way to think through it.
What does the Odoo legacy surcharge actually mean?
Odoo's covered versions are currently v17, v18 and v19. These are the three most recent major releases. If you are running anything older, a 25% surcharge applies to your annual Enterprise subscription at your next renewal, for any renewals after 4 July 2025.
There is no hard deadline forcing you off an old version. The surcharge is simply the price for staying put. Think of it less as a cliff edge and more as a toll road. You can keep driving but the meter keeps running.
Do the maths before you decide anything
Before weighing up your options, do one simple calculation. Divide your upgrade project cost by the annual surcharge amount. That figure tells you roughly how many years before the upgrade pays for itself in avoided fees alone.
Upgrade cost / Annual surcharge cost = Number of years before upgrade pays for itself
As a rule of thumb, if the number of years is under two, the financials favour upgrading now. Beyond three or four years, paying the surcharge while you plan properly can make sense, as long as you actually have a plan and a timeline.
2 things make the maths worse the longer you wait:
- The surcharge compounds every year you stay behind
- Odoo has introduced 7% annual price indexation on contracts which means the base figure the surcharge is calculated on keeps going up.
How customised is your Odoo instance?
This is often the factor that tips the decision. A relatively standard Odoo setup is faster and cheaper to upgrade. A heavily customised one, with custom modules, bespoke integrations or significant workflow modifications, requires that code to be reviewed, rewritten or validated against the new version.
The further behind you are, the bigger the gap. Moving from v16 to v19 means crossing three major versions. Each one may have introduced framework-level changes that affect your custom code.
If your instance has significant customisation, get a proper scoping quote before you try to compare upgrade cost against surcharge cost. Without it you are comparing guesses.
Odoo upgrades and Australian compliance obligations
For Australian businesses, staying on an older version is not just a cost question. It has real compliance implications.
Newer versions carry ATO-approved payroll updates, PEPPOL e-invoicing improvements and STP Phase 2 support. These do not always backport to older versions and the compliance obligations only grow over time.
If your business uses Odoo for payroll, accounts payable or ATO reporting, a legacy version carries risk that does not show up in the surcharge fee. That risk is worth factoring in as a separate line item when you are making the call.
Your hosting environment affects your options
Where you run Odoo changes how much flexibility you have.
On-premises deployments give you the most control. You can technically stay on an older version indefinitely, pay the surcharge and keep operating. The main risks over time are security vulnerabilities building up and third-party integrations eventually becoming incompatible.
Odoo.sh is more constrained. Each version has roughly a six-year hosting lifespan and the underlying Ubuntu OS has a four-year life. Very old versions cannot stay on Odoo.sh indefinitely, regardless of what you are willing to pay.
Odoo Online customers largely have this decision made for them. Upgrades are managed as part of the SaaS service.
Be realistic about your internal capacity
Upgrades take internal resource. Key users need to be available for testing, documentation needs updating and there is always a settling-in period where things slow down before they speed up.
If your business is mid-restructure, working through an acquisition or simply short on project bandwidth right now, deferring for 12 months and paying the surcharge can be the right call operationally.
The danger is that 12 months becomes indefinite. If you are paying the surcharge, it needs to be a bridge to a planned upgrade, not a way of avoiding the conversation.
So should you upgrade or pay the surcharge?
Pay the surcharge if your upgrade break-even is beyond three years or if your instance is heavily customised but you have a real upgrade project scheduled within the next 12 to 18 months.
Upgrade now if the break-even is under two years, if you have compliance exposure on payroll or e-invoicing or if you are already planning other significant changes to the business anyway.
The scenario that hurts everyone is deferring with no plan at all. The further behind you fall, the harder and more expensive the eventual upgrade becomes and the surcharge keeps growing in the background the whole time.
If you want to talk through your specific situation, get in touch with our team. We are happy to help you work through the numbers.