Skip to content
A small yellow Under Construction sign resting on a laptop keyboard.
A laptop keyboard with a small Under Construction sign on the spacebar.

Buying Odoo

Author
Clovis de Bontin
Published
6 November 2026
Reading time
7 min read
All articles

What an Odoo version upgrade has to settle first

An Odoo upgrade is a project when you have custom modules, integrations, or data you cannot recreate. It is a smaller project when you are on standard apps and can rehearse the move. The version number is not the scope.

The implementation sequence is on how an implementation runs. This article is the upgrade checklist.

Name what you run

Write down the release, the edition and the host before anyone discusses the release you want. A move from an older long-term series is a different job from a move from last year's version. The edition decides which apps exist. The host decides what can be tested and how the database is restored.

Then list the custom code. Every module, who wrote it, whether the source is available, and whether the author is still reachable. A module with no source is not a small risk. It is a rewrite waiting to be discovered.

Ask the partner to confirm the upgrade path in writing before the date is fixed. Some moves need an intermediate version, and a database that has been customised for years may need a first hop before the current release. A path that is assumed is a delay found late.

What has to survive

  • Custom modules, and whether each one still earns its maintenance cost.
  • Integrations: payments, tax filing, warehouse hardware, ecommerce and banks.
  • Open orders, stock, the chart of accounts and the audit trail.
  • Reports and print templates that the business sends to customers.
  • Permissions and approval rules, which are easy to recreate wrongly.
  • A rehearsal on a copy, with a person who can sign the result.

The list is longer than most upgrade quotes assume. That is the point. A quote that covers the migration script but not the integration retest is not a quote for the same project.

Ask for the quote by line: the rehearsal, the module remediation, the integration retest, the data migration and a period of support after cutover. A single number hides which of those the partner has included, and which one you will discover on the weekend.

The rehearsal is the project

Restore a copy of production, or use a staging environment, run the upgrade, and test the workflows that carry money: a sales order, a purchase, a stock move, a bank reconciliation, a VAT return and a payroll export. Fix what fails on the copy. Then run it again.

A rehearsal that only opens the login screen proves the upgrade ran. It does not prove the business can trade on Monday. Give the rehearsal a named owner from each team and a defect log with an owner per line.

The cutover window

We do not publish a typical cutover window. It depends on transaction volume, stock complexity, the number of integrations and how many people have to be on call. A weekend is a common pattern. The length of the weekend is a scope decision, and the technical partner dates it after the rehearsal.

The cutover plan needs a freeze, a final data load, a reconciliation, a go/no-go decision and a rollback. If the rollback is "we will fix it forward", say that out loud before the weekend starts.

Questions for the partner

  1. 01Which release, edition and host are we moving from, and to?
  2. 02Which custom modules are in scope, and who owns each one after the move?
  3. 03Which integrations are retested, and who owns the third party?
  4. 04What is the rehearsal plan, and who signs it off?
  5. 05What is the rollback, and how long does it stay available?
  6. 06What happens to open orders, stock and work in progress during the freeze?

The partner who can answer those six questions in writing has a plan. The one who answers with a date has a sales estimate.

I sincerely hope this was helpful, and if you have any remark, suggestion or question, you can email me at louis@cdb.solutions or DM me on LinkedIn.

Thank you,

Clovis

Next step

See this in practice

Book a free demo. The technical partner for your country shows the apps that fit, at no charge.

Canonical URL: https://www.cdb.solutions/articles/odoo-version-upgrade

FAQ

Answers to the questions this article raises

The questions buyers ask most, answered here. If yours is not covered, ask us directly.

01Should we wait for the next major version?
Only if the capability you need is in that version and you have confirmed it in the release notes. Waiting without that check is a delay, not a plan.
02Who does the upgrade?
The technical partner for your country. Softhealer in the United Kingdom. AppNvent everywhere else. The agreement is with that partner.
03How long does an upgrade take?
We do not publish a duration. It depends on the custom code, the integrations, the data and the rehearsal. The technical partner dates it after discovery.

Next step

Book a free demo

Tell us the country and the operation. The technical partner for your country shows Odoo against your process, at no charge.

+33 7 69 45 83 27UK with SofthealerEverywhere else with AppNvent

Free demo

Put this against your own operation

Country, industry and company size. The technical partner scopes the work and holds the agreement.

  • Country chooses the partner. The UK is implemented with Softhealer. Everywhere else, with AppNvent.

  • The demo is specific. Industry and company size tell the technical partner which apps to show you.

  • No charge, no obligation. Scoping and any agreement come later, and only if you want them.

Tell us about the operation

01/06

United Kingdom: we implement with Softhealer, our technical partner. The agreement is with Softhealer.

Optional
Optional

Routed to Softhealer for United Kingdom. See our privacy policy.