End of support
Odoo provides three years of standard support per major version. Beyond that, you need to buy paid extended support.
Upgrade your custom modules and your data to Odoo 18, 19 or 20. Tell us about your project: we send you a written estimate before any commitment.
An Odoo version that leaves standard support stops receiving fixes under it. The longer you wait, the bigger the gap to close.
Odoo provides three years of standard support per major version. Beyond that, you need to buy paid extended support.
Once standard support ends, security fixes are no longer provided under it, yet your ERP holds your most sensitive data.
A modernised interface, new modules and better integrations: recent versions make daily work simpler.
Every release brings database and interface optimisations.
Connectors, localisations and third-party modules target recent versions and become hard to find for old ones.
Custom modules written for an old version pile up. Migrating them early costs less than migrating them all at once later.
Standard Odoo and your customisations are not migrated the same way. We work where your project is unique.
Python, XML views, JavaScript (to OWL) and styles: each module adapted to the new version, with a list of points to review by hand.
Migration scripts, carrying over your custom fields and models, integrity checks and accounting totals before and after.
With a valid Enterprise contract, Odoo upgrades the standard applications of your database through its platform. Your custom modules must be ready for the target version before that step: we migrate them, including those that depend on Enterprise.
Migration of the database and your own modules, with the community (OCA) modules available for the target version. Coverage of standard data depends on community tooling: we spell it out in the estimate.
We study your project (version, modules, data volume) and send a written estimate, lot by lot.
Your custom modules adapted to the target version, then reviewed by a developer.
We work on a copy of your database. Your production is not touched during test runs.
Modules installed on the target version, existing tests run, accounting totals checked, then acceptance by your own users.
Cutover planned with you, in a window whose length is estimated in the quote, then support and fixes after go-live.
Starting versions: Odoo 12 to 19 (Odoo 10 and 11 on request). Target versions: Odoo 18, 19 or 20, Community or Enterprise. Other combinations are possible depending on the state of your code.
It depends on the number of custom modules, the data volume and the gap between versions. We give a timeline estimate in the quote.
The price depends on the number and complexity of modules, the starting version and the quality of existing code. We do not publish a fixed rate: you receive a written quote, lot by lot, before any commitment.
It depends on your code. The study shows, module by module, what migrates as is, what needs adapting and what must be replaced, notably when a module depends on code that has disappeared from Odoo.
We work on a copy of your database, under a confidentiality agreement, with access limited to what is strictly needed. Your production keeps running normally during test runs.
No. Test runs happen on a copy. Only the final cutover requires an interruption, whose length is estimated and planned with you.
On Enterprise, with a valid contract, Odoo handles the upgrade of standard applications. We migrate your specific code and prepare the go-live. On Community, we also migrate the database; coverage of standard data depends on community tooling.
Describe your situation in a few lines. We come back with the useful questions, then a written estimate.