SAP ECC Conversion Before 2027 Is a License Position, Not a Slide
SAP closed 2025 with €10.53 billion in software support revenue (down 7 percent from €11.29 billion, while software licenses fell 29 percent to €0.99 billion). In the same Q4 2025 statement, SAP said the constant-currency support decline will accelerate as more customers transform to the cloud. Customer NPS dropped to 9, below the 12–16 target, “driven primarily by lower NPS scores from on-premise customers who have yet to transition to cloud.” Mainstream cover for ECC still ends in 2027. Extended maintenance runs to 2030. The SAP ECC conversion clock did not move.
That’s the problem.
This is not an investor miss you can leave with finance. The SAP ECC conversion you are being sold is a license event. Support that did not shrink is the bill you are still paying. Cloud revenue can grow and the 2027 deadline can still land on an estate you have not recast. If you cannot put ECC entitlements against an S/4 or Cloud ERP Private quote this week, you are walking in with last year’s invoice.
What SAP’s own numbers actually say
Do not let SAP frame this as whether you want innovation in the cloud. The right question is narrower: what ECC paper do you still hold, what have you already bought or subscribed to in order to start an S/4HANA move, and what does the next conversation consume that you cannot yet name.
Gartner, reported by CIO in June 2025, put the installed-base math in public. At the end of 2024, only 39 percent (about 14,000 of 35,000 worldwide ECC customers) had moved to S/4HANA. At that rate Gartner projected 17,000 still on ECC by 2027, and about 13,000 still there in 2030. IDC, in the same piece, expected 40 to 45 percent of ECC users to remain on the older ERP through 2027. Forrester’s Akshara Naik Lopez put more than 40 percent beyond 2027.
“Bought a start” and “converted the estate” are not the same object. Neither Gartner nor SAP publishes an ECC-to-S/4 exchange rate you can brief as fact. If someone walks in with a ratio, it is their commercial model, not a published rule.
SAP’s own 2025 results are consistent with that lag. Cloud revenue hit €21.02 billion. Cloud ERP Suite grew 28 percent to €18.12 billion. Support, the line that is supposed to fall as cloud subscriptions replace on-prem cover, is still a ten-billion-euro business. SAP is telling investors the decline will now accelerate. That is a forecast. It is not your conversion date.
A conversion quote without ECC entitlements is a number against a ghost estate
Look at your own SAP file. Most SAM teams still have a row that says ECC, a named-user count, and a maintenance invoice. Those three facts do not tell you whether the quote walking in is a like-for-like S/4 conversion, a Cloud ERP Private subscription, or a stay-on-ECC instrument dressed as a cloud deal.
If your reports still treat “SAP” as one product, you are reading a reporting layer. You have a maintenance invoice. You do not have a commercial outcome.
This is not a criticism of the teams building those reports. Traditional SAM tools collect installs and answer slowly. Nobody built a report called “what does an S/4 conversion consume against the ECC we still hold.” The gap is interpretation work. An analysis that arrives after the account team has framed the meeting is a document. One that arrives during the meeting is a decision input.
Picture your procurement director the week a conversion quote lands. The CIO wants to know whether you are in the 39 percent who have already started. Finance wants a stay-versus-convert number. The account team will walk in with Cloud ERP Private. If SAM needs three weeks to recast ECC entitlements against that quote, the headline becomes the file.
That recast is a renewal-optimization problem: the ECC paper you still hold against the conversion quote, this week. The Cloud ERP Private unbundling and the 2027 ECC deadline are already on the record. That was a packaging event. This is the 2025 support line still sitting at €10.5 billion, with the same 2027 clock.
The 2030 door is a subscription, not a pause button
SAP’s support strategy still points at the same calendar. Mainstream cover for Business Suite 7, including ECC, ends in 2027. Extended maintenance is available at a premium through the end of 2030. Price that premium on the estate you actually run, not on a slide that assumes you will be gone.
The 2030 and 2033 instruments are a different object. In February 2025, SAP previewed SAP ERP, private edition, transition option: a cloud subscription centered on ECC, for purchase from 2028, in use from 2031 to 2033. Stefan Steinle was explicit. It is “not a maintenance prolongation of SAP ERP.” Systems have to move to SAP ERP, private edition before the end of 2030. SAP HANA is the only supported database. The offering comes at an expanded fee in 2031–2033 versus a comparable cloud subscription before 2031. Customers who finish the transformation by the end of 2030 do not need it.
Those are commercial instruments, not a conversion and not a published exchange rate. A stay of execution you have not priced is not a plan.
Once the estate is in a cloud contract, the next SKU is easier to attach: Business AI, Business Data Cloud, the next named agent. SAP said Business AI was included in two thirds of Q4 2025 cloud order entry. That is SAP’s growth story. If you cannot say what you converted, you also cannot say what you are about to be sold.
What to have before 2027
Do this in the next thirty days, as a decision pack, not a project.
| What you produce | Why it has to be on paper |
|---|---|
| ECC entitlements you still hold | Named users, engines, and unused engines. A conversion quote without this list is a number against a ghost estate. |
| What you already bought or subscribed to for an S/4HANA start | The 39 percent metric is a commercial start, not a converted estate. Know whether you are in that group, and what those licenses cover. |
| A conversion scenario with no invented rate | Ask SAP for the conversion on your contract. Write it down. Do not brief a ratio nobody published. |
| Extended-maintenance cost at the premium through 2030 | Mainstream ends 2027. The premium is the price of staying on vendor cover, not the 2030/2033 subscription. |
| Which door you would actually take | Cloud ERP Private, an S/4 conversion you already funded, ECC private edition to 2030, the Transition Option to 2033, or something else. Name one. |
Then say, in one page, whether the next conversation is a conversion you can price, extended cover you can defend, or a 2030/2033 subscription that keeps ECC. A headline without that page is a document. A live position you can brief in fifteen minutes is a decision input.
Can a non-specialist walk the CIO through that pack today? If the answer is no, you do not have a SAP ECC conversion position. You have a maintenance invoice and a deadline.
The decision layer, not another migration spreadsheet
You already have a maintenance invoice, an install list, and a migration slide. The gap is not another inventory. The gap is turning that estate into a decision: what ECC you still hold, what you have already bought to start S/4, what a conversion consumes on your paper, and what should happen before 2027. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next.
If you are heading into a SAP conversion or extended-maintenance conversation this year and your tools still need three weeks to turn “we run ECC” into hold-versus-convert, book a Software Intelligence Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let SAP frame this as whether you want innovation in the cloud. The right question is: what ECC entitlements do we still hold, what have we already bought or subscribed to in order to start S/4, what does conversion cost on this contract with no invented rate, and what would we still buy if the 2025 support line had never been the argument. That is a data question, not a sales question.
The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
