SAP's Q2 beat was strong, but the real story is the forced migration clock behind it. ECC customers now have less than 18 months before mainstream support ends, and SAP's cloud backlog shows many of them are moving because they have to.
SAP gave investors the kind of quarter they wanted on July 23. In its quarterly statement for the three months ended June 30, 2026, the company reported total revenue of €9.878 billion, up 9% from a year earlier and ahead of SAP's own analyst consensus median of €9.849 billion. Cloud revenue reached €6.281 billion, up 22%. Current cloud backlog hit €22.929 billion, up 27%.
That backlog number deserves more attention than the revenue beat. Revenue tells you what SAP has already booked. Backlog tells you what customers have already committed to buy. For a company this large, a 27% rise is not background noise. It says enterprise buyers are signing before the bill comes due.
SAP also raised, or more accurately reset, its 2026 non-IFRS operating profit outlook to €11.8 billion to €12.2 billion at constant currencies. The company said the new range reflects more than €100 million of expected dilution from two acquisitions that closed in July: Dremio on July 6 and Prior Labs on July 16. Free cash flow for the quarter was €3.002 billion, up 27% from a year earlier. Solid numbers. The market could read them.
The deadline is doing sales work
The honest answer is deadline pressure as much as product pull. SAP's own maintenance page says mainstream maintenance for SAP Business Suite 7 core applications runs until the end of 2027, with optional extended maintenance available through the end of 2030. For most ECC customers, the key date is still December 31, 2027. After that, standard maintenance no longer carries the same safety net for routine support, legal updates and fixes unless customers pay for the extended path.
The math bites. SAVIC Technologies, citing Gartner and CIO research, says only about 39% of ECC customers had licensed S/4HANA by the end of 2024, leaving more than 60% of the installed base without the platform they need for the next phase. SAVIC also puts typical migrations at 18 to 36 months, with complex multi-country estates running even longer. If you haven't started by mid-2026, you're not planning early. You're racing the calendar.
That is why SAP's backlog looks so powerful. Every quarter of cloud growth includes some customers choosing new capability, but it also includes companies finally admitting that waiting is no longer neutral. A finance system does not become easier to move because the board waited another quarter. Custom code does not clean itself up. Testing does not shrink because the deadline is close.
Joule, SAP's generative AI assistant, gives the sales story a sharper edge. CIO reported in May that SAP's AI offer for on-premises legacy customers came with a condition: customers had to shift at least 50% of maintenance spending to the cloud before enabling Joule assistants on premises. That is a blunt lever. It turns AI curiosity into cloud commitment.
There is real product work underneath it. SAP's Help Portal lists Joule capabilities in S/4HANA Cloud Public Edition across finance, sourcing and procurement, sales, supply chain, asset management and other areas, including the ability to view business data and perform transactions in conversation. SAP also describes Joule Work as the place where assistants coordinate agents and workflows across SAP and non-SAP systems. If you've spent years inside SAP's older transaction-code world, that shift is not cosmetic. It changes where the work starts.
The work spills beyond SAP
A €22.9 billion cloud backlog also means a lot of implementation work SAP itself will not deliver. Accenture, Deloitte, Capgemini and regional SAP specialists are staring at a multi-year pipeline of conversions, data cleanup, testing and change management. That work is not theoretical. It sits inside live payroll systems, manufacturing runs, procurement approvals and financial close processes.
Startups near the SAP stack should pay attention too. Data migration tools, testing automation, custom extension builders, training software, security tooling, you name it. A forced platform migration of this size tends to feed the surrounding ecosystem, because customers need more than a license. They need a way to move without breaking the business.
Dremio and Prior Labs show SAP knows the migration wave has limits. SAP announced Dremio in May as a data lakehouse deal meant to connect SAP and non-SAP data for analytical and AI workloads. Prior Labs is more pointed. SAP said it will invest more than €1 billion over four years to scale the Freiburg-based company into a frontier AI lab focused on tabular foundation models, the kind built for structured business data rather than free-form text.
Frankly, the Q2 beat is almost secondary to what the backlog implies. SAP is growing because it owns software that many large companies depend on, and because the legacy version now has a visible clock on it. The companies that haven't started are not waiting for the perfect moment. They're running out of runway.
Also read: Y Combinator's Fall 2026 wish list puts a sitting Army Secretary in the founder pitch room • Trump's expanded AI data center pledge covers 80% of the U.S. grid but has no teeth to enforce it • Devin AI and GPT-5.6 Sol Ultra crack math problems that stumped researchers for half a century
