Upgrades and migration: frequently asked questions
Questions and answers
How often should we upgrade Odoo?
Odoo releases a major version every year and supports the three most recent. Most of our clients upgrade every one to two years, which keeps each upgrade small. Falling several versions behind turns an upgrade into something closer to a re implementation.
What does an upgrade involve?
An assessment of your modules, customisations and integrations; migration or replacement of custom code; repeated test upgrades of a copy of your production database; user testing of every process against a checklist; and a planned cut over with a rollback option. Enterprise customers use Odoo's upgrade service for the standard data; we handle the code and the testing.
Will our customisations survive the upgrade?
Custom modules must be migrated to the new version, and we review each one against the new standard features. Some are kept, some are replaced by configuration and some are retired. Studio changes are usually carried automatically but are tested like everything else.
Can you migrate our data from another system?
Yes. We have moved data from spreadsheets, accounting packages and older ERP products. The method is the same: agree what moves, clean the master data, map it, load it in rehearsals and reconcile balances and open items before go live. Our data migration guide sets it out in detail.
What should we do with historical data?
Usually keep it accessible in the old system in read only mode or in an archive, and load only opening balances and open items into Odoo. Migrating years of closed transactions is expensive and rarely used. We help you decide per data set.