At some point during the planning of your upgrade from one version of Odoo to another, the discussion will inevitably touch on the subject of custom migration scripts. And, in truth, the answer always seems to hinge on exactly what you’ve built on top of Odoo, rather than the migration itself.
Here’s a quick breakdown to help you decide between a custom Odoo migration script and a regular migration.
What an upgrade actually covers
Odoo’s own Upgrade Service handles the technical conversion of your database, meaning your standard modules and standard data, so they work correctly on the new version. It is a technical procedure that can be used by any customer with Odoo Online, Odoo.sh, or a private server at any time an upgrade is needed.
In most cases, the Upgrade Service will not handle custom modules or those developed partially in-house and partially with support from Odoo, unless they are actively maintained under the organization’s subscription to ongoing services. It also doesn’t clean up messy pre-existing data or fix configuration issues you’ve been living with for years, with the sole exception of Studio customizations, which upgrade automatically if Studio itself is active on your subscription.
Therefore, the entire consideration for external migration services boils down to the presence and degree of impact of customizations on the instance.
When do you need one?
There is a strong likelihood that you will need either a fully custom script or at least a migration plan that goes beyond the standard migration procedure if any of the following applies to your instance:
. There are modules, processes, or automation not natively supported by Odoo, whether they are built in-house or through third-party channel
. There is a significant amount of legacy data that will require processing and cleansing prior to migration
. There is a need to consolidate information from other systems or applications into Odoo
. Your internal business logic requires the use of fields, records, or data structures not found in the standard Odoo modules
On the other hand, if the instance uses primarily default Odoo modules with limited Studio customization, it is safe to go with a standard migration.
…And what if you don’t?
The single greatest cause of migration failure stems from attempting to migrate complex processes or data with insufficient preparation. It is not uncommon for organizations to attempt to migrate such processes on their own or with external developers who are not familiar with their intricacies.
Such actions will invariably result in some data being misplaced or lost, potentially disrupting processes that may not be noticed until weeks or months after the migration’s completion. Unless explicitly planned, processes relying on this data or utilizing unsupported fields and records will cease to function correctly, and the migration’s overall success will be difficult to assess accurately.
A poorly handled migration run can lead to a substantial amount of extra work being generated, both for the migration service handling it and the client in whose database it is installed.
It is important to note that despite migration being a technical process, it is one that deeply affects the business operations of nearly every department. As such, it should be approached with care and handled by someone with expertise in Odoo’s technical intricacies as well as a basic understanding of business logic.
That is why most companies that handle Odoo migrations are implementation partners with years of experience in the field. After reviewing the request, their technical staff will be able to advise the client on the scope of work entailed by the migration, including whether an individual instance will require a custom migration script, additional processing of data, or can be handled with standard procedures.
Summary
A custom Odoo migration script is rarely necessary but can be prohibitively expensive to ignore. In cases when the instance utilizes heavily customized processes and automation or hosts large amounts of legacy data, it is the safer, more cost-effective choice. This guide should help you understand the business case for choosing between a standard or a custom migration.
If you are unsure what category your instance falls under, that is a sign that you should ask for a more detailed assessment prior to initiating the upgrade.
