Skip to content
العربيةLet’s talk

Practical guide

Odoo version upgrades: what to audit and rehearse first

Audit Odoo extensions, integrations and workflows before a version upgrade, with a test register, release criteria and practical recovery questions.

Lava Solutions · · 5 minute read

Network cables and illuminated equipment behind mesh doors in server racks.
Illustrative stock photo. Photo: Taylor Vick / Unsplash.

Before upgrading an existing Odoo system, establish whether the next version preserves the work your business needs to complete. A database that opens successfully is only the starting point. Your decision should rest on tested processes, compatible extensions and a release plan that explains what happens if a critical check fails.

This guide concerns moving an existing Odoo database to a newer version. Initial spreadsheet imports belong to a different exercise. Product references use Odoo 20 documentation checked on 17 November 2026; they do not establish that a particular target version is available for your database today. Confirm the supported path, edition and hosting arrangement with the responsible administrator or provider.

Identify the change you are approving

Write down the current version, proposed target, hosting type, installed applications and accountable business owner. Keep edition changes and hosting moves explicit: Odoo's upgrade documentation distinguishes these from a version upgrade. Combining several changes without separate acceptance criteria makes failures harder to diagnose.

Define the reason for the upgrade and the processes that must remain usable. For example, “the sales team can fulfil and invoice an existing order” is a testable requirement; “everything works” is not. Record any intentionally changed process so testers know which differences are expected.

Build a dependency register before booking the cutover

Use a short register to expose items whose compatibility cannot be inferred from a successful standard upgrade. Include small operational details such as document layouts and barcode devices when staff depend on them.

DependencyQuestion for the ownerEvidence to collect
Custom or third-party moduleWho maintains the target-version code and its dependencies?Identified release and completed business tests
Document or reportWhich fields, totals and language layouts are essential?Reviewed output from representative records
External integrationWho owns both ends and the failure queue?Normal, rejected and repeated-message results
AutomationWhat triggers it, and what must remain paused during testing?Approved test trigger and expected result
User role or deviceCan the intended user finish the task on the equipment actually used?Observed task result under intended permissions

Odoo's customized-database upgrade guide requires attention to custom code as well as the database. Ask maintainers to confirm their responsibilities and target compatibility. Review whether an extension is still needed before spending effort adapting it. Freeze discretionary changes during the rehearsal, and record essential fixes so the tested code remains identifiable.

Prepare a test environment with controlled connections

Request or prepare an upgraded test copy through the procedure for your hosting arrangement. Record its source backup time, code revision and configuration differences. Avoid a test result whose underlying data or code cannot be reproduced.

Odoo's neutralization guidance lists disabled outgoing email, scheduled actions and bank synchronization in testing copies. Have the administrator inspect custom connections and access separately. Neutralization does not establish anonymization; arrange appropriate test credentials and data controls.

On Odoo.sh, a staging merge transfers source code rather than database changes, according to the branch documentation. Record configuration steps separately and rehearse how they reach production. Do not assume a manual correction in staging will appear in the live database.

Compare business outcomes, not screenshots alone

Choose a small set of records that represent real complexity: an open order, a partial delivery, a return, a document in Arabic and a transaction involving an integration. Use approved records or realistic synthetic equivalents. Capture the expected outcome before testing the new version.

For each scenario, record the starting reference, acting role, action, expected result, actual result and evidence. Compare meaningful quantities, balances, relationships and document contents. Investigate differences rather than assuming either version is correct. A changed button position may need updated instructions; a missing transaction or incorrect total needs a different response.

Include restrictions in the checks. A warehouse operator should complete the assigned stock task, while access to unrelated information should still follow the approved design. Run cross-application handoffs through to their intended stopping point instead of checking each menu in isolation.

A fictional exception worth rehearsing

Fictional example, not a customer case: a distributor uses an extension that passes delivery references to another system. A normal delivery works in the upgraded copy, but repeating the same message creates a second external record. The test team records the original and repeated message identifiers, the expected single result and the duplicate result.

The integration owner fixes the issue and reruns the affected scenarios. The team also checks that a failed message is visible to the person responsible for resolving it. This example illustrates acceptance evidence; it does not claim that Odoo itself causes or automatically prevents that failure.

Rehearse the release and recovery decision

Run the final procedure with a sufficiently recent approved copy and the exact code intended for release. Document transaction-entry restrictions, backup handling, responsibilities, validation order and communication to users. Use the rehearsal to inform the operational window; do not treat another company's timing as your downtime estimate.

A recovery plan needs more than “restore the backup.” Identify who can authorize recovery, which backup and attached files are required, how restoration will be validated, and how transactions created after the backup will be reconciled. Odoo's upgrade procedure does not provide a downgrade to a previous version. Have the hosting team confirm a workable recovery approach instead of promising an automatic reverse upgrade.

  • Proceed: critical scenarios pass, dependencies have owners, and the release and recovery procedures are agreed.
  • Delay: unexplained financial or stock differences, broken required integrations, or unavailable target-version extensions remain.
  • After release: review representative live transactions and assign every remaining issue to an owner.

Review the configuration and customization guide when deciding which extensions to retain. To scope an upgrade review within Lava's Odoo services, send an enquiry with your current version, hosting type, key applications and known extensions.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗