S/4HANA modernization: decisions before design
An ERP program moves risk across processes, integrations, data and operating ownership. Resolve the decision boundaries before choosing the implementation path.
The critical readiness question is not only where S/4HANA will run, but which business processes, dependencies and operating responsibilities the enterprise is prepared to change.
1. Confirm the business case
Separate mandatory platform requirements from process improvement, legacy simplification and analytics ambitions. A technically feasible migration is not automatically an economically justified transformation.
2. Establish five decision gates
| Gate | Minimum questions | Evidence |
|---|---|---|
| Business scope | Which processes change? Which remain standardized? | Process variants, pain points and accountable business owners |
| Application landscape | Which satellites remain, retire or require remediation? | System inventory, dependencies and lifecycle constraints |
| Integration | Where are SAP-native patterns justified and where is enterprise iPaaS needed? | Interface inventory, patterns, ownership and recovery requirements |
| Data | Which data is trusted, migrated, archived or governed? | Data ownership, quality baseline, retention and reconciliation rules |
| Operations & controls | Who supports releases, security, resilience and exceptions? | RACI, service-level objectives, compliance and cutover readiness |
3. Treat clean core as a boundary, not a slogan
Evaluate extensions against supported APIs, released interfaces, upgrade compatibility, lifecycle maintenance and legitimate business differentiation. Standardization is valuable where process variation does not create measurable advantage.
4. Record the architecture recommendation
State the target operating assumptions, transition options, principal dependencies, unresolved risks and decisions requiring business or technology leadership approval. Mark unknowns explicitly.
Failure mode: announcing a platform strategy while critical process ownership, master data dependencies or cutover constraints remain untested.
Official references
SAP S/4HANA Cloud documentation · SAP S/4HANA overview. Confirm edition and feature availability against current product documentation.