NextFin News - SAP’s cloud transition is still doing the job management promised it would do: turning a legacy maintenance schedule into recurring revenue growth. In the first quarter of 2026, SAP said cloud revenue rose 19% year on year to €5.962 billion, while current cloud backlog reached €21.932 billion, up 20% from a year earlier. The company also kept full-year cloud revenue guidance at €25.8 billion to €26.2 billion. Those numbers matter because the older Business Suite 7 and ECC systems are now running toward a firm maintenance cliff, with mainstream support set to end in 2027 and extended maintenance to end in 2030.
The central question is not whether SAP can keep growing cloud revenue. It can, and it is. The question is how much of that growth is still a normal software upgrade cycle and how much is a structural conversion forced by time. The answer is increasingly structural. Once a vendor tells customers that mainstream maintenance ends in 2027 and extended maintenance ends in 2030, the incentive to wait gets weaker by the quarter. For large enterprises running payroll, procurement, supply chain and financial controls on SAP systems, that deadline is no longer a theoretical future problem. It is a budgeting and risk-management problem today.
The latest quarter shows the mechanism clearly. Backlog is the bridge between sales pressure and future revenue, and SAP’s current cloud backlog of €21.932 billion means the migration pipe is not just open; it is already loaded. Cloud ERP Suite revenue rose to €5.214 billion in Q1, up 23% year on year and 30% at constant currencies, which suggests the company is not merely winning infrastructure deals but pulling customers into its core application suite. That distinction matters because suite migration is harder to unwind than a narrow product swap. It embeds SAP deeper in the customer workflow and makes later switching costs higher, not lower.
The support deadline is the real lever. SAP told customers that Business Suite 7 mainstream maintenance runs through the end of 2027 and extended maintenance through the end of 2030. In a vendor relationship built on uptime and compliance, maintenance is not an abstract line item. It is the service that keeps systems patched, supported and operational. When that service runs out, delaying migration becomes a cost trade-off, not a strategic stance. That is why SAP’s cloud growth can keep surprising the market even when the top-line narrative is already familiar: the deadline changes the customer’s option value. The longer they wait, the more expensive waiting becomes.
“We had a strong start to the year, with Current Cloud Backlog growing by 25% and Cloud Revenue up 27% at constant currencies.”
That quote from SAP’s investor-relations material is useful because it ties growth to both demand and visibility. Revenue alone can flatter. Backlog alone can mislead. Together, they show a company still converting the old installed base into a subscription stream. The fact that SAP kept cloud revenue guidance for 2026 at €25.8 billion to €26.2 billion reinforces that this is not a one-quarter spike in sentiment. It is a plan with a full-year runway.
The market already knows the story in broad outline. SAP has been telling investors for years that cloud and AI are the destination, and it has repeatedly pushed customers toward RISE with SAP and related migration programs. What the market still has to decide is whether the support cliff creates a durable re-rating or just front-loads revenue. That is the second-order issue. The first-order read is simple: customers migrate, cloud revenue rises. The second-order effect is more interesting: the composition of SAP’s revenue shifts toward recurring subscriptions and away from legacy support, which usually commands a better multiple because the cash flow is more visible and the customer relationship is stickier.
That does not mean the transition is linear. SAP itself said current cloud backlog growth should slightly decelerate in 2026, which is the first clue that the easiest conversions are not infinite. Large enterprise migrations are slow, expensive and operationally messy. The support cliff can pull demand forward, but it can also create a later digestion period once the obvious holdouts have moved. That is why this is structural in direction but cyclical in pace. The direction changes the business. The pace still moves with implementation capacity, budget windows and macro conditions.
Why The Maintenance Clock Changes Behavior
What exactly does a maintenance deadline do to a customer? It turns inertia into a measurable cost. A company can postpone a discretionary software refresh, but it cannot easily let core ERP systems drift when the patches, support and upgrade path are tied to a hard date. SAP’s 2027 and 2030 milestones therefore create a forced-choice environment. Customers can either pay to extend, accelerate migration or absorb more operational risk. None of those options are free. That is why the support schedule matters more than a normal product roadmap: it changes the economics of delay.
This is also why the cloud backlog is the more important indicator than the revenue beat. Revenue captures what has already happened. Backlog captures what is already committed. With €21.932 billion in current cloud backlog, SAP has built a sizeable buffer of future business that should flow through as migrations convert from planning to execution. The fact that backlog was up 25% at constant currencies while cloud revenue was up 27% at constant currencies shows the pipeline is still being replenished even as it is being harvested. That combination is what investors want in a transition story: enough backlog to support the near term, and enough actual revenue to prove the migration is real.
Why does this look structural rather than cyclical? Because the driver is not a temporary surge in demand or a one-off price increase. It is a permanent policy choice about support. The history of cyclical enterprise spending is full of delayed upgrades that eventually get deferred again when budgets tighten. This case is different because the cost of delay rises as the deadline approaches. A cyclical cycle needs demand to normalize and then mean-revert. A structural migration needs a rule change, and SAP’s support calendar is exactly that. The rule changes the customer’s decision function.
That does not make every quarter strong. It means the baseline of demand is higher than it would be without the deadline. It also means SAP’s cloud growth can survive a soft macro backdrop better than a typical discretionary software vendor. Enterprises can cut projects, but they are less willing to let core systems drift into unsupported territory. In that sense, the company’s maintenance policy is a form of commercial gravity.
There is a reason SAP keeps linking the story to Business AI as well as cloud ERP. The AI pitch helps management frame migration as modernization rather than compliance. That matters because it broadens the customer’s internal case for moving. A compliance argument gets signed when risk is intolerable. A modernization argument can win earlier, before the deadline has become painful. SAP is effectively trying to convert a forced move into a proactive one.
What The Market Has Already Priced, And Where It Can Still Be Wrong
Is the market already pricing this? Partly. SAP’s cloud transition is not a hidden catalyst, and the company’s 2026 cloud revenue guide was already public in April. But the market tends to price the headline growth rate more readily than the durability of the conversion path. What it may still be underpricing is the second-order quality shift: cloud revenue plus backlog visibility plus the steady erosion of legacy support revenue. That combination can matter more than a single-quarter beat because it changes the shape of earnings and cash flow over several years, not just one quarter.
Viewed that way, the strongest counter-thesis is not that SAP’s cloud story is fake. It is that the story is old and the easy upside has already been captured. Large customers know the deadlines. Consulting partners know the deadlines. Investors know the deadlines. If the market is already expecting migration, then only an acceleration versus those expectations should move the multiple materially. And SAP itself warned that backlog growth should slightly decelerate, which is a meaningful brake on the idea that the conversion wave can keep steepening.
That counter-view deserves respect because enterprise migrations are notoriously sticky. Budgets are finite. Integration work is hard. Not every customer can move on SAP’s timetable. If the migration turns out to be more lumpy than linear, the cloud growth rate may settle into a slower, more ordinary pattern even though the long-term direction stays positive. In that world, the support deadline still matters, but it functions more like a sales accelerator than a full valuation reset.
The falsifying signal for the structural thesis is clear: if current cloud backlog growth falls sharply and stays below cloud revenue growth for several quarters, while cloud revenue itself slows materially from the low- to mid-20% constant-currency range and the 2027 deadline fails to pull remaining customers forward, then the deadline is not a regime change. It is just a timing tool. If that happens, the market should stop treating the support cliff as a multi-year growth engine.
For now, the evidence still leans the other way. The company’s own numbers show a business that is not merely defending share but monetizing an installed base that has to move. That is different from a generic cyclical upswing. It is a policy-driven transformation of demand.
What Comes Next By Time Horizon
In the short term, SAP should continue to benefit from the visibility that backlog provides and from the steady conversion of legacy customers into cloud contracts. That does not guarantee a straight line in the share price or the revenue profile, but it does make the operating story more predictable than a pure discretionary software cycle. The immediate beneficiaries are the cloud and migration businesses; the exposed group is the legacy revenue base that shrinks as customers move.
In the medium term, the focus shifts to whether backlog growth remains healthy as the most urgent migrations are completed. If SAP keeps showing cloud revenue above the pace of broader revenue growth, the market will likely continue to reward the mix shift. If the backlog starts to flatten, the market may conclude that the deadline pulled forward more demand than it created. That is the next test: not whether migration exists, but whether it can keep compounding after the most obvious holdouts move.
In the long term, the support cliff is structural because enterprise architecture rarely reverts once a platform move is done. The real long-run question is what happens after the forced migration wave peaks. Can SAP keep turning the new cloud base into durable expansion through AI, suite adoption and cross-sell, or does growth settle back to the low end of enterprise software norms once the legacy base is mostly gone? That answer will determine whether the transition becomes a one-time conversion or a lasting re-rating story.
The base case is that SAP keeps converting the installed base, backlog stays supportive and cloud revenue continues to outgrow the broader business. The upside case is that AI-linked products and suite migration keep the funnel open longer than expected, extending the transition beyond the initial support dates. The downside case is that migrations slow after the easiest customers move, backlog growth decelerates faster than management expects and the market starts treating the deadline as a timing device rather than a growth driver.
The key numbers to watch are simple: backlog growth, cloud revenue growth and the pace of legacy support decline. If those stop moving in the same direction, the story weakens fast. If they keep moving together, SAP’s maintenance calendar remains one of the most reliable demand engines in enterprise software.
SAP is not just selling cloud software. It is selling time, and the clock is finally working in its favor.
Explore more exclusive insights at nextfin.ai.
