A straight answer

Does Odoo's 25% surcharge apply to Community edition?

Written for business owners, not developers · ~4 min read

Short answer: no. If you run the free, self-hosted Community edition, Odoo's April 2026 surcharge doesn't cost you a cent. But before you close the tab — the reasons to upgrade an old Community system are real, they're just different ones.

What the surcharge actually is

From April 2026, Odoo adds 25% to Enterprise subscription fees for companies that renew while running a version more than three releases behind the latest. It's a pricing mechanism on Odoo's own subscriptions — a nudge to get paying customers onto recent versions.

Self-hosted Community users don't have a subscription with Odoo. No subscription, nothing to surcharge. If someone is using the surcharge to hurry you into an upgrade and you're on Community, they haven't looked closely at your setup.

So can you just stay put?

For a while, yes — your system won't stop working in April 2026 or any other date on a calendar. The pressure on old Community versions doesn't arrive as a bill. It builds quietly, in three ways:

1. Security fixes stop

Odoo publishes security fixes for its three most recent versions. Once yours falls off that list, newly discovered holes stay open on your server — and your Odoo holds your customers, invoices, prices, and possibly employee data. If your system is reachable from the internet, this is the risk that should genuinely worry you.

2. The ground under it ages out

Your Odoo version was built for particular versions of Python and PostgreSQL — the language and database it runs on. Those have their own retirement dates. As they pass, routine things get fragile: a server operating-system update breaks the install, hosting providers drop support, and fewer people know how to keep the old stack alive. Old ERPs rarely fail dramatically; they just get more expensive to keep breathing.

3. Community modules move on

Much of what makes Community powerful is the ecosystem of free community-maintained modules (the OCA and others). Maintainers put their energy into current versions. Bugfixes and improvements stop landing on old branches, so any community modules you rely on are slowly frozen in time — bugs included.

The one cost that does grow: the jump itself

Every version between you and the current release adds changes that eventually have to be crossed — data structures, custom-feature adjustments, all of it at once. Upgrading from 16 is a modest project; the same system left until it's on the same six-version gap is a noticeably bigger one. Waiting doesn't avoid the cost, it compounds it. (For real numbers, see the pricing guide.)

No deadline panic needed — just a real number

There's no cliff-edge date for Community users, so don't let anyone sell you one. What's worth having is a fixed price for the upgrade, so "someday" can become a decision. We quote within 24 hours, and you pay only after you've seen your upgraded system working.

What upgrading involves

Less than you might fear: a backup of your database and a copy of your custom features, uploaded through a secure page. We move everything to the version you choose, check the numbers match, and hand you a working copy to try. The plain upgrade guide walks through it step by step.

Find out what your upgrade would cost

Send us a backup and your custom features. One fixed price within 24 hours — free, no meeting, and you only pay once you've seen it working.

Get your fixed quote