SAP’s pre-Q3 2026 backlog test: contracted demand is not completed migration

By Sarah Chen, Lead SAP Architect, SAPExpert.AI
Market analysis | Reporting date: 13 October 2026

SAP’s €22.929bn current cloud backlog is strong evidence of contracted demand—and the wrong instrument for certifying a 2027 migration plan. At June 30, backlog grew 26% at constant currencies. Q2 cloud revenue also grew strongly, demonstrating monetization rather than merely accumulated commitments. Neither metric counts accepted production migrations. SAP Q2 financial statement

Reasonable inference: The defensible thesis is not that SAP’s migrations are failing. Contracted demand, revenue timing and deployment completion are different questions. Larger transformations may explain longer revenue ramps, but the supplied evidence does not establish their schedules or connect them to customer-level acceptance.

The investor’s test is whether commitments translate into revenue on an intelligible schedule. The buyer’s test is whether its charges, resources and accepted production scope align. This report’s five-part scorecard keeps those tests separate rather than treating SAP’s financial strength as project assurance.

This remains a pre-results assessment. A September 21 secondary preview schedules SAP’s Q3 call for October 21, 2026; it is not a Q3 financial disclosure. drillr Q3 earnings preview

1. What the market has actually measured

SAP defines current cloud backlog, or CCB, as contractually committed cloud revenue expected to be recognized over the upcoming 12 months. It includes new contracts and renewals; periods subject to specified termination rights are excluded. CCB is therefore a forward revenue stock—not quarterly new bookings, paid consumption or a migration-completion measure. SAP performance-measure definitions

The disclosed Q2 signals are substantial. All growth rates below are at constant currencies unless explicitly marked otherwise. SAP Q2 financial statement

Signal	Reported result	What it establishes—and what it does not
Current cloud backlog, June 30	€22.929bn; +26%, or +27% reported	Qualifying contracted revenue commitments within the next-12-month window; not a count of new migrations.
Q2 cloud revenue	€6.281bn; +24%	Revenue monetization; not the contribution from newly completed migrations alone.
Q2 Cloud ERP Suite revenue	€5.525bn; +27%	Strong monetization in the disclosed suite category; not accepted production scope or active-user evidence.
Q2 non-IFRS operating profit	€2.743bn; +9%, or +7% reported	A financial result influenced by more than deployment execution.

Renewals matter to commercial durability. Their inclusion also means that backlog growth cannot be interpreted as an equivalent increase in migration volume. The metric measures revenue commitments, not a population of customers transitioning to production.

Cloud revenue growth had been 27% in Q1, compared with 24% in Q2. That trajectory deserves monitoring, but comparing revenue growth with CCB growth does not produce a conversion rate. One measures a period’s revenue flow; the other measures a forward-looking stock whose contract composition can change. SAP Q2 presentation

For buyers, two boundaries are critical. The June 30 CCB window does not cover all of calendar 2027. Nor does SAP’s definition identify an individual buyer’s subscription-start trigger, invoice date, acceptance condition or termination liability. Excluding certain terminable periods from a financial metric does not confirm protective exit rights in a customer agreement. SAP performance-measure definitions

2. Large-deal ramps: plausible explanation, missing schedule

SAP’s January presentation reported year-end 2025 total cloud backlog of €77.288bn, growing 30%, against current cloud backlog of €21.052bn, growing 25%, at constant currencies. The divergence makes revenue timing relevant. It does not reveal the schedule of any particular transformation contract. SAP FY2025 presentation

An AI-generated Q4 summary attributes slower CCB growth to larger transformations with longer ramp periods. Its provenance is weaker than a primary transcript, and it contains a material unit error: it prints CCB as “€21 million,” whereas SAP reports €21,052 million, or €21.052bn. The primary figure controls; the causal explanation remains a hypothesis. Intellectia Q4 summary · SAP FY2025 presentation

Inference: Longer ramps are compatible with a healthy transformation pipeline. They are also compatible with commitments whose operational benefits arrive later. The distinction is not whether a deal is large, but whether its financial and delivery schedules are understood and mutually workable.

The missing analytical object is a consistent cohort bridge:

• How much growth comes from new contracts versus renewals or expanded scope?
• When do the relevant subscriptions start?
• Which quantities and fees step up, and when?
• How does recognized revenue relate to those schedules?
• Which corresponding production waves have been accepted?

The supplied excerpts provide neither quarterly new-bookings figures nor a large-deal backlog-to-revenue cohort bridge. They cannot establish the duration or effect of 2026 ramps.

Recommendation: Ask for consistently defined evidence, not simply a larger-deal narrative. An anonymized cohort view could improve market visibility. Procurement still requires the buyer’s own dates, charges, accepted scope and accountable delivery commitments.

3. The strongest counterargument: SAP is already monetizing

The strongest objection to a skeptical backlog reading is straightforward: SAP is not reporting only contracts. Cloud and Cloud ERP Suite revenue are growing materially. Those results weaken an “all demand, no activity” thesis. SAP Q2 financial statement

Christian Klein also attributes Q2 cloud revenue growth to “solid execution” of on-premise-to-cloud ERP migrations. He says AI and Business Data Cloud were embedded in more than 90% of the 50 largest deals. These are relevant management statements, but the excerpt provides no migration count, accepted-scope measure or completion denominator. Deal inclusion does not establish paid consumption or production use. Third-party-hosted Q2 transcript

Reasonable inference: Revenue growth and management commentary are consistent with meaningful migration activity. They do not establish its scale or allow buyers to extrapolate readiness to their own projects. Financial confidence and project approval need not move together.

The same distinction applies to strategy. Klein describes the Autonomous Enterprise launch at Sapphire; a strategy launch does not establish general availability, customer deployment or contractual delivery capacity. Q2 management commentary

SAP’s presentation displays AI process and productivity improvements alongside an internal efficiency-run-rate target exceeding €2bn by end-2028. Claimed customer/process gains and a future internal target are different evidence categories. The supplied excerpt lacks sufficient cohort, baseline and measurement detail to verify migration outcomes or transfer those claims into a buyer’s business case. SAP Q2 presentation

Slower profit growth is likewise not a proxy for migration delays. SAP says its 2026 profit outlook was updated for dilution from Dremio and Prior Labs; a deployment-only explanation would omit that disclosed factor. SAP Q2 financial statement

What would change this assessment?

A stronger completion conclusion requires verifiable production acceptance linked to contracted scope, subscription starts and ramp schedules, with a defined population and reporting period. Even a completion count needs a stable scope definition and denominator.

An execution-risk conclusion requires documented missed commitments, accountable delivery obligations and resulting commercial exposure. Missing disclosure alone establishes neither success nor failure. The present finding is an evidence gap, not a failed-migration verdict.

4. A buyer scorecard for 2027 plans

Recommendation: Approve commercial commitment and deployment readiness through separate gates. Do not average them into one reassuring status: a protected contract cannot substitute for production evidence, and a credible delivery plan cannot erase an unprotected charge ramp.

These are procurement checks, not claims about SAP’s standard terms.

• Green: Written and binding where contractual; verifiable where operational.
• Amber: Draft terms, incomplete evidence or sales assurance.
• Red: Missing, contradictory or commercially unprotected.

Check	Evidence required for green	Decision if unresolved
Subscription starts	By contracted scope: signing, service availability, subscription start, invoice start, planned go-live and acceptance dates. Identify the precise event triggering charges.	Resolve charge exposure before approval; do not assume these clocks coincide.
Staged charges	Dated quantities and fees, minimum commitments, step-ups, true-ups, unused entitlements and renewal assumptions. Document agreed milestone linkage or delay credits.	Model cash exposure independently of deployment progress; defer unprotected incremental commitments.
Delivery commitments	Migration waves, scope, accountable SAP/partner/buyer roles, committed resources, dependencies, acceptance criteria and dates; written escalation, change control and slippage remedies.	Treat an unresourced date as an assumption, not a commitment.
Deployment and outcome proof	Production acceptance by entity, process and wave; usage evidence and comparable references. For savings: baseline, measurement period, methodology and customer attestation.	Label delivery unverified—not failed. Separate AI entitlements from active consumption.
Maintenance and dual running	Written confirmation of product- and contract-specific support eligibility, end dates, overlap costs and exit conditions.	Keep budget assumptions open; do not rely on a universal deadline.

Separate the commercial clocks

The first task is reconciliation, not color assignment. Signing, availability, subscription commencement, invoicing, go-live and acceptance need not be the same event. The CCB definition cannot tell a buyer which one triggers its charges. SAP performance-measure definitions

Recommendation: Maintain one scope-level schedule containing all six dates, the charge trigger and the evidence supporting each entry. Model cash charges separately from vendor revenue recognition.

Compare calendar-based and milestone-linked step-ups on both charge certainty and pre-use exposure. If pursuing milestone linkage, define acceptance and the handling of delayed, disputed or changed milestones. Ask what remains payable during delay and how unused entitlements are treated. Do not assume credits exist until agreed.

Connect the plan to people and dependencies

Recommendation: For every wave, identify accountable SAP, partner and buyer roles, committed resources, required skills, dependencies and acceptance authority. Confirm that the resources support the dates used in the investment case.

Responsibility matters as much as timing. A missed date should be assessed against the agreed obligations and dependencies, not automatically attributed to SAP or the implementation partner. Change control should reconcile revised scope with dates, acceptance criteria and the fee schedule.

If value depends on an announced capability, request binding delivery scope rather than treating the announcement as an available production dependency. The supplied strategy commentary does not establish 2027 staffing or delivery capacity. Q2 strategy and execution commentary

Distinguish readiness, acceptance and value

Agreed acceptance criteria for a future wave demonstrate planning readiness—not completed deployment. Production acceptance establishes delivered scope; it does not, by itself, verify savings.

Recommendation: Keep separate records for contracted entitlement, accepted production scope, actual usage and measured outcomes. For claimed benefits, require the baseline, measurement period and methodology before incorporating them into an approved business case. Comparable references should support due diligence, not replace the buyer’s own acceptance evidence.

Verify maintenance rather than importing a deadline

A secondary migration thesis asserts a 2027 ECC mainstream-maintenance deadline and extended maintenance to 2030 with a surcharge. The packet contains no primary policy document establishing product-specific eligibility or terms. Keep 2027 as the buyer’s planning horizon, not a verified universal cutoff. Request written confirmation before budgeting support, overlap or exit costs. drillr migration thesis

Test negotiating flexibility—do not book it

UpperEdge argues that cost-management pressure could create commercial flexibility. This is an advisory inference, not an offered discount or contractual commitment. UpperEdge Q2 buyer commentary

Recommendation: Test clearer start triggers, staged quantities and slippage protection alongside price. A lower headline fee and protection against charges preceding productive use address different risks. Exclude prospective concessions from the approved budget until documented.

5. The pre-Q3 watchlist: test explanations, not percentages

The next disclosure can refine the financial trajectory. It establishes deployment completion only if it adds evidence beyond aggregate financial growth.

Recommendation: Compare current and total backlog, revenue periods and currency bases consistently. Look for separation of new contracts, renewals and scope changes, and for a ramp explanation that becomes measurable. Do not divide CCB growth by revenue growth and label the result migration conversion.

The useful scenarios are conditional decision paths, not forecasts:

Scenario	Evidence that would support it	Buyer response
Large-deal ramps become substantiated	A consistent backlog/revenue cohort bridge, dated ramp schedules and corresponding accepted production waves.	Align commitments with the validated schedule; retain wave-level acceptance controls.
Monetization advances, delivery visibility remains weak	Revenue continues to demonstrate monetization, but completion scope and denominators remain undisclosed.	Maintain separate commercial and deployment approvals; obtain project-level proof.
Execution risk becomes documented	Missed committed milestones, attributable delivery failures and identifiable charges or overlap costs before productive use.	Use agreed escalation and remedies; reconsider further unprotected commitments.

For investors, missing completion disclosure limits the operational conclusion without negating reported revenue. For buyers, stronger financial results do not resolve an incompatible charge and delivery schedule. Conversely, slower aggregate growth would not establish that an individual deployment has failed.

For partners and technical leaders, the actionable measure remains accepted scope against committed resources and dates. Vendor-level momentum cannot clear an individual production-acceptance gate.

What to do next

• Do now: Assign an owner to each scorecard row and reconcile subscription, invoice, charge-ramp and migration dates.
• Defer: Final reliance on a 2027 delivery date until resources, dependencies, acceptance criteria and slippage treatment are documented.
• Measure: Accepted scope, usage, schedule variance and dual-running exposure separately from contracted demand.
• Challenge: Request the large-deal cohort bridge and written support terms. Treat missing evidence as a due-diligence task—not automatic proof of failure.

Sources and limitations

This report uses only the supplied excerpts. Primary financial evidence comes from SAP’s Q2 statement, Q2 presentation and performance measures, dated July 23, 2026, plus the FY2025 presentation, dated January 29, 2026. These are document dates, not verified posting dates.

Management commentary comes from a truncated, third-party-hosted transcript. Secondary material includes the September 21 preview, September 3 migration thesis, July 27 buyer commentary and an AI-generated Q4 summary. Publication dates for the transcript and AI summary are unknown. The summary’s unit error is rejected; the migration thesis’s ambiguous metric periods and uncorroborated adoption estimates are not used to quantify completion.

Confidence is high in the reported metrics and backlog definition, limited in the large-deal ramp explanation, and insufficient to establish migration-completion rates or specific 2027 delivery readiness. No unseen document content, independent completion records or Q3 results have been assumed.