Odoo Upgrade Services

Short answer: Vayasoft upgrades Odoo 16, 17 and 18 databases to Odoo 19. We port custom modules, check Studio changes and test everything on a copy of your database before production is touched. Vayasoft is an official Odoo Ready Partner based in India, with offices in Pune and Indore. We’ve completed 15+ Odoo implementations over 7+ years. Every upgrade starts with a health check and ends with a parallel check and a dated cut-over plan. Timelines depend on size and are set after the health check.

Why upgrade

Odoo releases a new major version every year. Each release brings fixes, security updates and new features. Odoo supports only its three most recent major versions, so older ones stop receiving fixes and security updates. Staying behind means a bigger and riskier jump later, with more custom code to port at once. Upgrading in planned steps keeps each step small.

Upgrade paths to Odoo 19

Your versionPath to Odoo 19Notes
Odoo 1616, 17, 18, 19Three steps. Each step is tested before the next.
Odoo 1717, 18, 19Two steps.
Odoo 1818, 19One step.

We upgrade one major version at a time, which keeps each step testable. If you run a version that isn’t listed, tell us and we’ll confirm the path during the health check.

What happens to custom modules and Studio changes

  • Custom modules are usually the main effort. Each module is ported to the new version and then tested. Simple, well-documented modules move quickly. Heavily customised modules take longer, and code that edits Odoo’s core files often has to be rebuilt.
  • Studio changes are stored in your database and carried across. Any field, view or automation that depends on a changed part of Odoo is checked and fixed.
  • Third-party apps need a version that works on the target release. We check each one and list any that need replacing.
  • Standard configuration, such as taxes, workflows and user rights, normally carries over. We verify it anyway.

If a custom module needs to be rebuilt, our Odoo customisation services cover that work. If the health check shows that an older setup needs redesigning rather than porting, that is closer to an Odoo implementation project, and our cost guide for India explains how that effort is estimated.

The upgrade process

  1. Health check and inventory. We list custom modules, Studio changes, third-party apps, integrations and data volumes.
  2. Plan and go or no-go. We agree the path, scope, timeline and risks. You approve before work starts.
  3. Backup. We take a full backup of production.
  4. Test database. We restore the backup to a separate test database and run the upgrade there. This is the first real test, and production is not touched.
  5. Port and fix. On the test database, we port custom modules and fix Studio items and third-party apps.
  6. User testing. Your team tests daily tasks, reports, integrations and printed documents. We fix what they find, then re-run the upgrade on a fresh copy so the final run is clean.
  7. Parallel check. For an agreed period, the same transactions run through the live system and the upgraded test system. We compare sales and purchase totals, stock levels, ledger balances and key reports. Every difference is explained before cut-over. The length of this period is set during planning.
  8. Cut-over. We announce a downtime window, stop changes on production, take a final backup, run the upgrade and check key screens and reports.
  9. Hypercare. We watch the first weeks closely, then hand over to your Odoo support plan.

What sets the timeline

SizeTypical scope
SmallA few apps, few custom modules, standard data
MediumSeveral apps, some custom modules and Studio changes, one or two integrations
LargeMany apps, heavy customisation, multiple companies or integrations

Timelines are set after the health check. They depend on custom code, integrations and how quickly your team can test.

Frequently asked questions

Do we have to go through every version?

Yes, we upgrade one major version at a time. Each step can then be tested and checked before the next one starts.

Will we lose data during an upgrade?

Not if the process is followed. Production is upgraded only after a full backup, a tested upgrade on a copy and a final check. Backups are kept until you accept the upgrade.

Will the upgrade need downtime?

Yes, for the final cut-over. The window length depends on your database size and is agreed during planning.

Do Odoo Online customers need an upgrade project?

On Odoo Online, Odoo runs the platform upgrade. Custom modules, Studio changes and integrations still need checking and porting, and that is where we help.

Can you upgrade an Odoo.sh or on-premise system?

Yes. Odoo.sh and on-premise systems follow the same steps. On on-premise, we also agree the server and backup plan with your IT team before the test database is built.

Talk to Vayasoft

Still on Odoo 16, 17 or 18? Book a free 30-minute call at https://vayasoft.com/book-a-consultation/. We’ll run a first check of your version, custom code and Studio changes, and tell you what an upgrade would involve.

About Vayasoft: Vayasoft is an official Odoo Ready Partner based in India. From our offices in Pune and Indore, we implement, customise, upgrade and support Odoo for manufacturing, distribution, solar EPC, retail and service businesses, and we publish our own apps on the Odoo App Store.