Odoo Migration: the complete guide to upgrading to version 19 (and preparing for 20) in 2026
Your ERP Odoo is the heart of your business: it centralizes your sales, your accounting, your purchases, your inventory, and your projects. But a high-performing ERP must evolve with you. Staying stuck on an old version means accumulating technological debt, missing out on features that have become native, and soon paying more for the same thing.
This complete guide answers all the questions our clients have before migrating: why to do it, when to start, how it actually unfolds, what happens to your custom modules, and what changes internally. Each section links to a detailed article for further reading.
The difference between an Odoo migration and an update
The two are often confused, but they are two different things.
An update involves installing minor patches within the same major version (for example, going from 19.1 to 19.3). These are mainly security patches, performance improvements, and small feature additions. It's light and risk-free.
A migration, it is moving from one major version to another (for example from 17 to 19). There, the modules sometimes change profoundly, some features move or become native, and your custom developments need to be adapted. It's a real project, but a well-defined project when it is well supported.
This guide is about the migration : the transition from one major version of Odoo to a more recent version.
Why migrate now: the 3 signals
Three signals indicate that it is time to migrate your Odoo.
- The loss of official support. Odoo actively maintains its most recent versions. Since the revision of its support policy in July 2025, the publisher continues to support older versions, but now applies a 25% surcharge on licenses for versions that are too old. Falling behind ultimately ends up costing more.
- The need for new features. Each annual edition of Odoo brings significant improvements: usability, billing, subscription management, and, since version 19, a native integration of artificial intelligence. What you had custom developed a few years ago may now be offered as standard.
- Performance issues. As data and old modules accumulate, an ERP slows down. A migration is an opportunity to clean up and start fresh on a healthy foundation.
Odoo 16, 17, 18, 19, 20: where are you and where to go?
Odoo releases a major new version every year, in the fall, during its Odoo Experience event in Brussels. Version 19 was released in the fall of 2025 and is the current version in 2026. Version 20 is expected in the fall of 2026 (you understand the flow).
Here’s how to locate your version and where to head next:
| Version | Release | Support status | Notable new features | e3k advice |
|---|---|---|---|---|
| Odoo 16 and earlier | 2022 and before | Subject to a 25% surcharge | — | Migrate as a priority |
| Odoo 17 | 2023 | Still covered, but in the window to watch | — | Plan quickly |
| Odoo 18 | 2024 | Supported | Quote calculator, proposal generator | Migrate for the new features |
| Odoo 19 | 2025 | Current version | Native AI (agents, LLM connector), billing and subscription improvements | Recommended target |
| Odoo 20 | Fall 2026 | Upcoming | AI in support layer, natural language search | Target if migration after the fall |
How a migration works at e3k
Good news: a migration requires much less effort from your teams than an implementation. We handle most of the technical work.
How to migrate your custom modules from Odoo 18 to Odoo 19
This is often the real challenge of a migration. In an Odoo instance, there are generally three types of modules that are not part of the standard: your custom developments, community modules purchased on the Odoo Marketplace, and old customizations that may no longer be necessary.
For each, the question arises in three cases:
-
Is the need now covered by the native?
In this case, we abandon the custom code in favor of the standard, which eases your future migrations. -
Is there a compatible community module?
We buy and install the updated version. -
Is custom development still relevant?
If yes, we migrate it.
What changes internally and how to succeed in adoption
A successful migration does not stop at go-live. Your teams must take ownership of the changes — new menus, new procedures, new features. This is where the return on investment is determined.
At e3k, we plan for supplementary training focused on what changes (especially in accounting and on the most used modules), and we can train a super-user from the staff (internally) who becomes the liaison for their colleagues on a daily basis. Good change management makes all the difference between a tool that is adopted and a tool that is circumvented by users.
How long it takes and when to start
The duration of a migration depends on the complexity of your instance: number of modules, volume of customizations, data quality. What matters most is to start at the right time.
The ideal schedule follows the rhythm of Odoo. The new version is released in the fall; the migration tools stabilize in the following months; migration projects then follow from winter to spring. For companies that want to avoid the 25% surcharge on their licenses, there is a deadline to meet, and it is better to plan early to avoid being rushed.
Our recommendation: do not let more than two to three versions pass before migrating. Beyond that, the technological lag becomes such that some developments must almost be redone.
How to prepare your database before an Odoo upgrade
Your data is what you have that is most important: customers, suppliers, items, accounting history. A poorly prepared migration risks transferring them in disorder - or worse, corrupting them.
The image is that of a move. You don’t want to lose anything along the way, and you want everything to be well organized in the new place. Many companies rush to go faster and end up with disordered data in their new system: it’s like moving without sorting, transporting old junk along with the good furniture.
At e3k, we take the time to do things right. Before moving anything, we examine your data with you: we clean up, we validate, we ensure that everything is clean and useful. A migration is also an excellent opportunity to deduplicate and normalize your references. On go-live day, we systematically check that the accounting balances and the number of the last invoices have followed correctly, to ensure that no information has been lost.
A practical tip on history: it is not always necessary to take everything back. Reference data (customers, suppliers, items, stocks) and the accounting history of recent years generally suffice for operational and legal needs. Taking back ten years of history can burden the migration without real daily benefit.
Mistakes to avoid during a migration
Over the years, we have seen the same traps come back. Knowing them is already avoiding them.
Migrating without clear objectives or a timeline is like going on a trip without a map: it costs more and takes more time. A good migration starts with an analysis of the existing situation and a framing meeting.
This is the primary cause of problems in production. Poorly prepared or poorly tested data turns into a headache once online.
Reproducing your old system to the letter in the new version is counterproductive. Odoo has its own ways of doing things, often more efficient, and every unnecessary customization is a recurring maintenance cost.
Your teams need to adopt the new features. Without training or follow-up, resistance sets in and the value of the migration is lost.
Migrating at the last minute just to avoid overload, without auditing the state of the instance, is taking an unnecessary risk. It's better to plan early.
Why choose e3k for your migration services
At e3k, we act as an integrator that is part of our clients' team. Our migration approach is based on a few simple principles: a thorough analysis of the existing before proposing anything, a service offer aligned with your true needs, the protection of your data at every step, and a support before, during, and after the migration, including training.
We do not just move your system from one version to another: we take the opportunity to modernize it, remove what is no longer useful, and provide you with the new features that matter to your business.
Need help?
In this section, you can effectively answer the most frequently asked questions about migration, from users to pricing.
Am I at risk of losing data during migration?
No, if the migration is well managed. Your data is your most valuable asset: at e3k, we validate it at every step and check the accounting balances on the go-live day to ensure that nothing has changed.
Is it better to migrate to Odoo 19 or wait for Odoo 20?
It depends on when you migrate and your priorities. Version 19 is the current and proven version; version 20 brings new AI capabilities. We help you choose based on your context during the assessment.
How much time do my teams need to dedicate to this?
Much less than for an implementation. The essential technical work is carried out by e3k. On your side, it mainly involves testing the new base and attending some supplementary training.
How often should we migrate?
Ideally every two to three years (try to keep up with the releases of new versions of Odoo). Waiting longer creates a technological lag that complicates the migration and can lead to an overload on your licenses.
What are the key steps to successfully migrate Odoo?
igration technical and testing (UAT), followed by Go-live.
How much does an Odoo migration cost?
To avoid surprises, an audit by a certified partner is essential. At e3k, this initial diagnosis secures your budget before the project launch.