Preparing for an Odoo 20 upgrade is a business-continuity task best approached at a measured pace. At the time of writing, Odoo has not confirmed the final Odoo 20 feature set, so we recommend avoiding assumptions about what the new release will change or add. An upgrade should also be treated as an opportunity to review whether your current Odoo setup still reflects the way the business operates. Over time, companies often accumulate custom fields, automated actions, reports, integrations, and process changes that were introduced to solve specific problems. Before upgrading, it is worth confirming which of these changes are still necessary and which can be simplified or removed.
We encourage you to focus on the parts of your current environment that already support daily work. By reviewing your customizations, data, integrations, workflows, and internal resources now, you can make a calmer, better-informed decision when official Odoo 20 documentation becomes available.
Prepare Now for a Confident Odoo 20 Upgrade
For Canadian manufacturers, distributors, and service businesses, fall is often a practical time to begin Odoo upgrade planning. Teams are reviewing year-end capacity, setting budgets, scheduling production, and deciding where IT time will go in the next fiscal period. That makes it a sensible moment to identify risks before calendars become crowded.
An Odoo 20 migration may affect more than the screens employees use each day. It can involve custom modules, connected systems, business data, approval processes, reporting, and the people responsible for supporting each area. We find that early preparation helps turn unknowns into a manageable review list.
The goal is not to commit to a production upgrade before you are ready. It is to understand what you have today, what your business depends on, and what deserves closer attention once Odoo confirms the release details. That groundwork can reduce surprises during testing and help protect day-to-day operations.
Map What Supports Your Odoo Environment
Start by creating a current-state inventory of everything that extends or depends on Odoo. Undocumented changes are often where uncertainty begins. A field added years ago, an automated email, or a tailored approval step may still support an important business process, even if nobody remembers why it was created.
We recommend documenting custom modules, custom fields, automated actions, custom reports, security rules, modified screens, and tailored workflows. The goal is to separate business capabilities that still matter from old workarounds, duplicate functions, or changes that no longer bring much value.. For Odoo environments with significant customization, this review can also help identify areas that may require additional development or testing during the upgrade. A custom manufacturing workflow, accounting report, approval rule, or automated action may work reliably today but still require validation after the database and modules are upgraded. Documenting these dependencies before the release gives your team a clearer starting point for the technical review.
Dependencies deserve the same attention. A custom manufacturing flow may rely on several connected modules. A report may depend on scheduled actions, custom fields, and an outside data feed. Mapping those relationships helps you estimate the real scope of an Odoo 20 upgrade.
As you review the environment, ask practical questions:
- Which customizations support production, sales, finance, or customer service?
- Which modules rely on other custom modules or third-party apps?
- Which changes have a clear business owner who can help test them?
- Which workarounds may be candidates for retirement or replacement?
This review gives leaders a clearer picture of maintenance needs before specific Odoo 20 migration impacts are known.
Safeguard Workflows, Data, and Integrations
What matters most is whether complete business processes hold up end to end. A successful upgrade is one where employees can still process orders, replenish inventory, plan production, ship products, invoice customers, close the books, and trust their reports.
We suggest identifying the workflows that cannot fail during or after an Odoo 20 upgrade. For manufacturers, that may include production planning, work orders, quality checks, inventory movements, and purchasing. For distributors and service businesses, quote-to-cash, procure-to-pay, invoicing, payment processing, and management reporting may take priority.
Connected systems should be part of this review. The same principle applies to Odoo integrations that support everyday transactions. If an external system creates sales orders, updates inventory, sends payment information, or transfers customer data, the integration should be included in the upgrade test plan. A technically successful Odoo upgrade is not enough if an important connection stops transferring data correctly. Your Odoo environment may exchange information with e-commerce platforms, shipping carriers, payment providers, payroll systems, CRM tools, business intelligence platforms, EDI systems, or shop-floor equipment. Confirm which connections are needed every day, who maintains them, and whether the responsible provider or internal team will be available to review compatibility.
Focus your integration review on:
- Third-party and Community apps that need version support
- External systems that send data to or receive data from Odoo
- Integration owners, support contacts, and maintenance responsibilities
- Processes that could stop if an integration needs changes
Data protection also belongs in upgrade readiness. We recommend validating that database backups can actually be restored, not simply created. Confirm whether attachments, documents, integration settings, and supporting configurations are included. If you run Odoo on premises, review server capacity, operating system support, database compatibility, and who is responsible for the underlying infrastructure. It is also useful to define who is responsible for confirming the backup, restoration process, and recovery steps before the production upgrade. This responsibility should be clear between the internal team, IT provider, and Odoo implementation partner when multiple parties are involved.
Plan a Controlled Odoo 20 Migration
A separate testing environment gives your team room to assess changes without putting live operations at risk. Production should not be the first place where you discover that an accounting process, custom module, integration, or manufacturing workflow needs attention. The testing environment should reflect the most important parts of the production setup, including relevant customizations, integrations, user permissions, and business data needed for realistic scenarios. The closer the test environment is to real operating conditions, the easier it is to identify issues before they affect employees or customers.
Testing should be led by real business scenarios, not isolated screens. For example, your team may create an order, confirm stock availability, trigger purchasing or production, complete delivery, issue an invoice, record payment, and then confirm that reporting remains accurate. That sequence reflects the way customers and employees experience the system.
Keep a clear issue log as testing progresses. Each entry should identify the affected workflow, business impact, owner, priority, and next action. With that information in hand, your leadership team can decide whether to proceed, delay the production upgrade, replace a dependency, or adjust an internal process.
Testing should involve the people who actually use each business process. Finance users should validate accounting workflows, operations teams should test inventory and purchasing, and production teams should verify manufacturing processes.
Business users are best positioned to confirm the system still supports the way the company operates, beyond what technical testing alone can show. An Odoo upgrade checklist can keep business, finance, operations, IT, and implementation partners aligned. Before Odoo 20 arrives, review these readiness areas:
- Custom modules identified, customizations documented, and module dependencies reviewed
- Third-party and Community apps assessed, with external integrations inventoried
- Critical workflows identified, database backup validated, and a testing environment planned
- Testing responsibilities assigned, a production upgrade window considered, post-release testing prepared, and internal IT or partner availability confirmed
Timing should reflect the way your business actually operates. Avoid periods such as seasonal demand peaks, inventory counts, production launches, month-end close, annual audits, or major customer commitments whenever possible. September planning can help reserve the right people and testing time before year-end schedules and future roadmaps are fixed.
Decide What Should Be Tested First
Not every part of an Odoo environment carries the same level of business risk. Start with processes that directly affect customers, cash flow, production, inventory, or regulatory reporting. These areas should receive priority during upgrade testing because problems in these workflows can have an immediate operational impact.
For example, a manufacturer may prioritize production orders, inventory movements, purchasing, quality checks, and delivery operations. A distributor may focus on sales orders, stock availability, purchasing, shipping, invoicing, and payment processing. Service businesses may give greater priority to quotations, project delivery, timesheets, invoicing, and customer communication.
Prioritizing tests this way allows teams to use their available testing time where potential disruption would matter most.
Revisit Your Plan When Odoo 20 Is Confirmed
Preparation gives you a clear view of your current environment, operational dependencies, and available resources, so you can decide with confidence once the official release information is available.
Once Odoo confirms Odoo 20 and its final feature set, compare the official documentation with your inventory of custom modules, apps, integrations, data, and workflows. At that point, separate the upgrade work into three practical categories: changes required for compatibility, improvements that would be useful but are not essential, and customizations that may no longer be needed. This helps prevent the upgrade from becoming an unnecessarily large project and keeps the focus on business continuity. Your readiness findings can then shape a realistic plan for scope, testing, timing, risk controls, and support. A well-prepared upgrade is one that fits your operational calendar and protects the business processes your team relies on every day.
Protect Operations Through Every Upgrade Stage
Kodershop helps organizations align technical decisions with the priorities that keep operations moving. Our team can assess the risks, dependencies, and opportunities involved in your Odoo 20 upgrade so stakeholders can move forward with greater confidence. To discuss your business requirements and support options, contact us today.