← Odoo ERP

Odoo ERP services · Odoo Migration & Upgrade

Upgrade Odoo without breaking the things that work.

Older Odoo versions eventually lose support and security fixes. Most businesses know they need to upgrade. What holds them back is the fear that custom modules, reports and integrations will stop working. That fear is reasonable, and it's why we test everything on a copy first.

Odoo Accounting dashboard with sales, purchase, bank and tax return widgets
After an upgrade, accounts should open exactly where they left off: same balances, same reconciliations, same tax setup.

How we upgrade without surprises

01

Audit what you have

We list every installed module, custom development, report, automated action and integration, and check which are still used. It's common to find that a good share of the customisation can be dropped.

02

Decide what to port, replace or retire

Some custom features now exist in standard Odoo. Others need to be rewritten for the new version. You get a clear list with effort for each.

03

Upgrade a copy of your database

Standard data is upgraded using Odoo's upgrade process (Enterprise) or community tooling such as OpenUpgrade. Custom modules are ported and tested against your real data.

04

Test with your team

Your key users run their daily work in the upgraded copy: orders, deliveries, invoices, reports. We fix what they find and repeat until it's clean.

05

Cut over quickly

On the agreed date, we take a final copy, upgrade it and switch over, planned for a quiet period so your team loses as little working time as possible.

Common reasons people put off upgrading

  • You're on an older Odoo version, and every feature you want needs an upgrade.
  • Whoever built your custom modules is no longer around.
  • The last upgrade broke the invoice layout and the shipping integration for weeks.
  • You want to move from Community to Enterprise, or from your own server to Odoo.sh.
  • You're on another ERP or accounting system and want to move onto Odoo.

What the upgrade includes

  • An audit of modules, customisations and integrations
  • Custom modules ported, replaced or retired, with reasons
  • A tested, upgraded copy before anything goes live
  • A short, planned cut-over with a rollback plan
  • Notes for your team on what changed in their screens

Upgrade questions

Can we skip versions, for example jump three versions at once?

Yes. The data upgrade passes through each version behind the scenes, but you only go live once. Custom modules are ported straight to the target version.

Will we lose historical data?

No. Your full history comes across: orders, invoices, stock moves and accounting entries. We compare key figures such as stock value and receivables before and after to prove it.

How much downtime should we expect?

It depends on the size of your database. We rehearse the whole upgrade on a copy first, so we know how long the real switch takes before we schedule it.

We're not on Odoo yet. Can you migrate us from another system?

Yes. That's closer to an implementation with a data migration at its core. See Odoo Implementation.

Stuck on an older Odoo version?

Tell us your current version, hosting and roughly how much custom work you have. We'll tell you what the upgrade involves.