One of the biggest mistakes I see in ERP transformation is the belief that success happens at go-live.
It does not. Go-live is important, but it is not the finish line. It is the point where the real test begins. Once the system is live, the business has to prove that it can actually work differently, make better decisions, and create measurable value from the investment. That is why I found the recent SAPinsider discussion so relevant. The framing was not just about implementing SAP. It was about whether transformation delivers long-term business value.
This matters even more now because SAP decisions are happening under real time pressure. SAP states that mainstream maintenance for SAP Business Suite 7 core applications runs through the end of 2027, with optional extended maintenance through the end of 2030. At the same time, SAPinsider benchmark reporting says legacy SAP ECC and Business Suite usage has dropped below 50%, 30% of surveyed organizations are already fully live on SAP S/4HANA Cloud Private, and 73% are at some stage of transition. That means companies are no longer discussing whether change is coming. They are deciding how to move, how fast to move, and whether they will create value from it.
What I have seen in practice is that many ERP projects still get managed like technical deployments instead of business transformations. The organization focuses on milestones, system configuration, data migration, testing cycles, and cutover. All of that matters, of course. But a system can go live on schedule and still fail in the ways that matter most. Teams may not trust the data. Reports may exist, but decisions may still be made outside the system. Legacy habits may survive under a new interface. In some cases, workloads even go up after deployment because old workarounds disappear before stronger processes are put in place. That pattern is not surprising when you look at the broader transformation data. McKinsey has said that roughly 70% of transformations fail, and BCG has reported that only about 30% of digital transformations achieve their objectives.
To me, that is why the real issue is not software alone. It is operating discipline.
The migration-versus-modernization distinction is more important than many companies admit. Migration is moving to a new platform. Modernization is changing the way the business operates. Those are not the same thing. A company can migrate and still carry forward weak process ownership, poor governance, unclear accountability, and unnecessary customization. When that happens, the business may have a newer ERP environment without achieving better execution. The architecture may look cleaner, but the organization still struggles to produce better outcomes. That is why the most important ERP question is not simply whether the new system is live. It is whether the business is improving after it goes live.
In my view, successful ERP transformation depends on a few non-negotiables.
First, it has to be tied to business outcomes, not just technical completion. The real measures of success are things like better margin visibility, faster decision-making, stronger inventory control, more reliable planning, lower total cost of ownership, and greater operational resilience. Those are the kinds of outcomes the SAPinsider discussion emphasized, and I think that is exactly the right lens.
Second, companies need to get the process foundation right before they start talking too aggressively about automation, analytics, or AI. If the data is weak, the workflows are inconsistent, or accountability is unclear, advanced tools do not solve the problem. They simply make the confusion move faster. SAPinsider’s CIO agenda itself framed value realization, transformation, and decision quality as central concerns, which reinforces the idea that technology alone is not enough.
Third, leadership has to stay involved after go-live. Too many organizations treat post-implementation optimization as a secondary phase, when in reality that is where much of the value is won or lost. Prosci’s research on change management found that stronger management of the people side of change correlates with better outcomes on project objectives, schedule, and budget, and its later research reported that among organizations measuring compliance and overall performance, 76% met or exceeded project objectives. That is a strong reminder that adoption, accountability, and follow-through are not soft issues. They are performance issues.
That is why I do not think ERP should be viewed as an isolated IT project. I think it should be treated as a business operating model decision. The companies that create real value are the ones that use ERP to strengthen how they govern processes, measure performance, and align teams across the business. The software matters, but the discipline behind it matters more.
Go-live is not the proof of success.
Value is.