A common worry for companies stuck on an old Odoo version is that they will have to rebuild from scratch. Usually they don’t.
What you keep when you upgrade
- Every transaction: invoices, payments, stock moves, sales history.
- Configuration: chart of accounts, taxes, routes, approval rules, user rights.
- Integrations: payment, shipping, eCommerce and banking, retested rather than rebuilt.
- User habits: people keep working in the system they know.
When reimplementing does make sense
- The business has changed shape. New entities, a new operating model or a different industry focus that the old setup can’t express.
- The data is unreliable. Years of workarounds have left balances or stock you no longer trust, and cleaning them costs more than starting fresh.
- Customisation replaced standard Odoo. When core flows such as accounting or MRP were rewritten rather than extended, and newer Odoo now does the job natively.
A five-question test
| Question | Points to upgrade | Points to reimplement |
|---|---|---|
| Do your core processes still fit? | Yes | No |
| Do your balances and stock reconcile today? | Yes | No |
| Is most custom code extending Odoo, not replacing it? | Yes | No |
| Do you need your transaction history in the same system? | Yes | No |
| Can you live with a few weeks of testing, not months of rollout? | Yes | No |
Three or more answers in the first column: upgrade. The upgrade estimator shows how big that upgrade is likely to be.
The middle path: upgrade and simplify
The best upgrade projects often do both. We upgrade the database, then retire custom modules that newer Odoo versions make unnecessary. You keep your history and end up with less code to maintain. The free assessment flags which modules are candidates for retirement.
FAQ
Is reimplementing Odoo cheaper than upgrading?
Rarely. A reimplementation repeats configuration, data migration, training and integration work, and you lose transaction history unless you migrate it separately.
Can we upgrade and clean up at the same time?
Yes. Removing unused modules and replacing custom code with newer standard features is often the most valuable part of an upgrade project.