Odoo releases one major version a year. Staying on an old version eventually costs you: support drifts away, security fixes go missing, new features pass you by. Here is the checklist we follow for a migration to Odoo 19, whatever the starting version.
Why migrate, and when?
- Security and support: Odoo only maintains the most recent versions. Check the official support page to see where yours stands.
- Compliance: regulatory changes, such as e-invoicing, are handled in recent versions.
- Performance and usability: each version improves the interface and speed.
- Features: new apps and new options become available.
The right time is rarely "some day": choose a quiet period for your business and, for accounting, a date close to a closing.
Step 1: the starting audit
You can only migrate well what you know. First of all, take inventory:
- the exact version and edition (Community or Enterprise);
- the list of installed apps and those actually used;
- custom modules developed for you;
- third-party apps, with their compatibility with Odoo 19;
- connections with other tools: website, bank, carrier, external accounting;
- custom reports, views and automations;
- the data volume and the history to keep.
Step 2: clean up before migrating
This is the step people are tempted to skip, and the one that saves the most time. Archive obsolete records, merge duplicates, remove modules nobody uses any more. Every item removed is one less to test and fix.
Step 3: migrate a copy
Migration is first done on a copy of your database, never on the production database. For Enterprise customers, Odoo provides an upgrade platform; for Community, the community maintains dedicated tools. In both cases the raw result needs fixing: the gaps between versions, especially when you jump several versions at once, do not fix themselves.
Step 4: adapt custom modules
Modules developed for you must be reviewed, adapted and tested. This is often where most of the workload hides. Take the opportunity to ask whether each development is still needed: some functions have become standard in recent versions.
Step 5: test with real scenarios
Do not settle for a technical test. Have your teams replay the flows that matter:
- quote, order, delivery, invoice, payment;
- purchase, receipt, vendor bill, payment;
- stock movements and inventory;
- accounting closing and bank reconciliation;
- printouts and reports used every day.
Compare balances with your accounting: a discrepancy is a signal to handle before switchover.
Step 6: prepare the teams
A new version changes screens and habits. Plan a short training on the differences, plus reinforced support in the first days. This avoids a migration that is technically successful but badly experienced.
Step 7: the switchover
- set a switchover window outside your peak activity;
- freeze entries in the old database during the final import;
- plan a rollback in case a blocking issue appears;
- monitor the first days closely and fix discrepancies quickly.
Common pitfalls
- jumping several versions without going through a test copy;
- discovering late that a third-party app is not compatible;
- not involving users in testing;
- migrating without cleaning up, and finding your duplicates in the new version;
- forgetting external connections, which silently stop working.
Frequently asked questions
Can we go straight from 15 to 19?
Technically this is possible in some cases, but the bigger the gap, the more checks are needed. In every case, go through a test copy before touching production.
How long does a migration take?
From a few weeks to several months, depending on the number of custom modules, data quality and your teams' availability for testing.
Do we have to stop working during the migration?
No: preparation and testing are done on a copy while you carry on working normally. Only the final switchover needs a short interruption.
Have your migration assessed
To find out where you stand, our Odoo migration page presents the method we apply. You can also ask for a diagnostic or book a call with an expert.