In short: Porting a custom module from Odoo 19 to 20 starts with the server (Python 3.12 or later, PostgreSQL 16 or later). Then check the code: binary fields now use a new BinaryValue type, Model._table_query is removed, record rules are replaced by a domain on the access right, and stored mail tracking values are gone. Request an upgraded test database and port at the same time, because Odoo will not upgrade a database until every custom module exists for 20.0.
Odoo 20 was unveiled on 24 September 2026 at Odoo Experience in Brussels. This checklist is for developers who maintain custom modules and integrations. For a tour of the new features, read our Odoo 20 features guide.
Each item below names where it is confirmed: Odoo's own documentation, or at least two independent sources. It is a starting list, not a full porting manual, so read Odoo's changelog for your own code as well.
Start with the server, not the code
Odoo 20 raises the minimum Python and PostgreSQL versions, so a module cannot load on an older server. Odoo's installation documentation lists the change.
| Requirement | Odoo 19 minimum | Odoo 20 minimum |
|---|---|---|
| Python | 3.10 | 3.12 |
| PostgreSQL | 13 | 16 |
Odoo chose these minimums with Debian 13 and Ubuntu 24.04 in mind, whose Python version is 3.12. If your production server runs an older operating system, plan the server change together with the module port, and check that every third-party Python package you use supports 3.12.
The porting checklist
Every item shows what changed, what to check in your code, and where we confirmed it.
Framework and ORM
Binary fields · Source: Odoo changelog and one partner guide
Binary fields use a new BinaryValue type
What changed. The type of Binary fields is now BinaryValue, which has a filename. Odoo no longer base64-encodes values across the whole data flow, and the RPC format for binary fields changed.
Check. Any code that encodes or decodes base64 on a binary field, and every integration that uploads or reads files over RPC, such as EDI, e-invoicing, document scanners and online stores.
Reports · Source: Odoo changelog and one partner guide
Model._table_query is removed
What changed. Odoo removed Model._table_query in 20.0. Many custom reports built on database views relied on it.
Check. Search your modules for _table_query and plan a replacement for each report that uses it.
Website · Source: Odoo changelog and one partner guide
request is removed from model code
What changed. The changelog says request was removed from the code of models and env.website was added.
Check. Models and website modules that import request to find the current website.
Caching · Source: Odoo changelog
ormcache is thread-safe with automatic signaling
What changed. Odoo made ormcache thread-safe and automated its signaling.
Check. Custom caches and any manual cache invalidation or signaling code.
Write order · Source: Odoo changelog
Field updates and inverses run in a fixed order
What changed. In both create() and write(), field updates and inverse execution are now ordered by (field.write_sequence, field_index).
Check. Inverse methods and computed fields that only worked because of the old order.
Chatter · Source: Odoo release notes, via two partner guides
Stored mail tracking values are removed
What changed. Odoo's release notes say tracking values were removed and the tracking message is generated on the fly. Admins who still need the old values can install a dedicated module.
Check. Reports, exports and code that read stored tracking values.
Older deprecations · Source: Odoo changelog
Jumping from Odoo 16, 17 or 18? Check the deprecations on the way
What changed. The changelog lists name_get() as deprecated in 17.1, read_group as deprecated in 18.2 in favour of _read_group and formatted_read_group, and odoo.osv plus record._cr, record._context and record._uid as deprecated in 19.0. It also adds @api.private in the 19.1 online version.
Check. Whether your modules still call any of these. You can upgrade straight from an older version, so these changes arrive in one go.
Security
Access rights · Source: Odoo release notes and changelog, via two partner guides
Record rules are replaced by a domain on the access right
What changed. Odoo's release notes say access rights were simplified by removing record rules and adding a domain directly at the access right level. The changelog adds a domain operator named access that checks the permissions of the comodel, and lists ir.access, which merges ACLs and record rules, under the 19.4 online version.
Check. Every record rule your modules ship. Then sign in as a user from each group on the upgraded test database and confirm what they can see and edit.
Web layer and interface
HTTP · Source: Odoo changelog and one partner guide
A new HTTP server, and renamed JSON routes
What changed. Odoo 20 runs on a new HTTP server based on h11. The 19.4 changelog also says JSON controllers were renamed to jsonrpc. They are called the same, but the type declared in the Python files changed.
Check. Custom controllers, portals and website modules, and the type declared on your JSON routes.
Interface · Source: Odoo release notes, via two partner guides
Font Awesome is replaced by Material Symbols
What changed. Odoo's release notes say Font Awesome icons were replaced by Material Symbols icons.
Check. Custom views, buttons and website snippets that use Font Awesome classes.
Mobile · Source: Odoo release notes, via two partner guides
Push notifications no longer use Firebase
What changed. Push notifications run on Odoo's own push tools.
Check. Any integration that assumed Firebase.
Business apps
Accounting · Source: Odoo release notes, via two partner guides
Chart of accounts, assets, payments and bank entries
What changed. Parent accounts replace account groups and account codes become optional. Depreciation models replace asset models. Payment statuses are renamed, so "In Process" becomes "Paid" and "Paid" becomes "Reconciled". Every journal entry that touches a bank account must originate from a bank transaction. The Employee Expenses menu is removed and approved expenses create draft bills.
Check. Reports, imports and filters that use account groups, assume every account has a code, or use the old payment labels. Also check code that posts manual entries to a bank account.
Operations · Source: Odoo release notes, via two partner guides
Returns, manufacturing, project and Field Service
What changed. The return wizard is removed. Flexible consumption is now the default, and "Produce" and "Produce All" are merged into one button. The project profitability report is replaced by budget and margin reports. Field Service is discontinued and its features moved into Planning.
Check. Customisations of the return flow, code that presses or overrides the old manufacturing buttons, and anything built on the Field Service app.
How to port without blocking the upgrade
Odoo's documentation says a database with custom modules cannot be upgraded until a version of those modules exists for the target version. It recommends requesting the upgraded database while you upgrade the code. In practice:
- List your modules. Uninstall the ones you no longer need on Odoo 19 first. Each one removed is one less to port and test.
- Ask vendors for Odoo 20 builds of every third-party module, and get a date before you book the upgrade.
- Request an upgraded test database. On Odoo.sh, every commit you push to the staging branch restores the upgraded backup and updates all custom modules, so you test against clean upgraded data.
- Port the modules in parallel using the checklist above.
- Run the test pass below, then request the production upgrade.
Test pass for the upgraded database
- Security. Sign in as a user from each group and compare what they see with Odoo 19.
- Files. Upload and download attachments through every integration that handles binary fields.
- Reports and printouts. Run each custom report. Odoo also redesigned product, manufacturing and packaging labels in 20.0, so print them.
- Scheduled work. Odoo neutralises test databases, which disables scheduled actions and replaces outgoing mail servers. Run scheduled flows by hand.
- Accounting. Post an invoice and a bill, register a payment and reconcile it, then compare balances with the Odoo 19 database.
- Integrations. Payment providers, shipping connectors, marketplaces and anything that calls the API. See our Odoo integration services if one needs rework.
Which version to port from
Odoo's support documentation says you can upgrade from any version that is still supported, or whose standard support ended less than six months ago. Odoo 17's standard support is listed as ending in September 2026, so that window is open now. Odoo 18 and 19 are listed as supported until September 2027 and September 2028. If your upgrade also changes your licence count, read our guide to Odoo 20 Light User pricing before you set a date.
Need the modules ported for you? TheERPBot upgrades Odoo databases, custom modules and integrations. See our Odoo upgrade services or contact us with your current version and a list of custom modules.
Frequently asked questions
Can I port straight from Odoo 16, 17 or 18 to Odoo 20?
Yes. Odoo's documentation says you can upgrade from any supported version, or one whose standard support ended less than six months ago, to a supported major version. A bigger gap means more changes to your custom code, so also read the deprecations listed in the checklist.
Which Python and PostgreSQL versions does Odoo 20 need?
Odoo's installation documentation lists Python 3.12 or later and PostgreSQL 16 or later. The minimums were Python 3.10 and PostgreSQL 13 for Odoo 19.
Do my record rules still work in Odoo 20?
Odoo's release notes say record rules were removed and a domain was added at the access right level. Treat every record rule your modules ship as something to review, and test each user group on the upgraded copy of your database.
Why might my file upload integration break?
Binary fields now use a BinaryValue object, and the RPC format for binary fields changed. Integrations that send or read files as base64 need testing against Odoo 20.
Can Odoo upgrade my database if a custom module is not ready?
No. Odoo's documentation says a database with custom modules cannot be upgraded until a version of those modules is available for the target version.
Sources
- Odoo 20.0 ORM changelog: odoo.com/documentation/20.0/developer/reference/backend/orm/changelog.html
- Odoo standard and extended support: odoo.com/documentation/master/administration/standard_extended_support.html
- Odoo documentation change for the Python and PostgreSQL minimums: github.com/odoo/documentation/pull/14771