For steel and mining plants still running SAP ECC, 2027 is not the year to decide what migration should look like. It is the deadline they are already working backwards from. Mainstream SAP ECC support ends in December 2027, with extended maintenance available until 2030 at a premium. Migrating to SAP S/4HANA needs to begin well before then.
For plants where production, maintenance, inventory and quality are tightly connected, migration cannot be treated as a last-minute IT exercise. The decisions made now will determine what gets migrated, what needs fixing, and when the plant can safely transition. This is especially important for organisations planning SAP S/4HANA on premise deployments.
This blog covers three decisions plants need to lock now: which processes to migrate first, which data to clean, and when to secure the plant shutdown and cutover window for SAP S/4HANA.
The Three Migration Decisions Steel & Mining Plants Must Lock Now
1. First, Lock the S/4HANA Processes That Keep the Plant Running
The first decision is not simply, “Which SAP modules do we migrate?” It is: Which processes can the plant not afford to disrupt?
For steel and mining operations, migration priorities should focus on processes that directly affect production continuity and asset availability:
- Production Planning and execution
- Materials Management
- Plant Maintenance
- Quality Management
- Finance and Controlling
These processes are closely connected. Materials availability affects production, maintenance supports asset availability, and operational transactions need to flow accurately into costing.
That is why an SAP steel industry or SAP for mining industry migration should be sequenced around operational dependencies, not just a technical module list.
SAP S/4HANA adds capabilities such as real-time maintenance analytics and 50+ Fiori apps, but the benefits depend on getting the scope right. Lock the critical processes first.
2. Next, Clean the Data Those Processes Depend On
Once the S/4HANA scope is clear, the next decision is straightforward:
What data actually needs to move with those processes?
Steel plants can hold millions of equipment records, maintenance histories and BOMs built up over decades. Complex asset hierarchies may include blast furnace refractory tracking, ladle lifecycle data and multi-level rolling mill configurations.
Mining operations have their own data challenges. Equipment such as haul trucks, excavators, crushers and conveyors generate extensive maintenance histories and component records. Remote mine sites also add complexity, with inconsistent master data, limited connectivity and different maintenance practices across locations.
The challenge is not just moving this data to S/4HANA. It is deciding what remains accurate, relevant and usable.
For critical data, plants need to decide what to:
- Clean and migrate
- Migrate as-is
- Archive
- Retire
This covers material masters, equipment, functional locations, BOMs, maintenance plans, inventory, vendors and costing structures.
Custom ABAP also needs early review. A significant portion of custom code typically requires adaptation for SAP S/4HANA Solutions compatibility. SAP Readiness Check and the Custom Code Migration Worklist can identify dependencies early.
Data validation should involve maintenance, production, procurement and finance, not just IT. Clean the data before migration testing exposes the gaps.
3. Then, Lock the Plant Shutdown and Cutover Window
Now comes the decision that turns the migration plan into an operational reality:
When can the plant actually move?
For an office environment, ERP cutover might happen over a weekend. Steel and mining plants rarely have that flexibility. Blast furnaces, casters, rolling mills and heavy mining equipment cannot simply stop because the ERP system is being migrated.
The shutdown window needs to be identified early and planned around the plant. Consider:
- Planned maintenance shutdowns
- Furnace relining and major equipment outages
- Production cycles
- Raw-material availability
- Inventory position
- Seasonal demand
- Customer and dispatch commitments
Then work backwards from the required production restart, accounting for data migration, validation, system freeze and final data preparation.
The shutdown window is not just an IT milestone. It affects testing, data readiness, contingency planning and maintenance continuity. Plants must also decide how maintenance work orders will be handled while SAP is unavailable.
This is particularly important for SAP S/4HANA on premise, where infrastructure and cutover activities require careful coordination.
Reserve the cutover window early. The plant’s operating calendar should shape the migration, not the other way around.
These Three Decisions Are Connected
The sequence is important because each decision determines the next.
| Decision to lock now | What it determines |
| S/4HANA scope | Which processes and modules are critical, and their dependencies |
| Data readiness | Which master and operational data needs to be cleaned, migrated, archived or retired |
| Shutdown window | When testing, system freeze, cutover and production restart can safely happen |
The sequence is straightforward: Scope first, then Data, then Cutover. You cannot properly clean migration data until you know which processes depend on it. Likewise, cutover preparation cannot be finalized until the required data is ready and testing requirements are clear.
The plant shutdown window also depends on this sequence. Without a clear scope, known dependencies and validated data, it is difficult to confidently plan testing, system freeze and production restart. That is the sequence steel and mining plants need to lock now, not in 2027. This approach gives SAP S/4HANA migration the planning discipline required for complex industrial operations.
Why Waiting Until 2027 Creates the Risk
The biggest danger is not simply reaching the ECC end-of-support date. It is reaching 2027 with unresolved scope, incomplete data, unremediated custom code and a shutdown window that does not work for production.
The numbers already show how little room there is for that approach. Migration projects are averaging 30% longer than planned, only 8% are completing on schedule, and nearly two-thirds have exceeded their original budgets. For an ERP for steel industry or mining environment, there is another constraint: the plant still has to produce.
Starting the migration conversation in 2027 means compressing decisions that should already be underway, including process prioritization, data cleanup, custom-code assessment, testing, user preparation and cutover planning. The deadline may be 2027. The planning window is now. For organisations migrating to SAP S/4HANA, that leaves little room for avoidable delays.
Conclusion: Decide What Moves. Clean What Moves. Reserve When the Plant Moves.
For steel and mining plants, SAP S/4HANA migration is not something to solve when ECC support ends. The real work is deciding early what the plant needs, which data is ready to move, what needs remediation, and when operations can safely transition.
Getting these decisions right creates the room needed for proper testing, custom-code remediation, user preparation and cutover planning. Waiting until 2027 does the opposite. It turns a structured migration into a compressed exercise where production continuity is at stake. For an ERP for steel industry or SAP for mining industry environment, that preparation matters even more because the migration must work around production realities.
Planning your move from SAP ECC to S/4HANA? Talk to Geschäft Formulae and start locking the decisions that 2027 will not give you time to make.
FAQs
1. When should steel and mining companies start migrating from SAP ECC to SAP S/4HANA?
Steel and mining companies should begin planning their SAP S/4HANA migration well before the 2027 ECC support deadline. Scope definition, data cleanup, custom-code assessment, testing and cutover planning can take significant time, especially when migration must work around plant operations.
2. What should steel and mining plants migrate first to SAP S/4HANA?
Plants should first prioritize the S/4HANA processes that are critical to production continuity, including production planning, maintenance, inventory, procurement, quality and finance. The exact sequence should depend on process dependencies and the plant’s operating requirements.
3. What data should be cleaned before migrating to SAP S/4HANA?
Before migration, companies should review material masters, equipment records, functional locations, BOMs, maintenance plans, inventory, vendor data and costing structures. Each dataset should be classified for cleaning and migration, migration as-is, archiving or retirement.
4. Why is the plant shutdown window important for SAP S/4HANA migration?
The shutdown window determines when the plant can safely freeze the existing ERP system, complete data migration, validate the new environment and restart production. For steel and mining operations, it must be planned around maintenance shutdowns, production cycles, equipment outages, inventory and customer commitments.
5. What are the risks of waiting until 2027 to migrate to SAP S/4HANA?
Waiting until 2027 can compress critical activities such as scope definition, data remediation, custom-code adaptation, testing, user preparation and cutover planning. For steel and mining plants, this can increase the risk of delays, cost overruns and disruption to production.