Skip to Content

Upgrading to Odoo 20: Cost, Timeline, What Breaks and How to Plan It

When to move from Odoo 16, 17, 18 or 19, how the upgrade works on each type of hosting, and what drives the time and the cost
November 15, 2026 by
Upgrading to Odoo 20: Cost, Timeline, What Breaks and How to Plan It
Hassan Tabbal

Odoo 20 came out in September 2026. For a database with Odoo Enterprise and no custom modules, Odoo converts the data for free and most of the work is testing and training. Custom modules, apps bought from the Odoo Apps store and integrations are what make an upgrade long and expensive, because Odoo doesn't convert them unless you pay for their maintenance. On Odoo 16 or 17 you're already outside standard support and should plan the move now. On 18 or 19 you have time to plan it properly.

This guide is for companies on Odoo 16 to 19, whatever the hosting. For the new features themselves, read our article on what's new in Odoo 20.

Should you upgrade to Odoo 20 now?

Odoo supports each major version for three years of standard support, and security updates only come during that period. After it, extended support is available for an extra fee, only on Odoo.sh (for a limited number of versions) and on your own servers. Here's where each version stands according to Odoo's support table:

  • Odoo 16: standard support ended in September 2025.
  • Odoo 17: standard support ended in September 2026.
  • Odoo 18: supported until September 2027.
  • Odoo 19: supported until September 2028.
  • Odoo 20: released in September 2026, supported until September 2029.

There's also a cost to staying behind on Enterprise. Odoo's Enterprise Subscription Agreement covers the three most recent major versions, which today are 18, 19 and 20. For a database on an older version, the agreement adds a fee of 25% of the yearly subscription, charged once a year and no earlier than six months after a new major version comes out. A company still on Odoo 17 should expect it in next year's budget.

What we'd suggest for each version:

  • On Odoo 16 or 17: start now. You've lost security updates, and Odoo lets you jump straight to 20.
  • On Odoo 18: plan the upgrade for the first half of 2027, so you're done well before support ends in September 2027.
  • On Odoo 19: move when a feature in Odoo 20 pays for itself or when a quiet period comes up. There's no deadline pressure yet.

For manufacturers: upgrade or stay?

A factory can't stop for a broken work order, so manufacturers have good reasons to be careful. Staying put for a while makes sense when you're on 18 or 19, your shop floor depends on custom modules or machine integrations that would all need rework, or a peak season or stock count is coming. Upgrading soon makes more sense when you're on 16 or 17 without security updates, your custom code is small, or you're about to add something new, such as a second plant or quality checks, which you'd otherwise build twice.

Either way, plan the cut-over between production peaks, and have your planners and floor supervisors test bills of materials, routings, costing and work orders on a copy first. If your technicians use the Field Service app, Odoo 20 folds it into Planning, so they'll need some retraining.

How an Odoo upgrade works on each type of hosting

Odoo's upgrade documentation follows the same order everywhere. You request an upgraded test copy of your database, bring any custom modules to the new version, test the copy, report issues to Odoo, and only then upgrade production. Your live database is unavailable while it upgrades, so Odoo recommends doing it when nobody needs the system, and rehearsing the whole process the day before.

The test copy is neutralized so it can't touch the real world. Scheduled actions and outgoing emails are switched off, payment providers and delivery carriers are put in test mode, and bank synchronization is disabled.

Odoo Online

On Odoo Online, a database on a major version must be upgraded every two years, and one on the in-between online versions must move a few weeks after the next one is released. Odoo notifies you in the database a few weeks before the deadline. Until then you can request a test copy from the database manager, check it and trigger the upgrade yourself. If nothing happens by the deadline, the upgrade runs automatically, and once it's done there's no going back.

Odoo Online runs standard Odoo and Studio only, so the main risks are Studio automations and reports that depend on how standard screens used to work. Our article on Odoo Studio on Odoo Online covers what the upgrade guarantees and where it can still go wrong.

Odoo.sh

On Odoo.sh you start the upgrade on a staging branch, and an upgraded copy of your latest production backup comes back on it. Each time your developers push code to that branch, the custom modules are tested again on a fresh upgraded copy. When staging passes, the same happens on the production branch. If the production upgrade fails, the platform rolls it back. On Odoo.sh you get two more years after the three years of standard support to complete your upgrade.

Your own servers

On premise, you can stay on a version as long as you like, without security updates once support ends. With Enterprise, you send a copy of your database to Odoo's upgrade platform (from the command line or the upgrade page) and restore the upgraded copy yourself. The files attached to your records aren't sent, so your team merges them back before testing. Odoo 20 also needs Python 3.12 or later and PostgreSQL 16 or later, according to Odoo's installation guide, so a server set up for Odoo 16 or 17 may need its own upgrade first.

What Odoo's upgrade service covers, and what it doesn't

With Enterprise, upgrading to the latest version is free, including the support needed to fix problems caused by the upgrade. The service terms list exactly what's included:

  • all of Odoo's standard apps;
  • customizations made with Studio, as long as Studio is still installed and the subscription is active;
  • custom code covered by a maintenance of customizations subscription, which Odoo bills monthly per 100 lines of code at the price written in your quote.

The same terms list what isn't included:

  • cleaning old data and configuration;
  • modules written in-house, by a partner or by a third party, when they aren't under a maintenance contract;
  • training your users on the new version.

The agreement leaves it to you to check and approve the upgraded database, and you can request as many test upgrades as you need. Note too that if you buy maintenance for a custom module only when the upgrade comes, Odoo can charge a one-time fee for each month of coverage missing in the past 12 months.

What usually breaks in an Odoo upgrade

Odoo's standard apps upgrade well. Problems come from what was added around them over the years.

  • Custom modules: Odoo won't upgrade a database until every custom module installed in it has a version for the target release. Each major version renames or removes things custom code relies on, and Odoo's documentation makes fixing that the job of whoever maintains the module.
  • Apps store modules: Third-party apps need a version for Odoo 20 from their publisher. If one isn't ready, you wait, replace it or have it ported.
  • Reports and documents: Custom invoice, delivery and payslip layouts need checking line by line.
  • Integrations: Links to banks, payment gateways, e-invoicing, marketplaces and machines need testing. In Odoo 20 the format for sending files through the API has changed.
  • Automations and Studio work: Automated actions, server actions and fields computed with Python run against Odoo's internal names. When those change, the rule fails or does something different.
  • Access rights: Odoo 20 merges access rights and record rules into one mechanism, so custom rules about who sees which records need a review.
  • Local rules: Tax, payroll and e-invoicing modules that don't come from Odoo must be ready for the new version too.
  • Habits: A changed screen stops people even when nothing is broken. Odoo 20 changes how accounting handles bank entries, assets and expenses, for example.

Odoo Community and OpenUpgrade

Odoo's upgrade service is only for Enterprise. Community databases are upgraded with OpenUpgrade, an open-source project of the Odoo Community Association (OCA). It covers Odoo's own Community modules, one major version at a time, so going from 16 to 19 means three upgrades in a row, each with its own testing. Your custom and OCA modules still have to be migrated separately.

Timing matters too. On the OCA's tracker for version 19, almost all of Odoo's Community modules are done. Work on version 20 started at the end of September 2026, and in mid-November its core parts were still in progress. A Community database can reach Odoo 19 with OpenUpgrade today, while the path to 20 isn't ready yet. Exporting your data into a fresh database is the other route, and it loses history and the links between records.

How to plan your Odoo 20 upgrade, step by step

  1. Take stock. List your apps, custom and Apps store modules, integrations, Studio changes, automations and key reports, and who maintains each one.
  2. Freeze and cut. Stop new development during the upgrade, as Odoo recommends. Then check each customization against Odoo 20: some can be dropped because the standard now covers them, which means less to upgrade and less to maintain afterwards.
  3. Clean your data. Archive duplicate customers, old products and unused settings before the move. Odoo's service doesn't clean data, and whatever is messy today moves to Odoo 20 with you.
  4. Request a test upgrade and adapt the code. Get the upgraded copy early, then bring your custom and Apps store modules to Odoo 20 and install them on it.
  5. Test the way you work. Have the people who use Odoo every day run real processes from purchase to payment, plus every integration and printed document.
  6. Train, rehearse and set a date. Show each team what changed on the test copy. Request a fresh test upgrade close to go-live, rehearse the day before, and pick a quiet time such as a weekend outside month-end.
  7. Plan for the bad day and the first weeks. Keep a full backup from before the upgrade and agree who decides to stop if something goes wrong. On Odoo Online there's no way back once it's done. After go-live, keep someone close to users to fix problems quickly.

How long an Odoo upgrade takes and what drives the cost

Most of the effort goes into custom code: the number and size of your custom modules, and how many of them Odoo 20 makes unnecessary. After that come Apps store modules that need porting or replacing, integrations, the size of the jump (19 to 20 has far less to absorb than 16 to 20), the volume and state of your data, how many teams and companies have to test and sign off, and on your own server, any Python or PostgreSQL upgrade.

A standard Enterprise database on Odoo Online moves fastest, and most of the time goes into testing and training. A heavily customized database takes longer, because the code has to be rewritten and tested before the database can move. On Enterprise you pay for the work on custom code, data cleanup, testing support and training, while the conversion of standard apps is included. For the full picture of Odoo's running costs, see our guide on how much Odoo costs.

How NavyBits can help with your Odoo 20 upgrade

NavyBits has been an official Odoo partner since 2017, with 10 Odoo-certified experts, and a senior engineer leads every project. We upgrade and support systems we built and systems built by other partners. Our Lebanon localization suite already runs on Odoo 20 in production, so Lebanese companies can move their dual-currency books, CNSS payroll and VAT with the rest of the system.

  • Assess: we review your database, modules, integrations and hosting against Odoo 20, and give you a written report on what moves over, what needs work and in what order. An upgrade or takeover assessment costs around $3,000. After the free call we send an official quote for your system, and when the budget is tight we can shape a smaller assessment around it.
  • Build: we bring your custom code to Odoo 20, run the test upgrades, help your team test and train, and plan the cut-over with you. The effort is estimated in days from the assessment.
  • Maintain: after go-live we support your users and keep your system ready for the next version.

See how it works on our Odoo support and upgrades page. For a first read before the call, our free Odoo self-check takes about two minutes, and an engineer replies to every one.

FAQ

Can I upgrade from Odoo 16 or 17 directly to Odoo 20?

Yes, with Odoo Enterprise. Odoo lets you upgrade from any version to any major version still under standard support, so you don't have to stop at each version in between. A bigger jump means more to test. With Community and OpenUpgrade you go one version at a time.

Odoo 18 vs Odoo 20: should I wait or upgrade?

Odoo 18 is supported until September 2027, and Odoo 20 until September 2029. If your system is stable and nothing in Odoo 20 matters to you yet, you can plan the upgrade calmly for the first half of 2027. If you want the new AI agents or accounting features, or you're about to build something new, upgrade first and build on Odoo 20.

What are the Odoo 20 requirements?

On your own server, Odoo 20 needs Python 3.12 or later and PostgreSQL 16 or later, and the pgvector extension for its AI features. On Odoo Online and Odoo.sh, Odoo manages this for you. Your custom and Apps store modules also need versions written for Odoo 20.

Odoo's upgrade service or OpenUpgrade: which one should I use?

It depends on your edition. Odoo's service is included with Enterprise and upgrades standard apps and Studio work, from any version to the latest. OpenUpgrade is the open-source route for Community, one version at a time, and its Odoo 20 version was still being built in November 2026. Your own custom modules need their own migration either way, unless Odoo maintains them under a maintenance of customizations subscription.

Is there an Odoo upgrade calculator?

A reliable price needs someone to look at your custom code, Apps store modules and integrations, because they make up most of the work. Use the cost drivers above as a checklist or take our two-minute self-check, and an assessment turns it into a written plan and estimate.

How long does an Odoo 20 upgrade take?

A standard database moves fastest, with most of the time spent testing and training. Custom modules and integrations add time, because each one has to be adapted and tested first. The go-live itself takes a quiet day or weekend.

Plan your Odoo 20 upgrade with an engineer

In a free 30-minute call, tell a senior engineer which version you're on, how you host Odoo and what's been customized, and you'll hear what your upgrade involves and what to look at first.

Upgrading to Odoo 20: Cost, Timeline, What Breaks and How to Plan It
Hassan Tabbal November 15, 2026
Share this post
WhatsApp usAI agent replies 24/7
Book a free 30-minute call