On this page · 10 sections
- The policy changed, and a lot of published advice has not caught up
- What the surcharge attaches to
- The break-even calculation your quote should contain
- Why the licence number in your quote may be wrong
- What an Odoo engagement should actually cover
- India-specific considerations
- Why eCorpIT
- FAQ
- How eCorpIT can help
- References
Summary. Odoo began invoicing a 25% surcharge in April 2026 on any Enterprise subscription running a version older than the three most recent releases. The charge attaches to contracts renewed after 4 July 2025, and it hits Odoo.sh and on-premise customers; Odoo Online users are upgraded automatically and are excluded. In India the Custom plan carries a promotional rate of ₹890 per user per month billed yearly against a ₹1,150 list rate, and Standard runs ₹580 against ₹725, on the India and South Asia pricelist checked on 17 August 2026. The bigger change is not the money. Odoo also stopped ending support at three years, so a version can now stay supported for up to six years on Odoo.sh before removal. That makes upgrading an arithmetic problem rather than a deadline, and a good deal of the Odoo advice circulating in 2026 is still written against the retired rule.
If you are collecting quotes for an Odoo build or upgrade, one number should shape the conversation: 0.25 multiplied by your annual Enterprise subscription, charged every year you stay on an old release. Set that against the one-time cost of upgrading and you have your answer. Anyone opening with "your version is end of life, migrate now" is quoting a policy Odoo has replaced.
The policy changed, and a lot of published advice has not caught up
Until 2025, Odoo supported the three most recent major versions and older releases simply stopped receiving fixes. That is why so many guides still say a version dies after about three years. It is not how the current contract works.
Robert Versteeg of Kilurion, a Netherlands-based Odoo implementation partner, put the change plainly in February 2026: "Odoo Enterprise now offers support for all versions of Odoo. Versions will no longer automatically lose support after three years." Kilurion's summary adds that a version can run up to six years on Odoo.sh, that entitlement to support, bug fixes, upgrades and security updates continues, and that anything older than three major releases carries the 25% surcharge on the annual subscription. Much Consulting reached the same conclusion in June 2026: "The company now offers support for all versions indefinitely, but continued coverage of older releases comes at an extra cost."
The stale advice sits right next to it. A version support and LTS timeline guide published on 24 March 2026 by DeployMonkey tells readers on Odoo 14 or 15 to "migrate immediately — you are on unsupported software", lists Odoo 16 as end of life, and builds its table on an annual October release. Odoo 19 shipped on 18 September 2025 at Odoo Experience in Brussels, and under the revised terms none of those versions is unsupported. They are surcharged. Different problem, different price tag.
Urgency is now a commercial choice rather than a technical cliff. Worth knowing before you accept a rushed re-implementation.
What the surcharge attaches to
The mechanics matter more than the percentage, because the trigger is a contract date rather than a calendar date. VentorTech, an Odoo Gold Partner, documented the cases in February 2026, and Master Software Solutions set out the same rules in May 2026, noting that "the three covered versions (as of 2025) are Odoo 17, 18, and 19. Everything from Odoo 16 downward is now classified as a 'Legacy Version.'"
| Situation | Renewal date | Result from April 2026 |
|---|---|---|
| Legacy version, renewed before 4 July 2025 | Pre-cutoff | No surcharge until that contract ends |
| Legacy version, renewed after 4 July 2025 | Post-cutoff | 25% on the annualised price |
| Legacy version renewed February 2026, upgraded before April | Post-cutoff | No surcharge, version is covered |
| Legacy version renewed February 2026, upgraded in July 2026 | Post-cutoff | 25% applies for that yearly cycle |
| Any version on Odoo Online | Any | Excluded, Odoo upgrades these automatically |
Two details catch people out. On a multi-year contract the annualised price is the total divided by the number of years, so a five-year renewal on Odoo 15 is assessed against one-fifth of contract value each April. And finishing an upgrade in July does not reverse a charge levied in April. The check happens on a date; the work has to land before it.
Sources disagree on two points, and you should confirm both against your own signed agreement rather than any blog. Most partners date the first invoices to April 2026, but Much Consulting writes March 2026. And while Master Software Solutions and Much Consulting both put the legacy floor at version 16 and earlier, SIT Web describes it as version 14 or older and more than four years old. A month either way changes a renewal decision.
Odoo has published no explicit time limit for staying on a legacy release on-premise. Odoo.sh is different, because the hosting itself expires: version lifespan there is six years and the underlying Ubuntu images last four, which is why Odoo 14 is being removed from Odoo.sh on 31 October 2026 whatever anyone is willing to pay.
The break-even calculation your quote should contain
VentorTech states the arithmetic directly: the yearly surcharge is 0.25 multiplied by your annual Enterprise subscription, so break-even years are roughly upgrade cost divided by that surcharge.
Work it for a 25-user Indian company on the Custom plan at the ₹890 promotional rate. Annual subscription is ₹2,67,000, so the surcharge is ₹66,750 a year. A ₹4,00,000 upgrade pays for itself in about six years of avoided surcharge. A ₹12,00,000 re-implementation never pays for itself on surcharge grounds and has to be justified on features, security or the Odoo.sh removal date instead.
| Users on Custom plan | Annual licence at ₹890 | Annual 25% surcharge | Upgrade that breaks even in 3 years |
|---|---|---|---|
| 10 | ₹1,06,800 | ₹26,700 | ₹80,100 |
| 25 | ₹2,67,000 | ₹66,750 | ₹2,00,250 |
| 50 | ₹5,34,000 | ₹1,33,500 | ₹4,00,500 |
| 100 | ₹10,68,000 | ₹2,67,000 | ₹8,01,000 |
| 250 | ₹26,70,000 | ₹6,67,500 | ₹20,02,500 |
Read that the way a finance director will. Below roughly 50 users the surcharge rarely justifies a painful migration on its own, and the honest recommendation is often to stay put and budget the extra 25%. Above 100 users it starts funding real engineering and the upgrade becomes the cheaper path within a couple of years. The real cost is almost always the customisations, not the version bump.
Two technical items drive that customisation cost more than anything else. DeployMonkey's breakdown of the Odoo 14 end-of-life position notes that version 14 requires Python 3.6 to 3.8, all of which are themselves end of life, so a v14 estate is carrying an unsupported runtime as well as an old application. It also flags the two breaking changes that generate most upgrade hours: the removal of attrs across all views plus the move to OWL 2.x in version 17, and the module renames in version 19, including SEPA to ISO 20022. Inventory how many of your custom views and payment integrations touch those before anyone quotes you a number.
Why the licence number in your quote may be wrong
Search for Odoo pricing in India and the figures disagree by more than 25%, which is confusing until you notice they are quoting different things. The OEC.sh India pricelist page, updated 17 August 2026, shows both numbers on the India and South Asia pricelist (PL178INR).
| Plan | Yearly, promotional | Yearly, list | Monthly, promotional |
|---|---|---|---|
| Standard | ₹580/user | ₹725/user | ₹760/user |
| Custom (Enterprise) | ₹890/user | ₹1,150/user | ₹1,140/user |
That resolves the apparent contradiction in the market. When Banibro quotes ₹750 to ₹950 for Standard and ₹1,150 to ₹1,450 for Custom, it is quoting list-rate territory, not the promotional rate a first-year buyer sees. A quote built on the promotional number is a quote built on a number that moves.
Multi-year terms rise rather than fall in promotional terms: Custom is ₹890 at one year, ₹950 at two and ₹1,028 at five. Two other movements belong in the model. Odoo raised subscription prices in the United States and Canada by up to 30% from 2026, and revised its indexation clause so new contracts and renewals allow increases of up to 7% per annum rather than per renewal period. A flat five-year licence line is wrong by construction.
Ask any Odoo development company for the pricelist name, the promotional-versus-list basis, and the indexation term. A partner who cannot say which of those three is in the proposal has not read the contract.
What an Odoo engagement should actually cover
Odoo is a Python application, and most of the cost in a real project sits in the code around it rather than in configuration. Our Python development capability and our broader custom software development work are the same discipline applied here.
A scope worth paying for covers five areas.
Version and hosting decision. Which release, on Odoo Online, Odoo.sh or on-premise, with surcharge exposure and the Odoo.sh expiry date written into the recommendation rather than assumed away.
Custom module development. Studio covers a surprising amount, but anything carrying real business logic belongs in a versioned module with tests, because that code is what makes the next upgrade expensive.
Integration work. Payment gateways, GST e-invoicing, warehouse hardware, banking feeds, and whatever CRM already exists. Integrations are where upgrade cost concentrates, so they get inventoried before anyone quotes an upgrade.
Data migration. Chart of accounts, open documents, historical transactions, and the reconciliation that proves the migration was clean.
Upgrade path. A written plan for the next two versions with the break-even arithmetic attached, so the decision gets made on numbers.
Our delivery process is unglamorous and it works: audit the current instance and its customisations; agree target version and hosting with costs attached; build and test in staging against a production copy; cut over with a rollback plan and a reconciliation checklist; support through the first financial close, which is when the real defects surface.
India-specific considerations
India sits on the India and South Asia pricelist alongside Bhutan, Maldives and Sri Lanka, and OEC.sh ranks it 19th of 20 pricing tiers, so Indian buyers are not on a discounted tier despite the rupee denomination. Budget accordingly. Banibro puts full implementation cost in India between ₹90,000 and ₹40,00,000, with mid-sized companies typically at ₹3,00,000 to ₹12,00,000, which is a reasonable sanity check on any proposal you receive.
Two local factors change scope. GST e-invoicing and e-way bill obligations mean accounting and inventory need working integrations rather than manual exports, and those integrations are version-sensitive, which feeds straight back into the upgrade decision. Separately, any Odoo instance holding customer or employee records falls within the scope of the Digital Personal Data Protection Act 2023, so hosting location, access control and retention need deciding at design time. We design Odoo deployments aligned with DPDP requirements; we do not describe any deployment as certified compliant.
Odoo 20 is expected at Odoo Experience in Brussels on 24 to 26 September 2026. When it ships, Odoo 17 becomes the fourth-newest release and moves into surcharge territory. If you are on 17 today and building a 2027 budget, that is the date to plan against.
Why eCorpIT
eCorpIT is eCorp Information Technologies Private Limited, founded in 2021 and based in Gurugram. We are a senior-led, multi-disciplinary engineering organisation, CMMI Level 5 appraised, MSME certified and ISO 27001:2022 certified, and we work as technology partners of AWS, Microsoft and Google.
For Odoo that means treating the ERP as a Python application with a support calendar attached, not as a configuration exercise. We will tell you when the arithmetic says to stay on your current version and pay the surcharge, because a migration that does not pay for itself is not a project worth selling. Engagements run either as a fixed-scope implementation with a defined module and integration list, or as a dedicated senior team retained monthly for continuous development and upgrades. We quote against your actual user count, pricelist and customisation inventory, not a published rate card.
Related reading: our guides to ERP software development and to application modernisation from monolith to microservices cover the adjacent decisions.
FAQ
How eCorpIT can help
We build and upgrade Odoo systems as engineering projects: an audit of your current instance and customisations, a version and hosting recommendation with the surcharge arithmetic attached, custom module development, integration and data migration, then support through the first financial close. We will say so when staying on your current version and paying the 25% is the cheaper answer. To have the version math run against your actual user count and customisation inventory, contact us.
References
_Last updated: August 18, 2026._
