Upgrading to Odoo 20 in the UAE: now, or later?

Odoo 20 was released on 24 September 2026. Since then, the question we keep hearing from clients in Dubai and across the UAE is simple: should we upgrade now, or wait? The honest answer depends on which version you run, how much custom code sits on top of it, and what else your finance team has on its calendar, starting with UAE e-invoicing. This guide covers who should move now, what changes technically, how we run a safe upgrade, and what really drives cost and timeline.

Who should upgrade to Odoo 20 now, and who should wait

• Starting a new implementation: start on Odoo 20. There is no reason to go live on an older version, but leave room in the plan for the fixes that always follow the first weeks of a major release.
• On Odoo 19: no rush. Upgrade when a specific Odoo 20 feature pays for itself, such as AI agents inside your automations, continuous production, or the new UAE payroll reports. Some UAE items, like the FTA VAT audit file and the WPS export alignment, are already available from 19.0.
• On Odoo 17 or 18: start planning now. Odoo has long supported only the three most recent major versions, so 17 is at the end of that window with 20 out. Check Odoo's supported-versions page for your exact dates.
• On Odoo 16 or older: you are already outside support. Treat this as a project, not an update, and plan it before something forces an emergency migration.
• Close to your e-invoicing go-live: wait. Don't run a major version upgrade and an e-invoicing integration in the same quarter. Get e-invoicing live and stable first.

What changes under the hood in Odoo 20

New features are the easy part. These changes, all from the official Odoo 20 release notes, are the ones that break custom modules, reports and integrations:

• Record rules are gone. Access rights are simplified, with a domain set directly on the access right. Custom security built on record rules has to be rebuilt and retested user by user.
• Chatter tracking is rebuilt. Tracking values are removed and tracking messages are generated on the fly. A dedicated module restores tracking values if you still need them. Reports that read tracking data directly need rework.
• Account groups become parent accounts, and account codes become optional. Financial report customisations and BI exports that group by account group need checking.
• Payment statuses are renamed. "In Process" becomes "Paid", and "Paid" becomes "Reconciled". Any dashboard, automation or integration that filters on payment status must be updated, or it will quietly report the wrong numbers.
• Apps merged or retired: Field Service is discontinued and merged into Planning, work entries are removed from Payroll, asset models are replaced by depreciation models, and Font Awesome icons give way to Material Symbols.
• AI now needs IAP credits. All AI features, including the new agents that can create and update records, consume paid credits bought through Odoo's In-App Purchase service. Plan that running cost before you switch AI on.

For the full feature rundown, including AI agents, MCP, offline mode and the accounting, inventory and payroll changes, read Muhammad Salman Ali Khan's guide to Odoo 20 new features.

What Odoo 20 changes for UAE businesses

• A new chart of accounts redesigned to comply with IFRS and UAE Commercial Companies Law, with 6-digit numbering, reverse-liquidity sequencing, statutory equity reserves and parent account groups. Existing databases need a deliberate decision on whether and how to map to it.
• FTA VAT audit file generated from the general ledger (available from 19.0).
• Payroll reports: a new Emiratization Compliance report in line with MoHRE regulations, an End-of-Service Benefit report that computes EOSB liability at any date, revised GPSSA and ADPF contributions, adapted DIFC DEWS treatment, and a WPS export better aligned with MoHRE (available from 19.0).
• E-invoicing is not native yet. The UAE section of the Odoo 20 release notes has no PINT AE e-invoicing feature. Under Ministerial Decision No. 244 of 2025, businesses with revenue of AED 50 million or more must appoint an Accredited Service Provider by 30 October 2026 and go live by 1 January 2027. Everyone else appoints by 31 March 2027 and goes live by 1 July 2027.

In practice, upgrading to Odoo 20 does not solve e-invoicing for you. Our UAE e-invoicing guide explains the mandate, and our UAE e-invoicing service connects your Odoo to the Accredited Service Provider you appoint, on Odoo 19 or 20.

How we run an Odoo 20 upgrade

Our upgrade process is boring by design. Boring is what you want when the system runs your invoicing, stock and payroll.

• 1. Assessment. We review your current version, editions, apps in use, integrations and data volume, and check your calendar for VAT returns, payroll runs and e-invoicing milestones, so the upgrade lands in a quiet window.
• 2. Custom module audit. Every custom and third-party module is classified: keep and port, replace with a standard Odoo 20 feature, or retire. Anything touching record rules, tracking values, account groups or payment statuses is flagged first. Deleting code is the cheapest migration. Porting is handled by our custom development team.
• 3. Test migration on a copy. We upgrade a copy of your production database, never production itself, and run your real flows on it: quote to invoice, purchase to payment, payroll, VAT reporting.
• 4. User acceptance testing (UAT). Your key users test their own daily work on the upgraded copy and sign off. Renamed statuses and moved buttons are covered in short, role-based training sessions.
• 5. Cutover. A planned freeze, a final migration of live data, reconciliation checks against the old system, and go-live, scheduled away from month-end close.
• 6. Hypercare. Close support in the weeks after go-live, when real-world edge cases surface. After that, our support and AMC takes over.

What drives the cost and timeline of an Odoo 20 upgrade

We will not quote a number before we see your database, and you should be wary of anyone who does. These are the factors that move the budget and the date:

• Version gap: moving from 19 to 20 is a very different project from moving from 15 or 16.
• Custom modules: how many there are, how well they are written, and how many touch the areas Odoo 20 changed. This is usually the biggest single driver.
• Third-party apps: whether each vendor has released an Odoo 20 version, or whether it has to be ported or replaced.
• Integrations: banks, e-commerce, logistics, BI and, soon, your e-invoicing ASP. Each one needs retesting against renamed fields and statuses.
• Data volume and history: larger databases take longer to migrate and reconcile, and old data quality issues surface during testing.
• Chart of accounts decision: staying on your current structure or moving to the new UAE chart of accounts.
• Companies and users: multi-company setups, branches and the number of user roles to test.
• Your team's availability for UAT. Testing, not the migration script, is where most of the time goes.

Comparing Odoo 17 with 19 first? Our Odoo 17 vs 19 upgrade guide covers that decision.

Plan your Odoo 20 upgrade with Knova

Our Odoo upgrade services in Dubai cover the whole path, from the first assessment to hypercare, for companies across the UAE and the GCC. Tell us your current version and your e-invoicing deadline, and we will tell you honestly whether Odoo 20 makes sense now or later. Contact us, book a discovery call below, or message us on WhatsApp.