Odoo Updates · Odoo 19

Odoo 19 vs Odoo 18: what changed and should you upgrade?

What to check in accounting, manufacturing and eCommerce, what the upgrade path looks like in practice, and how to think about timing now that Odoo 20 has shipped.

By Octagotech Team7 min readUpdated

Key takeaways

  • Test bank reconciliation, tax setup and MRP planning first on a staging copy; they are where an accounting or shop floor team feels an upgrade.
  • Custom modules, not the standard apps, usually decide how long the upgrade takes.
  • From 16 or 17, a direct upgrade to 19 is normally workable through Odoo's upgrade service, with a test run first.
  • Upgrade to 19 now and plan Odoo 20 for 2027, unless a version 20 feature is critical to you.

Update, September 2026: Odoo 20 was released in September 2026. The advice below still holds: land on 19 first, and plan the move to 20 once the first rounds of fixes are in (see what shipped in Odoo 20). Still on 17? Read what the end of its standard support means.

Odoo 19 shipped in 2025, and many databases running Odoo 18 now face the same question: is it worth migrating, and when? The answer depends on which modules you actually use and how much customization you have built up. This article covers where an upgrade to 19 touches accounting, manufacturing and eCommerce, what the upgrade path looks like in practice, and how to think about timing now that Odoo 20 has shipped.

Odoo's release notes for 19 list what changed. What follows is what we test first, because those are the areas where a team notices an upgrade.

Accounting: bank reconciliation and tax

The accounting area most likely to change how your team works day to day is bank reconciliation. Matching bank statement lines to invoices and bills is sensitive to how consistently vendor names, references and amounts appear in your feeds, so a change in the matching logic shows up quickly in daily closes.

The practical test is simple. On a staging copy of 19, run your reconciliation models and a month of real bank statements, then compare what auto-reconciles with what does on 18. Do the same for your tax setup: fiscal positions, rounding rules and any US multi-state configuration that was built through workarounds. For multi-state businesses, this is worth an explicit test script.

Reconciliation is the kind of area that does not make a headline features list but decides whether your accounting team loses an hour a day. Test it with your own data before you rely on any general claim.

Manufacturing: MRP planning and work orders

For manufacturing clients, the upgrade review centers on planning and the shop floor. Check whether planned orders still reflect what your work centers can absorb, how the work order and tablet views behave for operators, and whether time tracking and step-by-step instructions still sit where your operators expect them. Compare each against 18 on a staging copy before sign-off, and read Odoo's release notes for the changes that apply to your version.

Two other manufacturing areas are worth a test script:

  • Scrap and rework flows, and whether they still trigger the quality checks you rely on.
  • Lot and serial number traceability reports, which matter most for regulated industries like medical device manufacturing. Run a forward and a backward trace on a known lot and confirm the result.

Website builder and eCommerce

If you maintain a complex Odoo website, the website builder is where upgrades most often surprise teams: custom snippets and themes built on one version's structure can behave differently on the next, and the failure is usually "it looked fine in the editor but broke on mobile."

On eCommerce, test product variants, checkout and payment flows on staging, on a phone as well as a desktop. Variant images, shipping steps and payment providers are the pieces that most often need rework.

Key takeaway for eCommerce businesses: If you are running Odoo 18 eCommerce with significant product catalog complexity or mobile traffic, test variants and checkout early, on a phone as well as a desktop, and let the result decide the timing.

What the upgrade path actually looks like

Odoo provides an official migration script path from 18 to 19. For a clean, lightly customized Odoo 18 database, the technical migration takes 2–5 days of engineering work. For a database with substantial custom modules, plan for considerably longer, and most of that time is testing, not the migration itself.

A realistic sequence for a mid-size business:

  1. Phase 1: Audit. Inventory all custom modules, identify which have changed APIs in Odoo 19, and build a test plan covering your critical workflows.
  2. Phase 2: Staging migration. Run the migration on a copy of your production database, update custom module code, and execute the test plan.
  3. Phase 3: UAT. Key users validate the staging environment against their daily workflows. Do not skip this: edge cases surface here.
  4. Go-live: Cutover. Final migration on production, typically over a weekend. Plan for 4–8 hours of downtime.

The things most likely to extend that timeline are heavily modified accounting configurations (custom tax codes, multi-currency setups), custom reports built on the old QWeb engine, and any third-party integrations that talk directly to Odoo's database rather than through the API.

Who should upgrade now vs. wait

Upgrade now if: you are on a version that has left standard support, you are working around MRP planning limitations, your accounting team is spending significant time on manual reconciliation, or you are running eCommerce with noticeable mobile drop-off. Check Odoo's release notes for 19 against that list to see which of those pain points it addresses.

Wait if: you went live on Odoo 18 in the last six months, you have a high volume of custom modules that have not been tested against Odoo 19, or your business is in a seasonal peak period. A botched migration during peak season costs more than a smooth one after it.

There is also a third camp: businesses that should be planning now even if they do not execute immediately. If you are on Odoo 16 or 17, the move to 19 crosses more than one release. For an Enterprise database, a direct upgrade to 19 is normally workable through Odoo's upgrade service, with a test upgrade first; your custom modules are rewritten once, for 19. Community databases move one version at a time with OpenUpgrade. Starting that planning conversation now is worth it.

The Odoo 20 question

Odoo 20 shipped in September 2026. Should you skip 19 and go straight to 20? In most cases, no.

Odoo releases annually, and each version has a three-year standard support window. Odoo 20 is brand new, with all the first-adopter risk that comes with that, and the ecosystem takes time to catch up: marketplace apps need a release for 20, and the OCA's OpenUpgrade project only opened its 20.0 branch on September 28, 2026.

Migrating to Odoo 19 puts you on a stable, well-supported version with a clear path to 20 when you are ready. The businesses that tend to fall furthest behind on Odoo versions are the ones that perpetually wait for the next release.

On Odoo 20 timing: Unless a feature in version 20 is specifically critical to your operations, upgrade to 19 now and plan the move to 20 for 2027, once the version has matured and community support is broader.

Common upgrade mistakes we see

Across upgrade projects, these are the failure modes that come up repeatedly:

  • Migrating without a test plan. Running the technical migration is the easy part. Not having written test cases for your critical workflows (order-to-cash, purchase-to-pay, production scheduling) means you discover problems in production rather than staging.
  • Underestimating custom module updates. Odoo changes internal APIs between versions. A custom module that worked perfectly in 18 may fail silently in 19 rather than throwing an error: data writes that do nothing, computed fields that return stale values. Audit every custom module before migration, not during.
  • Keeping old data hygiene problems. A migration is a good time to clean up duplicate partners, stale product categories, and orphaned records. Carrying dirty data into a new version makes the migration harder and the new install messier.
  • Cutting over without a rollback plan. Things go wrong. Know exactly what your rollback procedure is before you start the production cutover: which backup you will restore, who makes the call, and how you communicate to users.
  • Not briefing end users. Version changes to the interface are not dramatic, but they are real, particularly in manufacturing and accounting. Users who expect the Odoo 18 interface will be confused by small but impactful changes. A 30-minute walkthrough before go-live saves hours of support tickets after it.

Odoo 19 is a solid release. Whether the upgrade is worth doing now depends on your current pain points, your customization footprint, and your capacity to absorb a migration project.

If you want to know what your upgrade would cost, what it would deliver, and whether to do it now or wait, that is the conversation we have with clients before any work starts. Book a discovery call.

Decide when to move to Odoo 19

The first call takes 30 minutes.

Or email sales@octagotech.com