Skip to Content

Odoo Upgrade Cost: What Custom Module Upgrades Cost and How to Estimate Yours

How Odoo partners price module upgrades, what drives the cost, how to count your custom code and what waiting on an old version costs.
19 November 2026 by
Odoo Upgrade Cost: What Custom Module Upgrades Cost and How to Estimate Yours
Tejas

Cost guide

The cost of an Odoo upgrade is mostly the cost of your custom modules. Odoo moves its standard apps and your data to the new version, but custom code has to be ported to every version you cross. Published prices for that work run from a few hundred euros for one small module to well over €10,000 for a large customization.

How much does an Odoo upgrade cost?

An Odoo upgrade costs the work of making your custom modules run on the new version, plus your own testing time. Odoo Enterprise includes the upgrade of its standard apps and data in the subscription. For custom code, published prices start at a few hundred euros for one small module; 10,000 lines moved from Odoo 17 to 19 cost €5,000 at TeqStars' published price.

An upgrade has two parts, and they are priced separately. The first is the database: Odoo's upgrade service converts the data of the standard apps, and an Enterprise subscription already pays for it. The second is everything Odoo did not write: your custom modules and the third-party apps you installed. Odoo's documentation leaves out the upgrade of additional modules that are not covered by a maintenance contract, so this part is yours, or your partner's.

The two parts depend on each other. A database with custom modules cannot be upgraded until a version of those modules exists for the target version of Odoo. That is why the custom code sets both the price and the date of an upgrade. If you also want a partner to run the database move, the test upgrade and the switch-over, that is a project of its own, such as our Odoo migration service.

Why custom modules decide the cost of an Odoo upgrade

Every Odoo version changes the framework that custom modules are built on: views, model methods, the JavaScript client and the names of fields that other modules rely on. A module written for one version has to be rewritten and tested for the next, and again for each version after it. The size of your database hardly matters for this work; the amount and the shape of your code do.

  • €16per 100 lines of custom code a month, Odoo's own fee to maintain and upgrade it
  • 8 to 15 hoursper version for a simple module, in one partner's published cost calculator
  • 25%added to an Enterprise subscription on a version older than the supported ones

Odoo publishes its own price for custom code: a maintenance contract at €16 per 100 lines a month, upgrades included. That is €19,200 a year for 10,000 lines, paid every year rather than once, and it is the most useful benchmark when you compare quotes.

How Odoo partners price an upgrade: per hour, per module or per line

Four pricing models are in use, and only some of them tell you the price before the work starts. The figures below are the ones published on the providers' own pages in November 2026.

Pricing modelHow it worksPublished pricePrice known up front
Odoo's maintenance of custom code A monthly fee per 100 lines, upgrades included €16 per 100 lines a month Yes, every month
Hourly Developer hours, estimated after an audit and billed as worked About USD 175 an hour at a Western partner; USD 20 to 45 an hour for India-based teams billing foreign customers No, an estimate
Per module A fixed price for each module after a code review From €400 per module, tests included, at one French partner Yes, after the review
Per line of code Lines counted with Odoo's cloc command, times a rate per line €1 per line plus a fee per database at one specialist; €0.40 per line at TeqStars Yes, from the line count

The hourly figures turn into a price per module once you add the hours. One partner's calculator puts a simple module, with about ten models, a few views and no JavaScript, at 8 to 15 hours per version, and a complex one at 30 to 60 hours. At USD 175 an hour, a simple module costs USD 1,400 to 2,625 for each version it crosses; at USD 20 to 45 an hour, USD 160 to 675. The hours are the uncertain part, which is why an hourly quote is an estimate and a price per line or per module is a commitment.

Your custom code, not your data, decides what an Odoo upgrade costs.

What drives the cost of upgrading custom Odoo modules?

Six things decide how much work a module upgrade takes. Check them before you ask for a price, so every quote covers the same scope.

How much custom code you have

Lines of Python, JavaScript, XML and CSS, as Odoo's cloc command counts them. It is the measure Odoo uses for its own maintenance fee.

How many versions you cross

Each version has its own changes, so moving from Odoo 15 to 18 means three rounds of porting in one project.

How the code is written

Modules that override core methods or extend the JavaScript client take several times longer than modules that add fields and views.

Whether tests exist

Tests prove that the upgraded module still works. A module without tests needs them written, or a longer manual check.

Third-party apps

Apps from the Odoo Apps Store usually get new versions from their vendor. An app that is no longer maintained becomes custom code.

Changes to your data

When the new version renames or moves fields that your modules use, the upgrade needs scripts that carry your data across.

How to estimate your Odoo upgrade cost, line by line

You can work out a range yourself before you talk to any partner. The line count is the number every per-line quote starts from.

  1. List your custom and third-party modules

    Take every folder in your custom addons path and note which modules you wrote and which came from the Odoo Apps Store.

  2. Count the lines with odoo-bin cloc

    Run odoo-bin cloc -p path/to/module for one module, or odoo-bin cloc -c odoo.conf -d your_database for every extra module installed in a database. The cloc command leaves out the manifest, tests, migration scripts, bundled libraries and demo data.

  3. Note the versions you cross

    Count the major versions between your current version and the target, for example two from Odoo 17 to 19.

  4. Check your Apps Store apps

    Open each app's page and look for the target version. A maintained app is updated by its vendor and leaves your count.

  5. Price it against the benchmark

    Multiply the line count by a per-line price and compare it with Odoo's maintenance fee for the same lines, €192 per 100 lines a year.

Send the same count to every partner

Quotes are only comparable when they cover the same modules, the same versions and the same tests. Give every partner your line count per module and ask what their price includes.

What does staying on an old Odoo version cost?

Waiting is not free either. Odoo's standard support covers each version for the first three years after its release; after that, extended support requires an additional fee. Under the Enterprise Subscription Agreement, a database on a version older than the covered versions pays an extra 25% of the annualized subscription price.

Odoo.sh removes old versions for good

According to the Odoo.sh FAQ, Odoo 15 will be removed from Odoo.sh on 31 October 2027, and each version is phased out on 31 October of the year it turns six. A database on Odoo.sh has to be upgraded before that date.

The extra 25% is charged for every year the upgrade is put off, while porting the modules is paid once. Put the two numbers side by side before you decide to wait.

How to keep the cost of an Odoo upgrade down

Most savings come before anyone touches the code: less code to port, and a clear scope to price.

  • Uninstall and remove modules nobody uses before you count the lines
  • Check which custom features the new version now covers as standard, and drop that code
  • Upgrade one version at a time, so each port stays small
  • Keep tests for the main flows of every module, so each upgrade is checked quickly
  • Buy maintained apps from the Odoo Apps Store instead of copying them into your own code
  • Ask for a fixed price on a stated line count, with the versions and tests written in

A fit-gap check tells you which custom features the target version covers as standard. At TeqStars we ported our own catalogue of Odoo apps to Odoo 20 this autumn, 82 apps and more than 440,000 lines of code, and we have run several upgrades in one project for customers, such as a German spice and tea business moved from Odoo 14 to 16, 17 and 18.

If you want a fixed price instead of an estimate, our Upgrade Desk publishes its rate per line of code and turns your line count into a quotation within one working day.

Frequently asked questions

Does Odoo charge extra for upgrades?

Odoo Enterprise includes the upgrade of the standard apps and your data in the subscription. Custom modules are upgraded by Odoo only under its maintenance contract for custom code, at €16 per 100 lines a month. Without that contract, you or your Odoo partner port the custom modules to each new version.

Is it cheaper to skip Odoo versions when upgrading?

Skipping versions does not skip the work: each version you cross still has to be ported, only in one larger project. Some partners charge less for each further version in the same job; TeqStars charges €0.10 per line for each further version against €0.40 for the first. Meanwhile an unsupported Enterprise database pays 25% more.

Why do quotes for the same Odoo upgrade differ so much?

Quotes often cover different scopes: one includes the database move and testing, another only the code. An hourly quote is an estimate of hours, while a price per line or per module is fixed. Compare quotes only on the same line count, the same versions and the same tests.

How do I count the lines of code in my Odoo modules?

Use the cloc command that ships with Odoo: odoo-bin cloc -p path/to/module counts one module, and odoo-bin cloc -c odoo.conf -d your_database counts every extra module of a database. It counts Python, JavaScript, CSS, SCSS and XML, and leaves out tests, migration scripts, bundled libraries and demo data.

Does the size of my Odoo database change the upgrade cost?

Not for the custom modules: porting them depends on the code, not on the number of records. The size of the database matters for the test upgrade and the switch-over of the database itself, which Odoo's upgrade service handles for Enterprise customers.

Share this post
Tags