Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

ERP End of Support: The Vendor-by-Vendor Calendar for Planning 2027-2030

SAP, Sage, Microsoft, Oracle, Infor, Odoo: ERP end-of-support table checked against vendor pages, with verification date and decisions by deadline.

ERP End of Support: The Vendor-by-Vendor Calendar for Planning 2027-2030

Is your ERP still supported, and for how long? Many CIOs and CFOs cannot answer that question in under a day, because every vendor speaks a different language: mainstream maintenance, extended support, continuous updates, “the last three versions”. This article pulls those rules into a single reference table, with the official URL behind each date.

Verification date: 17 November 2026. Each deadline below was re-read on the vendor’s own page on that date, unless stated otherwise. When a date could not be confirmed on an official source, it is written “not confirmed”. We would rather leave a gap in the table than invent a date.

Why the end-of-support date is a business risk, not just an IT one

An ERP that falls out of support keeps running the next day. That is exactly what makes the risk insidious: nothing breaks, but everything becomes more fragile.

  • Security. No more regular security patches, or only as an exception. Your ERP holds your financial, customer and HR data, which makes it a prime target.
  • Compliance. Regulatory updates (e-invoicing, tax filings, accounting standards) are delivered on supported versions. At Microsoft, the Dynamics FAQ states that non-security updates, tax and regulatory updates and service packs are reserved for customers covered by a service plan (Microsoft Learn, Dynamics Lifecycle FAQ). For e-invoicing, see our January 2027 ERP regulatory calendar.
  • Third-party ecosystem. Operating systems, databases, browsers and connectors keep moving. A third-party vendor or an integrator may refuse to certify its module on a version that is out of support.
  • Audit and insurance. An external auditor or a cyber insurer may ask for proof that critical systems are maintained.

The hidden cost of standing still is detailed in our article on ERP technical debt and the business case for the executive committee (in French).

Summary table of deadlines

VendorProduct / versionEnd of standard supportExtended supportOfficial source
SAPERP 6.0 EHP 6 to 8 (Business Suite 7)31/12/20272028 to end of 2030, with a 2-point premium on the maintenance basesupport.sap.com
SAPBusiness One 10.031/12/2028 (“dates subject to change”)Not confirmedsupport.sap.com
SAPBusiness ByDesignNo end date announced (secondary source only)Not applicableNot confirmed on any SAP page read for this article
MicrosoftDynamics NAV 201811/01/2023 (ended)12/01/2028Microsoft Learn
MicrosoftDynamics AX 2012 R312/10/2021 (ended)10/01/2023 (ended)Microsoft Learn
MicrosoftDynamics 365 Finance & OperationsModern policy: continuous updates, no usable end date per versionNot applicableMicrosoft Learn
MicrosoftDynamics 365 Business Central (SaaS)Modern policy: “In Support”Not applicableMicrosoft Learn
OracleE-Business Suite 12.2Premier Support announced through at least 2036 (a more recent Oracle document mentions 2037, not re-read)Not confirmedblogs.oracle.com/ebs
OracleJD Edwards EnterpriseOneAligned with the same “at least 2036” commitment, not re-read on a dedicated JDE pageNot confirmedblogs.oracle.com/ebs
OdooLast three major versionsRolling, see Odoo sectionNot applicableodoo.com/documentation
SageSage 100 (France)Not confirmedNot confirmedNo official page read
SageSage X3Not confirmed for current versionsNot confirmedSage Community, lifecycle policy
SageSage 50Not confirmedNot confirmedNo official page read
InforLN, M3, CloudSuite IndustrialPer-version schedule, customers onlyNot publicly confirmedInfor Concierge (customer access)
CegidERP rangeNot confirmedNot confirmedNo official page read

How to read the table: a “Not confirmed” cell does not mean the product is at risk. It means we could not read a date on a publicly accessible page on 17 November 2026, and that you should request it from your vendor or integrator in writing.

SAP: ECC 6.0, Business One, ByDesign

ECC 6.0 (EHP 6 to 8). SAP states that it provides mainstream maintenance until the end of 2027 for the core applications of Business Suite 7, followed by three years of extended maintenance, from early 2028 to end of 2030, for a premium of two percentage points on the maintenance base (SAP Support, Business Suite 7). The exact scope of extended support is described in SAP Note 52505, available to logged-in customers only: read it before deciding to stay.

For the full analysis of the options, see our ECC 2027 guide for late movers. In one line: end of 2027 for mainstream, end of 2030 for extended, and the premium comes on top of a maintenance bill that no longer delivers any innovation.

Business One. Version 10.0 is in mainstream maintenance until 31 December 2028, with the caveat that dates are subject to change (SAP Support, Business One). According to the same page, versions 9.3 and 8.82 have already ended their mainstream maintenance period. If you are still on one of them, you are already outside standard coverage.

Business ByDesign. Secondary sources indicate that SAP stopped selling it to new customers from April 2026, with no end date for existing customers. We did not re-read that announcement on an SAP page: treat it as not confirmed and ask for the commitment in writing before building a plan on it.

Third-party support option. Rimini Street and Spinnaker offer alternative support for SAP. The trade-offs (scope, regulatory fixes, exit) are covered in our third-party support comparison.

Sage and Microsoft

Sage: 100, X3, 50

Sage publishes a lifecycle policy for Sage X3 on its community site, with three states: Current, Standard and Extended (Sage Community, Sage X3 Lifecycle Policy). We could not read on an official page the end date of the X3 versions currently deployed in France, so it is shown as not confirmed in this table.

For Sage 100 in France and Sage 50, we found no usable official page to pin down a date. US resellers describe a rolling rule for Sage 100 (a North American product, not to be confused with the French offering): the current version plus the two previous ones. That rule is not demonstrated for the French offering. Write to your Sage contact to get, per version, the end-of-support date and the date of the annual statutory updates.

Microsoft: NAV, AX, Business Central, Finance & Operations

Legacy NAV and AX versions. Dynamics NAV 2018 left mainstream support on 11 January 2023 and its extended support runs until 12 January 2028 (Microsoft Learn). Dynamics AX 2012 R3 ended mainstream support on 12 October 2021 and extended support on 10 January 2023 (Microsoft Learn, Dynamics FAQ). Customers still on AX 2012 R3 therefore no longer receive security fixes from Microsoft.

Finance & Operations. The online service falls under the modern lifecycle policy: Microsoft updates continuously, and the customer can postpone one consecutive service update, but not indefinitely (Microsoft Learn, F&O lifecycle policy). Microsoft states that it does not investigate or fix issues on a version that has reached end of service. The risk is no longer a distant date, it is update discipline: if your environments fall more than one version behind, the pause option disappears.

Business Central (SaaS). Same modern logic: the lifecycle page shows “In Support” with no retirement date (Microsoft Learn). Your deadline is the schedule of your extensions and regression tests, not an end date.

Oracle, Infor, Odoo, Cegid

Oracle E-Business Suite and JD Edwards. Oracle announces that Premier Support for EBS 12.2 is extended through at least 2036 (Oracle, EBS blog). One search result indicates that this date was pushed to 2037 in a more recent Oracle document, which we could not re-read: check the “Oracle Support Policies” page on the day you decide. JD Edwards EnterpriseOne is presented under the same commitments, but we did not re-read a dedicated JDE page, hence the “not confirmed” label. One caution: the support date says nothing about the underlying infrastructure (database, operating system), whose deadlines are separate.

Infor LN, M3, CloudSuite Industrial. Infor distinguishes three phases (mainstream, extended and sustaining maintenance) and publishes per-version schedules in its customer portal, Infor Concierge. They are not public, so we cannot quote any date. Ask your account manager for the Product Life Cycle extract for your exact version.

Odoo. The official documentation states that Odoo provides support and bug fixes for the last three major versions (Odoo, Supported versions). A major version is released every year, so the window slides forward by one year with each release, and a version that stands still falls out of support after roughly three years. The precise end-of-support dates per version are in the table on that same page; we could not re-read it in full for this article, so check it directly. For an Odoo ERP “frozen” for more than three years, the question is no longer “when” but “already”. Our major upgrade methodology covers this case.

Cegid. We found no public, dated lifecycle policy for the ERP range: not confirmed. Request it in writing, product by product.

What to do depending on the deadline

The right trade-off depends less on the vendor than on how far away the deadline is.

Less than 12 months

No time for a full migration project. Three actions:

  1. Secure: document compensating controls (application firewall, network segmentation, enhanced logging).
  2. Buy time: subscribe to the vendor’s extended support or to third-party support, knowing the exact scope (regulatory fixes included or not).
  3. Start scoping the target in parallel, so that extended support remains a bridge and not a permanent state.

Between 12 and 36 months

This is the most rewarding window. You can compare upgrade, migration to another ERP and buying time, with a real business case. A mid-market ERP project takes several quarters of preparation before the first line of configuration: if the end date is 24 months away, scoping must start now.

More than 36 months

No urgency, but no comfort either: this is the time to remove the obstacles that will slow down the future project (data cleansing, fewer custom developments, interface inventory). Enter the date in the multi-year budget.

Upgrade, migration or third-party support

SituationLogical option
Healthy vendor product, version simply oldUpgrade to the current version
Product at end of life, or vendor strategy incompatible with your directionMigration to another solution
Need for stability on a system that rarely changes, target project not readyThird-party support, as a time-boxed bridge

Third-party support is not a plan: it is a delay. Set an exit date for it at signature.

Quarterly verification checklist

To schedule on the ERP steering committee agenda, every quarter:

  1. Record the exact version of each ERP and each module in production (not “SAP”, but the release level).
  2. Re-read each vendor’s official lifecycle page and note the date you read it.
  3. Escalate every “not confirmed” date in a letter to the vendor or integrator, requesting a written answer.
  4. Check the dates for the underlying infrastructure: database, operating system, browsers.
  5. Check that next year’s statutory updates are covered by your maintenance contract.
  6. For SaaS offerings under a modern policy: check that your environments do not exceed the tolerated update lag.
  7. Recalculate the time remaining and place it in one of the three zones (under 12 months, 12 to 36 months, over 36 months).
  8. Update the budget and the risk in the IT risk register.

Take stock of your situation

If you do not know which zone your ERP falls into, or if your vendor will not give you a date, an ERP situation audit can produce within a few weeks a map of versions, confirmed deadlines and the gaps to fill. Contact us to discuss it.

Further reading: SAP ECC 2027, guide for late movers, major ERP upgrade methodology, third-party support from Rimini Street and Spinnaker and ERP technical debt and the executive committee business case (in French).