SAP SE: SAP SE is an enterprise software company founded in 1972. It reported $39.7B in FY2025 revenue and is led by Christian Klein.
SAP SE: Key Facts
| Company Name | SAP SE |
|---|---|
| Founded | 1972 |
| Founder(s) | Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther |
| Headquarters | Walldorf, Germany |
| Industry | Enterprise software |
| CEO | Christian Klein |
| Employees | 109K |
| Market Cap | $210.0B |
| Revenue (FY2025) | $39.7B |
| Stock Symbol | SAP (NYSE) |
| Website | https://www.sap.com |
| Last Reviewed | 2026-05-02 |
| Data As Of | 2025 |
- Revenue sourced to SEC filing and/or company annual report
- Primary sources include SEC filings, annual reports, and investor materials where available
- For informational purposes only - not financial advice
- Last updated: May 2026
In March 2024, SAP briefly became the most valuable company in Europe. Not a bank, not an oil major, not a luxury house — a German enterprise software firm that most consumers have never heard of. That fact alone tells you something important about where economic power actually lives.
SAP doesn't make anything you'd recognize on a shelf. It makes the systems that track what's on the shelf, who ordered it, what it cost, when it shipped, and whether the supplier got paid. Roughly 77% of global transaction revenue runs through SAP software at some point. That's not a marketing claim — it's a structural reality of how multinational commerce operates. When a Fortune 500 CFO closes the books, when an automotive plant schedules production across fourteen countries, when a pharmaceutical company validates a batch for regulatory submission — odds are, SAP is underneath.
FY2025 revenue hit $39.7 billion. Net income: $7.9 billion. The company employs about 109,000 people and serves over 400,000 customers. But the number that actually matters right now is $25.6 billion — that's the current cloud backlog, representing contracted future revenue that hasn't been recognized yet. It grew 25% year-over-year. That backlog is the clearest signal that SAP's massive cloud transition isn't just a strategy deck. It's converting.
SAP SE: Key Facts
- SAP SE was founded in 1972.
- Founded by Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther.
- Headquarters: Walldorf, Germany.
- Country: Germany.
- CEO: Christian Klein.
- Approximately 109K employees worldwide.
- Market capitalization: $210.0B.
- Annual revenue: $39.7B (FY2025).
- Net income: $7.9B.
- Publicly traded: SAP.
- Industry: Enterprise software.
- Listed on a public stock exchange.
- Founded in 1972 by Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther.
- Headquartered in Walldorf, Germany.
- Leadership field lists Christian Klein in the reviewed record.
- Latest reviewed revenue is $39.7B for FY2025.
- SAP SE's latest reviewed revenue is $39.7B.
- SAP SE's strategy: SAP is moving customers to cloud ERP, Business Technology Platform, data products, and AI copilots while simplifying its portfolio.
- SAP SE's main risk: The main exposures are cloud migration complexity, competition from Oracle and Workday, execution of AI monetization, and customer transformation fatigue.
SAP SE: SAP SE: SAP SE Company Timeline
Five former IBM employees founded Systemanalyse Programmentwicklung to build real-time, integrated business software.
Dietmar Hopp, Hasso Plattner, Claus Wellenreuther, Klaus Tschira, and Hans-Werner Hector founded Systemanalyse Programmentwicklung to build real-time business software. The founding mattered because large companies were still relying on batch processing and custom systems for critical records. [source]
SAP launched its first financial accounting system, RF, with the R standing for real time. [source]
The RM materials management system connected purchasing, inventory management, and invoice verification. [source]
The company began developing R/2, expanding from early modules toward a broader enterprise software suite.
SAP began developing R/2, the second generation of its software, as it moved toward a broader mainframe-based suite. R/2 helped turn customer-specific lessons into repeatable enterprise software for larger organizations. [source]
R/3 brought SAP into the client-server era and supported international ERP adoption.
The R/3 success story began in 1992 as client-server architecture opened a new growth phase. The product helped multinationals standardize operations across countries, subsidiaries, currencies, and business functions. [source]
The first customers started using HANA, creating the database foundation later used by S/4HANA.
SAP says the first customers started using the in-memory database HANA in 2011. HANA mattered because it reduced reporting latency and became the technical foundation for S/4HANA. [source]
S/4HANA became the next-generation ERP platform and a core part of the cloud migration strategy.
SAP launched S/4HANA four years after the first HANA customers. The product tied ERP modernization to in-memory computing and later became the centerpiece of the company's cloud migration strategy. [source]
The company introduced a generative AI copilot for cloud enterprise applications.
SAP announced Joule in September 2023 as a natural-language copilot embedded across its cloud enterprise portfolio. The launch showed that the company wanted AI tied to business context in HR, finance, supply chain, procurement, and customer experience workflows.Joule generative AI copilot is announced is supported by the 2023 source, so the timeline rests on a verifiable event. [source]
SAP completed the LeanIX acquisition in November 2023. LeanIX added enterprise architecture management tools that help customers assess IT landscapes and plan modernization programs, which fits the S/4HANA migration agenda. [source]
The WalkMe acquisition added digital adoption tools for business transformation programs.
SAP completed the WalkMe acquisition in September 2024 with an equity value of about US$1.5B. WalkMe added digital adoption technology intended to guide users through workflows across business applications. [source]
FY2025 reporting showed EUR21.0B in cloud revenue and 86% more predictable revenue.
The FY2025 integrated report data shows EUR36.8B in total revenue, EUR21.0B in cloud revenue, and 86% more predictable revenue. These figures show the financial scale of the cloud transition and the importance of recurring revenue. [source]
What Is the History of SAP SE?
The board at Imperial Chemical Industries' German subsidiary probably didn't realize they were making history in 1972. They just needed their financial accounting to stop lagging behind reality by twenty-four hours. But when they handed that problem to a scrappy five-person outfit called Systemanalyse Programmentwicklung — five guys who'd just walked out of IBM Germany — they became the first customer of what would eventually process 77% of the world's transaction revenue.
Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, and Claus Wellenreuther didn't leave IBM because they hated the company. They left because IBM kept canceling the projects they cared about. The five had been working on an internal initiative to build integrated business applications — software that could connect accounting to inventory to purchasing in real time — and IBM shelved it. The founders took the idea with them. Not the code. The conviction.
Their first office was in Weinheim, not the Walldorf campus people associate with SAP today. The early product, retroactively called R/1, did one thing that no enterprise software of the era did well: it processed financial transactions as they happened, on a single shared database, rather than batching them overnight. That sounds trivial now. In 1972, it was borderline radical. Most corporations ran separate programs for payroll, inventory, and accounting, each maintaining its own data, each producing reports that were already stale by the time a manager read them.
The credibility problem was severe. Here were five former employees of a hardware giant, asking conservative German industrial firms to trust their payroll, their tax filings, their materials planning to a startup's software. The founders solved this the hard way: they sat inside customer operations for weeks, learned how procurement clerks actually processed purchase orders, watched how plant managers tracked materials, and then wrote modules that mirrored those real workflows. Every implementation taught them something that went back into the product. That's the origin of SAP's deepest competitive trait — it doesn't just sell software, it sells codified business processes.
R/2 arrived in 1979 and changed the commercial model entirely. Instead of custom projects for each client, SAP now had a standardized mainframe suite that could be configured for different industries. A chemical company and an automotive manufacturer could run the same core system with different parameters. That repeatability created a flywheel that still spins today: more customers meant more process knowledge, which improved the software, which attracted the next customer.
But the real inflection point — the moment SAP went from successful German software company to global infrastructure — was 1992. R/3 moved everything to client-server architecture just as globalization was forcing multinationals to standardize operations across dozens of countries, currencies, and subsidiaries. The timing was almost absurdly perfect. Companies needed one operating language for finance, logistics, and HR across borders. R/3 was that language. Within a few years, every major consulting firm had built an SAP practice, and the ecosystem became self-reinforcing in ways the founders probably never imagined when they were debugging accounting modules for ICI in a rented office.
SAP SE was founded in 1972 in Walldorf, Germany by Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther. The company operates in Enterprise software and is led by Christian Klein. Revenue model: SAP earns revenue from cloud subscriptions, software support, licenses, services, and enterprise applications across finance, supply chain, HR, procurement, and analytics. SAP SE reported $39.7B in revenue for fiscal year 2025. Market capitalization stands at approximately $319.9B. The company employs approximately 109K people globally. Competitive position: SAP's advantage is its embedded ERP footprint, mission-critical business processes, enterprise data, and deep industry-specific workflows. Strategic direction: SAP is moving customers to cloud ERP, Business Technology Platform, data products, and AI copilots while simplifying its portfolio.
Early Challenges
SAP had to win trust before it could sell scale. In 1972, the founders were a small group of former IBM employees asking conservative industrial customers to run critical accounting and materials processes on standard software. They worked close to early customers such as the German subsidiary of Imperial Chemical Industries and built practical modules before the company had a large brand. The early test was whether real-time, integrated business software could be reliable enough for finance and operations; that credibility later made R/2 and R/3 possible.
Pivot
SAP moved from mainframe-centered systems toward client-server architecture with R/3.
Pivot
SAP moved into in-memory computing through HANA, reducing reporting latency and creating a database foundation for later ERP modernization. The shift required deep product work because core applications had to use a different data architecture.
Pivot
SAP pushed customers toward S/4HANA Cloud and subscription pricing as enterprise software buying moved toward SaaS. The transition increased recurring revenue potential but also made migration cost and change management central customer concerns.
Pivot
SAP sharpened its focus on industry cloud, S/4HANA migration, Business Technology Platform, and portfolio simplification. The change responded to customers that wanted cloud modernization without losing industry-specific process depth.
SAP SE: SAP SE: Expert Analysis
Editor's Note
The lazy reading of SAP is that it is a slower European software company trying to catch up with American cloud vendors. We think that misses the central fact of the business. SAP was not based on delighting a department head with a standalone application; it was centered on standardizing the operating logic of large companies. That design choice from 1972 still explains why FY2025 revenue reached $39.7B and why customers keep renewing systems they may also complain about. What the market often misses is the difference between user preference and institutional dependency. A sales team can dislike a tool and still switch to another CRM over several quarters. A global manufacturer cannot casually replace the software that connects materials planning, procurement, tax, inventory valuation, supplier payments, and financial close. SAP's least fashionable characteristic, its process depth, is also the reason competitors struggle to dislodge it at the core. The Qualtrics episode is useful because it shows both ambition and discipline. SAP paid $8B in 2018 for a company with a strong experience-management story, then later stepped back when the fit with the ERP-centered strategy looked less compelling. That was not a small mistake, but it clarified the portfolio. Under Christian Klein, SAP has become more focused on S/4HANA Cloud, Business Technology Platform, business transformation management, and AI embedded in operational workflows. Hasso Plattner's HANA bet remains the underappreciated strategic event. The company did not defend ERP by adding a thin analytics layer. It rebuilt the database foundation and then used that architecture to create S/4HANA. That matters because real enterprise modernization is rarely a front-end redesign; it is usually a deeper change in data structures, transaction speed, integration, and governance. There are reasons to stay skeptical. Migration fatigue is real. Oracle can use database and finance relationships to pressure SAP. Workday can keep winning HR buyers who want a simpler cloud-native experience. Microsoft can surround SAP with Azure, Teams, Power Platform, Fabric, and Copilot. Our thesis is that SAP's future will be decided by conversion quality, not announcement volume. Joule, WalkMe, LeanIX, Signavio, BTP, and Industry Cloud only matter if they make it safer for customers to move the operating core into the cloud. The question for the next cycle is whether SAP can make modernization feel less like a forced migration and more like the rational next chapter of systems customers already rely on.
Strategic Insight
Everyone focuses on SAP's technology — HANA, S/4HANA, Joule, BTP. But the real strategic asset is something far less glamorous: institutional memory.
A large SAP customer doesn't just store data in the system. They store decisions. Twenty years of purchase orders encode supplier relationships. A decade of financial closes encode accounting judgments. Custom workflows encode organizational politics that nobody remembers the origin of but everyone depends on. That accumulated institutional knowledge is what makes SAP irreplaceable — not the database speed, not the UI, not the AI features.
This creates a paradox that most analysts miss. SAP can't innovate too aggressively without threatening the very thing customers value most: continuity. If SAP forced customers to abandon their customizations, rebuild their integrations, and retrain their teams every five years, the switching cost argument would collapse. Customers stay because SAP promises to carry their institutional memory forward through each technology generation — from R/3 to ECC to S/4HANA.
The AI opportunity is real precisely because of this dynamic. Generic AI (ChatGPT, Copilot) can summarize documents and write emails. But it can't tell a CFO why Q3 margins in the Brazilian subsidiary dropped 200 basis points, cross-referenced against supplier price changes, currency movements, and production schedule delays — all within the context of that specific company's data. Joule can, because it sits on top of the transactional record. If SAP executes this correctly, institutional memory becomes institutional intelligence. That's the upgrade path that justifies the valuation premium.
SAP SE: SAP SE: Founders
Hasso Plattner
Hasso Plattner became SAP's most visible technical founder and one of the most influential figures in enterprise software. He helped shape the company's early product logic, supported the R/3 breakthrough, and later pushed SAP toward in-memory computing through HANA. After serving in executive roles, he became chairman and continued to influence long-term technology direction. Plattner's lasting impact is the belief that business software should be redesigned at the data and architecture layer when customer requirements change. That philosophy is visible in the HANA-to-S/4HANA transition and in SAP's current effort to build AI on top of trusted business data. Beyond SAP, he funded research and education initiatives, including the Hasso Plattner Institute, reinforcing his reputation as both technologist and institution builder.
Dietmar Hopp
Dietmar Hopp played a central role in SAP's early commercial and operational development. He helped the company move from founder-led projects into a repeatable enterprise software business serving industrial customers. After SAP became a global company, Hopp became known as an investor and philanthropist, funding healthcare, education, sports, and regional development projects in Germany. His lasting influence on SAP is visible in the company's emphasis on long-term customer relationships and operational seriousness. SAP's early success depended on convincing buyers that standardized software could handle real business complexity, and Hopp was part of the founding team that made that credible. His post-SAP work also reflected the wealth creation and institution-building effect of Germany's most successful software company.
How Does SAP SE Make Money?
SAP's revenue model is deceptively simple at the top level — sell software subscriptions to large companies — but the mechanics underneath reveal why this business is so durable and so difficult to replicate.
Start with the numbers: $39.7 billion in FY2025 revenue, split across four streams that are shifting fast. Cloud subscriptions are now the dominant growth engine. In Q1 2026 alone, cloud revenue hit $7.0 billion, growing 27% year-over-year in constant currency. That's not a rounding error on a $40 billion base — it's a structural acceleration. Software support (annual maintenance from on-premise customers) still generates substantial recurring income at margins above 90%, but it's a melting ice cube as customers convert to cloud. Traditional license revenue — the old model of selling perpetual software rights — has shrunk to near-irrelevance in new bookings. Services revenue covers consulting, implementation, training, and premium support.
The real insight into SAP's economics isn't the revenue split. It's the switching cost architecture. A typical large SAP customer has 15-25 years of transaction history embedded in the system. Country-specific tax configurations for every jurisdiction they operate in. Custom approval workflows that took a decade to build. Integration points with hundreds of surrounding applications — payroll providers, banking systems, logistics platforms, regulatory reporting tools. Ripping that out isn't a technology project. It's an organizational near-death experience. That's why SAP's customer retention rates stay high even when satisfaction surveys are mediocre.
The cloud transition is being packaged through two commercial programs. RISE with SAP targets large enterprises moving complex on-premise landscapes to managed private cloud. GROW with SAP targets midmarket and greenfield customers adopting public cloud with faster deployment. Both bundle infrastructure, migration tooling, Signavio process intelligence, and LeanIX architecture planning into a single commercial relationship. The packaging matters because it converts what used to be a scary multi-vendor transformation into a single contract with SAP.
SAP spends roughly $7 billion annually on R&D — maintaining the ERP platform, building cloud infrastructure, developing AI through Joule, and extending the Business Technology Platform. That's capital-light compared to hardware companies but heavy compared to pure SaaS vendors, because SAP has to maintain backward compatibility with decades of customer customizations while simultaneously building forward.
The 86% predictable revenue figure (combining cloud subscriptions and software support) is the metric that explains the valuation. At roughly $210 billion market cap — about 5.3x trailing revenue — investors are paying for the combination of high retention, expanding cloud margins, and the structural tailwind of the 2027 maintenance deadline that creates a multi-year pipeline of forced migration activity. Every customer who hasn't moved to S/4HANA Cloud is, in effect, pre-sold revenue waiting to convert.
Revenue Streams
- Cloud subscriptions: Cloud subscriptions
- Software support: Software support
- Licenses: Licenses
- Services: Services
What Products and Services Does SAP SE Offer?
SAP S/4HANA Cloud (Cloud ERP)
SAP's current-generation ERP suite runs finance, procurement, manufacturing, supply-chain, and reporting workflows on the HANA architecture. It is the central product in SAP's migration from on-premise license economics to recurring cloud subscriptions.
SAP Business Technology Platform (Platform and integration)
BTP combines integration, analytics, database, application development, automation, and AI services so customers can extend SAP systems without altering the ERP core. It is strategically important because it keeps data and custom workflows inside the SAP ecosystem.
SAP SuccessFactors (Human capital management)
SuccessFactors provides cloud HR tools for recruiting, performance management, learning, workforce planning, and employee records. SAP uses it to compete with Workday and to keep HR data connected to finance and operations.
SAP Ariba (Procurement network)
Ariba supports sourcing, supplier management, procurement, and business network transactions between buyers and suppliers. It extends SAP's role from internal ERP processes into external supplier collaboration.
SAP Concur (Travel and expense management)
Concur manages corporate travel booking, expense reporting, invoice capture, and spending controls. Its value rises when companies connect employee spending with finance, compliance, and reimbursement workflows.
SAP HANA (Database and analytics)
HANA is SAP's in-memory database architecture that supports real-time transaction processing and analytics. It became the technical foundation for S/4HANA and SAP's broader data strategy.
SAP Signavio (Business process transformation)
Signavio helps customers model, analyze, and improve business processes before and during ERP transformation. It supports SAP's effort to make migration less risky and more measurable.
Joule (Business AI copilot)
Joule is SAP's generative AI copilot embedded across cloud applications to answer business questions and automate workflow steps. Its monetization depends on whether customers see measurable productivity gains inside SAP processes.
What Is SAP SE's Competitive Advantage?
Ask any enterprise CTO why they haven't replaced SAP, and you'll get the same answer in different words: "We can't." Not "we don't want to" — we literally cannot, without risking operational collapse.
That's not hyperbole. A large SAP customer typically has 15-30 years of transaction history in the system. Tax configurations for 40+ countries. Custom approval workflows that encode institutional knowledge nobody documented anywhere else. Integration points with banking systems, logistics providers, regulatory bodies, and hundreds of internal applications. The data model isn't just storing information — it IS the company's operational memory. Replacing it would be like performing a brain transplant on a patient who needs to keep working full-time during surgery.
The numbers bear this out: SAP estimates 77% of global transaction revenue touches its systems. That's not market share in the traditional sense. It's infrastructure penetration. When Walmart processes a purchase order, when Siemens schedules production across fourteen plants, when Nestlé consolidates financial results across 188 countries — SAP is the substrate.
Beyond raw lock-in, there's a knowledge advantage that's genuinely hard to replicate. SAP has spent fifty years encoding industry-specific business processes. Automotive supply chain sequencing. Pharmaceutical batch validation. Oil and gas joint venture accounting. Utility meter-to-cash workflows. These aren't features you can build in a hackathon. They represent decades of sitting inside customer operations and learning how regulated, complex industries actually work. Workday can't replicate that in HR alone. Salesforce certainly can't from the CRM layer.
Then there's the ecosystem effect. Over 25,000 partners — Accenture, Deloitte, IBM, Capgemini, and thousands of specialized firms — have built their consulting practices around SAP. Millions of professionals worldwide are trained on SAP systems. That creates a self-reinforcing cycle: companies stay on SAP partly because it's easier to find implementation talent for SAP than for any alternative. The ecosystem IS the advantage, as much as the software itself.
SAP's competitive moat in enterprise resource planning is perhaps the most underestimated in all of enterprise software. SAP ERP systems run the core financial, manufacturing, supply chain, and human resources processes for 77% of the world's transaction revenue — meaning that more than three-quarters of all commercial transactions globally touch an SAP system at some point in the value chain. The S/4HANA migration cycle creates a multi-decade runway of consulting, licensing, and cloud subscription revenue as 30,000+ enterprise customers transition from legacy SAP ECC systems to the cloud-native platform. Each migration represents $10-500 million in total project cost for large enterprises — a switching barrier that makes SAP's customer base effectively permanent.
Who Are SAP SE's Main Competitors?
The company that should worry Christian Klein most isn't Oracle, even though Larry Ellison's team is aggressively targeting SAP's installed base with Oracle Cloud ERP migration incentives. It's Microsoft. And the reason is strategic geometry, not product quality.
Oracle attacks SAP head-on: replace the ERP, replace the database, replace the stack. That's a frontal assault, and frontal assaults against entrenched infrastructure rarely succeed at scale. SAP customers have 15-30 years of transaction history, tax configurations for 40+ countries, and integration points with hundreds of surrounding systems. Oracle's converged-stack pitch — why run SAP on our database when you could just run our applications? — is intellectually clean but operationally terrifying for most CIOs.
Microsoft plays a different game entirely. Azure hosts SAP workloads. Teams replaces SAP's collaboration layer. Power Platform automates workflows that used to require SAP customization. Copilot answers operational questions that Joule wants to own. Fabric consolidates analytics data that BTP is designed to capture. Microsoft doesn't need to rip out SAP's ERP core. It just needs to surround it — capturing the growth budget while SAP retains the maintenance revenue. Death by a thousand integrations rather than a single replacement decision.
Workday occupies a narrower but painful position. In HR and finance for companies that don't need deep manufacturing or supply chain integration, Workday's cloud-native deployment speed genuinely embarrasses SAP's transformation timelines. Months versus years. SuccessFactors competes directly, but Workday's brand among HR buyers remains stronger, and every HR win gives Workday a foothold to expand into adjacent finance processes.
ServiceNow is eating workflow automation. Salesforce owns the customer-facing layer. Dozens of vertical SaaS startups are nibbling at industry-specific processes that SAP bundles but doesn't always execute brilliantly.
SAP's defense is integration depth that no single competitor can replicate. Multinational accounting, procurement, manufacturing planning, tax compliance, master data governance, and regulatory reporting within one transactional system — that's not a feature list, it's a moat measured in decades of accumulated process knowledge. The acquisitions of LeanIX and WalkMe are tactical acknowledgments that the moat only holds if the migration journey feels manageable. Make it too painful, and customers will look around while they're in transit. Make it smooth enough, and the 77% of global transaction revenue that already touches SAP stays exactly where it is.
How Has SAP SE's Revenue Grown Over Time?
The most interesting number in SAP's financials isn't the $39.7 billion top line. It's the gap between cloud growth and total growth.
Total revenue grew in the low double digits in FY2025. Cloud revenue grew 27% in Q1 2026. That divergence tells you exactly what's happening: SAP is cannibalizing its own maintenance revenue — deliberately — to build a faster-growing, higher-quality subscription base. The old model (sell a perpetual license, collect 22% annual maintenance) generated fantastic margins but lumpy, decelerating revenue. The new model (cloud subscriptions with expansion over time) sacrifices near-term revenue per customer but creates a compounding base.
Net income of $7.9 billion on $39.7 billion in revenue gives you roughly 20% net margins — respectable for enterprise software but not yet at the 25-30% level that pure cloud companies achieve at scale. That gap is the transition tax. As the cloud mix increases and implementation services become a smaller share, margins should expand. SAP's own guidance implies this trajectory.
The current cloud backlog of $25.6 billion is the forward-looking metric that matters most. It represents contracted revenue that hasn't been recognized yet — essentially, money in the bank that will flow through the income statement over the next 12-24 months. Growing at 25% year-over-year, it provides the kind of revenue visibility that makes CFOs sleep well.
One financial fact that deserves more attention: SAP's market cap briefly exceeded $320 billion in early 2025, making it the most valuable company in Europe. For a firm that sells back-office software to other businesses — no consumer brand, no viral growth, no hardware margins — that valuation reflects something profound about where durable economic value actually accumulates.
Revenue History Source: SEC filing
| Fiscal Year | Revenue | Net Income | Source |
|---|---|---|---|
| 2017 | $28.2B | — | Annual Report / Investor Relations |
| 2018 | $26.7B | — | Annual Report / Investor Relations |
| 2019 | $29.8B | — | Annual Report / Investor Relations |
| 2020 | $29.5B | — | Annual Report / Investor Relations |
| 2021 | $29.1B | — | Annual Report / Investor Relations |
| 2022 | $31.9B | — | Annual Report / Investor Relations |
| 2023 | $33.7B | — | Annual Report / Investor Relations |
| 2024 | $36.9B | — | Annual Report / Investor Relations |
| 2025 | $39.7B | — | Annual Report / Investor Relations |
What Companies Has SAP SE Acquired?
| Year | Company | Value | Strategic Purpose | Outcome |
|---|---|---|---|---|
| 2010 | Sybase | $5.8B | SAP acquired Sybase to strengthen database, mobile, and data-management capabilities as enterprise computing moved toward real-time analytics and mobile access. | The deal supported SAP's data and mobile ambitions, though HANA became the more important long-term architecture. Sybase's value was strongest as a bridge into database independence and enterprise mob |
| 2011 | SuccessFactors | $3.4B | SAP acquired SuccessFactors to enter cloud human capital management across large volumes and respond to the rise of SaaS HR competitors. | SuccessFactors remains a central SAP cloud product and helped shift the company toward subscription revenue. The integration challenge persisted, but the deal clearly expanded SAP's cloud relevance. |
| 2012 | Ariba | $4.3B | SAP acquired Ariba to expand into cloud procurement and supplier network transactions. | Ariba became a key part of SAP's business network strategy. The deal achieved its strategic goal by giving SAP a durable procurement cloud asset tied closely to ERP data. |
| 2014 | Fieldglass | Undisclosed | SAP acquired Fieldglass to add vendor management and external workforce capabilities. | Fieldglass strengthened SAP's spend-management suite and broadened the company's workforce story. Its impact is meaningful but more specialized than SuccessFactors or Concur. |
| 2014 | Concur | $8.3B | SAP acquired Concur to enter cloud travel and expense management at global scale. | Concur remains an important SAP cloud application. The deal gave SAP scale in travel and expense, although the pandemic later pressured corporate travel volumes and highlighted the need for broader sp |
| 2018 | Qualtrics | $8.0B | SAP acquired Qualtrics to combine operational data from SAP systems with experience data from customers, employees, products, and brands. | SAP later spun off Qualtrics, making the deal a mixed outcome. It influenced SAP's data narrative, but the separation showed that attractive SaaS assets only create lasting value when they strengthen |
| 2021 | Signavio | Undisclosed | SAP acquired Signavio to help customers analyze, redesign, and improve business processes during transformation projects. | The acquisition fits SAP's cloud migration agenda well because customers need process visibility before changing ERP systems. Its success depends on how deeply SAP embeds it into transformation progra |
| 2023 | LeanIX | Undisclosed | SAP acquired LeanIX to add enterprise architecture management and help customers map complex IT landscapes. | LeanIX is strategically coherent because it addresses the planning work that slows ERP modernization. Its long-term value depends on attach rates to RISE with SAP and S/4HANA projects. |
| 2024 | WalkMe | $1.5B | SAP acquired WalkMe to improve digital adoption, workflow guidance, and user productivity across SAP and non-SAP applications. | The acquisition directly targets migration friction, one of SAP's biggest obstacles. It is too recent for a full financial verdict, but the strategic fit is clearer than the Qualtrics deal. |
SAP SE: SAP SE: Controversies & Legal Issues
2010 — Oracle TomorrowNow intellectual-property lawsuit
Oracle accused SAP subsidiary TomorrowNow of improperly downloading Oracle software and support materials. SAP admitted wrongdoing related to the subsidiary, and the case became a major reputational setback because it involved direct misconduct in enterprise software support.
Outcome: SAP shut down TomorrowNow and ultimately resolved the dispute through a large settlement and governance changes.
2019 — European scrutiny of licensing and ecosystem practices
SAP faced public and regulatory attention in Europe over software licensing, indirect access, and the degree of control it exerted over customers and partners. The criticism reflected a broader concern that mission-critical software vendors could use complex contracts to limit customer flexibility.
2021 — U.S. Export-control settlement
U.S. Authorities said SAP allowed software access in restricted countries, exposing weaknesses in compliance controls across global cloud and software operations. The matter was serious because SAP serves regulated multinational customers that expect strict controls over access and data use.
Outcome: SAP cooperated, paid penalties, and strengthened export-control monitoring and internal compliance systems.
2021 — Qualtrics spin-off strategy criticism
SAP's decision to take Qualtrics public after buying it for $8B raised questions about whether the acquisition had been strategically coherent. Investors questioned whether SAP had overpaid for an attractive SaaS asset that did not fit cleanly with core ERP priorities.
Outcome: The spin-off helped SAP simplify its story and refocus on cloud ERP, BTP, data, and AI, but the episode remains a capital-allocation caution.
Who Leads SAP SE?
Hasso Plattner
Chairman (2003–present)
As chairman, Hasso Plattner shaped the era in which SAP had to defend ERP against database rivals, cloud challengers, and changing customer expectations. His most important decision was backing HANA, an expensive in-memory computing bet that gave SAP control over a deeper layer of its architecture. That decision later enabled S/4HANA and gave SAP a technical answer to Oracle's database strength. Plattner also supported long-term R&D investment even when short-term investor pressure favored easier margin expansion. The measurable outcome was a rebuilt product foundation that still anchors SAP's
Bill McDermott
CEO (2010–2019)
Bill McDermott led SAP through a more aggressive global sales and acquisition era. He expanded SAP's U.S. Profile and used deals including SuccessFactors, Ariba, Fieldglass, Concur, and Qualtrics to build a larger cloud application portfolio. Those decisions helped SAP catch up in SaaS categories where cloud-native rivals were gaining attention. The tradeoff was complexity: the company inherited multiple platforms, cultures, and user experiences that later had to be integrated. The measurable outcome was a broader cloud revenue base and stronger brand visibility, but also a strategic cleanup j
Christian Klein
CEO (2020–present)
Christian Klein's era is defined by focus. He pushed SAP toward S/4HANA Cloud migration, Business Technology Platform, business AI, and a clearer portfolio after the acquisition-heavy period. He supported the Qualtrics separation, strengthened transformation-management assets through LeanIX and WalkMe, and positioned Joule as an AI layer for business workflows rather than a generic assistant. The measurable outcome is a higher cloud mix and FY2025 revenue of $39.7B, with SAP reporting a high share of more predictable revenue. His remaining test is whether migration can scale without exhausting
Henning Kagermann
CEO (1998–2009)
Henning Kagermann led SAP after the R/3 expansion era and through the shift toward service-oriented architecture, global scale, and broader enterprise applications. His leadership professionalized SAP as a global public company and helped it defend the ERP core while expanding into adjacent business software categories. Kagermann also oversaw the period when SAP had to respond to internet-era expectations and a more aggressive Oracle. The measurable outcome was a larger international footprint and a stronger enterprise customer base that later became the installed foundation for cloud migratio
How Is SAP SE Growing?
SAP's growth story comes down to one massive bet: converting 400,000+ customers from on-premise ERP to cloud subscriptions before competitors can poach them during the transition chaos.
The forcing mechanism is the December 2027 end-of-mainstream-maintenance deadline for ECC 6.0. After that date, customers either pay premium extended maintenance rates through 2030 or migrate. That deadline isn't just a product lifecycle decision — it's the largest coordinated enterprise software migration in history, creating a multi-year pipeline of consulting demand, subscription conversion, and platform expansion.
Two commercial programs carry the execution. RISE with SAP wraps infrastructure, migration tooling, Signavio process intelligence, and LeanIX architecture planning into a single contract for large enterprises. GROW with SAP does the same for midmarket customers with faster deployment and lower upfront cost. The packaging is strategic: it turns a terrifying multi-vendor transformation into one relationship with one throat to choke.
Beyond the migration itself, SAP is making a calculated bet on AI as a retention and expansion lever. Joule isn't a chatbot bolted onto the side of the product. It operates within live business data — answering questions about specific purchase orders, flagging budget variances, suggesting actions on supplier delays. The thesis is that AI built on twenty years of a customer's actual transaction data is fundamentally more useful than generic AI that doesn't know the difference between that company's approved suppliers and its blacklisted ones.
The industry cloud strategy is the quieter but potentially more durable play. Vertical-specific processes for automotive, retail, utilities, banking, and healthcare create switching costs that horizontal competitors like Oracle or Workday can't easily replicate. A generic ERP can handle accounting. Only SAP's automotive industry cloud handles sequenced just-in-time delivery scheduling across a multi-tier supplier network with country-specific customs documentation. That specificity compounds over time.
Everything depends on one variable: conversion velocity. If SAP can move its installed base to S/4HANA Cloud at a pace that outstrips customer patience for alternatives, the math is straightforward — $25.6 billion in current cloud backlog growing 25% annually compounds into a $50+ billion revenue business by 2028 with cloud margins expanding toward 75%. The December 2027 end-of-mainstream-maintenance deadline for ECC 6.0 is the forcing function, but forcing functions only work when the alternative is worse than compliance. If enough large enterprises decide that paying premium extended maintenance through 2030 is less painful than a $20-100 million transformation, the conversion timeline stretches and the growth premium in SAP's $210 billion valuation starts to look fragile. Oracle doesn't need to win these customers outright. It just needs them to hesitate long enough to take a meeting. The AI layer through Joule adds a wrinkle: customers who convert early get twenty years of transactional data feeding contextual intelligence that late movers won't have. That creates a first-mover advantage within SAP's own base — an unusual dynamic where the vendor's most loyal customers become its best-served ones. Whether that's enough to turn migration fatigue into migration urgency is the $50-80 billion question separating a 15% grower from a 10% grower.
What Are the Biggest Risks Facing SAP SE?
The most dangerous thing happening to SAP right now isn't Oracle or Workday. It's migration fatigue.
Here's the problem: SAP has told 400,000+ customers that their current systems hit end-of-mainstream-maintenance in December 2027. That deadline is supposed to create urgency. And it does — but it also creates resentment. Moving from ECC 6.0 to S/4HANA Cloud isn't a software upgrade. It's a business transformation that can cost $20-100 million for a large enterprise, take 2-4 years, and require redesigning processes that have been stable for decades. Many CIOs are privately furious about being forced into this on SAP's timeline.
That resentment creates a competitive opening that didn't exist five years ago. When a company has to undergo massive disruption regardless, the switching cost argument weakens. Oracle is aggressively targeting SAP's installed base with Oracle Cloud ERP, offering migration incentives and a simpler converged stack. Some customers are genuinely evaluating alternatives for the first time in twenty years — not because Oracle's product is obviously better, but because if you're going to suffer through a transformation anyway, why not at least look around?
The AI monetization question is subtler but potentially more consequential. SAP is embedding Joule across its portfolio, but enterprise buyers are deeply skeptical of paying premium prices for AI features that haven't proven ROI. If generative AI becomes a table-stakes expectation — something every vendor includes for free — then SAP's billions in AI investment won't generate incremental revenue. It'll just be the cost of staying relevant.
Finally, there's the margin compression problem that nobody talks about publicly. Cloud subscriptions initially generate less revenue per customer than the old license-plus-maintenance model. SAP is essentially trading high-margin support revenue for lower-margin cloud revenue in the short term, betting that volume and expansion will compensate over time. That bet is probably correct, but it creates quarterly earnings pressure that makes Wall Street nervous.
SAP SE: SAP SE: Quick Reference Q&A
Q: When was SAP SE founded?
A: SAP SE was founded in 1972 by Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther.
Q: Where is SAP SE headquartered?
A: SAP SE is headquartered in Walldorf, Germany.
Q: Who is the CEO of SAP SE?
A: The CEO of SAP SE is Christian Klein.
Q: What is SAP SE's annual revenue?
A: SAP SE reported annual revenue of $39.7B in FY2025.
Q: How many employees does SAP SE have?
A: SAP SE employs approximately 109K people worldwide.
Q: What is SAP SE's market cap?
A: SAP SE's market capitalization is approximately $210.0B.
Q: What is SAP SE's stock ticker?
A: SAP SE trades under the ticker SAP on the NYSE.
Q: What country is SAP SE from?
A: SAP SE is a Germany-based company.
Q: What industry is SAP SE in?
A: SAP SE operates in the Enterprise software industry.
Q: What companies has SAP SE acquired?
A: SAP SE has acquired Sybase, SuccessFactors, Ariba, among others.
Q: How does SAP SE make money?
A: SAP's revenue model is deceptively simple at the top level — sell software subscriptions to large companies — but the mechanics underneath reveal why this business is so durable and so difficult to replicate. Start with the numbers: $39.7 billion in FY2025 revenue, split across four streams that are shifting fast. Cloud subscriptions are now the dominant growth engine. In Q1 2026 alone, cloud rev
Q: What does SAP SE do?
A: SAP SE is the world's largest enterprise application software company, providing ERP, supply chain, HR, finance, procurement, and industry-specific business software to 400,000+ customers in 180+ countries. Founded in 1972 in Walldorf, Germany by five former IBM engineers, SAP reported $39.7B in FY2025 revenue with $7.9B net income. Q1 2026 showed strong cloud momentum: cloud revenue grew 27% (con
Q: How did the US Export Control Violations case affect SAP SE?
A: SAP was fined by US authorities for violating export control laws related to sales to restricted regions. The company allowed unauthorized access to software in certain countries. The violations occurred over multiple years due to compliance failures.
Q: migration economics at SAP SE?
A: The first challenge is migration economics. Moving from ECC or heavily customized on-premise systems to S/4HANA Cloud can require process redesign, data cleanup, testing, training, and partner consulting, so many customers treat it as a multi-year business program rather than a software upgrade.
Q: How does SAP SE's revenue mix actually work?
A: SAP SE earns through Cloud subscriptions, Software support, Licenses, Services. SAP earns money from cloud subscriptions, software support, licenses, and services tied to enterprise applications.
Q: Which competitor pressure matters most for SAP SE?
A: SAP SE is compared against oracle-corporation, microsoft-corporation, salesforce-inc. SAP competes layer by layer rather than in one neat category.
Q: How should readers interpret $39.7B for SAP SE?
A: Start with SAP SE's $39.7B FY2025 revenue, then separate license history from cloud conversion quality.
Q: What strategic decision most shaped SAP SE's current model?
A: The growth plan is based on converting the installed ERP base to cloud while adding products that reduce migration pain.
Q: What is SAP SE's primary revenue source?
A: SAP SE's revenue profile is based on Cloud subscriptions, Software support, Licenses, Services. The file reports $39.7B in FY2025, so the revenue model should be read through those disclosed streams rather than a generic industry label.
SAP SE: SAP SE: Frequently Asked Questions: SAP SE
Who is the CEO of SAP SE?
The CEO of SAP SE is Christian Klein. The company was founded in 1972.
What is SAP SE's annual revenue?
SAP SE reported approximately $39.7B in annual revenue. See the financials page for the full revenue history.
How does SAP SE make money?
SAP's revenue model is deceptively simple at the top level — sell software subscriptions to large companies — but the mechanics underneath reveal why this business is so durable and so difficult to replicate. Start with the numbers: $39.7 billion in FY2025 revenue, split across four streams that are shifting fast. Cloud subscriptions are now the dominant growth engine. In Q1 2026 alone, cloud rev
What does SAP SE do?
SAP SE is the world's largest enterprise application software company, providing ERP, supply chain, HR, finance, procurement, and industry-specific business software to 400,000+ customers in 180+ countries. Founded in 1972 in Walldorf, Germany by five former IBM engineers, SAP reported $39.7B in FY2025 revenue with $7.9B net income. Q1 2026 showed strong cloud momentum: cloud revenue grew 27% (con
When was SAP SE founded?
SAP SE was founded in 1972, by Dietmar Hopp, Hasso Plattner, Hans-Werner Hector, Klaus Tschira, Claus Wellenreuther, in Walldorf, Germany.
How did the US Export Control Violations case affect SAP SE?
SAP was fined by US authorities for violating export control laws related to sales to restricted regions. The company allowed unauthorized access to software in certain countries. The violations occurred over multiple years due to compliance failures.
migration economics at SAP SE?
The first challenge is migration economics. Moving from ECC or heavily customized on-premise systems to S/4HANA Cloud can require process redesign, data cleanup, testing, training, and partner consulting, so many customers treat it as a multi-year business program rather than a software upgrade.
How does SAP SE's revenue mix actually work?
SAP SE earns through Cloud subscriptions, Software support, Licenses, Services. SAP earns money from cloud subscriptions, software support, licenses, and services tied to enterprise applications.
Which competitor pressure matters most for SAP SE?
SAP SE is compared against oracle-corporation, microsoft-corporation, salesforce-inc. SAP competes layer by layer rather than in one neat category.
How should readers interpret $39.7B for SAP SE?
Start with SAP SE's $39.7B FY2025 revenue, then separate license history from cloud conversion quality.
What strategic decision most shaped SAP SE's current model?
The growth plan is based on converting the installed ERP base to cloud while adding products that reduce migration pain.
What is SAP SE's primary revenue source?
SAP SE's revenue profile is based on Cloud subscriptions, Software support, Licenses, Services. The file reports $39.7B in FY2025, so the revenue model should be read through those disclosed streams rather than a generic industry label.
SAP SE: SAP SE: Sources & References
- SAP official company history (2026) [official_company_source]
- SAP early years history (2026) [official_company_source]
- SAP Integrated Report 2025 financial data (2025) [annual_report]
- SAP investor relations reports (2025) [annual_report]
- SAP 2025 Form 20-F filing (2025) [sec_filing]
- SAP Joule announcement (2023) [news]
- SAP LeanIX acquisition completion (2023) [news]
- SAP WalkMe acquisition completion (2024) [news]
- SAP 2025 annual report [source]
- SAP restructuring announcement [source]
- Gartner Cloud ERP peer reviews market page [source]
- https://www.sap.com/about/company/history.
- https://www.sap.com/integrated-reports/2025/en/datahub/financial-data/five-year-summary.
- https://www.sap.com/investors/en/reports.
- https://www.sec.gov/Archives/edgar/data/1000184/000110465926020058/sap-20251231x20f.
- https://www.sap.com/about/company/history/1972-1980.
- https://data.sec.gov/api/xbrl/companyfacts/CIK0001000184.
- https://www.sap.com/documents/2026/02/408e3d6d-fd7e-0010-bca6-c68f7e60039b.
Bottom Line
SAP SE is a growing Enterprise software with $39.7B in annual revenue as of 2025. SAP's advantage is its embedded ERP footprint, mission-critical business processes, enterprise data, and deep industry-specific workflows. The primary risk: The main exposures are cloud migration complexity, competition from Oracle and Workday, execution of AI monetization, and customer transformation fatigue.
