SAP has already booked your migration into its 2027 revenue plan, and roughly 17,000 ECC customers are projected to miss the date anyway. This page shows how to read that asymmetry and turn it into named concessions: zero-uplift initial terms, capped renewal escalators, and a RISE proposal reduced 20 to 40 percent.
SAP has already booked your migration into its 2027 revenue plan, and roughly 17,000 ECC customers are projected to miss the date anyway. This page shows how to read that asymmetry and turn it into named concessions: zero-uplift initial terms, capped renewal escalators, and a RISE proposal reduced 20 to 40 percent.
Read SAP's own guidance before you read the end-of-maintenance notice. SAP has told the market that total revenue growth reaccelerates in 2027 and that software support revenue declines faster over the same window, and both of those lines depend on the remaining ECC base converting to cloud subscriptions on roughly the schedule SAP published. That is the whole tell. A technical date on your side is a booked number on theirs. If you slip, SAP does not experience an inconvenience; SAP reports a miss against guidance it already gave investors, in a quarter where the account team's compensation is measured on RISE bookings and migration commitments. That asymmetry is the entire negotiation, and most buyers hand it back for free by treating December 2027 as a wall rather than as the vendor's forecast assumption.
Now price your side of the same date honestly, because that is what turns a posture into leverage. Standard SAP support runs 22 percent of net license value. Extended maintenance on ECC 6 EHP 6 through 8 carries an additional two percentage points to December 31, 2030, roughly a 9 percent increase on the support line. On a 4 million dollar annual support bill that is about 360,000 dollars a year for three more years of runway, call it a little over a million dollars total. Compare that to the cost of signing a multi-year RISE ACV commitment you sized under time pressure, where a 25 percent FUE overcount and a 5 percent annual escalator compound across a five-year term into seven figures of avoidable spend. In my experience across the table from this vendor, buyers who quantify the extension premium before the first RISE meeting negotiate from a completely different posture than buyers who arrive assuming 2027 is non-negotiable. The extension is budgetable. A rushed cloud commitment is not reversible.
The extension premium is a line item you can approve in a budget meeting; a mis-sized five-year RISE commitment is a decision you live with until 2032.
Treat 2027, then, as the date SAP needs you to hit, and price your willingness to help them hit it. That willingness has a number attached, and you should be the one who names it.
At the end of 2024, roughly 39 percent of SAP's approximately 35,000 ECC customers, about 14,000 organizations, had purchased S/4HANA transition licenses. Interpret that correctly: a license purchase records intent, sometimes only shelfware bought to lock a discount, not a completed migration. The share of customers actually running S/4HANA in production is materially lower than 39 percent. Gartner projects roughly 17,000 holdouts at the deadline and more than 13,000 still on ECC in 2030, three years past the date SAP built its forecast around. Fabio Di Capua's line to SAP is the cleanest statement of the position: you convinced less than half your clients to migrate in fifteen years. That is not a customer failure. It is a product adoption problem the vendor is trying to solve with a calendar.
Be careful with denominators when you quote this in the room, because SAP's team will pounce on a sloppy number and use the correction to reset the whole conversation. The 39 percent figure counts transition licenses sold. The widely quoted 85 percent figure describes the share of the installed base affected by the 2027 end of mainstream maintenance. Different measures, different arguments, both true. Cite the one that fits your point and say which one you are using.
| Figure | What it measures | How to use it |
|---|---|---|
| ~35,000 ECC customers (end-2024) | Total base facing the date | Establishes the scale SAP must move |
| ~39% with transition licenses | Licenses bought, not migrations done | Ceiling on real conversion, use as your headline |
| ~17,000 holdouts at 2027 (Gartner) | Projected misses at the deadline | Proof the cliff cannot be enforced |
| 13,000+ still on ECC in 2030 | Post-deadline persistence | Supports a 2030 extension ask |
| 85% of installed base affected | Exposure to end of maintenance | SAP's framing, expect it quoted back |
The operational takeaway: you are not an exception pleading for accommodation, you are one of many thousands in the same position, and SAP's sales organization knows the pipeline math better than you do. Pair this with an understanding of what the account team is actually compensated on and you can see why a credible "we will extend and revisit in 2029" costs them more than it costs you.
A deadline is only credible if the vendor can afford the consequence of customers ignoring it. Gartner's projection of more than 13,000 accounts still running ECC in 2030 is the number that breaks the cliff argument, because SAP cannot let thirteen thousand production estates fall off support without handing the third-party support market a permanent installed base. That is the arithmetic SAP's own field organization understands better than you do. Third-party support quotes reviewed in the market run 45 to 55 percent below SAP standard support, which is priced at 22 percent of net license value annually. Once a CIO has signed a three-year third-party agreement and lived through two clean quarters of it, the support revenue does not come back on any timeline SAP's plan contemplates, and the S/4HANA conversation gets postponed by the length of that contract. Shelfware carried at 10 to 25 percent of the annual fee is the other quiet drain: every account SAP pushes hard enough to trigger a support review becomes a candidate for permanent revenue loss rather than a conversion. Price the reinstatement exposure before you use any of this as a threat, because back-maintenance and reinstatement fees have run 150 to 200 percent of lapsed support in reviewed cases, and a bluff you cannot fund is worse than no bluff. The practical consequence is that SAP does not enforce uniformly. It enforces selectively, on accounts with weak internal alignment and no advisory support, and it offers everyone else extended maintenance (roughly two additional percentage points, about a 9 percent cost increase, through the end of 2030), bridge arrangements, and quiet date extensions. Your job in the room is to be visibly in the second category. Say plainly that you have priced the alternatives and that your board has not approved a 2027 go-live, then let the account team decide which bucket you belong in.
The number your account executive defends internally is not your go-live date. It is current cloud backlog, which stood at EUR 22.9 billion at Q2 2026, up 27 percent (26 percent at constant currencies). Christian Klein called that 26 percent an acceleration versus Q1, which only mattered because CCB had lagged cloud revenue growth for the two prior quarters. Cloud revenue grew 22 percent in the same period, and SAP has told investors to expect total revenue growth to pick up in 2027 while software support revenue declines faster, an outcome that only works if the remaining ECC base converts on schedule. Read that as a commitment SAP made to the market on your behalf, without asking you. The only instrument that closes a CCB gap is a signed multi-year RISE ACV, and a signed ACV requires your signature. There is no shortage of SAP capacity to deliver; there is a shortage of names on paper in the last three weeks of a quarter. That makes your signature the scarce good in the room, and scarcity is the whole basis for a price concession. The compensation structure makes it personal: the customer engagement executive is paid on RISE bookings, S/4HANA migration commitments, and renewal value, which is why the same person who cites the 2027 date will also find a way to close in December. Understand what SAP sales reps are actually paid on before your first pricing conversation, and calendar the negotiation backward from the fiscal boundary so that quarter-end and fiscal-year timing works for you rather than against you. Strong outcomes cluster in the last seven days of a period, not because SAP is generous then, but because the CCB gap is visible then.
There is no shortage of SAP capacity to deliver; there is a shortage of names on paper in the last three weeks of a quarter.
The reason you are not signing on SAP's calendar is not that you dislike the calendar. It is that the industry's own delivery record says the project cannot be compressed into the window SAP has drawn. The Horvath 2025 study of 200 SAP user companies found projects running 30 percent longer than planned, only 8 percent finishing on schedule, more than 60 percent over budget, and only 37 of the 200 having actually completed migration. ISG's February 2026 research puts nearly 60 percent of projects delayed and over budget, with two thirds still in planning. Read those together and the honest conclusion is that a 2027 go-live commitment made in 2026 has roughly a one-in-twelve chance of being kept. That is not stalling, that is arithmetic, and it is the version of your position that survives contact with your own CFO and audit committee.
Say it that way at the table, because it changes what you are asking for. You are not asking SAP to relax a deadline; you are asking SAP to price the subscription against the schedule its own customer base actually delivers. Three asks follow directly. First, a phased FUE ramp: pay for the users who are live, not the users in the target state, with named tranches tied to go-live waves rather than to calendar quarters. Second, a delayed subscription start, ninety to one hundred eighty days past signature, so you are not funding a cloud contract while ECC still carries the transactions. Third, migration credits sized to your project, not to the basic implementation RISE deals typically fund before additional work drops onto SAP consulting rates of $250 to $400 per hour, which independent advisers put 30 to 50 percent above equivalent offshore or nearshore work. Bring your own systems integrator quote and make SAP fund the delta. If SAP argues the ramp is unusual, note that its own installed base has produced 37 completions out of 200 attempts, and ask which of those two numbers it wants written into your payment schedule.
Leverage that is not converted into clause language is just a feeling. Anchor the commercial conversation on the third-party benchmark band of $190 to $360 per FUE per month for RISE private edition, and say out loud that SAP publishes no list price for that edition, so the "discount" on the first proposal is measured against a number SAP invented. Volume bands matter: reviewed deals at 300 to 500 FUE land at 40 to 50 percent off, and 500-plus FUE reaches 50 to 65 percent where you commit multi-year and aggregate services. Across more than fifty reviewed RISE proposals, advisers consistently found 20 to 40 percent of proposal value removable through escalation clauses, unused BTP credits, and FUE ratchet mechanics. Your target is not a percentage off the AE's spreadsheet. It is a per-FUE net rate you can defend against the benchmark, with the ratchet gone. Time the close using SAP's own reporting cycle: what the account team is paid on is current cloud backlog, which is why understanding what SAP sales reps are actually compensated on and working backward from quarter and fiscal-year end moves more money than another round of feature debate.
| Your ask | SAP's likely counter | Target landing point |
|---|---|---|
| Net rate inside the $190 to $360 per FUE benchmark, ratchet deleted | "That band is not our pricing." Offers a bigger percentage off an unpublished list | 40 to 50 percent off proposal at 300 to 500 FUE, 50 to 65 percent above 500 FUE, ratchet removed in writing |
| Zero uplift for the full initial term | CPI-linked or "market adjustment" language, 3 to 7 percent | Zero uplift for the initial term, then 1 to 2 percent cap or a fixed dollar cap at renewal |
| BTP credits above the 1 percent of net ACV formula | Points to the standard floor of EUR 10,000 and cap of EUR 20,000 | Credits sized to your actual BTP roadmap, cap lifted, unused balance rolls forward |
| AI Units capped, not metered | Use-based default at roughly $0.08 to $0.18 per action | Hard annual cap or fixed AI Unit pool, overage rate locked for the term |
| Phased FUE ramp plus 90 to 180 day delayed start | Full contracted volume billed from signature | Billing tied to go-live tranches, with unconsumed FUE not invoiced |
You are not asking SAP for a discount off list; there is no list, so every number on that proposal is negotiable by definition.
Put all five asks in one document, price each one, and tell SAP which two are walk-away items. Vendors concede against a ranked list and stall against a wish list.
Nothing about this playbook is improvised, and after twenty five years across the table from this vendor I can tell you the sequence rarely varies. First comes escalation above your account executive: the AE loses control of the date, so the customer engagement executive, then a regional cloud lead, then someone with "transformation" in the title arrives to reframe your refusal as a governance failure rather than a commercial position. Treat that as a signal, not a threat. It means the account is material to a current cloud backlog number that grew 26 percent at constant currency in Q2 2026 and needs signed multi-year ACV to keep growing. Our note on when to escalate above your SAP account executive works in both directions: if they escalate first, match the level and put your CFO in front of theirs. Second comes the security and compliance narrative about unsupported ECC. Counter it with facts: mainstream maintenance for ECC 6 EHP 6 to 8 runs to December 31, 2027, and extended maintenance costs roughly two additional percentage points on the 22 percent base (about a 9 percent increase) through December 31, 2030. That is a supported, patched, contractually documented state, not a risk position, and your auditors can be told so in writing. Third comes a measurement or audit request landing suspiciously close to your renewal window. Do not fight the request; slow it, scope it, and refuse to let indirect access findings and RISE pricing sit in the same conversation. Fourth comes the claim that current discount levels expire with the deadline. They do not. Discounts expire when the quarter closes without a signature, which is your lever, not theirs. Fifth, and only if you have hinted at leaving maintenance, comes reinstatement pricing quoted at 150 to 200 percent of lapsed support. Price that exposure yourself, in a spreadsheet, before you ever say the words "third party support" out loud, because an unpriced threat is a gift to the other side. And be clear that the 2026 support adjustment (local CPI, capped at 5.0 percent) is standing policy applied to everyone, not a penalty triggered by your refusal to sign. If your AE presents it as consequence, correct the record on the call.
Thirty days, four moves, in this order. One: build the hard walkaway number. Model extended maintenance on ECC through December 31, 2030 at 22 percent plus two points, add the CPI-capped adjustments, and total the cash cost of staying put. That figure is your ceiling on RISE year one, and every concession ask flows from it. Two: model reinstatement exposure at 150 to 200 percent of lapsed support so the third party support option is priced before it is ever mentioned. Three: get a one-page internal position signed by the CFO and CIO stating that the migration date is set by your own programme evidence (readiness gates, data remediation status, test cycles) and not by SAP's maintenance calendar. Circulate it internally so no executive gets picked off in a side conversation. Given that only 8 percent of the 200 companies in the Horváth study finished on schedule and 60 percent blew the budget, that document is defensible, not obstructive. Four: calendar backwards from December 31 and target signature inside the final seven days, with your best-and-final held until then. Our work on SAP quarter-end and fiscal-year timing sets out the operational readiness required to actually hit that window: legal pre-cleared, security review closed, signatory available. A strong outcome looks like a proposal cut 20 to 40 percent, zero uplift on the initial term, and a renewal escalator capped at 3 percent.
Mainstream maintenance for ECC 6 EHP 6 to 8 ends December 31, 2027, but extended maintenance is available through December 31, 2030 at roughly two additional percentage points on the standard 22 percent support rate, about a 9 percent cost increase. That is a budgetable bridge, not a cliff. Gartner projects more than 13,000 customers will still be running ECC in 2030, which tells you how enforceable the date really is.
Reviewed RISE proposals commonly come down 20 to 40 percent from the first offer. Deals in the 300 to 500 FUE range typically land 40 to 50 percent off, and 500-plus FUE deals with multi-year commitment reach 50 to 65 percent. There is no published list price for the private edition, so any per-FUE figure you see is a third-party benchmark rather than a rate card, and you should treat it as a sanity check, not an anchor.
SAP has already booked the holdout conversion into its own forward guidance, with revenue growth expected to reaccelerate in 2027 as remaining ECC customers move. If you slip, that is a reported miss for SAP as much as a project delay for you. Combine that with current cloud backlog pressure, EUR 22.9 billion at Q2 2026, and your unsigned RISE ACV becomes the thing SAP needs more than you need the migration.
Only after you have priced the consequence. Third-party support quotes run 45 to 55 percent below SAP standard, which is real leverage, but reinstatement and back-maintenance fees run 150 to 200 percent of lapsed support if you ever return. Model that number first, and only raise the alternative when you are prepared to actually take it.
SAP's default is CPI-based or a fixed 3 to 5 percent annual escalator. The target is zero uplift for the initial term, which has been agreed on large strategic deals, with a capped mechanism at renewal. Acceptable fallbacks are a 1 to 2 percent annual cap or a fixed dollar cap per year, and you should also close the FUE ratchet so mid-term consumption changes cannot reprice the deal upward.
Calendar the negotiation backwards from December 31 and aim for signature in the final seven days of the fiscal year, when the customer engagement executive's compensation on RISE bookings and migration commitments is most exposed. Quarter-end helps, but SAP's fiscal year-end is where the largest structural concessions, not just discount points, become available.
How to migrate from SAP ECC to S/4HANA without overpaying: conversion contracts, RISE alternatives, indirect access exposure, and the leverage you hold.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
