Odoo upgrades

Move to Odoo 20 with your customisations understood, not broken

Odoo releases a new major version every year and supports each one for three years. If your database is falling behind, the risk grows quietly. We review every custom module, test the upgrade on a copy of your data, and move you across with no surprises.

Accredited partner · Certified team · Audited security

  • Odoo Partner
  • Odoo Certified
  • ISO 27001 certified
  • ISO 9001:2015 certified
  • Cyber Essentials certified
See all partnerships and certifications →

Upgrade warning signs

Is your Odoo version holding you back?

Tap any that apply. Each sign points to a reason upgrades get postponed, and to the risk of postponing them again.

We are still on Odoo 16 or earlier

Root cause: Standard support for Odoo 16 ended in September 2025, so new bugs and security issues are no longer fixed under standard support.

Cost if ignored: You carry unpatched risk, or pay extra for extended support to stand still.

Custom modules are the reason we never upgrade

Root cause: Custom code must be updated to each new Odoo version by whoever maintains it, and often nobody owns that job.

Cost if ignored: The longer you wait, the more versions of change the code must absorb.

Odoo 17 felt new, but its support is ending

Root cause: Odoo plans standard support for Odoo 17 to end in September 2026, three years after its release.

Cost if ignored: A database that felt current becomes the next upgrade emergency within months.

Our integrations use XML-RPC or JSON-RPC

Root cause: Odoo has deprecated these older external APIs in favour of JSON-2, with removal of the remaining services already scheduled.

Cost if ignored: Integrations that work today can fail outright after a future upgrade.

We see new features but cannot use them

Root cause: Improvements arrive in new major versions, so an older database misses what Odoo has built since you went live.

Cost if ignored: Your team keeps workarounds that a newer standard feature already solves.

The last upgrade broke things we only found later

Root cause: The upgrade went straight to production without enough testing of real business flows on an upgraded copy.

Cost if ignored: Disruption after go-live, and a team that now fears every upgrade.

Tick the ones that apply

Each of these is manageable with the right preparation. We will show you what your upgrade really involves.

How we upgrade

Review, rehearse, then upgrade

We follow Odoo’s own upgrade process and wrap it in SCALE milestones. You see a tested, upgraded copy of your database before your live system changes, and you sign off each stage.

01Upgrade assessment

Know what you are dealing with.

What we do

We list every installed module, custom field, Studio change and integration, then classify each one: still needed, now covered by standard Odoo, or ready to retire. You get a clear view of effort before committing.

You receive

“Which of these customisations would you build again if you started today?”

02Code and integration update

Bring custom work up to date.

What we do

Custom modules we keep are updated to the target version, and anything replaced by standard features is removed. Integrations still using the deprecated XML-RPC or JSON-RPC endpoints are moved to Odoo’s JSON-2 API.

You receive

“Which integration would stop trading if it failed on Monday morning?”

03Test upgrade

Upgrade a copy, not your live data.

What we do

We request an upgraded test database from Odoo and test it alongside your key users. Views, reports, email templates, automations and full business flows are checked against a test plan we agree with you.

You receive

“Which month-end report must look exactly right before you will sign off?”

04Production upgrade

Switch over when use is lowest.

What we do

We schedule the production upgrade for a quiet window, because the database is unavailable while it runs. Afterwards we repeat the critical checks and stay on hand while your team settles into the new version.

You receive

“Who needs to know about the upgrade window, inside and outside the business?”

After the upgrade

A supported Odoo that keeps moving forward

Support

Running a version outside standard support

On Odoo 20, with standard support for years ahead

Custom code

Modules nobody dares touch

Fewer, documented modules that are ready to upgrade

Integrations

Built on deprecated XML-RPC endpoints

Moved to the JSON-2 API Odoo now recommends

Features

Workarounds for gaps Odoo has since closed

Newer standard features in daily use

Confidence

Upgrades postponed year after year

A tested, repeatable route to each new version

What is included

Our Odoo upgrade service covers

Upgrading is more than running a script. These are the pieces we take responsibility for, from first assessment to the week after go-live.

Customisation audit

Every custom module, Studio change and automation reviewed, with a recommendation to keep, replace with standard Odoo or retire it.

Custom module updates

Code we keep is updated to the target Odoo version, because Odoo requires custom modules to be ready before the database can be upgraded.

API modernisation

Integrations on the deprecated XML-RPC or JSON-RPC endpoints moved to Odoo's JSON-2 API, which uses API keys for authentication.

Test database and UAT

An upgraded copy of your database tested against your real business flows, with your key users involved before anything changes in production.

Production cut-over

The live upgrade scheduled for a low-usage window, followed by checks on critical flows, reports and integrations before your team returns.

User change briefing

A short, role-based summary of what looks and works differently in the new version, so users are not surprised on day one.

Hosting fit finder

Find your best-fit Odoo hosting model in 60 seconds.

Answer six quick questions. We will score each hosting model against your answers and explain why, just as we would in a consultation.

Question 1 of 6

Honest fit

Is an Odoo upgrade right for you now?

This is right for you if

It is probably not right if

Why Thoughtlogik

Why upgrade with Thoughtlogik

We follow Odoo's process

Test database, business flow testing, then production. We use Odoo’s documented upgrade route rather than shortcuts that leave hidden problems behind.

Honest about custom code

We will tell you when a custom module is no longer worth keeping. Every module you retire is one less thing to upgrade next time.

Odoo developers in-house

Our own certified delivery team in India writes and maintains Odoo modules, including apps we publish on the Odoo marketplace ourselves.

Signed-off milestones

Assessment, code update, test upgrade and production each end with your sign-off, so you decide when the live system changes.

Find out what your upgrade really involves

Share your current Odoo version and hosting. We will review your modules and integrations and tell you honestly what it will take to reach Odoo 20.

Try Odoo free

Start your free Odoo trial

Explore Odoo's apps in your own trial database. When you are ready, we will help you configure it for how your business really works.

FAQs

Questions buyers ask us

Odoo 20 is the latest major version, released in autumn 2026. Odoo publishes a new major version roughly every year and provides standard support for each major version for three years, covering helpdesk support, bug fixing and security updates. We recommend planning upgrades well before your version leaves standard support.

Odoo stops providing standard bug fixes and security updates for it. Extended support is available for an additional fee, with bug fixes depending on feasibility. Odoo also only upgrades to supported versions, though the last unsupported version can still be an upgrade target for up to six months after its end of life.

Usually yes. Odoo’s upgrade process takes a database to a supported target version without stepping through every release in between. Your custom modules, however, must be updated to the target version, and the bigger the jump, the more change that code needs to absorb. Our assessment estimates that effort before you commit.

Odoo Enterprise includes upgrade requests for the standard database. Custom modules are only covered if they are maintained under Odoo’s paid arrangement for extra modules. Most businesses with custom code need a partner to update and test it, which is the work we take on.

Yes, the production database is unavailable while the upgrade runs. That is why Odoo recommends planning it for a time when usage is minimal. Because we time the test upgrade first, you will know roughly how long the window needs to be before you book it.

Odoo has deprecated its XML-RPC and JSON-RPC endpoints in favour of the newer JSON-2 API. Some services are already removed in Odoo 20 and the rest are scheduled for removal in a later version. We check every integration during assessment and move those at risk to JSON-2.

Start your project

Ready to upgrade your Odoo?

Tell us about your business and goals. A certified consultant will get back to you within one working day with practical next steps.

  • Free, no-obligation consultation
  • UK-based Zoho and Odoo partner
  • Clear plan, milestones and pricing

Learn how we helped 100 top brands gain success