S/4HANA migration for banks: why the choice between brownfield, greenfield, and selective data transition comes down to cost
Mainstream maintenance for ECC 6.0 systems ends on December 31, 2027. An extension until 2030 is possible, but it comes with a 2 percentage point surcharge on the maintenance base—in practice, this means 9 to 12% higher total costs. Starting in 2031, Customer-Specific Maintenance will take effect: no more Legal Changes updates, no security guarantee, and no SLAs. Banks that do not plan their migration now will end up paying more either way.
The real question, therefore, is not whether to migrate, but how. And this decision has a direct impact on project costs, duration, and the quality of the resulting process landscape.
Starting Point: More than just a technical upgrade
Institutions facing an S/4HANA migration usually have several areas requiring attention at the same time. The IT architecture has evolved over the years and has become correspondingly complex. Data volumes have increased, authorization models have at least room for optimization, and the resulting license costs are often higher than necessary. Ignoring these issues during migration and simply changing the system version does not solve any problems. It merely carries them over into the new system generation.
Proper migration preparation therefore covers more than just a technical upgrade:
- Evaluation of the business case,
- Selection of the appropriate deployment model,
- Optimization of licensing,
- Validation of infrastructure parameters and
- Definition of the target architecture.



