An Odoo upgrade rarely fails because of the software itself. More often than not, it is caused by an overlooked element, a missed customization, an unreviewed business process or an unprepared team. Gaps in preparation, rather than the platform itself, are the key reason why ERP setups miss their intended business objectives.
This checklist covers all the essential preparatory steps for an Odoo upgrade and migration, including the required post-production verification, based on the software’s official documentation and industry best practices.
1. Back up All Necessary Data Before Changes Are Made
Regardless of the upgrade method, the official Odoo documentation requires that before upgrading the production database, a working backup of all of its data be available and validated. The documentation also notes that a database backup is automatically produced before the upgrade starts, which is used to restore the system in case of an error.
For Odoo.sh and On-Premise hosting, Odoo specifically advises downloading a full local database dump (.zip or .dump). Having this file locally is essential because you will need to upload it to the upgrade platform multiple times throughout the testing, bug-fixing, and migration cycles.
Checklist
- Confirm that there is a recent working backup ready to be restored
- Ensure that at least one database backup, preferably recent, is available separately from the upgrade process for later reference
- Record the corresponding version of the database for the backup
2. Document Current Business Flows and Customization Needs
Before migrating to a new version, it is crucial to have a printed or digital description of the current business flows and customization needs. The documentation is not specific to Odoo, as it is the case for most ERP systems, but it remains vital, as poorly documented processes and the lack of training will lead to many post-production upgrade issues. It should include information on the company’s core processes, the list of applications and custom modules in use, and reports and automations the business relies on daily.
Checklist
- Make a list of custom modules, automations, reports, and other customizations in use
- Prepare a paper or digital description of core sales, purchasing, warehouse, and accounting processes
- Identify processes requiring additional time and attention after the upgrade
3. Prepare All Necessary Customizations
The Odoo documentation is explicit that prior to an upgrade, all company-specific custom module code must be made compatible with the target version. This step is particularly complicated and time-consuming for businesses relying on heavily-customized ERP systems, and it is usually one of the most underestimated parts of the migration process.
Checklist
- Compile a list of all custom modules and third-party apps in use
- Ensure that all customizations are compatible with the target version and upgraded to it
- Separate custom records marked with the “no update” flag and determine their status according to the new scripts
- Allocate sufficient time for this step, which is often much longer than the platform upgrade itself
4. Test Thoroughly Before Launching the Production Upgrade
Testing is another critical part of any Odoo migration. Before touching the production database, request an upgraded test copy and use it to get familiar with the new version and confirm every process still works as expected.
This test copy runs in a safe, contained environment: scheduled actions are switched off, outgoing emails are rerouted to a dummy server, and payment, delivery, and bank-sync connections are disabled. Nothing in it can reach a real customer, supplier, or bank account.
Use this window to walk through the basics, creating and editing sales orders, invoices, purchases, contacts, and companies, and, for multi-channel retailers, the full checkout flow from product selection onward. If the upgrade script gets revised for any reason, request a fresh test copy and run through everything again rather than assuming the fix holds.
Checklist
- Request an upgraded test database before initiating the production upgrade
- Perform a full production upgrade test, going through every business-critical procedure identified in step 2
- Compare product details, customer lists, and other relevant data between the two databases, ensuring that at least a small sample of products in terms of variety and price range is identical
- Report all discrepancies to technical support before proceeding to the next stage and request a new test database after all changes are made
- Repeat the test if any custom module or upgrade script changes
5. Prepare Users for the Upcoming Changes
Even a flawless production upgrade can be rendered ineffective if the company’s end-users are not aware of the upcoming changes and how to interact with the new system. The official documentation is not specific about this aspect of the migration, but most general ERP migration guidelines suggest planning end-user training in accordance with the project scope and timeline. The documentation recommends that businesses provide relevant user training, noting that users must know the differences affecting their daily operations.
Checklist
- Prepare a list of all critical processes, screens, or menus that will change after the upgrade
- Conduct separate briefings for all relevant personnel, focusing on the aspects of the new system they will use on a regular basis
- Designate a specific channel for user feedback in the first weeks following the launch
- Plan a cutover window and confirm with all users that all work is saved and they are logged out before the production upgrade launches, as the database will not be accessible during this time
6. Follow Up After Migration and Validate Performance
Testing shouldn’t stop once the production upgrade goes live. If the upgrade script gets revised at any point, request a new test copy and run through the validation steps again rather than assuming the previous round still holds.
The same level of care applies after go-live: check that reports, automations, and third-party integrations all behave correctly on the production instance, not just in testing. It also helps to give end-users a clear, dedicated channel to flag anything that looks off, since they’re often the first to spot a discrepancy the test phase missed.
Checklist
- Re-test all business-critical procedures identified in step 2 using the production database
- Confirm that all automation scripts, reports, and third-party applications are active and operating normally, as they are often disabled in test instances
- Gather user feedback and document any repeated issues or bugs
- Ensure that the backup from before the upgrade is accessible for at least as long as the time specified in step 1
Following these steps in roughly this order will make for a much smoother Odoo upgrade. Most of the trouble businesses run into comes down to a handful of avoidable mistakes: skipping one or more prep tasks, testing without a clear sense of which processes actually matter to the business, and putting off user training until too late. Treating the migration as one continuous process, rather than a checklist of disconnected steps, cuts down on errors and delays significantly.
An experienced Odoo partner earns their keep here. Their main value isn’t running the upgrade itself, it’s making sure none of these steps get skipped, since skipping them is usually what decides whether a migration succeeds or fails.
