DevTalents
Odoo migration since 2014

Odoo migration: move to the new version without losing anything

Upgrade of your Odoo database, Community or Enterprise, to a recent version, with your custom modules rewritten, or move of your data from another software. Every Odoo migration is tested on a copy of your database before we touch production.

  • Custom modules included
  • Test migration on a copy
  • Community and Enterprise
Billy, the DevTalents mascot, flying up to the new Odoo version on his rocket
Billy, the DevTalents mascot, climbing the steps of a growth chart
Every Odoo version

Odoo migration: two projects, not a simple update

Installing the new version is not enough. Two things have to move to it, and the second one usually sets the duration and the cost of the upgrade.

  • The database, converted with Odoo's upgrade service (Enterprise) or with OpenUpgrade (Community).
  • Your custom modules, rewritten wherever the new version changed the framework.

Coming from another ERP? We also move companies to Odoo: the data is extracted, cleaned and imported, then checked with your team on a test database.

Our Odoo implementation service
Why upgrade

When to plan your Odoo migration

Four situations that usually start the project.

Your version is no longer supported

Outside the last three versions, Odoo publishes no more security or bug fixes.

E-invoicing

Since September 2026, the French reform requires every company to receive electronic invoices. Recent versions handle Factur-X and Peppol.

E-invoicing in Odoo

Modules no longer updated

Odoo Store publishers and connector providers stop following old versions.

Odoo connectors

Features and speed

Each version brings new features and a faster interface, which your team often already asks for.

Scope

What we migrate

Everything your Odoo relies on, not only the database.

Version upgrade

Your database moved to a recent Odoo version, whether you skip one version or several.

Custom modules

Rewritten wherever the framework changed: Python API, views, OWL JavaScript, reports.

Odoo development

Odoo Store modules

Checked one by one: new version from the publisher, port, replacement or now covered by the standard.

Data from another software

Customers, products, stock, open invoices and balances taken over from your current ERP or spreadsheets.

Website and theme

Pages, theme and online shop adapted to the new version of the Odoo website builder.

Odoo theme development

Hosting

A move between Odoo Online, Odoo.sh and your own server can be done at the same time.

From your version

What changes from one Odoo version to the next

The further back your version, the more framework changes your custom modules have to cross. The main milestones:

From Odoo 10 or earlier

Python 2 and, on the oldest versions, the old ORM API: custom modules are mostly rewritten.

From Odoo 11 or 12

From Odoo 13, invoices became journal entries (account.invoice merged into account.move). Every accounting customization is reviewed.

From Odoo 13, 14 or 15

The web client has since moved to the OWL framework and assets are declared in the manifest: JavaScript widgets are rewritten.

From Odoo 16

Odoo 17 removed the attrs and states attributes from views: conditions are rewritten as Python expressions.

From Odoo 17

In Odoo 18, tree views became list views and several field attributes were renamed: views and reports are adapted.

From a recent version

Moving up one version is mostly code adjustments and tests. The best time to migrate, before the gap grows.

Which Odoo version to target?

Odoo releases a major version every year and supports the last three. On an older version you no longer get security or bug fixes, and recent features such as e-invoicing (Factur-X, Peppol) are missing.

We usually recommend the latest stable version, unless a module you depend on is not available for it yet. The module inventory tells us that first.

Duration and cost of an Odoo migration

Both depend on the same factors:

  • the number and size of your custom modules,
  • the gap between your version and the target,
  • the Odoo Store modules to port or replace,
  • the connectors to test (e-commerce, payment, carriers, banks).

We give you an estimate after the module inventory, not before.

Our method

How we migrate your Odoo

Five steps, the same whether you skip one version or five.

  1. Module inventory

    We list your modules: standard, from the Odoo Store, custom. For each one we check whether it exists in the target version, has to be ported, or can be dropped.

  2. Test migration

    We migrate a copy of your database. The copy is neutralized: no emails sent, no scheduled actions, no real payments.

  3. Your tests

    Your team checks its daily work on the migrated copy: quotes, invoices, stock, reports. We fix what comes up and run a second test migration if needed.

  4. Go-live

    The production database is migrated on a planned date, outside working hours, with a backup and a rollback plan.

  5. After go-live

    We stay available during the first weeks to fix what only shows up with real use.

Frequently asked questions about Odoo migration

How long does an Odoo migration take?

It depends mostly on the number of custom modules and on the gap between your version and the target. A database with only standard and Odoo Store modules goes faster. We give you an estimate after the module inventory.

How much does an Odoo migration cost?

The cost follows the same factors as the duration: custom modules to rewrite, number of versions skipped, Odoo Store modules to port, connectors to test. We send a quote after the module inventory, with the work listed module by module.

Do we have to migrate every year?

No. Many companies migrate every two or three years, before their version leaves the three supported by Odoo. Waiting longer makes the next migration bigger, because the code has to cross more versions.

Can we skip several Odoo versions at once?

Yes. The database is converted up to the target version, and your custom modules are rewritten directly for that version. The larger the gap, the more code there is to adapt.

Is there a risk of losing data?

We first migrate copies of your database, which your team tests. The production database is migrated only after your approval, with a full backup and a rollback plan.

Understanding Odoo's neutralized database

Do you migrate Odoo Community as well as Enterprise?

Yes. For Enterprise we use Odoo's upgrade service; for Community we use OpenUpgrade, the OCA migration scripts. In both cases, custom modules are ported by our developers.

Can we move from Odoo Community to Enterprise during the migration?

Yes, both can be done in the same project. We install the Enterprise modules on the migrated database and check that your custom modules work with them.

What about the modules bought on the Odoo Store?

We check whether each publisher offers the target version. If not, we port the module, replace it with an equivalent, or check whether the standard now covers the need.

Can you move us to Odoo from another software?

Yes. We extract the data from your current software, clean it, import it into Odoo and check it with your team on a test database before the switch.

Odoo implementation

Is your Odoo stuck on an old version?

Tell us your current version and your modules, we reply within 48 hours.

Discuss your migration
Billy, the DevTalents mascot, in a superhero cape