Skip to Content
Odoo Upgrade (Version Migration)

Upgrade Odoo Without a Long Weekend of Surprises

We run a full test upgrade on a copy of your database first, port your custom modules, and rehearse the cutover before the real one. Go-live day becomes a repeat of something that already worked.

Odoo Silver Partner Odoo Best Starter Winner

Is this for you?

Good fit if

  • ✓You run Odoo 16, 17 or older and want to get back to a supported version
  • ✓Custom modules or third-party apps have stopped you upgrading before
  • ✓You want Odoo 20 features or Light User pricing

Probably not a fit if

  • –You are on standard Odoo Online with no custom code; Odoo upgrades those databases for you
  • –You want to skip testing to save time

Why it matters now

Odoo supports the three most recent major versions. With Odoo 20 released in September 2026, that means 18, 19 and 20. Since April 2026, Enterprise subscriptions on older versions carry a 25% annual surcharge. Light User pricing applies only on Odoo 20. Details in our Odoo 20 Light User guide.

What you walk away with

An upgrade readiness report

Every custom module and third-party app, rated keep, port, replace with standard, or retire.

A test upgrade database

Your team can click through before anything is final.

Ported custom modules

Re-tested against the new version's standard flows.

A reconciliation check

Key balances, stock values and open documents compared before and after.

A cutover plan

With a rehearsal date, a go/no-go checkpoint and a rollback route.

How we work

1

Audit

We list every installed module, find the custom code and its dependencies, and check what the new version now does as standard.

2

Test upgrade

Standard data goes through Odoo's upgrade service (Enterprise) or OpenUpgrade (Community); custom data is handled by our own migration scripts.

3

Port and fix

Custom modules are rewritten where Odoo's framework changed, and the fit-gap is re-checked where standard Odoo now covers a feature.

4

User testing and rehearsal

Your team signs off the test database; we time a full rehearsal of the cutover.

5

Go-live and watch

A real cutover in an agreed window, then close monitoring of the first week of transactions.

Ways to engage

Fixed-price upgrade

Quoted after the readiness audit.

Audit only

The readiness report on its own, if your team will do the upgrade.

Ongoing partnership

Stay current with a planned upgrade each year.

Why teams choose TheERPBot

Odoo Silver Partner  Odoo Best Starter Award (India, 2026)

Read: Upgrade today, profit tomorrow: an electronics success story | Odoo upgrade services explained

Frequently asked questions

Yes. Odoo's upgrade service moves the standard data across several versions in one go. Custom modules still need porting to the target version.

No data should be lost, and we check this rather than assume it: balances, stock values and open documents are compared before and after the test upgrade and again at cutover.

Usually a planned window outside working hours. The rehearsal tells us the exact time for your database size.

Each is reviewed. Some get ported, some are replaced by features the new version now has as standard, and some are retired.

It depends on your version, your customizations and how Light User pricing affects your bill. Our readiness check answers that for your database.

Get an upgrade readiness check

We review your installed modules and tell you which version to target, what will need porting, and a fixed price.

Request readiness check