SAP Q2 2025 Results: What SAP's Commercial Pressure Means for Enterprise Buyers in 2026

Executive Summary

SAP's Q2 2025 financial results exposed a critical vulnerability in the company's cloud migration strategy. While headline numbers showed healthy cloud growth, the underlying metrics reveal that SAP is struggling to convert its installed ECC base to cloud. Only 39% of ECC customers had purchased S/4HANA licences by mid-2025—far below SAP's own migration targets. This creates extraordinary negotiation leverage for enterprise buyers in 2026.

When a vendor needs your deal more than you need theirs, commercial terms become negotiable. SAP's Q2 2025 results make this dynamic explicit. This analysis shows you how to read between SAP's earnings narrative to understand their commercial desperation, and how to use that intelligence to demand better contract terms, stronger pricing, and superior exit rights.

What SAP Actually Reported in Q2 2025

The Surface Story: Cloud Revenue Growth

SAP marketed H1 2025 results aggressively. Cloud and AI revenues grew. Cloud ERP bookings (RISE with SAP, GROW, Analytics Cloud) expanded. The narrative was simple: SAP is a cloud company now. Investors seemed to believe it.

But look deeper at what SAP's own earnings commentary revealed:

• Cloud Backlog Concerns: SAP disclosed that cloud backlog growth had decelerated. Cloud backlog is SAP's primary security blanket for investors—it represents contracted future revenue. When backlog growth slows, SAP's cloud migration bet is in trouble.
• Perpetual Licence Decline: Perpetual ECC and Business Suite revenues continued to contract. SAP is trying to kill perpetual ECC. But customers aren't moving fast enough.
• Maintenance Revenue Pressure: SAP's maintenance revenue (the cash goldmine from legacy systems) is still enormous but facing pressure from cloud migration. This creates conflict in SAP's own strategy.
• AI Unit Uptake Questions: SAP promoted AI Units aggressively in H1 2025, but there were no clear public disclosures about adoption rates. This silence is meaningful. When adoption metrics are hidden, adoption is slower than the vendor wants.

The real story is hidden in what SAP *didn't* emphasize: the company's failure to accelerate ECC-to-cloud migration at the pace it promised to investors.

The €2 Billion Migration Problem

Only 39% of ECC Customers Have Bought S/4HANA

SAP's own public commentary revealed a devastating statistic: approximately 39% of ECC customers had purchased S/4HANA licences by Q2 2025. This should be understood as a catastrophic miss on SAP's cloud migration roadmap.

What does this mean?

• 61% of ECC customers have not yet committed to S/4HANA. That's a huge portion of SAP's installed base still running legacy ECC R/3 systems, generating maintenance revenue but not driving cloud growth or AI Unit revenue.
• SAP's ECC 2027 deadline is now a crisis. SAP stopped supporting ECC 6.0 in 2023 and committed to ending all ECC 6.0 support by December 2027. With only 39% of customers migrated by mid-2025, SAP faced a two-year window to move 61% of its global customer base. That's impossible without massive price concessions.
• This creates a €2 billion+ hole in SAP's cloud revenue forecasts. If 61% of the installed base hasn't migrated, and SAP was banking on incremental cloud revenue from these migrations, the shortfall is staggering.

Why This Matters for Your Negotiations

When SAP approaches your organisation for ECC-to-cloud migration discussions—whether through a direct account executive, an audit offer, or a "compliance review"—the company is under commercial pressure to close the deal. SAP needs your licence purchase. This inverts the traditional buyer-seller dynamic where vendors hold the power.

The 39% problem means SAP will offer commercial incentives you would never have received in 2024:

• Large perpetual-to-cloud conversion credits (going beyond standard exchange rates)
• Longer contract flexibility and break-clause options
• Pricing caps on cloud consumption and AI Units
• Stronger service-level agreements and availability guarantees
• More generous exit terms from cloud subscriptions

The AI Revenue Narrative: Joule, Business AI, and Opaque Pricing

SAP's New Revenue Lever

In 2024, SAP began positioning itself as an AI-first company. By Q2 2025, this wasn't just marketing—it was core to SAP's growth narrative. Joule (SAP's generative AI assistant) and Business AI became premium add-ons to cloud subscriptions.

SAP introduced a new licensing dimension: AI Units. Unlike traditional named-user, enterprise, or server licencing, AI Units are opaque, consumption-based, and impossible to forecast accurately.

Why AI Pricing Is Deliberately Obscure

SAP insiders have been candid about AI Unit pricing: it is "neither transparent nor explainable." This is not a flaw. It is design.

Opaque pricing structures serve the vendor:

• Forecasting becomes impossible for buyers. Without clarity on how Joule usage maps to AI Unit consumption, without understanding unit cost structures, buyers cannot budget accurately. This uncertainty creates de facto lock-in.
• Price increases are hidden in consumption growth. SAP can adjust AI Unit pricing upward, and the change appears as higher consumption rather than higher unit cost. The audit trail becomes deliberately confusing.
• Buyers are discouraged from auditing usage. When the pricing model is unintelligible, buyers rationally stop trying to validate consumption accuracy. SAP benefits from this ignorance.
• Vendor lock-in intensifies. Once AI Unit consumption is embedded in your operations, switching vendors or disabling Joule/Business AI becomes operationally disruptive. SAP has created switching costs.

What This Means for Your Q2 2025 Cloud Negotiations

If you're discussing cloud migration or contract renewal with SAP in 2026, they will aggressively position Joule and Business AI as mandatory value-adds. Your negotiating leverage:

• Demand explicit AI Unit caps in your contract. Do not accept "consumption-based pricing" without absolute caps. Require SAP to guarantee maximum AI Unit consumption for a defined consumption window.
• Require transparent AI Unit pricing models. Get SAP to define in writing: How many AI Units does one Joule query consume? What are the per-unit costs? What happens if unit costs change? Demand pre-approval for any price adjustments.
• Negotiate AI Unit inclusions. Try to include a base allocation of AI Units in your cloud subscription without incremental cost. Make additional consumption opt-in rather than the default.
• Build kill-switch rights into your contract. Require the right to disable Joule/Business AI at any time without penalty. Don't let SAP create switching costs.

The Audit Connection: Why Q2 2025 Pressure Means More Audits in 2026

Historical Pattern: Missed Sales Targets → Audit Surge

There is a well-documented historical pattern in SAP's commercial strategy: when cloud migration bookings lag targets, audit volumes increase. This is not coincidental.

Audits generate compliance findings. Compliance findings create "remediation opportunities." SAP account executives then offer cloud licence purchases as the solution to audit-identified gaps. It's a three-step revenue recovery model.

Q2 2025 → H2 2025 & 2026 Audit Wave

Given SAP's disclosed Q2 2025 cloud migration shortfalls, you should anticipate:

• Increased audit activity in H2 2025 and Q1-Q3 2026. SAP's commercial teams are incentivised to close the 61% gap. Audits are a low-friction way to identify customers for cloud migration campaigns.
• More aggressive audit findings. When audits are quota-driven, findings become more expansive. What might have been a 10% user overages in 2024 becomes a 25% issue in 2026.
• Audit "opportunities" being packaged with cloud migration offers. Expect bundled proposals: "Resolve your audit findings AND migrate to S/4HANA on cloud, and we'll give you special pricing."
• Pressure to accept cloud as the "compliant" solution. SAP will position cloud migration as the cleanest way to resolve compliance gaps. This frames cloud as remediation, not a commercial decision.

What This Means for Your Next Renewal: Negotiating from Strength

Five Concrete Negotiation Demands

When SAP approaches you for contract renewal, migration discussion, or post-audit negotiation, you now understand the vendor's commercial vulnerability. Use this to extract:

The Timing Advantage

These demands are achievable in 2026 specifically because:

• SAP's fiscal year pressures align with your negotiation window. SAP's fiscal year ends 31 December. Q4 2026 is peak revenue-closure pressure. Your negotiation leverage peaks in Q4.
• The ECC 2027 deadline creates urgency for SAP, not for you. SAP has set 31 December 2027 as the ECC 6.0 end-of-support date. That deadline is SAP's problem. If SAP wants you to migrate before 2027, SAP will offer attractive terms.
• SAP's cloud migration targets remain unmet. The 39% problem persists into 2026. SAP cannot afford to lose deals over pricing. This creates unprecedented flexibility for buyer negotiation.

Reading SAP's Earnings Calls: A Buyer's Competitive Intelligence Guide

What to Listen For

SAP publishes earnings call transcripts quarterly. These documents contain explicit language about commercial priorities that enterprise buyers can weaponise in negotiations. Here's what to look for:

1. Cloud Backlog Language

When SAP discusses "cloud backlog," listen for:

• "Strong cloud backlog growth": Means SAP is securing commitments. Backlog growth is slowing, which signals weakness.
• "Accelerating cloud migration momentum": Corporate-speak for "we're behind plan, we're pushing harder." This signals desperation and negotiation opportunity.
• "Increasing customer consumption of cloud services": Avoiding language about "net new customers" suggests existing customer migration is the driver, not growth. Growth slowing = negotiation leverage for you.

2. Migration Targets and Achievement

SAP will occasionally disclose migration targets. The gap between target and achievement is your negotiation measure. In Q2 2025, the 39% ECC customer migration rate was the core vulnerability. Watch for similar disclosures.

3. AI Unit Language

When SAP discusses AI Units, look for:

• "AI Unit adoption" or "uptake": If SAP discusses adoption in vague terms (e.g., "growing adoption"), adoption is slower than desired. Vagueness = underperformance.
• "Enhanced AI Unit consumption models": This means SAP is changing how units are counted or priced. When vendors change metering models, the old model favoured the buyer. The new model favours the vendor.
• "Premium AI capabilities driving higher subscription value": Translation: "We're pushing customers to buy AI Units they don't need yet, to lock in consumption metrics."

4. Pressure Language: The Giveaway

SAP executives use specific phrases to signal commercial pressure:

• "Accelerating" (instead of "growing"): Admission of behind-target execution.
• "Increasing focus on" (instead of "delivering"): Priority shift. Why the shift? Because current priorities aren't working.
• "Strengthening customer engagement" (instead of "closing deals"): Euphemism for "we're having trouble converting customers."

When you hear these phrases in SAP's earnings calls, it signals a negotiation window. Note the date, and expect account executive contact within 6-8 weeks.

The 2026 Window: Peak Leverage Opportunity

Why 2026 is Different

Enterprise buyers have rarely enjoyed the negotiation leverage that exists in early-to-mid 2026. This is why:

• SAP's Q2 2025 results created an explicit migration shortfall. The 39% ECC conversion rate is now a matter of public record. SAP investors know the company is behind on cloud migration. SAP executives are under pressure to close the gap. You benefit from this pressure.
• The ECC 2027 deadline accelerates urgency. ECC 6.0 support ends 31 December 2027. That gives SAP 18-21 months to convert the remaining 61% of its ECC installed base. SAP cannot achieve this conversion without massive price concessions.
• Cloud competitive dynamics are tightening. Oracle, Microsoft (Dynamics 365), and others are aggressive in attacking SAP's cloud dominance. SAP cannot afford to lose deals to competitors. This drives down SAP's walk-away price.
• Your negotiation team has unprecedented information. You can read SAP's earnings calls, understand the 39% problem, comprehend the audit strategy, and walk into negotiations with forensic knowledge of SAP's commercial vulnerabilities. SAP account executives are rarely prepared for informed buyers.

Concrete Timeline

If you are planning contract renewal or migration discussion with SAP in 2026:

• Q1-Q2 2026: Begin preliminary discussions. Signal interest in cloud migration. Let SAP begin the sales process. Gather their proposals. Show you're seriously considering it.
• Q3 2026: Pause discussions. Let SAP sit with the deal in-flight. SAP's Q3 pressure to close will increase. Return to negotiations in mid-Q3 with tougher demands.
• Q4 2026 (Peak Leverage): Resume negotiations aggressively. Q4 is SAP's fiscal year-end crunch. Account executive quotas are on the line. This is when SAP will make its best commercial offer.

Timing your negotiation to align with SAP's fiscal year urgency is not sophisticated—it's standard buyer practice. But it's powerful.

Practical Next Steps: Preparing for Your 2026 Negotiations

Month 1: Build Your Intelligence File

• Download and read SAP's Q2 2025 earnings call transcript. Annotate the sections discussing cloud migration, ECC status, and AI Units.
• Identify the current SAP account executive assigned to your organisation. Learn their quota and commission structure (this information is sometimes available through LinkedIn or industry contacts).
• Document your current SAP licensing estate: perpetual ECC or Business Suite licence count, maintenance contract terms, any existing cloud subscriptions, AI Unit consumption (if applicable).
• Calculate what a conversion to cloud would cost under standard SAP pricing. This is your baseline negotiation anchor.

Month 2-3: Prepare Your Negotiation Roadmap

• Map your perpetual licence portfolio to potential cloud conversion rates. Use our table above to target 1.5x-2x conversion credits as a baseline demand.
• Develop three contract scenarios: (1) Renewal status quo, (2) Partial cloud migration, (3) Full cloud migration with exit options.
• Identify internal stakeholders: Finance (budgeting), Operations (service continuity), IT (technical requirements). Align them on negotiation priorities before SAP enters the room.
• Prepare questions for SAP that force transparency on pricing: "Show me the formula for AI Unit calculation." "What is the per-unit cost of AI Units?" "How will you measure consumption?" These questions expose SAP's opacity problem and demonstrate you're a sophisticated buyer.

Month 4+: Engage SAP from a Position of Strength

• When SAP initiates contact (and they will), respond positively but slowly. Signal interest. Don't close the deal in the first conversation.
• Request a detailed commercial proposal. Use SAP's proposal as the anchor point for your counter-demands. Every line item becomes negotiable when you've done your homework.
• Present your demands using the language from this analysis: "Given your Q2 2025 ECC migration achievement rate of 39%, we believe enhanced conversion credits of 1.75x are reasonable." This signals you've done your forensic analysis. SAP will take you more seriously.
• Hold firm on non-negotiables: AI Unit caps, exit flexibility, price escalation limits. These are the terms that protect your enterprise over a multi-year cloud journey.

Conclusion: The Reckoning Between SAP's Promises and Reality

SAP's Q2 2025 financial results exposed a fundamental gap between the company's cloud migration narrative and its real-world execution. Only 39% of ECC customers had purchased S/4HANA licences. Cloud backlog growth decelerated. The company's commercial pressure to close the ECC migration gap intensified. These are not abstract financial metrics. They are actionable intelligence for enterprise buyers.

When a vendor urgently needs to convert your installed base, when audit activity spikes to fill sales pipeline gaps, when contract flexibility suddenly becomes negotiable—these are the moments when buyer negotiation power peaks. 2026 is that moment for SAP.

Enterprise buyers who read this analysis and prepare accordingly will extract contract terms in 2026 that would have been impossible to achieve in 2024 or 2025. Larger conversion credits, longer flexibility windows, harder caps on AI Unit consumption, more transparent pricing—all become achievable when you understand the vendor's commercial vulnerability.

SAP's Q2 2025 results aren't just financial history. They're a roadmap to your negotiation victory.