What the date actually is
If you hold an on-premise SAP maintenance agreement, you have a perpetual licence to Solution Manager. SAP says so directly: customers with on-premise maintenance agreements retain the perpetual licence and can continue using Solution Manager after the end of mainstream or extended maintenance.
So 2027 is a support date. Corrections stop. Your right to run the software doesn’t.
It gets better than most people realise. If you take the optional extended maintenance for Business Suite 7 — the one that costs two percentage points on your maintenance basis and runs to the end of 2030 — you receive extended maintenance for Solution Manager 7.2 at no additional cost. Not a separate purchase. Included.
And the extended maintenance scope isn’t a token subset. Per SAP Note 3255311 it covers requirements management, project management, process management, test suite, change control management, IT service management and landscape management.
Change control management. ChaRM is in scope, to 2030, at no extra cost.
I’ve seen this described repeatedly as paid extended maintenance for selected functions. That framing is wrong in both halves, and it’s worth knowing which one you’re actually looking at before you build a plan around it.
The second date
Now change one variable.
Solution Manager usage rights are included in on-premise maintenance agreements. S/4HANA Cloud — including private edition — comes with its own cloud maintenance agreement.
RISE includes Cloud ALM. It does not include Solution Manager. If you move fully to RISE and retain no separate on-premise maintenance agreement, you have no Solution Manager usage right at all.
Not at end of maintenance. At the end of your on-premise agreement.
That’s a different kind of event, and the difference is the whole point of this piece.
An on-premise customer has a support problem. A RISE customer with no remaining on-premise agreement has an entitlement problem — and its date sits in their contract, not on SAP’s maintenance roadmap.
Exactly when that lands is a contractual question, not a roadmap one. It depends on when your on-premise maintenance agreement terminates — which is why the first action below is to confirm it in writing rather than assume it.
For an organisation converting during 2026, that clock may already have started, before the one everyone is planning around.
What travels with it
For organisations that built change governance on ChaRM — transport control, approval workflow, the release calendar, the audit trail internal audit has been shown for a decade — this isn’t a tool swap.
It’s the rebuild of the control framework that SOX evidence, release governance and segregation-of-duties testing currently rest on.
Test Suite goes the same way. So do process documentation and monitoring. Focused Build and Focused Insights are included in Solution Manager’s usage rights and follow the same maintenance conditions, so they travel with it too.
One precision point, because overstating this is the fastest way to lose an argument with someone who has read their own paperwork. RISE supplements have historically granted narrow web self-service rights inside Solution Manager Enterprise Edition — raising support tickets, checking status, confirming them, and change approvals directly related to those.
Supplement wording changes between versions. Check yours rather than taking mine. But whatever the current text says, understand what that entitlement is: a support interface. It is not ChaRM, and it will not carry a release process.
Three remedies, and what each actually costs
The first is to keep an on-premise maintenance agreement. If you retain any SAP product under on-premise maintenance, the Solution Manager entitlement survives — along with the perpetual licence and, if you’ve taken it, extended maintenance to 2030. For organisations moving only part of the estate, this is often already true and needs confirming rather than solving. It’s also the remedy most likely to disappear quietly, because as the remaining on-premise footprint retires, the entitlement retires with it. That’s a dependency with its own expiry date, and I’ve not yet seen an organisation tracking it.
The second is to subscribe to Solution Manager, private cloud edition. This is a real offering from SAP Enterprise Cloud Services, created specifically to give cloud-only customers access and usage rights to a Solution Manager 7.2 system in the private cloud. Worth knowing what you’re buying before anyone quotes it: it comes in two versions, and only the full stack carries what you’d recognise as Solution Manager. SAP is also explicit that it arrives unconfigured — basic configuration and process customising are yours to do or yours to pay for, on top of the subscription. So the cost isn’t the subscription. It’s the right tier, plus rebuilding your configuration in a new system, while running everything else. And the 2027 maintenance date still sits underneath it. This is a bridge, not a destination.
The third is to move to Cloud ALM. That’s SAP’s stated direction, entitlement is included with cloud subscriptions and Enterprise Support, and free usage runs to a baseline that covers almost every customer. It’s also, by SAP’s own account, not at parity — SAP says directly there is no feature parity between the two platforms. Whether Cloud ALM covers your ChaRM configuration is a scoping exercise, and it’s the one I’d run first, because the answer determines which of the three remedies you’re actually choosing between.
The shape of what’s being asked
You move your change governance — the control framework that produces your audit evidence — onto a new platform, on a deadline, while simultaneously running a conversion, a release upgrade and an integration rebuild. Same people, same twelve months.
And if you’re going to RISE, the clock on the thing you’re leaving may already be running.
That’s not an argument against Cloud ALM. Cloud ALM is where this is going, the entitlement is included, and it’s increasingly where agent observability lands too — which matters more every quarter.
It’s an argument against discovering the sequencing in month nine.
Why it’s missing from the business case
Because it isn’t a cost. It’s an entitlement change, and entitlement changes don’t generate a line item.
The RISE business case has a subscription figure, a migration figure, an infrastructure figure and a change-management figure. It rarely has a line for rebuilding change governance — because nobody costed it. The tool was always just there, included in an agreement that had been renewing since before most of the current team joined.
So start by establishing which clock you’re on. Confirm in writing whether you retain a Solution Manager usage right under your current agreement structure, and when that agreement actually terminates — that date, not a roadmap date, is the one that governs you. If the answer is yes via an on-premise agreement, find out what happens to it when the remaining on-premise footprint retires. Check whether you already hold extended maintenance for Business Suite 7, because if you do you have ChaRM to 2030 at no additional cost and considerably more room than you may think. Then scope Cloud ALM against your actual ChaRM configuration — not against Cloud ALM’s feature list, but against your approval workflow, your transport control, your release calendar, and whatever your external auditor has been shown for the last five years. The gap between those two lists is the real scope of the transition, and it’s a number you can produce in a fortnight.
This is one of five separate SAP clocks stopping in the same December, and the other four compete for the same people — which is next week’s problem.
Things that were always there don’t get costed. They get discovered.