Odoo 20 Custom Modules Upgrade: What Breaks and What It Costs to Fix
How to migrate custom modules to Odoo 20: the Python, XML, ir.access and Owl 3 changes that break code, a testing checklist, and what fixes cost.
Odoo 20 shipped in September 2026, and for most businesses the real question is whether the custom modules your operations depend on survive the jump. That is where most of the work in our Odoo upgrade services goes.
Related service: Odoo 20 release notes — every app's changes, explained app by app.
This is the Odoo 20 checklist for developers, IT leads and owners: Python, XML and Owl changes plus testing. For the general porting method on any version, read our guide to upgrading Odoo custom modules.
What breaks when you upgrade custom modules to Odoo 20?

Custom modules break in an Odoo 20 upgrade when they rely on framework behavior that Odoo changed or removed. Odoo's ORM changelog for Odoo 20 lists each change; these hit custom code most.
| What changed (release) | What it breaks in your code | Effort to fix |
|---|---|---|
| ir.access merges access rights and record rules (19.4) | Security CSV files and record rule XML | Medium |
| Model._table_query removed (20.0) | SQL-view reports and dashboards | High |
| request removed from model code, env.website added (19.4) | eCommerce, website and portal models | Medium |
| Binary fields use BinaryValue, raw data, not base64 (19.2, 19.3) | Code that encodes files by hand | Medium |
| Owl 3 in the web client (20.0) | Custom widgets, fields and views in JavaScript | Medium to high |
| Reporting engines made modular (19.4) | Custom PDF setups and heavy QWeb reports | Medium to high |
| New ir.config_parameter API (19.1) | Modules that read or write system settings | Low |
| "(copy)" added to duplicated name fields (20.0) | Duplicate logic that expects the old name | Low |
Also watch x2many fields: they now return only records the user can access (19.3), which can change report totals.
If you are coming from Odoo 17 or 18, add the earlier changes on top. Odoo 19.0 deprecated odoo.osv and the record._cr, record._context and record._uid shortcuts, and Online 18.2 deprecated read_group for backend use.
Why is an Odoo 19 to Odoo 20 upgrade bigger than it looks?
An Odoo 19 to Odoo 20 upgrade is bigger than it looks because Odoo.sh and self-hosted databases skip four Online releases and take all their changes at once. Odoo Online received 19.1 to 19.4 between majors; those versions never ship on Odoo.sh or on-premise.
| Where your Odoo runs | How Odoo 20 changes arrive | Custom code risk |
|---|---|---|
| Odoo Online | Gradually, through 19.1 to 19.4 | Low, mainly Studio edits |
| Odoo.sh on 19.0 | All at once in the jump to 20.0 | Medium to high |
| Self-hosted on 19.0 | All at once, plus new server requirements | Medium to high |
| Odoo 17 or 18, any hosting | Two or three majors plus every interim release | High |
Self-hosted teams also need new infrastructure. Odoo has raised the Odoo 20 install requirements to Python 3.12 (from 3.10) and PostgreSQL 16 (from 13). Plan the server upgrade before the code work.
How do you migrate a custom module to Odoo 20? The Python checklist
To migrate a custom module to Odoo 20, freeze development, fix it on an empty Odoo 20 database, then on an upgraded copy. Odoo's guide to upgrading a customized database starts with "Stop the developments and challenge them".
Work through the Python side of each module in this order:
- Retire first: list every module not authored by Odoo S.A. and drop what nobody uses or Odoo 20 now covers.
- Bump the manifest: set the version to 20.0.x, confirm every dependency still exists under the same name, and move security files to the new format.
- Run Odoo's code rewriter: odoo-bin upgrade_code with --dry-run lists the files Odoo's scripts would change. Odoo calls these scripts "a best-effort" and "not silver bullets", so review every diff.
- Replace _table_query models: rebuild SQL-view reports as regular models, computed fields with SQL, or standard pivot views.
- Remove request from models: pass values in from the controller, and use env.website for website context.
- Update binary handling: stop encoding and decoding base64 by hand, and read attachment data through the new BinaryValue object.
- Clear deprecations: swap self._cr, self._context and self._uid for self.env.cr, self.env.context and self.env.uid, and replace read_group calls.
- Write upgrade scripts: rename fields, models and XML IDs with migration scripts so data is not left behind.
The Odoo command-line reference documents upgrade_code and its --from, --to and --dry-run options.
Which XML, security and report changes break on Odoo 20?
Security files are the most common XML break on Odoo 20, because access rights and record rules now live in one ir.access model. In the Odoo 20 source, standard modules ship security/ir.access.csv, and the separate ir.rule model file is gone.
Odoo's Odoo 20 security reference describes the new record. Each line names a model, a group, an operation and an optional domain:
- Operation: a subset of "crud", for example "r" for read or "cd" for create and delete, instead of four permission columns.
- Domain: the old record rule domain now sits on the same line as the access right.
- Empty group: an access line with no group is a global restriction for every user, like an old global rule.
- Global rules intersect: Odoo warns that several global rules can remove all access, so test with an ordinary user.
Check views and reports too. Odoo lists "Xpath that moved or were removed from views" as a typical install error, and custom PDF reports need a fresh print test.
How do Owl 3 changes affect custom JavaScript in Odoo 20?
Odoo 20 runs the web client on Owl 3, so custom fields, widgets and views written for Owl 2 need code changes. Odoo loads an Owl 2 to Owl 3 compatibility layer, but it does not cover everything.
| Owl 2 pattern in Odoo 19 | What Odoo 20 standard code uses | Risk if left |
|---|---|---|
| static props and defaultProps | props = useProps(...) with t types | Component throws an error |
| useState and reactive | proxy, signal and computed | Import fails |
| useRef("name") | signal.ref() | Import fails |
| useExternalListener | useListener | Import fails |
| useEffect with dependency list | useEffect with automatic tracking, or useLayoutEffect | Effects run at the wrong time |
| t-portal and t-model | t-custom-portal, or t-model with signals | Template breaks |
In the Odoo 20 source, the compatibility layer rejects any component that defines static props or defaultProps with an error that asks you to use useProps. The bundled Owl 3 library no longer exports useState, useRef or useExternalListener.
The Owl team's draft migration guide also lists t-esc as removed. Open each custom screen with the browser console visible, because these failures appear at runtime.
How do you test a custom module before the Odoo 20 upgrade?
Test a custom module for Odoo 20 in four layers: a clean install, an update on real data, automated tests, then people running real flows. A module that installs cleanly can still compute the wrong amount or show a broken view.
- Empty database install: odoo-bin -d test_empty -i your_module --stop-after-init on Odoo 20, one module at a time, until there are no tracebacks or warnings.
- Update on a production copy: request an upgraded test database, then update your modules on it and read every ERROR, WARNING and deprecation line in the log.
- Python tests: run --test-enable with --test-tags /your_module, and tag tests post_install so they run after every module loads.
- JavaScript tests: move unit tests to Odoo's Hoot framework and keep a tour for each critical screen.
- Volume data: Odoo 20 adds a populate command that generates synthetic data from a blueprint, which helps you test reports at real volumes.
- User acceptance: key users run quote to cash, purchase to pay and month-end on the copy.
Odoo's Odoo 20 testing reference covers test tags, tours and Hoot. Test databases are neutralized, so scheduled actions and outgoing mail are off while you test.
Which custom modules break first in an Odoo 20 upgrade?
In-house and partner code breaks first, because Odoo's upgrade service does not cover it. Odoo's upgrade service terms exclude modules "created in-house or by third parties, including Odoo partners".
| Module type | Does Odoo's upgrade service move it? | Risk in Odoo 20 |
|---|---|---|
| Studio customizations | Yes, while Studio is installed and the subscription is active | Low, but test custom reports |
| In-house or partner modules | No, unless under a maintenance of customizations subscription | High |
| Paid App Store apps | No, you need the Odoo 20 build from the vendor | Depends on the vendor |
| Free community (OCA) modules | No, they wait for volunteer ports | Depends on timing |
Paid apps are often sold per version, so budget for the Odoo 20 build. Heavily customized systems should read our guide to the over-customized Odoo upgrade before scoping.
Will your integrations still work after the Odoo 20 upgrade?
Most integrations still work after an Odoo 20 upgrade, but file transfers and XML-RPC or JSON-RPC calls need checking. Odoo's external API documentation says the db service was removed in Odoo 20; common and object are scheduled for removal in Odoo 22 (fall 2028).
- File transfers: the RPC format for binary fields changed in Odoo 20, so connectors that upload or download attachments need testing.
- eCommerce, shipping and payment connectors: test them end to end, because they touch files, web requests and controllers at once.
- API move: start moving integrations to the JSON-2 API now; our JSON-2 API migration guide shows how.
How much does it cost to fix custom modules for Odoo 20?
The cost to fix custom modules for Odoo 20 depends on how many modules you have, how well they are written and how far behind you are, not on Odoo 20 itself. A few clean modules take days; undocumented code from several partners takes weeks.
| What drives the cost | Lower cost | Higher cost |
|---|---|---|
| Number of custom modules | A handful | Dozens |
| Code quality | Documented, with tests | Undocumented, written by several partners |
| Breaking changes hit | Settings, copy names, controllers | Security files, _table_query reports, Owl widgets |
| Starting version | Odoo 19.0 | Odoo 17 or older |
| Integrations | Few, using JSON-2 | Many, using file transfers and old RPC |
| Data quality | Clean | Needs cleanup before the upgrade |
As a ballpark from our Odoo upgrade cost guide, an Odoo 19 to 20 upgrade typically runs $1,500 to $3,000, 18 to 20 runs $3,000 to $6,000, and 17 to 20 runs $3,500 to $10,000. These are industry estimates; your modules decide where you land.
For a number on your system, try our free Odoo migration cost calculator. The biggest saving is retiring modules before anyone ports them.
Which industries feel Odoo 20 custom module changes most?
Businesses with custom website code, SQL reports or shop floor screens feel the Odoo 20 changes most.
| Industry | Pain or cost driver | Odoo approach | How iVentureTeam helps |
|---|---|---|---|
| Retail and eCommerce | Website models that read request directly | env.website and controller-side logic | Refactor portal and checkout code |
| Manufacturing | Custom shop floor widgets and costing reports | Owl 3 components, standard pivots | Port widgets, rebuild reports |
| Wholesale and distribution | Connectors that move labels and files | BinaryValue and JSON-2 API | Retest every file flow |
| Multi-company groups | Company record rules in old files | ir.access global and group lines | Rewrite and test access by user |
| Professional services | Portal access and timesheet reports | ir.access domains, x2many access checks | Verify portal views and totals |
Can you upgrade to Odoo 20 now, or should you wait?
Prepare your custom modules now, whatever your timing. Odoo's documentation says a customized database "cannot be upgraded until a version of your custom modules is available for the target version."
When we last checked Odoo's upgrade platform on 30 October 2026, 20.0 was not yet a target for existing databases. Recheck before you set a date.
- On Odoo 17 or older: start the audit and port now; moving to a supported version also clears the yearly 25% legacy surcharge.
- On Odoo 18 or 19: port modules now and upgrade once 20.0 opens.
- On Odoo Online: wait for Odoo's invitation, then test the upgraded copy before the due date.
Our post on upgrading on release day covers when to let the first patches settle.
How iVentureTeam helps with Odoo 20 custom module upgrades

iVentureTeam moves custom modules to Odoo 20 by auditing every module first, then porting only what your business still needs. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.
- Module audit: every custom, Studio, App Store and community module checked against the Odoo 20 changes, with a port, replace or retire call for each.
- Python, XML and Owl port: security moved to ir.access, _table_query reports rebuilt, and widgets moved to Owl 3 patterns.
- Testing: clean installs, updates on a production copy, module tests, tours and user acceptance, with checks from our Odoo upgrade verification guide.
- Cutover and support: a rehearsed go-live on a copy first, then close support in the first weeks.
Custom module upgrade case study: DeenSqure
DeenSqure shows what happens when custom modules block an upgrade, and how a module-by-module triage fixes it. The D2C retailer had run Odoo 14 for five years with 23 custom modules from three previous partners, and half the code was undocumented.
Two earlier upgrade attempts had failed because the custom modules broke during version testing. We started with a 2-week diagnostic: 9 modules were ported, 8 were retired in favor of standard Odoo 19 features, and 6 were deferred.
In 11 weeks DeenSqure moved from Odoo 14 to Odoo 19, with stock accuracy at 99.7% and 14 hours a week of manual reconciliation removed. Read the DeenSqure Odoo 14 to 19 migration case study.
The bottom line on custom modules in an Odoo 20 upgrade
An Odoo 20 upgrade breaks custom modules that touch security files, SQL reports, request handling, binary fields and Owl components, and Odoo's upgrade service will not fix them for you. The cost depends on your modules, not on Odoo 20.
Freeze development, retire what you do not use, port the rest on an empty Odoo 20 database, then test in layers. That keeps the bill predictable.
Ready to move your custom modules to Odoo 20?

Find out which of your modules break and what the fix costs, before you commit to a date. Get an Odoo 20 custom module audit, call +91-90235-15208, or email business@iventureteam.com.
Frequently Asked Questions
Can I upgrade to Odoo 20 right now?
+
Not an existing database yet. As of October 2026, Odoo's upgrade platform offers 19.0 as the newest target, and Odoo Online moves only on Odoo's invitation. You can start a new Odoo 20 database and port your custom modules now.
Will my custom modules work on Odoo 20?
+
Not without changes if they touch binary fields, _table_query reports, request in models, access rules or custom reports. Simple modules may need only small fixes, but every module should be tested on a copy first.
Does Odoo's upgrade service fix custom modules?
+
No. Odoo's upgrade service covers standard apps, Studio customizations and code under a maintenance of customizations subscription. Modules built in-house or by partners outside that contract are yours to migrate.
Do Odoo Studio customizations survive the Odoo 20 upgrade?
+
Odoo's upgrade service covers Studio customizations as long as Studio is still installed and your subscription is active. Still test custom reports and automations, because they sit closest to the changed engines.
How long does an Odoo 20 custom module upgrade take?
+
It depends on your modules. A few clean modules can take days, while dozens of undocumented ones take weeks. DeenSqure's 23-module triage and upgrade took 11 weeks, including a 2-week diagnostic.
Can AI tools migrate Odoo modules to Odoo 20?
+
AI tools can speed up routine code changes, but they do not know your business rules. Treat AI output as a first draft, and keep human review and real business-flow testing before go-live.
Can I upgrade from Odoo 17 or 18 straight to Odoo 20?
+
Yes, once Odoo opens 20.0 on its upgrade platform. The service can jump several versions, but your custom modules must absorb every change in between, including the Odoo 19 deprecations. Bigger jumps mean more code to fix.
When was Odoo 20 released?
+
Odoo 20 was released in September 2026, with standard support planned until September 2029. It is now one of the three covered versions, alongside Odoo 18 and 19.
Free Odoo upgrade plan
Worried about custom modules in your upgrade?
Tell us your version, edition and custom modules. We check what breaks, what it costs to fix and the safest path, before any work begins.
Free, with no obligation. A senior consultant replies within 12 business hours.
Free Odoo tools
All tools- Odoo Health CheckVersion, modules, findings and upgrade cost
- Odoo App SelectorWhich apps you need, by industry
- Odoo Project EstimateIndicative cost and timeline in minutes
- Odoo Implementation Cost CalculatorImplementation cost and timeline, in minutes
- Odoo Migration Cost CalculatorVersion jump or legacy ERP, priced in minutes
Continue reading
Odoo for Packaging Manufacturing: Costing by Product Line in Odoo 20
Odoo for packaging manufacturing: cost corrugated boxes, cartons, cups and bags by product line with BoMs, work centers, analytic plans and Odoo 20 tools.
Odoo 20 eCommerce: New Conversion and AI Features, Plus Upgrade Tests
Odoo 20 eCommerce explained: new conversion and AI features, payment provider changes, what breaks and a pre-upgrade test plan for orders and connectors.
Odoo 19 POS Review: QR Menu, Offline Mode, Hardware and Odoo 20
Odoo 19 POS reviewed: QR menu and kiosk ordering, offline limits, printers, IoT Box and payment terminals, plus what Odoo 20 changes and when to upgrade.
