Odoo version comparison

No, and we advise against it.
Odoo releases one major version a year. Following every release means spending your time on technical projects that bring no value to the business. The right pace is to stay within the three supported versions, which lets you skip one. What should trigger the decision is a specific business need or the approaching end of support, not Odoo's calendar.

No, they are no longer under standard support.
Odoo provides support and bug fixes for the last three major versions. Since the release of Odoo 20 in September 2026, the three supported versions are 18, 19 and 20. Standard support lasts three years, then paid extended support takes over, with fixes provided where feasible. Staying on 16 or 17 means that newly found bugs will no longer be fixed.

From a few days to several weeks, depending on your custom development.
A database close to the standard can be migrated in a few days. What makes the project longer is the custom development that has piled up, third-party modules and the volume of data to check. That is why we always start with an audit of your current setup before giving a timeline.

Each piece is reworked, and some disappear.
With every version, features that used to require custom development become part of standard Odoo. A good migration is a chance to remove code that is no longer needed rather than carry it over. We decide on each customization: rework it, replace it with the standard, or drop it because nobody uses it anymore.

Yes, and it is often the right choice.
Odoo chains the successive migration scripts, so the switchover remains a single operation for you. Skipping two versions costs less than two separate migrations. On the other hand, users face more changes, so training matters more.

Not if acceptance testing is done thoroughly.
The migration is done on a copy, never on production. We then compare the old and new databases, model by model and screen by screen. On a recent migration, this check covered thousands of contacts and journal entries, without a single discrepancy. Production only switches over after sign-off.

No, wait for the first round of fixes.
Odoo 20 was released in September 2026, and a major version stabilizes in the weeks after its release. Migrating on day one means living through the teething problems on your production database. We recommend waiting for the first stability updates, unless a specific feature of the new version justifies the risk.

The price depends on how far your database is from the standard.
A standard database means a modest budget. A heavily customized database requires reworking each development, and that is where most of the cost lies. The preliminary audit gives a firm quote, and its cost is deducted from the project if you entrust us with the migration.

Yes, and it is the item most often underestimated.
Moving to version 17 changed the entire interface, and version 20 redesigns the mobile app. A technically successful migration with poor change management leaves users lost and leads them to reject the tool. We always budget training time along with technical time.

Yes, and with us it is a mandatory step.
We set up a copy of your database in the target version, on which your teams run their own business scenarios. Each scenario you approve brings you closer to the green light. The switchover is never decided by us alone.

The approach is the same, but the technical options differ.
On Odoo Online, the migration is triggered from your account, and possible customizations are limited to configuration and Studio. On Odoo.sh, you have a test branch and a code repository, which makes it possible to rework custom development cleanly. Your hosting choice therefore drives the cost of your future migrations.

You do, based on a schedule we prepare together.
We suggest a window that takes into account your peak periods, your accounting deadlines and your teams' availability for acceptance testing. There is never a good reason to switch over the day before a closing or in the middle of your busy season.