Why ERP Isn’t Dying, It’s Being Rebuilt: The State of Enterprise Resource Planning in the AI Era

This article, which expands on insights from a recent episode of the Evolving ERP podcast, explains why ERP isn’t dying, but it is being rearchitected for the AI era.

Enterprise resource planning (ERP) software has been pronounced dead so many times that the announcement has lost all meaning. Articles calling ERP obsolete have been circulating since at least 2010, and each wave of new technology, cloud, mobile, and now AI, has generated a fresh round of obituaries.

The editors at Solutions Review think the framing is wrong, and the consequences of believing it are real. ERP is not dying. The assumptions that surround it are being replaced, and that is a very different problem for enterprise leaders to solve. This piece draws on conversations with practitioners in the ERP space, including the inaugural episode of Evolving ERP, a podcast from Inside Jam, to map what is actually changing and what it means for organizations trying to make smart long-term infrastructure decisions.

KEY FACTS: ERP in 2025 and Beyond

• The global ERP market was valued at approximately $67 million in 2025 and is expected to reach over $168 million by 2033 (Source: Grand View Research).
• SAP’s deadline for customers to migrate from ECC to S/4HANA is the end of 2027, when mainstream maintenance ends, affecting tens of thousands of enterprise installations worldwide.
• Gartner research finds that over 70 percent of recently implemented ERP initiatives will fail to fully meet their original business use case goals, and as many as 25 percent will fail catastrophically.
• ESG reporting mandates from the SEC (US) and the CSRD (EU) are creating new functional requirements for ERP systems, including emissions tracking, supply chain visibility, and sustainability accounting.

The “ERP Is Dead” Argument, and Why It Keeps Failing

The death narrative has two origins. The first was functional: early ERP systems were genuinely limited to back-office operations, leaving CRM, human capital management, and supply chain execution to separate point solutions. If ERP meant only a general ledger and an MRP module, then yes, it was insufficient as a business operating platform.

The second origin was cultural. ERP got associated with expensive, painful, multi-year implementations that changed business processes to fit software rather than the other way around. The Terminator imagery that circulates in ERP communities is not entirely satirical; it reflects a real anxiety about systems that feel imposed rather than chosen.

Both critiques have aged poorly. Modern ERP platforms, whether from SAP, Oracle, Infor, or a growing tier of mid-market and industry-specific vendors, have absorbed CRM, HCM, and supply chain functionality either natively or through standardized API connectors. The integration story, which was once a legitimate objection, is now largely resolved. Salesforce and an ERP back end communicate through standard connectors, and the functional boundaries that once separated these categories have blurred considerably.

What has not changed is the cultural and organizational challenge. ERP implementations still fail at high rates, and the reason is rarely the software. The cause is almost always the same: organizations go after innovation before they have stable, well-documented, consistently followed business processes.

The Process-First Imperative

The most durable insight in the current ERP discourse is also the least glamorous one: no amount of technology investment compensates for process dysfunction. This applies whether the technology in question is a cloud migration, an AI layer, or robotic process automation.

The practical implication for ERP buyers is significant. Before evaluating platforms, before issuing RFPs, before engaging systems integrators, enterprises need an honest process audit. Not a perfunctory documentation exercise, but a real assessment of which processes are standardized across the organization, which are workarounds that have calcified into habit, and which carry so much technical debt that they should be eliminated before any new system inherits them.

Data governance belongs in this same conversation. The ERP data quality problem is one of the industry’s worst-kept secrets. Legacy systems accumulate decades of inconsistent master data, duplicate records, and orphaned transactions that distort reporting and, increasingly, poison the AI models that organizations are now trying to build on top of their operational data. The phrase “garbage in, garbage out” has been in circulation since the earliest days of computing, but it has acquired new urgency as AI-driven analytics become part of the ERP value proposition. Hallucinations in AI outputs are frequently downstream symptoms of upstream data problems, not failures of the model itself.

Composable ERP and the End of the Monolith Mandate

One of the more consequential structural shifts in the ERP market is the move toward composable or modular architectures. The traditional model required enterprises to choose a single platform vendor and accept that vendor’s approach across all functional domains. That model still exists and still has defensible use cases, but it is no longer the only viable option.

Composable ERP, sometimes called post-modern ERP, allows organizations to assemble a functional stack from best-of-breed components connected through APIs and integration layers. A manufacturer might run SAP for core financials and production planning, a specialized MES for shop-floor execution, a separate analytics layer, and a cloud-based HCM platform, with all systems exchanging data through standardized connectors.

The appeal is obvious: organizations can adopt the best solution for each functional domain and avoid the compromise of using a generalist system everywhere. The risk is equally obvious: integration complexity multiplies, data governance becomes harder to enforce across system boundaries, and the total cost of ownership calculation becomes genuinely difficult to model.

The Cloud Migration Dilemma

The forced march to the cloud is creating real friction in the enterprise market, and it deserves more direct discussion than it typically receives. SAP’s 2027 deadline for S/4HANA migration is the most visible example of a dynamic that applies across the vendor landscape: software companies have compelling financial reasons to move customers to cloud subscriptions and are using maintenance deadlines to accelerate that transition.

The customer perspective is more complicated. Organizations that spent significant capital implementing and customizing on-premises ERP systems over 15 or 20 years are being asked to make another multi-million-dollar investment, often with the requirement to reduce or eliminate the customizations that made the previous system fit their specific business. The business case for that transition is not self-evident, and vendors have not always made it compelling.

The honest answer for most enterprises is that the decision framework should be driven by total cost of ownership analysis, not by vendor marketing timelines or fear of falling behind on innovation. Cloud ERP delivers real advantages in infrastructure management, continuous update cycles, and scalability. On-premise systems deliver real advantages in customization, data control, and predictable cost structures. The right answer depends on the specific organization, its industry, its regulatory environment, and its internal IT capabilities.

ESG as the Next Major ERP Frontier

Environmental, social, and governance (ESG) reporting is emerging as one of the most substantive new functional requirements in the ERP space, yet it receives less attention than it deserves compared with discussions of AI and cloud migration.

The regulatory pressure is accelerating on both sides of the Atlantic. The EU’s Corporate Sustainability Reporting Directive (CSRD) is already in effect for large companies and will expand to more organizations through 2026 and 2027. What makes ESG genuinely challenging from a systems standpoint is that compliance at the summary level, reporting aggregate emissions figures annually, is relatively tractable. Compliance at the operational level, tracking carbon footprint by product line, supplier, and production process in near-real time, requires capabilities that most ERP systems are still developing.

The supply chain dimension adds another layer of complexity. ESG obligations do not stop at the enterprise boundary. Scope 3 emissions reporting, forced labor due diligence, and supplier sustainability assessments require visibility into supply chain partners who may be running entirely different systems or no formal systems at all. This is an integration and data collection problem that ERP vendors have not yet solved at scale.

Workforce and the Human Side of ERP Evolution

The talent dimension of ERP is systematically undervalued in industry discourse. ERP systems are no longer IT projects in the traditional sense. A modern ERP implementation touches finance, operations, supply chain, HR, and increasingly customer-facing functions. The project team composition needs to reflect that scope.

The implication is that the ERP career path is genuinely broader than its reputation suggests. Deep technical expertise in SAP configuration or Oracle Fusion is valuable, but so is the ability to facilitate cross-functional process design workshops, manage organizational change, communicate complex system capabilities to non-technical stakeholders, and translate business requirements into system specifications. The demand for people who can bridge functional business knowledge and ERP technology is high and underserved.

There is also a generational interface problem that vendors are working to address. ERP systems running on decade-old UI paradigms are increasingly difficult to staff around, because the workforce entering the labor market has grown up with consumer-grade software experiences and finds green-screen or early-2000s web interfaces genuinely alienating. Mobile-first interfaces, dashboard-driven KPI views, and natural language query capabilities are not just cosmetic improvements; they are workforce enablement tools that affect adoption rates and, ultimately, the return on the ERP investment.

What Enterprise Leaders Should Actually Do

The gap between ERP potential and ERP reality is fundamentally an organizational readiness problem. Technology selection matters, but it is downstream of process maturity, data quality, and change management capability. Organizations that approach ERP decisions in that order, process first, data second, technology third, consistently outperform those that lead with platform selection.

For enterprises currently facing cloud migration decisions, the honest framework involves three questions. First, what is the real total cost of staying on-premises through the maintenance window and beyond? Second, what business capabilities does cloud migration enable that are genuinely unavailable or prohibitively complex on the current system? Third, what is the organizational capacity to absorb a major implementation while continuing to run the current business? Answering those questions honestly, rather than accepting vendor timelines as given, leads to better decisions.

For organizations evaluating composable or modular approaches, the critical variable is integration competency. A composable ERP stack is only as strong as the weakest integration point. Organizations without a strong internal integration architecture capability, or a trusted external partner who can provide it, should be cautious about the complexity they are taking on.

ERP is not a solved problem. It is an evolving one, and the organizations that will get the most from it are those that treat it as a continuous capability rather than a one-time implementation.

FAQ: Common ERP Questions Answered Directly

Is ERP actually dying? No. ERP market revenues are growing, adoption is expanding in mid-market segments, and major vendors are investing heavily in next-generation platforms. The “ERP is dead” narrative reflects dissatisfaction with specific implementations and outdated UI paradigms, not the obsolescence of ERP as a functional category.

Should we wait for AI capabilities to mature before upgrading our ERP? Waiting for AI maturity is not a sound strategy. AI capabilities in ERP are improving incrementally, not in discrete leaps. More practically, the data quality work required to make AI useful in an ERP context is the same work required to make the ERP itself useful. Start there.

What is the biggest reason ERP implementations fail? Process instability. Organizations that implement ERP without first standardizing and documenting their business processes effectively automate dysfunction. The software is rarely the primary cause of implementation failure.

How seriously should we take SAP’s 2027 S/4HANA deadline? Seriously, but not uncritically. Vendors have a history of extending deadlines when customer pressure is sufficient. That said, running unsupported enterprise software carries genuine risk, and the migration complexity only increases with delay. Organizations should be actively planning even if they do not expect to complete the migration by 2027.

What does ESG have to do with ERP? More than most organizations currently recognize. Scope 1, 2, and 3 emissions reporting, supplier sustainability due diligence, and social compliance tracking are all operational data problems that require ERP-level data infrastructure to address at scale. ESG is becoming a functional ERP requirement, not a separate reporting exercise.