★ WIDE MOAT STOCKS & COMPETITIVE ADVANTAGES ★

Checking

Stock Profile

SAP SE (SAP) Moat Analysis

SAP SE

SAP · XETRA

Market cap (USD)$253.7B
SectorTechnology
IndustrySoftware - Application
CountryDE
Data as of
Moat score
89/ 100

Weighted average of segment moat scores, combining moat strength, durability, confidence, market structure, pricing power, and market share.

Request update

Spot something outdated? Send a quick note and source so we can refresh this profile.

Overview

SAP reports through Applications, Technology & Support, or ATS, at 90.2% of H1 2026 revenue and 97.4% of segment profit, and Core Services at 9.8% and 2.6%. The moat sits in ATS: ERP systems of record create workflow and data switching costs, suite economics support cross-sell, more than 3,600 SAP and partner solutions reinforce complements, and EUR 22.9 billion of current cloud backlog supports revenue visibility. The European Commission's July commitments give on-premise customers more freedom to unbundle maintenance and support, limiting one source of lock-in. Core Services has no separately proven moat because consulting remains substitutable. Cloud migration execution, specialist-software displacement, hyperscaler competition, portability rules, cyber incidents and architecture shifts are the main risks.

Primary segment

Applications, Technology & Support

Market structure

Oligopoly

Market share

HHI:

Coverage

2 segments · 5 tags

Updated 2026-08-23

Segments

Applications, Technology & Support

Enterprise application software suites, ERP-centric cloud subscriptions, software support, and platform services

Revenue

90.2%

Structure

Oligopoly

Pricing

moderate

Share

Peers

ORCLMSFTCRMNOW+1

Core Services

Enterprise software consulting, implementation, and premium support (SAP landscapes)

Revenue

9.8%

Structure

Competitive

Pricing

weak

Share

Peers

ACNIBMCTSHDXC

Moat Claims

Applications, Technology & Support

Enterprise application software suites, ERP-centric cloud subscriptions, software support, and platform services

H1 2026 ATS revenue was EUR17.522bn out of EUR19.432bn, with EUR7.137bn of EUR7.324bn segment profit. The resulting normalized shares use SAP's current two-segment reporting and actual-currency non-IFRS figures.

Oligopoly

Data Workflow Lockin

Demand

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 2 of 5

Core ERP and adjacent suites sit in the system-of-record layer; migrations and process redesign create high change costs.

Data Workflow Lockin moat: definition, examples, and stocks

Erosion risks

  • Rise of modular, API-first best-of-breed stacks reduces suite dependence
  • Customer migrations to competitor clouds during major ERP refresh cycles
  • Data portability and interoperability mandates

Leading indicators

  • Net retention / renewal rates for cloud subscriptions
  • Share of customers adopting S/4HANA Cloud vs legacy ECC
  • Customer reported churn or competitive displacement in large deals

Counterarguments

  • Large enterprises can multi-vendor and standardize on hyperscalers with alternative app ecosystems
  • Cloud-native ERPs can win greenfield deployments faster than SAP migrations

Suite Bundling

Demand

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 3 of 5

Evidence

Evidence 3 of 5

ERP-centered suite plus adjacent LoB apps and analytics/AI creates cross-sell and reduces point-solution penetration in core processes.

Suite Bundling moat: definition, examples, and stocks

Erosion risks

  • Customer pushback against bundled pricing
  • Legally binding EU commitments constrain on-premise maintenance and support bundling for ten years
  • Best-of-breed vendors winning specific LoB categories

Leading indicators

  • Attach rates of BTP / analytics / LoB apps to core ERP deals
  • Average contract value (ACV) expansion for existing customers
  • Competitive win/loss on core ERP with/without suite

Counterarguments

  • Enterprises increasingly procure modularly and integrate through iPaaS
  • Suites can lag specialist functionality, driving selective replacement

Ecosystem Complements

Network

Strength

Strength 4 of 5

Durability

Durability 3 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 3 of 5

Large partner ecosystem builds extensions and delivers implementation capacity, reinforcing SAP adoption and creating complements around BTP and ERP.

Ecosystem Complements moat: definition, examples, and stocks

Erosion risks

  • Partner talent shifts toward competing platforms
  • Quality/control issues in partner-delivered implementations
  • Platform commoditization reduces extension differentiation

Leading indicators

  • Number of active partners and certified consultants
  • Partner-sourced pipeline / % revenue influenced by partners
  • Marketplace extension growth and usage

Counterarguments

  • Systems integrators can be platform-agnostic and steer customers to alternatives
  • Partners capture much of services profit, limiting SAP ability to enforce quality/pricing

Long Term Contracts

Demand

Strength

Strength 3 of 5

Durability

Durability 2 of 3

Confidence

Confidence 4 of 5

Evidence

Evidence 3 of 5

Recurring support and cloud subscriptions (plus multi-year cloud backlog) increase revenue visibility and reduce short-term competitive pressure at renewal.

Long Term Contracts moat: definition, examples, and stocks

Erosion risks

  • Renewal repricing pressure during IT budget downturns
  • Customer migrations off maintenance to competitor SaaS during modernization cycles
  • Shorter contract durations in SMB/upper mid-market

Leading indicators

  • Cloud backlog / remaining performance obligations trend
  • Recurring revenue mix and renewal rate
  • Support revenue stability vs cloud migration pace

Counterarguments

  • Contracts renew, but customers can use renewal cycles to demand concessions
  • Cloud contracts can be repriced downward if value perception declines

Compliance Advantage

Legal

Strength

Strength 3 of 5

Durability

Durability 2 of 3

Confidence

Confidence 3 of 5

Evidence

Evidence 3 of 5

Capabilities oriented toward public sector and regulated customers (e.g., security, sovereign cloud initiatives) can be a differentiator in high-compliance deployments.

Compliance Advantage moat: definition, examples, and stocks

Erosion risks

  • Regulation changes faster than product/security roadmap
  • Government procurement shifts toward open standards and interoperability
  • Competition from hyperscaler sovereign cloud offerings

Leading indicators

  • Public sector cloud wins and renewals
  • Security/compliance certifications achieved and maintained
  • Incidents that trigger increased scrutiny (breaches, outages)

Counterarguments

  • Large competitors also invest heavily in compliance certifications and sovereign cloud
  • Public-sector buying can be price-sensitive and policy-driven

Core Services

Enterprise software consulting, implementation, and premium support (SAP landscapes)

H1 2026 Core Services revenue was EUR1.910bn out of EUR19.432bn, with EUR187m of EUR7.324bn segment profit. Revenue and profit both declined year on year, reinforcing the decision not to assign a separate moat to substitutable consulting and premium-support delivery.

Competitive

Insufficient segment-specific evidence to assign a moat claim.

Evidence

other

embedding agentic AI into end-to-end business processes

Positions SAP around cross-functional enterprise processes, consistent with workflow lock-in.

other

preserves mission-critical business context across all data

SAP Business Data Cloud emphasizes mission-critical data context, increasing migration and redesign friction.

other

those using over four SAP solutions more than doubling since 2021

More than 20% of the customer base used over four SAP solutions in 2025, direct evidence of rising multi-product adoption rather than merely a broad catalog.

other

SAP manages ATS as one product portfolio; H1 Cloud ERP Suite revenue was EUR10.739bn of EUR12.244bn cloud revenue.

other

customers to choose different maintenance and support (M&S) service providers

This is material counterevidence: legally binding global commitments for ten years constrain on-premise support bundling, although they do not remove product-suite cross-sell.

Showing 5 of 14 sources.

Risks & Indicators

Erosion risks

  • Rise of modular, API-first best-of-breed stacks reduces suite dependence
  • Customer migrations to competitor clouds during major ERP refresh cycles
  • Data portability and interoperability mandates
  • Customer pushback against bundled pricing
  • Legally binding EU commitments constrain on-premise maintenance and support bundling for ten years
  • Best-of-breed vendors winning specific LoB categories

Leading indicators

  • Net retention / renewal rates for cloud subscriptions
  • Share of customers adopting S/4HANA Cloud vs legacy ECC
  • Customer reported churn or competitive displacement in large deals
  • Attach rates of BTP / analytics / LoB apps to core ERP deals
  • Average contract value (ACV) expansion for existing customers
  • Competitive win/loss on core ERP with/without suite

Keep the research going

Created 2025-12-30
Updated 2026-08-23

More Rankings & Systems

Curation & Accuracy

This directory blends AI‑assisted discovery with human curation. Entries are reviewed, edited, and organized with the goal of expanding coverage and sharpening quality over time. Your feedback helps steer improvements (because no single human can capture everything all at once).

Details change. Pricing, features, and availability may be incomplete or out of date. Treat listings as a starting point and verify on the provider’s site before making decisions. If you spot an error or a gap, send a quick note and I’ll adjust.