The quarter in numbers
SAP reported Q2 2026 results on July 23, and the headline metric is momentum. Cloud revenue rose 22% as reported and 24% at constant currencies to 6.3 billion euros. Total revenue climbed 11% at constant currencies to 9.9 billion euros, and non-IFRS operating profit grew 9% on the same basis to roughly 2.7 billion euros. The figure that moved the story was current cloud backlog, which reached 22.9 billion euros, up 27% as reported and 26% at constant currencies. That backlog is the contractual value SAP expects to convert to cloud revenue over the next twelve months, so it reads as a forward order book for the entire migration wave.
CEO Christian Klein framed the quarter in plain terms: "Q2 was an outstanding quarter," adding that backlog growth of 26% marked "an acceleration compared to Q1." He noted a "welcome trend reversal" after two quarters in which backlog lagged cloud revenue growth. For readers who track SAP as a proxy for enterprise commitment, that reversal matters more than any single revenue line. It tells us that after a period of hesitation, large buyers returned to signing the long-dated contracts that fund SAP's transition and, by extension, lock in their own roadmaps for the rest of the decade.
Backlog reacceleration is the real signal
Cloud revenue tells you what customers spent last quarter. Backlog tells you what they promised to spend next. The 26% constant-currency jump is the number we would put in front of a board, because it shows demand strengthening at the exact moment many CIOs assumed budgets were freezing under AI-infrastructure pressure. SAP is converting the end-of-maintenance clock on legacy ERP into signed commitments, and the acceleration suggests the fence-sitters are running out of runway. Every quarter that backlog outpaces revenue, SAP builds a larger cushion of contracted growth that insulates it from the quarter-to-quarter caution we are seeing elsewhere in enterprise software.
There is a strategic read here for buyers. A reaccelerating backlog gives SAP pricing confidence, which means the discounts available during a hesitant market tend to narrow as commitment builds. If your organization is still weighing a RISE with SAP move, the leverage math is shifting toward the vendor. Klein's disclosure that more than 90% of the 50 largest deals embedded AI and SAP Business Data Cloud tells us those flagship contracts are bundling the premium components. The clean-core, AI-attached deal is becoming the default shape of an SAP renewal, and waiting does not make that bundle cheaper.
The margin trim and what it says about SAP's appetite
Against the growth, SAP lowered its 2026 operating profit outlook to reflect the dilutive impact of its Dremio and Prior Labs acquisitions. The company was explicit that the guidance update reflects M&A dilution rather than any softening in the core business, and it reaffirmed the cloud and revenue trajectory. Coverage of the earnings call pegged the trim at roughly 80 million euros against the prior range. For a company throwing off this much cloud growth, a modest profit haircut to fund data and AI capabilities is a defensible trade, and management clearly wants investors to read it that way.
The acquisitions themselves signal where SAP intends to compete. Dremio brings data-lakehouse query capability and Prior Labs adds AI tooling, both feeding the Business Data Cloud layer that Klein put at the center of the quarter's largest deals. We read this as SAP buying its way toward owning the data plane beneath enterprise AI, so that agents and analytics run on SAP-governed data rather than a third-party stack. For CIOs, that ambition cuts two ways: it promises tighter integration, and it deepens the dependency on a single vendor for both the system of record and the intelligence layer on top of it.
The Autonomous Enterprise sits at the center
Klein tied the quarter to what SAP now calls its Autonomous Enterprise strategy, citing momentum across the Autonomous Suite and the Business AI Platform. The pitch is that ERP stops being a passive system of record and starts running processes with embedded agents that act on live business data. The 90% AI attach rate across the largest deals is the evidence SAP wants us to weigh: its biggest customers are not buying clean-core migrations alone, they are buying the agentic layer at the same time. That bundling is how SAP converts an infrastructure migration into a durable AI relationship.
We would caution CIOs to separate the roadmap from the runtime. An AI attach rate measures what customers licensed, not what reached production, and the gap between the two is the central governance problem of this cycle. SAP's advantage is that its agents operate inside a governed data model with existing controls, which lowers some of the deployment risk that plagues bolt-on AI tools. The open question is whether Business Data Cloud delivers measurable process automation fast enough to justify the premium, or whether the attach rate becomes shelfware that inflates backlog without changing how the business actually runs.
What this means for the migration on your desk
For any enterprise still running legacy SAP, the backlog acceleration is a signal to move deliberately rather than reactively. The contracts SAP is signing now define the reference architecture, the pricing bands, and the AI bundle that later buyers inherit. If you enter the negotiation as demand strengthens, you have less room to unbundle Business AI Platform components you may not be ready to operate. The disciplined path is to scope the migration around the modules you will genuinely run, secure multi-year price protection, and resist paying today for agentic capabilities your teams cannot yet govern or measure.
The counterweight is optionality. A RISE commitment consolidates infrastructure, software, and services under SAP, which simplifies vendor management and reduces integration overhead. It also concentrates risk in a single relationship at the moment SAP is expanding into the data and AI layers that used to be a competitive market. The right posture treats this quarter's numbers as confirmation that the migration window is real and closing, then negotiates hard on the terms that preserve your ability to bring your own data tools and models where the economics favor it.
The concentration question CIOs should own
SAP's Q2 makes the strategic direction unmistakable: it wants the system of record, the data cloud, and the agent layer to be one governed stack. That vision is attractive for the integration and control it promises, and it is exactly why boards should scrutinize the concentration it creates. When one vendor owns your finance core, your master data governance, your process mining licensing, and the AI that acts on all of it, your negotiating leverage at the next renewal depends entirely on how portable that data and those processes remain. The clean-core discipline that SAP preaches is also the practice that keeps your exit costs bounded.
The pragmatic conclusion is to treat SAP as a strategic platform while engineering for portability at the seams. Insist on documented data-extraction paths, keep integration logic outside proprietary layers where feasible, and benchmark the AI attach against real production outcomes before expanding it. SAP delivered a genuinely strong quarter, and the backlog reacceleration is good news for the reliability of the vendor you may be betting a decade of operations on. The task for the CIO is to capture that stability without surrendering the leverage that keeps a long-term SAP relationship honest.
