On January 29, 2026, SAP’s stock fell roughly 22%. Not from a scandal. Not from a product failure. From a guidance update about how quickly its installed base was converting to cloud software it had spent a decade building.
That sounds like a routine earnings miss. If you actually understand what ERP architecture does, it reads differently — as a market signal about the structural health of an entire software category.
SAP’s ECC end-of-life deadline is forcing a decision on tens of thousands of enterprises. The official answer SAP has been selling since 2015 is S/4HANA. Roughly 39% of SAP’s 35,000 ECC customers have taken it. The question for the other 61% is not just what to do about SAP — it is whether the monolithic ERP model itself is the right architectural foundation for the next decade. For a precise breakdown of what end of mainstream maintenance forces today, see our deadline explainer.
This article is our structured answer to that question. The honest verdict: “under structural pressure” rather than “obsolete” — but the evidence is specific and the argument is real. For the full decision-level detail, see our SAP ECC migration series.
Is the SAP Migration Crisis a Structural Inflection Point or Just an Upgrade Cycle?
Every ERP generation has had its painful upgrade cycle. SAP customers have been through R/2 to R/3, and every successive ECC version upgrade. Expensive, complained about, and eventually accepted — the installed base followed the path SAP laid out.
This cycle is different. That 39% migration figure across nearly a decade is not a typical adoption curve. Gartner projects 17,000 ECC customers — almost half the installed base — will still be on ECC when mainstream maintenance ends in 2027.
Here is the data point that matters. Bernstein Research analyst Mark Moerdler found that two-thirds of SAP’s new cloud customers are new to SAP entirely — not migrated ECC customers. A Freeform Dynamics survey of 455 organisations found 95% say building a positive ROI case for S/4HANA requires significant effort or is outright challenging. SAP’s own installed base is not following the intended path.
What makes this a structural inflection is that the installed base is routing around the official path. Kingfisher plc — the £13 billion UK retailer that owns B&Q and Screwfix — is the documented example. Rather than migrate to S/4HANA, Kingfisher moved its ECC system to Google Cloud with Rimini Street providing third-party support, then built an independent AI strategy using Google Cloud tools and Databricks.
The relevant analogy is the 2010s cloud disruption of on-premises software: installed base resistance, credible alternative paths, and growing VC investment. Whether this disruption follows the same arc is uncertain. But it is no longer a theoretical question.
Why Does $1.52 Trillion in Technical Debt Make This Moment Different?
The SAP ECC crisis is not a SAP-specific failure. It is one vivid instance of a structural problem running through enterprise software. The IT-CISQ 2022 report estimated accumulated software technical debt in the US at $1.52 trillion. Legacy systems consume resources that could fund modernisation — making modernisation progressively harder.
Monolithic ERP accumulates this debt in a specific way. Business processes are not documented externally — they are encoded inside the system. The finance workflow, the procurement approval chain, the inventory reconciliation logic: none of it lives in a process document. It lives in the ERP’s configuration. When support ends, you cannot simply move the data. You have to re-implement the business.
ECC migration costs range from $2 million for small organisations to over $1 billion for large enterprises. A Horváth study of 200 SAP user companies found migrations taking 30% longer than planned, with only 8% on schedule.
This is the structural trap. The more deeply a business is embedded, the more rational the deferral — until the deadline removes deferral as an option. “Just upgrade” is not a simple answer.
What Does the a16z Investment Thesis Actually Say About the Future of ERP?
In February 2025, Andreessen Horowitz published “The Opportunity for Next-Gen ERPs” — by partners Seema Amble, Eric Zhou, and Marc Andrusko. The thesis: the same conditions that enabled NetSuite to disrupt on-premises ERP are now emerging again, this time with AI-native ERP challenging cloud incumbents.
The NetSuite precedent is worth understanding. NetSuite was built for cloud-native mid-market when SAP and Oracle dominated on-premises. Oracle acquired it for $9.3 billion in 2016, roughly 15 years after launch. a16z argues AI is the equivalent forcing function — targeting two root causes of ERP failure: data ingestion (ERPs were not built for modern APIs) and data reconciliation (data failing to reconcile between sources like Salesforce and billing).
Rillet raised a $70 million Series B from a16z and ICONIQ in August 2025 — a16z putting capital behind its own analysis.
Is the analogy apt? The structural conditions are real. But AI-native ERP faces far more capable incumbents than NetSuite did in 2000, and the thesis depends on whether AI agents need clean modular data access to function — contested, not settled. Directionally credible. Not yet proven at enterprise scale.
Who Are the Next-Generation ERP Challengers and Are They Enterprise-Ready?
The a16z thesis named five AI-native ERP challengers. Doss raised an $18 million Series A (Theory Ventures, April 2025) — AI-native manufacturing and inventory management. Rillet raised $70 million Series B (a16z + ICONIQ, August 2025) — revenue accounting for SaaS companies. Campfire raised $3.5 million at Seed (June 2025) — SMB operations, earliest-stage and furthest from enterprise readiness. Toolkit is a fourth full AI-native rebuild. Endeavor is positioned as an AI engagement layer on top of existing ERP rather than a full rebuild.
The honest assessment: none of these have documented production deployments at the scale of a 500-person SAP ECC customer. Building vertically is architecturally sound — it is how credible challengers disrupt without replicating SAP’s horizontal breadth on day one. But it does mean they are not drop-in replacements.
What this means practically: track these for specific functional modules as part of a composable strategy. Think 3 to 5 years, not now.
For a deeper look at how composable ERP fits a near-term strategy, see composable ERP as the practical strategic alternative and how AI tools change the migration calculus.
SAP vs Oracle: Is Switching Vendors Just Trading One Lock-In for Another?
Oracle ERP Cloud (Oracle Fusion) is the primary incumbent alternative for large enterprises exiting the SAP ecosystem. If two-thirds of SAP’s new cloud customers are new to the vendor, as Moerdler found, then a substantial chunk of the ECC installed base moving to cloud ERP is choosing Oracle and others over S/4HANA. Oracle offers a fresh implementation rather than a constrained re-implementation inside SAP’s ecosystem.
The architectural counterpoint: Oracle ERP Cloud is also a monolithic integrated suite. Switching trades one vendor dependency for another. The architectural question about whether monolithic ERP can serve as a substrate for agentic AI orchestration applies equally to Oracle Fusion.
If your primary driver is escaping the specific complexity of the S/4HANA migration path, Oracle is a proven alternative. But you are solving the vendor lock-in problem specific to SAP, not the monolithic architecture problem.
What Did SAP’s 22% Stock Drop Actually Signal to the Market?
On January 29, 2026, SAP reported Q4 2025 results with cloud backlog deceleration guidance. The stock fell approximately 22%. Q4 2025 revenue was €36.8 billion, up 8% — the company is not in crisis. The drop was market pricing of risk.
Cloud backlog is the leading indicator of SaaS business health. When it decelerates, it signals that forward-contracted revenue — what SAP projected from ECC customers converting to S/4HANA cloud — is not materialising. SAP is acquiring new cloud customers, but its natural ECC migration cohort is not converting. Some are migrating to Oracle. Some are staying on ECC with third-party support.
For anyone thinking about architecture, the significance here is not SAP’s financial health — it is that institutional investors are now pricing the risk that the monolithic ERP conversion thesis will not materialise at scale.
Why Does Agentic AI Make Monolithic ERP Architecturally Problematic?
The architectural argument is real and specific — but the production evidence at scale is not yet there.
Agentic AI coordinates across procurement, finance, HR, and supply chain simultaneously — executing business processes that span multiple data sources and require cross-system action. To do this, it needs clean, modular, API-accessible interfaces.
Monolithic ERP’s structural constraint: data and business logic are deeply coupled within a single application layer. When an AI agent needs data across modules, it must work within the vendor’s own API surface and integration policy. The vendor controls the access layer.
The key framing here is “systems of record” — what monolithic ERP was built to be — versus “systems of action” — what agentic AI actually requires. In a composable architecture, each module exposes its own API surface. No single vendor controls the access layer.
What is settled: enterprises with composable architectures and open API access are better positioned to add agentic AI orchestration than those locked into monolithic systems.
Is Monolithic ERP Actually Obsolete or Just Under Structural Pressure?
Three structural forces are converging on monolithic ERP right now.
Commercial pressure: The installed base is resisting the official upgrade path. Freeform Dynamics found 83% of SAP organisations using modular architectures achieve above-average performance, versus 27% for traditional approaches.
Market pressure: VC is betting on AI-native alternatives. Oracle is capturing SAP’s natural migration cohort. The stock market is pricing conversion thesis risk. These are capital allocation decisions — people are voting with money.
Architectural pressure: There is a specific technical incompatibility between how monolithic ERP stores data and how agentic AI needs to access it. The argument is sound; the production proof at scale is still emerging.
What the evidence does not support: that monolithic ERP is definitively obsolete. SAP SE has €36.8 billion in revenue. Gartner’s Mike Tucciarone puts it plainly: “SAP ERP remains a trusted solution… We have not observed widespread movement in this direction yet.”
So here are your three paths today. Each is covered in full in our complete SAP ECC end of support guide.
Upgrade to S/4HANA: Lowest-risk for enterprises deeply embedded in the SAP ecosystem. Buys vendor support through the next decade. Defers the architectural question until the market is clearer.
Composable ERP: Replace individual modules with best-of-breed SaaS while extending ECC life via third-party support. Rimini Street supports SAP ECC through 2040 at 50–90% lower cost than SAP’s own pricing. This is the most architecturally sound path for agentic AI adoption — but it requires sustained architectural discipline.
Explore AI-native alternatives: Appropriate for specific functional domains — revenue accounting with Rillet, manufacturing with Doss. Not a wholesale ERP replacement today.
If you are not in the SAP ecosystem, the pattern still applies. The architectural question — can your core business systems serve as a substrate for agentic AI orchestration? — applies whether you run SAP, Oracle, or NetSuite.
Monolithic ERP is not dead. But the agentic AI argument is not going away.
For the specific migration decisions the SAP crisis forces, see our complete guide to SAP ECC end of support and what comes next.
FAQ
Is composable ERP just hype or a real architectural alternative?
It is operationally real. Kingfisher plc moved SAP ECC to Google Cloud with Rimini Street support and built an independent AI strategy without migrating to S/4HANA at all. Freeform Dynamics found companies using modular architectures achieve above-average performance 83% of the time, versus 27% for traditional approaches. The hype risk is overstatement — composable ERP requires sustained architectural attention, not plug-and-play.
What are the main alternatives to SAP S/4HANA migration?
Three documented paths: upgrade to S/4HANA; composable ERP — extend ECC life via third-party support and replace individual modules with best-of-breed SaaS; or migrate to Oracle ERP Cloud. AI-native ERPs like Doss, Rillet, and Campfire are a fourth option for specific functional domains, but none are proven as full SAP replacements yet.
What does a16z think about the future of ERP?
Andreessen Horowitz published “The Opportunity for Next-Gen ERPs” in February 2025, arguing AI is the same structural forcing function for ERP that cloud computing was in the 2000s. The precedent they point to is Oracle’s $9.3 billion acquisition of NetSuite in 2016. a16z invested in Rillet’s $70 million Series B in August 2025 — this is an active thesis, not just a published opinion.
Why did SAP’s stock drop in January 2026?
On January 29, 2026, SAP reported cloud backlog deceleration guidance — forward-contracted cloud revenue growing more slowly than projected. Q4 2025 revenue was €36.8 billion, up 8% — not a crisis. Bernstein analyst Mark Moerdler’s finding sums it up: two-thirds of SAP’s new cloud customers are new to the vendor, meaning SAP is not retaining its natural ECC migration cohort at projected rates.
Can enterprises really stay on SAP ECC beyond the 2027 support deadline?
Yes. Kingfisher plc is the documented example. Rimini Street supports SAP ECC through 2040 at 50–90% lower cost than SAP’s own pricing. SAP’s extended maintenance runs to 2030. Staying on ECC beyond 2027 is not theoretical — major enterprises are actively choosing it.
Are Doss, Rillet, and Campfire real competitors to SAP?
Not yet in the sense of full-enterprise displacement. These are early-stage companies building AI-native vertical ERP for specific use cases. The near-term use case is as point solutions within a composable strategy — revenue accounting with Rillet, manufacturing with Doss. For wholesale replacement of a 500-person SAP ECC deployment, they are not yet the answer.
Does moving from SAP to Oracle ERP Cloud solve the architectural problem?
No. Oracle ERP Cloud is also a monolithic integrated suite. Switching trades SAP vendor dependency for Oracle vendor dependency. The agentic AI orchestration constraints apply equally to Oracle ERP Cloud. If your primary driver is escaping the S/4HANA migration path specifically, Oracle is a proven alternative — but you are solving a vendor-specific problem, not the architectural one.
What is the architectural difference between monolithic ERP and composable ERP?
Monolithic ERP is a single integrated codebase — all modules sharing one database, business logic embedded in the system. Composable ERP is modular best-of-breed SaaS applications connected via APIs, each module owning its own data and API surface, replaceable without full rip-and-replace. The agentic AI consequence: composable ERP allows AI orchestration layers to access data through independent API surfaces; monolithic ERP constrains agents to one vendor’s integration policy.
What does the SAP crisis mean for companies not running SAP?
The pattern applies to any monolithic enterprise software dependency. The architectural question — can your core business systems serve as a substrate for agentic AI orchestration? — applies whether you run SAP, Oracle, or any other monolithic ERP. For SMB tech companies on NetSuite, the SAP crisis is a leading indicator of what mid-market cloud ERP incumbents may face as AI-native alternatives mature.
What is the NetSuite precedent and why does a16z use it?
Oracle acquired NetSuite for $9.3 billion in 2016, validating cloud ERP as a category. NetSuite launched in 1998, captured a segment incumbents were not serving, and grew to acquisition scale in roughly 15 years. a16z draws the analogy: AI-native ERP startups may capture vertical niches incumbent cloud ERP vendors do not serve well, and grow to compete at scale within a similar timeframe.
How is agentic AI different from traditional ERP automation?
Traditional ERP automation operates within the system’s process engine — automating steps the system already knows about. Agentic AI is an orchestration layer above the ERP, executing multi-step processes by calling data from multiple systems simultaneously and triggering actions across system boundaries. That is exactly why monolithic ERP creates structural friction for agentic workflows.
Is SAP S/4HANA the future or is it also becoming obsolete?
S/4HANA will be deployed at many large enterprises — it is not imminently obsolete. Structurally, it shares the monolithic architecture’s constraints on agentic AI orchestration. It solves the ECC end-of-life problem but not the longer-term architectural question. It buys 10–15 years of vendor support while the AI-native market matures. That might be exactly what you need.
