This page will be updated after the opening keynote of Odoo Experience, on 24 September 2026 in Brussels, as soon as the content of Odoo 20 is officially presented. As of the publication date (22 September 2026), the version has not yet been unveiled: no precise feature can therefore be reliably announced. This page describes what is confirmed today and how a Swiss SME should approach the question, independently of the exact content of the new version.
What is officially confirmed to date
Four elements are established and verifiable:
- Odoo 20 is unveiled on 24 September 2026 during the opening keynote of Odoo Experience, in Brussels.
- Odoo 19 is, as of today, the current stable version used in production.
- Odoo has historically released one major version per calendar year, and general availability generally follows the unveiling conference by a few weeks.
- Odoo is listed on the Swissdec register at the "swissdec certified basic" level, certificate no. 1203.25, for ELM 5.3 (verified on 22.09.2026 on swissdec.ch).
Everything else — features, modules affected, the extent of interface changes — remains to be confirmed after the keynote. A company already planning its migration based on rumours would be making a decision on uncertain ground.
The usual timeline of an Odoo version
A new major Odoo version generally follows three distinct phases, worth keeping in mind so as not to confuse "unveiling" with "ready for production":
| Phase | What it concretely means |
|---|---|
| Unveiling (keynote) | Public presentation of the direction and, generally, the first new features. The code isn't necessarily final. |
| General availability | Release of the installable version, on Odoo Online, Odoo.sh and on-premise. Historically a few weeks after the keynote. |
| Stabilisation | Successive patches, third-party module updates, feedback from the first production deployments. Can extend over several months. |
It's this last phase that explains why a company already in production on Odoo generally has no interest in migrating in the days following a version release.
Should you migrate to Odoo 20? Decision criteria for a Swiss SME
The question isn't "is Odoo 20 better than Odoo 19?" — that answer will depend on features still unknown today — but "does the migration have a concrete benefit for my business, at this particular moment?". The real criteria are as follows:
- End of support for the current version. Odoo's support schedule sets a deadline beyond which security patches are no longer guaranteed. This is often the most concrete trigger, independent of the new version's content.
- A proven functional need. If a new Odoo 20 feature meets a real, documented business need, the migration is justified. A migration "because it's the latest version" isn't justified on its own.
- The level of customisation of the current instance. The more custom development and third-party modules an instance has, the greater the migration effort — and the wider the timeline needs to be.
- Load on the tax and social calendar. A version upgrade in the middle of an annual closing, during VAT return periods or at year-end payroll increases operational risk. Choosing the migration window matters as much as the decision to migrate.
For a company already supported on its accounting aspects via Odoo accounting, these criteria are documented as part of a prior audit, not in the rush of an announcement.
What a version upgrade concretely involves
Migrating to a new major Odoo version isn't a simple application update. Several elements must be systematically checked:
- Third-party modules. Modules from the Odoo App Store or custom-developed aren't always available for a version that has just been released. Their compatibility must be checked module by module.
- Customisations. Any custom development (views, workflows, reports, automations) must be tested on the new version, as the API and module structure can change from one major version to the next.
- Swiss localisation (l10n_ch). The Swiss localisation module covers the chart of accounts, the QR-bill, payment formats and local tax specifics. Its availability and validation for the new version are a prerequisite, not an option.
- Payroll and Swissdec. The payroll module and its Swissdec certification are tied to a specific version. A version change may require revalidation of the configuration before any real payroll processing.
- Testing. A migration is tested on a staging environment, never directly in production, with a representative dataset and a documented cutover scenario.
- Data migration. Historical data (accounting entries, invoices, VAT returns, payroll history) must be carried over without loss or duplication, which requires an item-by-item check after migration.
This work is described in more detail on the Odoo migration page, regardless of the version concerned.
The special case of Swiss companies
A Swiss company upgrading versions must recheck elements that don't exist in the international version of Odoo, or that are specific to Switzerland:
- Chart of accounts: compliance with the Swiss (SME) chart of accounts and consistency of mapping accounts after migration.
- VAT tax positions: accuracy of the rates applied — 8.1% (standard rate), 2.6% (reduced rate) and 3.8% (accommodation), in force since 01.01.2024 — and, for eligible companies, consistency with the net tax rate method thresholds: maximum turnover of CHF 5,024,000 and maximum tax due of CHF 108,000/year, in force since 01.01.2025. Details of these rules are available on our Swiss VAT page.
- QR-bill: correct generation of the QR code, references and layout under the applicable ISO standards.
- ISO 20022: format of payment files sent to Swiss banks, to be revalidated after any migration affecting the finance modules.
- Payroll configuration: scales, salary certificates, social insurance returns and Swissdec transmission, to be rechecked before any real payroll run on the new version.
These checks form part of broader support for payroll and HR under Odoo, whose Swiss configuration is a permanent prerequisite, regardless of versions.
What AX-Fiduciaire does in this context
As an official Odoo partner based in Geneva, our approach to a new major version always follows the same order: audit before decision, decision before planning, planning before execution.
- Instance audit: inventory of installed modules, customisations and integrations in place.
- Impact analysis: assessment of what the version upgrade would concretely change for the company's accounting, VAT and payroll.
- Planning: choice of a migration window compatible with the company's tax and social calendar.
- Testing: validation on a staging environment before any go-live in production.
- Support: follow-up after migration, with verification of the Swiss-specific points listed above.
This support draws on our full Odoo offering, with ongoing support available via our Odoo support page. Companies based in the Lake Geneva region can consult local arrangements on Odoo in Geneva.
No recommendation to migrate to Odoo 20 will be made before the content of the version is officially known and a reasonable stabilisation period has passed. This page will be updated accordingly after 24 September 2026.