Which factors to consider for SAP ECC to SAP S/4HANA migration?
With SAP stopping mainstream support for SAP ERP 6.0 by 2025, the existing SAP installed base customers are looking for the right strategy to adopt SAP S/4HANA. Conversion to SAP S/4HANA requires careful planning and preparation. There are several factors to be considered before migrating from SAP ECC to SAP S/4HANA. We’ll discuss some of them in this article.
Heterogenic Application Landscape
This is one of the most important points to consider before migrating from SAP ECC to S/4HANA. If an organization has several diverse applications integrated to ECC, then the effort required to migrate is also more. However, once the migration is complete, it drastically reduces the Total Cost of Ownership (TCO).
Age of the legacy system
If an organization has been using SAP ECC for the past 10 years or more, then its high time to migrate to SAP S/4HANA. Most of the business processes or the business itself would have transformed in the last 10 years, for example, Mergers and Acquisitions or Diversifications might have happened. Hence, it is vital to move to the latest ERP suite in order to keep up with the business and technology trends.
Number of legal entities
Another standard factor to consider is the number of legal entities. This component decides whether to go for a System Conversion or a new implementation. We came across an organization which had 100different legal entities coupled with 10+ years of legacy data. In such cases, system conversion becomes an arduous task.
If the database size is less than 3 TB, then the system conversion process becomes easy. However, as it crosses a certain threshold value (may be 4TB or 5TB), then it becomes difficult atleast from a system conversion standpoint.
Impact on business
This is the most important aspect. The impact on business will be huge in the case of a new implementation. However, it is not so much in system conversion.
No. of ERP users
The number of ERP users should be less than 5000. Otherwise, the conversion process can become very complicated.
Cut-over strategy is an approach to migrate the data from a legacy system to the new SAP S/4HANA system. This cut-over period should be as minimal as possible. Typically, Kaar Tech takes a little more than a weekend or two and a half days to complete the cut-over process, but again, it varies with each organization and the amount of data to be migrated.
No. of production runs
The number of dry sandbox and productions that are to be done before the actual production must also be taken into account while migrating from SAP ECC to SAP S/4HANA.
SAP S/4HANA Adoption methods
Primarily, there are three SAP S/4HANA adoption scenarios.
- New Implementation
- System Conversion
- Landscape Transformation.
New implementation is typically used for scenarios where the landscape is huge, database size is extremely large or the legacy system is more than 10 years old. Most of the business processes would have changed and the amount of customizations, custom objects and custom transactions would be exceedingly large. Hence, in such cases, an organization would be better off with a new implementation than going for a system conversion.
Landscape Transformation is a method adopted by organizations who are not ready for a huge transformation, but want to experience the benefits of SAP S/4HANA. Typically, these transformation programs take anywhere between 18 to 24 months and it’s a huge period considering the business impact. Landscape transformation includes the consolidation of the current regional SAP Business Suite Landscape into one global SAP S/4HANA system either by converting it or by re-implementation with selective data migration. System Conversion is a very viable option for those organizations whose legacy system is 8 to 9 years old, have less than 3TB of data and less than 5000 ERP users. It is the complete conversion of an existing SAP Business Suite to SAP S/4HANA.