Odoo migration (18, 19, 20)

• Inventory of installed modules and clean-up
• Porting of custom modules with automated tests
• Migration of a copy of your production database
• User acceptance tests, then cut-over

Two sides to every migration

A migration has two parts: the code of every added module (Python, XML views, JavaScript) and the data of your database. In Enterprise, Odoo’s upgrade service migrates the standard part; in Community, we rely on the community tools (OpenUpgrade) and our own scripts for your modules.

Our method

1. Inventory: standard, purchased and custom modules — and which ones are still used.
2. Porting each custom module, with automated tests.
3. Install on a fresh database of the target version to catch dependency issues.
4. Migrate a copy of your production database and measure the duration.
5. User acceptance tests with a checklist per team.
6. Cut-over with a verified full backup (see automatic Odoo backups).

We port our own Odoo apps every year. Details in migrating an Odoo module to 19 and 20, and pricing in how much a custom Odoo module costs.