Implementation · Upgrades
What drives the cost of an Odoo upgrade
There is no price list for an Odoo upgrade, and any number given before someone has read your custom code is a guess. What we can explain is what sets the number: the cost drivers, what Odoo's own upgrade service covers, why waiting makes it bigger, and how to make it smaller.
Key takeaways
- Custom code usually sets the cost, above all code that touches the web client.
- Odoo's upgrade service is free for Enterprise, but it does not upgrade your custom modules.
- Community databases use the OCA's OpenUpgrade, one version at a time.
- Every year you wait adds a release of changes, and standard support lasts three years.
- Retire modules standard Odoo now covers, and keep the rest upgrade-safe with tests.
"How much will the upgrade cost?" is the first question in almost every upgrade conversation, and the answer depends on things nobody can see from outside the database. Two companies on the same version, with the same apps and the same number of users, can face very different upgrades, because one carries a few small modules and the other carries years of custom code written by several vendors.
We do not publish upgrade prices, and this article does not either. It explains what drives the cost, what Odoo's own upgrade service does and does not include, why the cost grows while you wait, and how we quote. If you know which version you are on and roughly what has been customized, you will be able to see which drivers matter for you.
What Odoo's upgrade service covers, and what it does not
For Enterprise customers, Odoo's upgrade service is part of the subscription. Odoo's documentation states that upgrading a database to the most recent version is free with Odoo Enterprise, including support to fix discrepancies in the upgraded database. The service covers every standard app, every customization made with Studio as long as Studio is still installed and its subscription active, and developments covered by a maintenance-of-customizations subscription with Odoo. It is limited to the technical conversion of the database: the standard modules and their data.
What it leaves out is usually where the cost sits. Odoo lists three exclusions: cleaning up existing data and configuration, upgrading modules written in-house or by third parties (Odoo partners included) that are not under a maintenance contract, and training on the new version. A database with custom modules also cannot be upgraded until those modules have a version ready for the target release. In practice, the service moves your data and Odoo's own apps, and everything your team or a previous partner built has to be made compatible with the new version by someone who reads the code.
Community databases have no upgrade service from Odoo. The usual route is OpenUpgrade, an open-source project of the Odoo Community Association (OCA), which provides migration scripts module by module and runs one version at a time, so moving from 15 to 18 means three consecutive migrations. The OCA publishes module coverage for each version step, and a module without scripts can make the migration fail or leave data incomplete. OpenUpgrade opened its 20.0 branch on September 28, 2026, and module coverage for that step will take time to build. On either edition the rule is the same: custom modules are yours to upgrade. For the wider trade-offs, see Odoo Community vs Enterprise.
The nine things that set the cost
Every upgrade quote we write comes down to the same drivers. Some are fixed by your history. Others you can change before the work starts.
Versions jumped. Odoo ships one major release a year, and each one changes some of the APIs, views and fields that custom code relies on. The changes stack. Going from 16 to 19 means handling what changed in 17, 18 and 19, even when the database moves in one request. Our guide to upgrading custom modules from 16 to 19 shows what that looks like in code.
How much custom code there is, and where it sits. The number of modules matters less than what they do. A module that adds fields and a report is cheap to move. Code that overrides core business logic, such as how stock is reserved or invoices are posted, needs careful testing on every release. Code that touches the web client costs the most, because Odoo replaced its legacy JavaScript widgets with OWL components and there is no mechanical conversion.
Marketplace apps. Each third-party app needs a release for the target version from its vendor, and the Odoo Apps store lists apps by version, so check there first. An app with no release has to be replaced by a standard feature, another app or a small custom module. Two apps that override the same method can also conflict after the upgrade, even if each works on its own.
Studio customizations. Studio changes are covered by Odoo's upgrade service while Studio is installed and subscribed, which makes them cheaper to carry than code. They still need testing, because a Studio change built on a standard view can behave differently when that view changes underneath it. If Studio has been uninstalled, its customizations lose that coverage.
Reports. Custom QWeb reports, such as invoices, delivery slips and certificates of analysis, are checked against what customers and vendors expect, and rebuilt where the layout changed. A report that renders is not the same as a report that is right.
Integrations. Every connection to a web shop, carrier, bank, EDI partner or in-house app has to be re-tested on the new version, and some need rework where the fields or endpoints they call have changed. Odoo's own upgrade guide lists integrations with external software among the things to test.
Data volume and rehearsal time. The production database is unavailable while it upgrades, so a large database needs a longer window. Odoo recommends requesting fresh test upgrades as you go and rehearsing the full upgrade the day before production. Each rehearsal on a large database takes engineering time, and very large tables sometimes need upgrade scripts of their own to keep the run inside the window. Data that needs cleaning is extra, since the upgrade service excludes it.
Testing and training. Someone has to run every business flow on the upgraded copy: buy, receive, make, sell, ship, invoice, pay and close. Users have to learn what moved. Odoo's service excludes training and leaves testing your business flows to you, and both grow with the number of apps and roles in use. Skip them and you trade an upgrade problem for the one in live on Odoo, but nobody uses it.
Hosting changes. Odoo's documentation says an upgrade does not cover changing hosting type, so a move between Odoo Online, Odoo.sh and your own servers is scoped separately. Self-hosted databases may also need a new server environment: Odoo 17 raised the minimum Python version to 3.10. Odoo Online does not allow custom modules that contain Python code, so a database with custom modules cannot move there without replacing them.
| Cost driver | What raises it | What lowers it |
|---|---|---|
| Versions jumped | Several releases skipped, with their changes stacked | Upgrading every release or two |
| Custom code | Overrides of core logic, legacy JavaScript widgets, no tests | Retiring modules the standard now covers, automated tests |
| Marketplace apps | No release for the target version, apps that conflict | Fewer apps, from vendors who publish every version |
| Studio customizations | Studio uninstalled, changes layered on views that moved | Studio kept installed and subscribed |
| Reports | Many custom layouts that customers check | Standard layouts wherever the format is not contractual |
| Integrations | Undocumented point-to-point connections | Documented APIs and native connectors |
| Data volume | Large tables, dirty data, long rehearsals | Data cleaned and archived before the upgrade |
| Testing and training | Many apps and roles, no written test scripts | Test scripts kept from the last upgrade, a super-user per team |
| Hosting | Changing platform or server stack at the same time | Same platform, new server prepared early |
Why waiting makes the upgrade more expensive
Odoo releases one major version a year and gives each one three years of standard support, covering helpdesk, bug fixes and security updates. In practice the three most recent releases are supported. With Odoo 20 released in September 2026, that means 18, 19 and 20, and 17 has left the window. Beyond three years, Odoo offers extended support only for a mandatory extra fee. For most databases we recommend landing on 19 now and moving to 20 once it matures. If you are on 17, our note on Odoo 17's end of support covers the options.
Each year you wait adds another release of changes to the rewrite, another round of deprecated APIs and more data to move. It also narrows the route. Odoo's documentation says its upgrade platform targets supported versions only, so a plan to step through an older release can close while you wait. On Odoo Online and Odoo.sh, the upgrade eventually becomes mandatory, on Odoo's schedule rather than yours. And the people who wrote your old code move on. An upgrade planned while they can still answer questions costs less than one that starts by reverse-engineering their work.
How we quote an Odoo upgrade
We audit the modules before we quote. The audit lists every custom module, marketplace app, Studio change, report, scheduled action and integration, and sorts each one into keep, replace with standard, or retire. It reads the code, not just the module list: what each module overrides, whether it touches the web client, and whether standard Odoo now does the same job. Only then do we write a number.
Once the scope is pinned down, the price is fixed and agreed before kickoff, and anything added later is scoped, quoted and approved by you before it is built. The work follows the five stages of our Odoo upgrade and migration method, each with exit criteria met before the next begins: the database is migrated and verified, custom modules are rewritten, new features are added, the new system runs in parallel beside the live one, and cutover happens in a quiet window.
One example is SF Dyes, a dye manufacturer that moved from Odoo 13 to 18 in one migration, with every custom module rewritten, barcode scanning and custom vendor reports added, and zero disruption at go-live. How we price engagements in general is on our pricing page.
How to lower the cost of this upgrade and the next
Start by retiring code. Odoo's own guidance for upgrading a customized database is to freeze development, compare each customization with what the standard product now does, and remove the overlap. Features that needed custom code a few versions ago are sometimes standard today, and a module you retire costs nothing to upgrade.
Upgrade more often. Odoo's documentation makes the point plainly: the smaller the version gap, the easier the upgrade should be. Moving every release or two keeps each rewrite small and keeps you inside standard support without paying for extended support.
Keep the code upgrade-safe. Build every customization as an inherited module rather than an edit to Odoo's core, keep logic out of the web client where you can, and ship each module with automated tests. Tests turn the next upgrade from guesswork into a list of failures to fix. Our note on how much Odoo customization is too much covers the rules we follow, and our customization services build to them.
Finally, prune. Uninstall apps nobody uses, prefer vendors who publish a release for every version, and clean or archive data before the upgrade rather than during it.
Make this upgrade pay for the next one. Our practice is to return every module we rewrite with automated tests, a migrations folder and an upgrade estimate for the next release, so the next upgrade is smaller.
Frequently asked questions
How much does an Odoo upgrade cost?
It depends on the version jump, how much custom code you carry and how much of it touches the web client, plus marketplace apps, reports, integrations, data volume and testing. We do not publish prices. We audit your modules first, then quote a fixed price once the scope is pinned down.
Is Odoo's upgrade service free?
For Enterprise customers, yes. It covers the standard apps, Studio customizations while Studio is installed and subscribed, and code under a maintenance-of-customizations subscription. It does not cover other custom or third-party modules, data cleanup or training.
How do we upgrade Odoo Community?
Odoo's upgrade service is for Enterprise. Community databases usually use OpenUpgrade, the OCA's open-source project, which migrates one version at a time with per-module scripts. Check its coverage tables against your installed modules before you plan, and budget for your custom modules separately.
Is it cheaper to wait and jump several versions at once?
Rarely. The changes between releases stack, so the code rewrite covers all of them either way, and running outside standard support means paying for extended support or going without. One larger jump does save a round of testing and a cutover, which is why we plan each case from its audit.
Planning an upgrade?
30 minutes: bring your version and module list, and we will tell you which cost drivers apply.
Book a discovery callKeep going
Related services and articles
Get your upgrade scoped
Custom modules audited before the quote, then five stages with exit criteria to a quiet cutover.
Odoo upgrade and migration servicesFive versions in one migration
SF Dyes moved from Odoo 13 to 18 with every custom module rewritten and zero disruption at go-live.
SF Dyes migration case study Odoo UpdatesUpgrading custom Odoo modules from 16 to 19: what changes
What breaks in custom modules between 16 and 19, with old and new code side by side.
ImplementationOdoo customization: how much is too much?
When to write a custom module, when to adapt the process, and how to keep code upgrade-safe.
Find out which cost drivers your upgrade carries
The first call takes 30 minutes.
Or email sales@octagotech.com- USA +1 917 254 9416
- India +91 8153897751