What Shapes an ERP Migration Strategy Today
An ERP migration strategy is the structured set of choices an organisation makes about whether to extend, replace, or consolidate its core business system, balancing operational risk, technical debt, cloud ambitions, and data needs to decide how ERP will support future automation, AI, and growth. In practice, that strategy now spans on‑premise extensions, cloud ERP consolidation, and full legacy system modernization on new platforms. The trade‑offs are sharp: cloud ERP promises AI‑ready data and faster reporting, while extension paths protect continuity in operations where downtime is unacceptable. At the same time, hidden costs from outdated ERP versions—such as slow reporting, manual workarounds, and lost productivity—erode the original investment’s return. Recent moves by Lwart Environmental Solutions and Levi Strauss show how risk tolerance, capital programs, and business model change turn this into a business decision, not only a technology one.
Lwart: Extending ECC for Stability and Sequencing
Lwart Environmental Solutions runs SAP ECC 6 at the centre of a large collection network, where any disruption would halt core operations. Facing a factory expansion expected to add 50% more production capacity, the company chose to extend its existing ERP instead of pursuing immediate legacy system modernization. It moved SAP ECC 6 support to Rimini Street, cutting ERP support costs by 50% and freeing budget and attention for physical infrastructure. Sequencing, not speed, defined its ERP migration strategy. Innovation continued at the edges: the IT team built a mobile application for drivers that removed the need for cash in the field while keeping the core system stable. This extension model favors continuity and targeted improvements, but it also accepts that some modernization and enterprise cloud migration will be delayed, with potential opportunity costs in analytics and AI.

Levi Strauss: Cloud ERP Consolidation on Azure
Levi Strauss chose a different path, using cloud ERP consolidation as the backbone of its wider digital overhaul. Microsoft reported that Levi’s migrated to Azure to bring nine ERP systems onto a single platform, supported by the Azure Migrate tool as part of a data‑center exit. According to Microsoft, “the company saw a two-times improvement in latency and a 60% improvement in maximum IOPS” after moving to the Next‑gen General Purpose tier of Azure SQL Managed Instance. The programme is part of a seven‑year push for a single global ERP platform, higher automation, and AI and agentic AI capabilities. This Azure ERP transformation reduces technical debt, speeds up migrations, and underpins a shift to a more data‑centric operating model, showing how enterprise cloud migration can deliver measurable performance gains while preparing ERP data for advanced analytics.
Modernization, AI Readiness, and Hidden Costs of Delay
The contrast between Lwart and Levi’s highlights how cloud migration and extension strategies answer different pressures. Cloud ERP and Azure ERP transformation efforts focus on creating AI‑ready infrastructure, standardised processes, and consolidated data for faster decisions and automation. Greenfield moves like Victrola’s SAP Cloud ERP Public Edition project show the upside: P&L reporting time dropped by 94%, from four hours to 10–15 minutes, and more than 250 hours of finance work was removed. Yet many organisations still live with older ERP versions where operational drift, manual workarounds, and spreadsheets absorb time and mask problems. Those hidden costs reduce productivity and dilute ROI. Choosing when to modernise versus extend depends on an organisation’s risk tolerance, the weight of technical debt, concurrent transformations such as plant expansions, and its appetite to re‑platform processes in pursuit of AI and direct‑to‑consumer growth.
How to Choose Between Extension, Consolidation, and Modernization
For leaders weighing ERP migration strategy options, the three paths suggest a decision framework. Extension fits when operational continuity is non‑negotiable and major capital projects already stretch the organisation; third‑party support can create breathing room while targeted innovations wrap around a stable core. Cloud ERP consolidation, as in Levi’s enterprise cloud migration, suits organisations battling fragmented platforms and aiming for standardised global processes and AI‑ready data. Full legacy system modernization or greenfield ERP is most compelling when existing customisations block change and when leaders accept constraints such as limited historical data in exchange for a clean start. Across all options, the main question is not whether to move to the cloud, but how ERP will support business transformation goals—ranging from supply‑chain agility to direct‑to‑consumer models—without imposing unacceptable risk or missing the next wave of AI‑driven value.






