
Summarize with AI
Odoo 20 upgrade checklist for custom modules, Owl 3 code, and integrations
Key takeaways:
- Odoo’s upgrade platform converts standard apps and data, but custom modules need their own migration work.
- Odoo 20 ships Owl 3, which replaces Owl 2 patterns such as useState and static props with signals and a props() function.
- Security rules, accounting structures, and tracking values all changed in Odoo 20, so many custom modules need more than a version bump.
- XML-RPC and JSON-RPC are on a removal path, so integrations should move to the JSON-2 API during the upgrade.
- Clean data and a fully tested copy of the database are the two best guards against a failed go-live.
An Odoo 20 upgrade checklist gives IT teams and business owners one shared view of what must change before the live system moves to the new version.
Odoo 20 came out in September 2026, and it changes more under the hood than most recent versions. The frontend framework moves to Owl 3, access rules work differently, and parts of the accounting model are new.
This guide works as an Odoo 20 migration checklist, covering the checks that matter for custom modules, Owl 3 code, integrations, and data in the order most projects run them.
What changed in Odoo 20 that affects upgrades
Most Odoo ERP upgrade problems come from a short list of core changes. The table below maps each one to what it means for custom code.
Teams can use it as a first scope sheet before any code is touched.
| Area | What changed in Odoo 20 | What to check in custom modules |
|---|---|---|
| Frontend | Owl 3 replaces Owl 2, with a partial compatibility layer | Custom widgets, views, dashboards, and POS screens |
| Security | Record rules are replaced by a domain on each access right | Every module that ships ir.rule records |
| Accounting | Parent accounts replace account groups, and depreciation models replace asset models | Custom reports and code that read account groups or assets |
| Chatter | Stored tracking values are removed and built on the fly | Code or reports that read tracking value records |
| External API | The XML-RPC db service is removed, and other RPC services are deprecated | Integrations that call /xmlrpc or /jsonrpc |
| AI features | All AI features now run on IAP credits | Budgets and any custom AI automations |
| Notifications | Push notifications run on Odoo's own tools instead of Firebase | Custom mobile or push logic |
In short, a module that installs cleanly can still fail in daily use. That is why each area needs its own test, not just an install log.
Odoo 20 upgrade checklist: readiness checks
Odoo upgrade preparation starts before any test upgrade. These checks show a database’s Odoo upgrade readiness, and they decide the scope, the timeline, and who owns each task.
- Support status: Odoo supports the latest three major versions. As a result, Odoo 17 left standard support when Odoo 20 arrived, which means no more bug and security fixes from Odoo for that version. Teams still on Odoo 17 should treat this upgrade as urgent rather than optional.
- Hosting path: Odoo Online, Odoo.sh, and on-premise databases each follow a different Odoo upgrade process. Odoo Online and Odoo.sh run the upgrade through Odoo’s own tools, while on-premise teams submit a database copy to the upgrade platform and install it on their own servers. The Odoo upgrade documentation explains each route.
- Technical requirements: On-premise servers should meet the Odoo 20 technical requirements, including the listed Python and PostgreSQL versions, before the test run. An outdated server stack can cause failures that look like code problems, which wastes debugging time.
- Module inventory: List every installed module and tag it as standard, custom, or third-party. Then note what each one does, which department relies on it, and who owns it, because this list becomes the scope of the whole project.
- Third-party apps: App Store modules are sold per Odoo version, so a module bought for Odoo 18 does not carry over automatically. Confirm that each vendor has an Odoo 20 release, and plan a replacement for any app that will not be updated.
- Change freeze: Pause new features on modules in scope while they are ported. Otherwise, developers end up chasing a moving target, and changes made in the old version are easily lost.
Odoo custom module compatibility checklist
Odoo’s upgrade service moves standard data, yet it cannot write an Odoo 20 version of a custom module. That work sits with the developer or partner. The gap is also costly to ignore. According to Deloitte’s 2026 research on technical debt, technical debt takes up 21% to 40% of IT spending, and every unported module adds to it.
- Security rules: Odoo 20 removes record rules and moves row-level filters into a domain on each access right. Any module that ships its own record rules must rewrite them in the new format, and every user group should then be retested, since a small mistake can hide records or expose them to the wrong people.
- Accounting code: Parent accounts now replace account groups, and depreciation models replace asset models. Custom financial reports, consolidation logic, or asset tools that read the old structures will break or return wrong totals until they are updated.
- Tracking logic: Odoo no longer stores tracking values for field changes in the chatter and builds them on the fly instead. Custom reports or audit tools that query those stored records need a new data source.
- Model changes: Fields get renamed, method signatures change, and small conventions shift, such as _rec_names_search moving from a list to a tuple. Each change is minor, but together they cause most install errors, so a line-by-line code review is worth the time.
- XML views: Inherited views attach to anchor fields in standard views. If Odoo renames or moves those fields, the custom view fails to load, so every inherited form, list, and search view needs a check.
- Upgrade scripts: When a custom module renames a field or moves data between models, migration scripts carry the existing data across. Pre-migration scripts run before the module updates and post-migration scripts run after, and Odoo’s upgrade-util library offers tested helpers for common tasks.
- Retire what is unused: Modules that nobody uses still cost porting and testing time. Uninstalling them before the upgrade shrinks the scope and removes code that would otherwise need upkeep for years.
Teams with many modules often plan this phase alongside Odoo module development, so rewritten modules follow current standards instead of old patterns.
Owl 3 changes for custom frontend code
Owl is Odoo’s JavaScript framework, and Odoo 20 moves it to version 3. The headline change is a new reactivity system built on signals, computed values, and effects. Odoo ships a compatibility layer, but it does not cover every pattern. The official Owl documentation is the reference for the new syntax.
| Owl 2 pattern | Owl 3 approach | What to check |
|---|---|---|
| useState and reactive | Signals, or proxy for simple cases | Every stateful component |
| this.props and static props | A props() function with a typed schema | Components that declare props or default props |
| useEffect with a dependency list | useEffect that tracks signals automatically | Effects that rely on dependency arrays |
| t-ref and t-model | Both now take signals | Forms and components that read DOM nodes |
| t-esc | t-out | Templates that still use t-esc |
| onWillUpdateProps | Removed, replaced by signal-based updates | Components that react to prop changes |
Because of this, Owl 3 porting is mostly hands-on work.
Scripts can handle repeated template changes. But stateful logic, custom field widgets, and POS screens need a developer to read and test each one.
Integration and API checks
Integrations often break quietly after an upgrade.
Odoo’s documentation states that the XML-RPC db service was removed in Odoo 20, while the remaining XML-RPC and JSON-RPC services are scheduled for removal in Odoo 22 in fall 2028. The JSON-2 API is the replacement.
- List every connection: Map each system that reads from or writes to Odoo, including payment gateways, shipping carriers, marketplaces, BI tools, and in-house scripts. Note which endpoint each one calls, since that decides how much work it needs.
- Plan the API move: Integrations that still use XML-RPC or JSON-RPC will work for now, but they are on a fixed removal path. Moving them to JSON-2 during this upgrade means one round of integration testing instead of two.
- Check plan limits: Odoo allows external API access only on the Custom plan. Teams on Standard should confirm their subscription before testing, or integrations will fail for licensing reasons rather than code.
- Review new AI options: Odoo 20 lets AI agents connect to the database over MCP and act on records. Some custom automations built in earlier versions may now be simpler to replace with Odoo 20 AI features than to port.
Data cleanup before the upgrade
Odoo data migration copies existing records into the new structure. It does not fix bad data. Cleaning it first also shortens the run and makes test results easier to check.
- Duplicate contacts: Duplicate customers and vendors split order history and payment records across two entries. Merging them before the upgrade, and filling in missing tax IDs, keeps invoices and reports accurate in the new version.
- Products: Archive products that are no longer sold, and fix wrong units of measure or categories. Clean product data reduces stock valuation errors, which are among the hardest problems to trace after an upgrade.
- Accounting: Reconcile open bank lines, post or delete draft entries, and record trial balance totals before the run. These totals become the baseline for checking that the upgraded books match the old ones.
- Inventory: Stuck transfers and negative stock often come from old workarounds. Resolving them first prevents errors during migration and makes stock comparisons after the upgrade far simpler.
- Custom fields: Many databases collect fields that were added once and never used. Remove those, and document which remaining fields must be kept, renamed, or mapped, so developers know exactly what to migrate.
- Attachments: A large filestore slows down both the test and the live upgrade, and it can stretch the maintenance window. Clearing old exports and duplicate files shortens the run.
Historical accounting records should never be deleted just to simplify an upgrade. Any corrections should follow the company’s accounting policy.
Odoo migration testing
A test upgrade on a copy of production is the only real proof that the plan works. Odoo neutralizes test databases, so emails and scheduled jobs do not reach real customers.
- Request a test upgrade: Upgrade a recent copy of production through the route for the hosting type. Record how long the run takes, because that number sets the length of the live maintenance window.
- Install ported modules: Install the Odoo 20 versions of all custom and third-party modules on the test database. Then review the logs for missing fields, broken views, and failed migration scripts, and fix errors before moving on.
- Run real workflows: Walk through complete processes, such as quote to invoice, purchase to receipt, stock transfers, payments, and manufacturing orders. Include returns, cancellations, and corrections too, since edge cases break more often than the main flow.
- Compare the numbers: Match the trial balance, stock valuation, open orders, and receivables against the totals recorded before the upgrade. Any gap should be explained before go-live, not accepted as normal.
- Test every role: Log in as a salesperson, accountant, warehouse user, and manager. The new access model can change what each role sees, and these issues rarely show up when testing as an administrator.
- Run user acceptance testing: Ask each department to complete its daily tasks in the test database and sign off. Business users often spot missing fields or changed steps that technical tests miss.
Repeat the test upgrade after major fixes, because a clean second run is a strong signal of readiness.
Go-live and rollback plan
The production upgrade should follow a written plan, not a deadline, and most Odoo ERP migration services treat this plan as a standard deliverable. Teams that prefer outside help often use Odoo migration services for this final stage.
- Maintenance window: Pick a quiet period, such as a weekend or month start after closing, and size it using the test upgrade time plus a buffer. Tell users in advance and pause integrations that would write data during the run.
- Final backup: Take a full backup of the database and filestore right before the upgrade, and confirm that it restores correctly. An untested backup is not a rollback plan.
- Go or no-go criteria: Agree in advance which problems stop the launch, such as accounting mismatches, failed payments, or broken stock moves. Clear criteria prevent a rushed decision late at night.
- Rollback rule: Restoring the backup brings back the old database, but any transactions entered after go-live must be re-entered by hand. For this reason, the rollback window should be short, usually the first hours after launch.
- Hypercare: Keep developers on call for the first one or two weeks. During this time, they watch logs, integrations, and scheduled jobs, and fix issues before they affect month-end or customer orders.
Plan the upgrade as a project
An Odoo 20 upgrade checklist turns a risky version change into clear tasks with owners and tests. The hardest parts are custom modules, Owl 3 code, and integrations, while clean data makes every step faster.
Following Odoo upgrade best practices, such as testing on a copy and cleaning data first, also makes this Odoo 20 migration guide reusable for future versions.
Experienced Odoo development services can scope this work early, so the business moves to Odoo 20 with its workflows and numbers intact.
FAQs
Similar Blogs


Odoo pricing explained: plans, costs, and hidden fees

Why Your Odoo Products Keep Getting Disapproved on Google Shopping (And How to Fix It)

Magento ERP Integration: Connecting to Odoo, NetSuite, and SAP





