ERP Modernization
ERP Modernization is the migration from a legacy ERP (typically SAP ECC, Oracle EBS, or a heavily-customized on-premise platform) to a modern cloud-first ERP — most commonly SAP S/4HANA, Oracle Fusion Cloud, Workday Financials, Microsoft Dynamics 365, or NetSuite for mid-market. SAP has set a forced deadline: standard support for SAP ECC ends in 2027 (extended to 2030 with paid maintenance), pushing thousands of enterprises into S/4HANA migrations whether they're ready or not. The technical migration has three patterns: greenfield (new instance, re-implement processes), brownfield (in-place conversion of existing system), and hybrid/selective (component-by-component move). The KnowMBA POV: ERP migrations fail when treated as IT projects instead of operating model rewires. The entire point of moving off heavily-customized ECC is to STOP customizing — to adopt the standard process and let the business absorb the change. CIOs who let the business say 'just rebuild our 4,000 customizations in S/4' are building the next legacy system on a more expensive platform.
The Trap
The trap is replicating customizations. Legacy ERPs accumulate decades of bespoke logic — custom transaction codes, modified standard tables, ABAP exits, custom reports, edge-case workflows added for one division 12 years ago. The 'safe' migration approach is to lift-and-shift these customizations into the new platform. This is why Lidl spent ~7 years and €500M+ on an SAP migration before abandoning it in 2018, and why Hershey's 1999 SAP go-live disrupted Halloween shipments and contributed to a quarterly profit miss. The new ERP wasn't the problem — preserving the old operating model on top of it was. A 'successful' migration that recreates 80% of customizations means: same operating costs, same upgrade pain, same vendor lock, just on a newer release. The trap also hides in the timeline: the IT project is 'done' when the system goes live; the operating model rewrite takes 2-3 more years and is usually un-resourced.
What to Do
Six moves. (1) Decide the strategic intent FIRST: cost reduction, operating model standardization, M&A platform readiness, or compliance — these drive different migration patterns. (2) Set a customization budget: e.g., 'we will allow only 50 customizations vs the current 1,800, and they require executive sign-off.' Forcing the conversation early surfaces which 'critical' customizations are actually optional. (3) Map current state vs standard process for each module — every customization should have a documented business reason that survives challenge. (4) Use the migration as the forcing function for process standardization across business units (single chart of accounts, single material master, single P2P process). (5) Stage the cutover by business unit or geography, not big-bang — Hershey-style failures are big-bang failures. (6) Budget 30-40% of total program for change management, training, and operating model design — not technology — and protect that budget when the IT side overruns.
Formula
In Practice
Lidl, the German discount grocer, attempted to replace its legacy Wawi inventory system with SAP HANA-based eLWIS starting in 2011. By 2018, after spending an estimated €500M and seven years, Lidl abandoned the migration and reverted to the legacy system. The widely-reported reason: SAP's standard inventory model used retail-price valuation, but Lidl insisted on continuing its purchase-price valuation approach — requiring deep customization that ultimately couldn't be made to work at scale. The lesson is foundational: when a company refuses to adapt its operating model to standard ERP processes, it inverts the value of moving to a modern platform. Hershey's 1999 SAP/Manugistics/Siebel triple go-live during peak Halloween shipping season produced an estimated $100M+ revenue impact and wiped quarterly earnings. Both cautionary tales share a root cause: ERP treated as IT replacement rather than operating model redesign.
Pro Tips
- 01
The customization count is the leading indicator. Pre-migration, count every Z-table, custom transaction code, and user exit in your legacy ERP. If the post-migration target is more than 10-15% of that count, the program will fail to deliver operating model benefits — you're rebuilding the legacy on a new platform. Force the question: which customizations exist because of competitive advantage vs. organizational stubbornness?
- 02
S/4HANA Cloud (public edition) forces standard processes by removing the ability to deeply customize. This is a feature, not a limitation. Enterprises with the discipline to choose public-cloud editions over private-cloud editions force their organizations into operating model standardization that private-cloud migrations let them dodge. The price of flexibility is failure to transform.
- 03
The CFO must own ERP modernization, not the CIO. Why? Because the value lever is operating model standardization (one chart of accounts, one source of financial truth, faster close), not technology refresh. When CIOs own it, the program optimizes for technical delivery; the business absorbs neither the discipline nor the benefit. When CFOs own it with CIO partnership, the standardization conversation has executive teeth.
Myth vs Reality
Myth
“Moving to cloud ERP automatically modernizes the business”
Reality
Moving to cloud ERP modernizes only the infrastructure. Without operating model redesign, you get the same business processes running on a more expensive cloud bill. The 'modernization' label refers to the technology stack, not the business — and conflating the two is how multi-hundred-million dollar programs deliver no measurable business outcome.
Myth
“Brownfield migration is lower risk than greenfield”
Reality
Brownfield migration is lower TECHNICAL risk because it preserves more — but that's also why it's higher BUSINESS risk. By preserving customizations, brownfield migrations preserve the very technical debt and process inflexibility that justified moving in the first place. Greenfield is higher technical risk but the only path that delivers operating model change. The 'safe' choice is often the one that wastes the investment.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your enterprise is 18 months into an SAP ECC → S/4HANA migration. The system integrator reports they've successfully replicated 1,400 of 1,800 legacy customizations on the new platform and the project is 'on track.' What should the steering committee do?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
ERP Modernization Program Outcomes
Large enterprise SAP S/4HANA and Oracle Fusion migrationsSuccessful (operating model transformed)
~20-25% of programs
Technically Delivered, Limited Business Value
~45-55% of programs
Failed / Abandoned / Reverted
~20-30% of programs
Source: Panorama Consulting Group ERP Reports (annual)
Customization Count Targets
Post-migration S/4HANA customization counts (large enterprise)Disciplined (true standardization)
< 50 custom objects
Moderate
50-200 custom objects
Heavy (legacy patterns preserved)
200-500 custom objects
Failure Mode (rebuilding legacy)
> 500 custom objects
Source: Hypothetical: composite from SAP partner delivery benchmarks
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Lidl
2011-2018
Lidl began an ambitious migration from its legacy Wawi inventory system to a SAP HANA-based platform called eLWIS in 2011. After approximately seven years and an estimated €500M, Lidl abandoned the project and reverted to the original legacy system. Reporting at the time pointed to a fundamental conflict: SAP's standard retail inventory model used retail-price valuation, while Lidl insisted on its existing purchase-price-based valuation approach. Bridging that gap required deep customization that ultimately could not be made to work reliably at Lidl's scale and process complexity.
Estimated Spend
~€500M
Duration Before Abandonment
~7 years
Outcome
Migration cancelled, reverted to legacy
Root Cause
Operating model vs. standard process conflict
When a business refuses to adapt its operating model to standard ERP processes, the migration becomes an attempt to recreate the old system on a new platform — the most expensive path with the least business value. Lidl is the canonical case for the principle: ERP modernization is operating model change, with technology as the enabler, not the goal.
Hershey
1999
Hershey attempted a big-bang go-live of SAP R/3, Manugistics demand planning, and Siebel CRM simultaneously in mid-1999, accelerating an originally 4-year program into 30 months to hit a deadline before Y2K freezes. The cutover landed during peak shipping season for Halloween candy. Order processing, warehouse management, and shipping all experienced severe disruptions. Hershey reported a 12% drop in Q3 1999 revenue and an estimated $100M+ revenue impact, attributed substantially to the ERP go-live disruption rather than demand softness.
Program Compression
48mo → 30mo
Cutover Approach
Big-bang, three systems simultaneously
Q3 1999 Revenue Impact
~12% decline
Estimated Revenue Disruption
$100M+
Big-bang cutovers during high-demand periods are catastrophic risk concentration. Hershey is the canonical case for staged cutover — by business unit, geography, or module — even when timeline pressure pushes toward a single switch. The compounding risk of three simultaneous system go-lives during peak season is what made the disruption uncontainable.
Decision scenario
The Customization Standoff
You are the CFO sponsoring a $110M, 3-year SAP S/4HANA migration. At month 14, the manufacturing division (35% of company revenue) has formally requested 280 custom modifications to preserve specific shop-floor workflows they say are 'core to operations.' The system integrator says implementing them adds $18M and 7 months. Your CIO supports approval. The S/4HANA delivery lead privately tells you these workflows are mostly standard with minor variations — the real driver is change resistance from a long-tenured ops leadership team.
Program Budget
$110M
Original Customization Target
<80 modifications
Manufacturing Request
280 modifications
Timeline Impact if Approved
+7 months
Cost Impact if Approved
+$18M
Decision 1
The CIO and head of manufacturing both push for approval, framing this as 'protecting business continuity.' The S/4HANA lead, off the record, says 80% of the requested modifications could be replaced by standard configuration plus modest process change. The board steering committee meets in two weeks.
Approve the request to preserve relationships with manufacturing leadership and avoid program controversy. Add the $18M and 7 months.Reveal
Reject the request as submitted. Require manufacturing to rationalize the 280 against three buckets — (a) competitive differentiation worth customization, (b) standard process possible with change management, (c) decommission. Bring the rationalized list back in 6 weeks.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn ERP Modernization into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn ERP Modernization into a live operating decision.
Use ERP Modernization as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.