Odoo 8 to 10
The longest jump
These versions run on Python 2. Odoo moved to Python 3 with version 11, so all added code must be rewritten. The database usually goes through several intermediate versions. We check the data at each step.
Odoo 8 → 20 · Community and Enterprise
Is your database on Odoo 8, 12, 14 or 16? We move it to the version you choose. We also port your custom modules and third-party modules. Everything runs on a copy first, checked by scripts, before the cut-over.
The path depends on your starting version and your edition. Here are the cases we see.
Odoo 8 to 10
These versions run on Python 2. Odoo moved to Python 3 with version 11, so all added code must be rewritten. The database usually goes through several intermediate versions. We check the data at each step.
Odoo 11 to 14
In Community, OpenUpgrade moves one version at a time: from 12 to 17 that is five passes. In Enterprise, Odoo’s upgrade service can target a recent version directly for the standard part.
Odoo 15 to 17
Two or three versions apart. Custom modules take most of the work, especially screens written in JavaScript.
Odoo 18 and 19
This is the upgrade we do every year for our own apps. The changes are known and the tests already exist.
The standard database is not migrated with the same tool in each edition. Added modules always need porting.
With OpenUpgrade, the OCA’s open-source project, and our own scripts.
Odoo’s service (upgrade.odoo.com) converts the standard part. It does not handle your custom or third-party modules: we port them.
First we migrate to the target version. Then we install the Enterprise modules with your Odoo subscription.
In a migration, the database is rarely the longest part. The added modules are. With each version, Odoo renames fields, changes functions and rewrites part of the interface.
We go through it ourselves. 22 of our apps on the Odoo store moved from version 18 to 19, then to 20. Each port was tested on a fresh database before release.

The same for a small database and a large one. Only the duration changes.
Your version, edition, modules and hosting. You get the migration path and a quote.
We work on a copy. Your Odoo keeps running as usual.
The copy moves to the target version. We time each step.
The same scripts run before and after the migration and compare the figures.
Your users test the migrated copy with a checklist per team.
Verified full backup, final migration, checks, then open on Monday.
The old database stays ready. If something blocks, we switch back.
Eyeballing is not enough on thousands of lines. Our scripts output the same figures before and after the migration, then compare them.
Customers, products, orders, invoices, journal items, attachments: table by table.
Trial balance per account, totals per journal, VAT per period.
Quantities per product and location, stock value.
Active accounts, groups, allowed companies.
Any gap stops the cut-over until it is explained.
Usually, based on database size and the number of added modules. The precise schedule comes after the audit.
A few users, few or no custom modules, one or two versions apart.
usually 1 to 2 weeks
An SME, several teams, some custom or store modules.
usually 2 to 6 weeks
Long history, several companies, many modules, or a start on Odoo 8 to 12.
over 6 weeks, schedule after audit
Most of the time goes into testing. The cut-over itself usually fits in a weekend.
Module inventory, migration path, quote.
free
A simple custom module, tested on the target version.
from €400
Copy, test runs, checks, acceptance, cut-over.
quoted after the free audit
VAT not applicable (French micro-business, article 293 B of the CGI).
We stay with you: follow-up after the cut-over, monthly support, training your teams on the new version.
See Odoo supportYes. It takes longer, because added code must move from Python 2 to Python 3. The database usually goes through several intermediate versions. The free audit tells you how many steps are needed.
In Enterprise, Odoo’s service can target a recent version for the standard part. In Community, with OpenUpgrade, it is one version at a time. Either way, every added module must exist in the target version.
It converts the standard part of an Enterprise database. It does not port your custom or third-party modules. That is the part we take on, along with following up the request.
Yes. All test runs use a copy. Your database only stops during the final cut-over, usually over a weekend.
Before the cut-over we take a full backup and check that it restores. The old database stays ready. If something blocks, we switch back to it.
Not quite. First the database is brought to the target version. Then the Enterprise modules are installed with your Odoo subscription. Community modules that do the same job must also be removed.
The audit is free. Porting a simple custom module starts at €400. The database migration is quoted after the audit, based on the starting version and the number of modules.
Tell us your version, edition and added modules. We reply within 2 business days and offer the free audit.
Ramira measures its audience with Google Analytics, only if you accept. You can change your mind with the “Manage cookies” link at the bottom of the page. Learn more