For SAP customers, “end of support” follows a defined sequence. Mainstream maintenance for Business Suite 7 ends in 2027. Paid extended maintenance runs through 2030. After that, customer-specific maintenance applies. A separate transition option extends support to 2033 for customers who move to SAP ERP, private edition.
Those dates settle when SAP customers must decide. They don’t settle what the business should run afterward. On-premises S/4HANA, hosted infrastructure, private cloud through RISE with SAP, public cloud, and third-party support all remain possible. Comparing SAP with Oracle and Microsoft shows which parts of SAP’s timeline are hard constraints and which are choices.
Which ERP Support Deadlines Should Companies Be Planning for Now?
For most SAP customers, the key date is 2027. SAP’s mainstream maintenance for Business Suite 7, including SAP ERP 6.0, ends in 2027, with optional extended maintenance through 2030. Customers that move to SAP ERP, private edition before then can use a transition option through 2033. Taken together, these dates give SAP customers two main planning horizons:
- 2030 if they stay on their current deployment
- 2033 if they commit to SAP’s private cloud path
Other vendors run on different clocks:
- Microsoft: Dynamics GP customers have until the end of 2029 for technical support and regulatory updates, and security patches continue into 2031.
- Oracle: Premier Support for its Applications Unlimited products is committed through at least 2037, which puts much less date pressure on its customers than SAP does.
Many SAP shops also run non-SAP ERPs in subsidiaries or acquired businesses. So companies need a lifecycle map of their whole ERP estate, not just the SAP core.
What Actually Happens When an ERP System Reaches End of Support?
For SAP ERP 6.0, end of support happens in stages rather than as a cliff:
- 2027: Mainstream maintenance ends.
- Through 2030: Extended maintenance continues service for an added fee.
- After 2030: Customers move to customer-specific maintenance.
At each stage, ECC keeps running, but SAP covers less and the customer carries more of the operational and compliance risk.
Other vendors also taper support, but along different curves. Microsoft’s lifecycle policy separates mainstream support from later phases and can offer security-only updates after other help ends. For Dynamics GP, new customers could no longer license subscriptions after April 1, 2026, while technical support continues through 2029 and security patches through 2031. Oracle’s Sustaining Support continues indefinitely, but it relies mostly on existing fixes and certifications.
SAP’s model sits in between. Its end dates are firmer than Oracle’s, but it offers more paid bridge options than a single cutoff would.
How Long Does an SAP S/4HANA Migration Take?
SAPinsider’s 2025 deployment research put the average SAP S/4HANA deployment at roughly 18 months, and a quarter of planned projects are expected to exceed two years. ASUG’s 2024 survey of 208 members found a 1.5-year average, but individual projects ranged from four months to six years.
That math matters for the 2027 date. An average-length project starting today would finish well after mainstream maintenance ends. For most ECC customers who haven’t started, extended maintenance or the transition option is therefore a practical bridge rather than an optional extra.
The broader ERP market moves somewhat faster. Panorama Consulting Group’s 2025 ERP Report recorded a nine-month median across vendors. In every case, scope matters more than brand:
- Carrying existing processes and customizations forward shortens projects.
- Process redesign, data cleanup, and broader transformation lengthen them.
Does an ERP Support Deadline Mean a Company Has to Move to the Cloud?
No, but SAP’s support policies clearly favor private cloud. SAP’s transition option offers the longest runway, to 2033, only to customers who move to SAP ERP, private edition. On-premises S/4HANA remains available for customers who want to keep running their own infrastructure.
SAP has also added flexibility. Changes introduced in July 2026 allow customers to split on-premises landscapes into separate commercial installations and make different support choices for each. For example, a company could move one business unit to RISE while keeping another on ECC under a different support arrangement.
Oracle takes the opposite approach. It commits Premier Support for on-premises Continuous Innovation releases of E-Business Suite, PeopleSoft, JD Edwards EnterpriseOne, Siebel, and Hyperion through at least 2037, and confirmed that date for E-Business Suite 12.2 in March 2026. Oracle customers can stay on-premises without date pressure. SAP customers can too, but the longest support comes with private cloud.
How Should SAP Customers Decide Whether to Migrate, Upgrade, Replace, or Extend?
SAP customers typically choose among these paths:
- A brownfield conversion to S/4HANA
- A greenfield reimplementation
- A selective data transition
- RISE with SAP private edition, including the transition option
- Public cloud
- Staying on ECC under extended, customer-specific, or third-party support
The right path depends on remaining support life, business requirements, migration effort, and the value the new platform would actually deliver. Customization, data quality, integration complexity, and process design often decide whether a move creates new capability or just recreates the old environment somewhere else.
PwC principal Shane Kondo defines data modernization as consolidating ERP and adjacent data onto a cloud-native platform, and he says business leaders should direct that work. His point underscores that an S/4HANA decision is also a data and operating-model decision. Panorama’s overrun data supports this: delayed sign-offs and resistance to standardization were leading causes of schedule slips.
This is where the vendor contrast matters most. An Oracle customer with support through 2037 must build the business case on value alone. An SAP customer has both a firm date and a business case to satisfy. The risk is letting the date stand in for the business case.
What This Means for ERP Insiders
Treat 2027 as a decision deadline, not a go-live deadline. Given typical S/4HANA timelines, architecture, sourcing, and funding choices need to be made now. Waiting pushes those decisions into the migration itself.
Use SAP’s new flexibility deliberately. The July 2026 changes let companies separate landscapes, infrastructure, and support choices instead of buying them as one package. That flexibility also adds responsibility for integration, security, and governance.
Don’t let the transition option substitute for a value case. A 2033 runway relieves immediate pressure, but it doesn’t resolve technical debt or capability gaps. Companies still need their own reasons for why staying or moving creates value.
A version of this article was first published by SAPinsider.
