Skip to Content

Upgrading Odoo to a new version: a practical plan

When to upgrade Odoo, how the upgrade service works for Online, Odoo.sh and on-premise, what happens to custom modules and Studio changes, how to test, and a step by step plan that keeps a company in Egypt or the Gulf running through the switch.
November 7, 2026

Odoo releases a major version every year, and each one improves localizations, e-invoicing connectors and usability. For companies in Saudi Arabia, Egypt and the UAE, staying on a supported version is not only about new features: tax authority integrations change, and fixes for ZATCA or ETA rules arrive on supported versions first. An upgrade is a project, not a button, but with a copy to test on and a clear plan it is routine.

FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.

Key points

  • Stay supported. Odoo supports the last three major versions.
  • Test on a copy. The upgrade service returns an upgraded copy of your database to test.
  • Custom code needs work. Custom modules must be migrated by a developer for each version.
  • Plan the switch. A short freeze and a weekend cut-over keep the business running.

When to upgrade

Odoo supports the three most recent major versions with fixes and security updates. Odoo Online databases are upgraded on a schedule, with a window to test and choose the date. Odoo.sh and on-premise customers decide when to upgrade, but staying more than two versions behind makes the jump harder and leaves you without fixes.

  • Upgrade when your version is close to the end of support.
  • Upgrade when a new tax requirement is only supported in a newer version.
  • Avoid upgrading in your peak season, at year end or during a tax filing month.
  • In the region, avoid the last weeks of Ramadan and the year-end close.
Team planning a software release on a calendar
An upgrade is a small project with a plan, a test and a cut-over.

How the upgrade works

For standard modules, Odoo's upgrade service converts your data to the new version. You request a test upgrade, receive an upgraded copy, test it, report any issues, and then request the production upgrade. Custom modules are not upgraded by Odoo: a developer migrates their code and data scripts to the new version, and they are tested together with the upgraded copy.

HostingHow to upgradeCustom modules
Odoo OnlineFrom the database manager, on Odoo's scheduleNot allowed; Studio only
Odoo.shUpgrade branch, test in staging, then productionMigrated by your developer in the branch
On-premiseUpgrade service with a database dumpMigrated by your developer

Hosting differences are explained in Odoo hosting options, and Studio changes in Odoo Studio.

A step by step plan

  1. Weeks 1 to 2

    Inventory custom modules and Studio changes; remove what is unused.

  2. Weeks 2 to 4

    Request a test upgrade; developer migrates custom modules.

  3. Weeks 4 to 6

    Key users test real scenarios; issues are fixed and retested.

  4. Week 7

    Short training on what changed; freeze on configuration changes.

  5. Cut-over weekend

    Production upgrade, smoke tests, go live on the first working day.

  • Test a full sales cycle, purchase cycle and month-end close on the copy.
  • Send test e-invoices to the ZATCA or ETA sandbox from the upgraded copy.
  • Compare trial balance, stock valuation and receivables before and after.
  • Print every customised report and check the Arabic layout.

After the upgrade

On the first days after an upgrade, expect small questions rather than big problems if testing was done properly. Keep the implementation team available, watch scheduled jobs and integrations such as e-invoicing, payment gateways and marketplaces, and collect feedback for small follow-up fixes.

3

Major versions supported

Yearly

New major version

6 to 8

Weeks for a typical upgrade project

1

Weekend for the cut-over

Moving from another system rather than an older Odoo is a different project; see data migration to Odoo and the go-live checklist. Ongoing help after go-live is in Odoo support after go-live.

FlexCode upgrades Odoo safely

We audit your customisations, migrate custom modules, run the test upgrade with your key users, check e-invoicing and reports, and manage the cut-over weekend.

Book a free call

Frequently asked questions

How many Odoo versions are supported?

The three most recent major versions.

Does Odoo upgrade my custom modules?

No. Odoo upgrades standard data; custom modules are migrated by a developer.

Can I test before upgrading production?

Yes. Request a test upgrade and test on the upgraded copy first.

How long does an upgrade take?

Typically six to eight weeks of preparation and testing, with a weekend cut-over.

Will my e-invoicing keep working?

Test it on the upgraded copy against the tax authority sandbox before going live.

Talk to us about how Odoo fits your business. Book a free call

Run invoicing, stock and accounts from one system.

FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.