How to Migrate Odoo 19 to Odoo 20: Complete Guide (Community & Enterprise)

Introduction: Why Migrate from Odoo 19 to Odoo 20?

Odoo 20 is set to launch at Odoo Experience 2026, taking place September 24 to 26, 2026 in Brussels. This release brings significant changes: Agentic AI that acts autonomously across modules, a simplified payroll system, a redesigned mobile app, and major technical changes including a move to Owl 3 and a new JSON-2 API.

If you are running Odoo 19, this is your window to plan. Odoo supports only the three most recent major versions with security updates. When Odoo 20 releases, Odoo 18 will still be supported, but Odoo 19 will move closer to the end of its support window.

But here is the crucial thing most guides do not tell you: the migration path is completely different for Community and Enterprise editions. Enterprise users get a free automated upgrade through Odoo's platform. Community users must use the open-source OpenUpgrade project — and the process is more involved.

In this guide, we will walk through the entire migration process for both editions, covering database migration, custom module migration, and the critical technical changes in Odoo 20 that will affect your integrations and frontend code.

Community vs Enterprise: Understanding Your Migration Path

Before you do anything, you need to know which path applies to you. The difference is not just about features — it is about who handles the technical migration.

Important: Enterprise databases are much easier to upgrade because Odoo handles the process. Community requires technical expertise. If you are on Community and considering upgrading to Enterprise, now is the ideal time — the migration effort can be combined.

Phase 1: Pre-Migration Assessment (Both Editions)

Never start a migration without understanding what you are migrating. The assessment phase is where migration projects succeed or fail.

Step 1: Audit Your Custom Modules

Open a spreadsheet and list every custom module in your instance. For each module, note:

• Module name and location (which addons folder)
• Who built it (in-house, freelancer, third-party vendor)
• Is it still used? (many custom modules are abandoned but never removed)
• Does Odoo 20 offer it natively? (if yes, retire the custom module)
• Dependencies (which other modules does it rely on?)

Sort your list into three buckets: Standard Odoo (handled automatically), Third-party apps (waiting on vendor), and Your custom code (your responsibility).

Step 2: Identify Integrations That Will Break

Two things will definitely break in the Odoo 20 migration: XML-RPC integrationsand custom frontend code.

XML-RPC is Going Away

For years, external systems communicated with Odoo using XML-RPC. Odoo has deprecated these endpoints, and they are scheduled for full removal in Odoo 22 (fall 2028). The replacement is the JSON-2 API.

The JSON-2 API is cleaner but not a drop-in replacement. It requires:

• API keys with limited lifetime instead of passwords
• Named parameters instead of positional
• A database header in requests
• Proper HTTP error handling

Every integration using XML-RPC must be rewritten. List them all now.

Owl 3 Frontend Changes

Odoo's web framework, Owl, moves to version 3 in Odoo 20. Any custom module with its own frontend components (customer portals, custom dashboards, bespoke UIs) must be ported manually. This is developer work, not an automatic conversion.

Step 3: Check Third-Party App Readiness

For every paid or third-party app you use, check whether the developer has committed to an Odoo 20 release. Their timeline is theirs, not Odoo's. A single critical app that is not ready can hold up your entire migration.

Step 4: Prepare Your Database

Before any migration, clean your data. Migration is a rare opportunity to improve data quality:

• Archive inactive products and contacts
• Remove duplicate records
• Clean up unused fields and tables
• Verify data integrity

Phase 2: Migrating Custom Modules

This is the real work. Whether you are on Community or Enterprise, custom modules require attention. Enterprise users get help from Odoo's upgrade team, but the code must still be adapted.

Step 1: Refactor for Upgrade Safety

Before porting, review each custom module for upgrade-unsafe patterns:

Step 2: Update the Module Manifest

In the __manifest__.py file, update the version number to match Odoo 20 conventions and verify all dependencies are correct.

Step 3: Write Migration Scripts (If Needed)

If your custom module changed its data structure, you need a migration script. Odoo supports upgrade scripts invoked during module updates.

Place these in a migrations/ folder inside your module. The script'smigrate() function runs during upgrade.

Step 4: Test Extensively

Build automated tests for critical workflows. Test both the module installation and the upgrade process with realistic data.

Phase 3: Database Migration — Enterprise Edition

Enterprise users have the easiest path. Odoo provides an automated upgrade platform at upgrade.odoo.com.

Step 1: Download a Database Backup

From your Odoo instance, download a backup dump of your database. Do not include the filestore for the initial upload.

Step 2: Upload to the Upgrade Platform

Go to upgrade.odoo.com and upload your backup file. Odoo will run the automated upgrade process.

Step 3: Create a Staging Environment

Once the upgrade completes, you will receive a link to the upgraded database. Create a new staging environment in Odoo.sh (or your hosting platform) and import the upgraded database there.

Step 4: Test Everything

Run through all your business processes in the staging environment. Check:

• Custom modules install and function
• Integrations work with the new API
• Reports and dashboards display correctly
• User permissions and security groups
• Scheduled actions and automated workflows

Step 5: Report Discrepancies

If you find issues, report them via Odoo's helpdesk. The upgrade team will manually adapt your scripts. This process can take several weeks, so report early.

Step 6: Go Live

Once testing passes, upgrade your production database by downloading the final upgraded version and importing it into your live environment.

Timeline: Enterprise upgrades typically take 2 to 4 monthsdepending on queue position. The sooner you submit, the faster it goes.

Phase 3: Database Migration — Community Edition

Community users must use OpenUpgrade, the open-source migration framework from the Odoo Community Association (OCA).

Step 1: Install OpenUpgrade

The OpenUpgrade project provides migration scripts for each version. You need:

• openupgrade_framework module
• openupgrade_scripts module
• openupgradelib Python library

Install openupgradelib from GitHub:

Step 2: Make a Copy of Your Database

Never run migrations on your live database. Create a full backup and work on a copy.

Step 3: Prepare Addons Folder

Organize your addons directory with versions:

Your custom modules for Odoo 20 should be in the 20.0/ folder.

Step 4: Configure Odoo for Migration

Run Odoo with the OpenUpgrade framework loaded. The recommended command includes:

Step 5: Run the Upgrade

Run the migration using the OpenUpgrade Docker image or directly with odoo-bin. The process will:

• Run migration scripts for standard modules
• Attempt to migrate custom modules
• Log any errors or missing migration scripts

Step 6: Fix Errors and Repeat

Expect errors. OpenUpgrade will tell you which modules lack migration scripts. You may need to write these yourself. The process is iterative: run, fix, repeat.

Step 7: Test Thoroughly

Once the migration completes without errors, test every business process. OpenUpgrade handles data migration, but edge cases and custom logic need manual verification.

Step 8: Deploy to Production

After successful testing, repeat the process on your production database during a maintenance window.

Migrating from Community to Enterprise During the Upgrade

If you are on Community and want to move to Enterprise, Odoo 20 is an ideal time. The process combines the version upgrade with an edition change.

Step 1: Back Up Your Community Database

Download a full backup of your Community instance, including the filestore.

Step 2: Install Enterprise Components

On a fresh Odoo 20 Enterprise installation, restore your Community database. Install the web_enterprise module and enter your Enterprise subscription code.

Step 3: Audit Custom Modules

Many Community custom modules exist because the feature was missing. Enterprise may now offer it natively. Retire these modules to reduce technical debt.

Step 4: Test in Staging

Test the combined migration on a staging copy. Verify that Enterprise modules install correctly alongside your remaining custom modules.

Step 5: Go Live

Once validated, deploy to production. Your database is now on Odoo 20 Enterprise.

Critical Technical Changes in Odoo 20

Beyond the migration process itself, Odoo 20 introduces technical changes that affect custom code.

Pre-Migration Checklist

Before you begin, complete every item on this list.

Data Preparation

• Full database backup (SQL dump + filestore)
• Data cleanup (archive inactive records, remove duplicates)
• Verify database integrity

Module Preparation

• Complete module inventory
• Refactor custom modules for upgrade safety
• Update module manifests
• Write migration scripts where needed
• Prepare Odoo 20 compatible addons folder

Integration Preparation

• List all XML-RPC integrations
• Plan JSON-2 API rewrites
• Identify Owl frontend components
• Check third-party app Odoo 20 readiness

Environment Preparation

• Set up staging environment
• Ensure correct Python and PostgreSQL versions
• Configure backups for the migration process
• Plan maintenance window

Common Migration Mistakes to Avoid

• Migrating on production directly: Always test on a staging copy first.
• Skipping the audit: You cannot migrate what you do not know exists.
• Forgetting integrations: XML-RPC and Owl changes break more than you expect.
• Migrating every custom module: Some are obsolete; retire them instead.
• Not testing with real users: Technical tests do not catch workflow issues.
• Starting too late: Enterprise upgrade queues fill up after Odoo Experience.
• Skipping data cleanup: Migration is your chance to fix data quality.
• No rollback plan: Always have a way to revert if things go wrong.