Mainstream maintenance for SAP ECC 6.0 and Business Suite 7 ends on 31 December 2027. Extended maintenance runs through 2030 at a 2-point uplift — 24% instead of 22% — and after that only customer-specific maintenance remains. SAP designed the date to drive RISE and S/4HANA adoption. Used correctly, the same date is the strongest negotiating position SAP customers will have this decade.
SAP mainstream maintenance for ECC 6.0 and Business Suite 7 ends on 31 December 2027. SAP offers extended maintenance through the end of 2030 at a 2-percentage-point premium — so 24% of net license value instead of the standard 22% Enterprise Support rate — covering fixes and legal/regulatory updates but no new innovation. After 2030, customers who have not moved are placed on customer-specific maintenance, which is narrower in scope and individually priced. The date is firm enough to plan around and is the single most important clock in the SAP relationship right now.
The key reframe: the deadline is real, but it is not only SAP's. Every ECC customer who has not yet chosen a destination is a contestable account, and a contestable account negotiates from strength. The deadline is leverage that expires — use it before it does.
This is a sub-guide in our SAP support strategy pillar. It pairs with SAP third-party support and SAP support fee negotiation, and sits under our SAP vendor practice and SAP audit defence service. For the broader end-of-life picture see SAP ECC end-of-life options.
Three phases follow the deadline, each with a different cost and value profile. Understanding where you sit on this timeline determines which destination is realistic and how much leverage you still hold.
| Phase | Period | Support fee | New innovation | Practical meaning |
|---|---|---|---|---|
| Mainstream maintenance | Until 31 Dec 2027 | 22% (Enterprise) | Yes | Business as usual |
| Extended maintenance | 2028–2030 | 24% (+2pt) | No | Paid runway |
| Customer-specific maintenance | 2031+ | Bespoke, higher | No | Narrowed, costly |
| Third-party support | Any time | ~50% lower | No | Independent route |
That is a negotiating asset, not a problem — but only until you commit. We model the options with you while leverage is highest.
Four routes lead out of the 2027 deadline, and the right one depends on your innovation roadmap and risk appetite, not on which SAP markets hardest. RISE with SAP moves you to the cloud with support embedded in the subscription. S/4HANA on-premises keeps you in control but continues the 22% on a converted base. Staying on ECC with extended maintenance buys runway at 24%. Staying on ECC with third-party support cuts cost roughly in half but freezes innovation. SAP will steer every conversation toward RISE; an independent comparison keeps all four honest.
| Destination | 5-yr support cost | New innovation | Lock-in | Best fit |
|---|---|---|---|---|
| RISE with SAP | Embedded (subscription) | Yes | High | Committed to cloud + innovation |
| S/4HANA on-premises | 22% on converted base | Yes | Moderate | Control + roadmap |
| ECC + extended maintenance | 24% | No | Low | Buying decision runway |
| ECC + third-party support | ~50% lower | No | Low | Stable, deferred migration |
"The customers who lose most at 2027 are the ones who let the date make the decision for them. The date should sharpen the negotiation, not replace it."
The 2027 timeline, the destination comparison, the rebasing model, and the third-party savings math — in one research paper.
Because SAP's revenue model depends on converting the ECC installed base before the clock runs out, which means SAP wants your decision more than you need to make it quickly. A customer who walks into a renewal having already decided on RISE has surrendered all leverage; a customer who keeps RISE, S/4HANA on-premises, and ECC-plus-third-party genuinely on the table forces SAP to compete for the outcome it most wants. The extended-maintenance runway to 2030 exists precisely so you do not have to decide under duress — and a credible third-party support quote means you can afford to wait indefinitely if SAP will not meet a fair number.
The practical play is to treat 2027 as the trigger for a structured options evaluation that runs 18–24 months ahead of it, not as a cliff to scramble toward in 2027 itself. The conversion economics are in S/4HANA migration before 2027 and the RISE specifics in RISE with SAP explained.
Now — the leverage is highest furthest from the deadline. Concretely, an ECC customer should begin a destination evaluation no later than 18–24 months before any forced decision point: long enough to run a genuine third-party RFP, complete a license rebasing, and model the RISE-versus-on-premises-versus-third-party economics before SAP's deal desk knows which way you will jump. Customers who start in 2027 are negotiating against a cliff; customers who start in 2026 are negotiating against options. The cost difference between those two postures, across a five-year horizon, is routinely eight figures on a large estate.
$1.8B+ in documented client savings across 340+ engagements. Buyer-side only since 2016. Gartner recognised.
Weekly compliance intelligence for IT leaders.