Migration from SAP ERP to SAP S/4HANA
With SAP S/4HANA, you can not only manage your business in real time, but also modernize and automate your business processes at the same time. We guide you through a secure and goal-oriented migration or new implementation and show you what to look out for along the way. In addition to the traditional transformation, we also consider the future operating model and help you determine whether cloud-based ERP scenarios are a viable option alongside established approaches.
Are you ready for the switch to SAP S/4HANA?
By the end of 2027 at the latest, all SAP ERP users should have switched to SAP S/4HANA, after which they will only wait until 2030 and for an additional charge.
We therefore recommend that you start now with initial pilot projects and system analyses—and consciously use this transformation as an opportunity to set a strategic course. With INFORMATICS as your partner, the first essential step on the "Road to S/4HANA" has already been taken. We provide structured support through every phase—from analysis and selecting the right migration approach to evaluating future-proof operating models.
Step by step, we guide you through the key stages of your “Road to S/4HANA” with our recommendations and practical tips.
Step 1
System evaluation by means of basic packages
Start planning your migration from your SAP ERP system to S/4HANA today and ensure your system landscape is fully prepared for the transition. The three tools— Readiness Check, Process Discovery, and the ATC Check —for the pre-project phases lay the technical groundwork for a successful implementation project.
At the same time, the insights gained provide a solid foundation for making decisions about the future direction of your ERP strategy—both in terms of the appropriate migration approach and the question of the future operating model, such as whether cloud-based options should be considered alongside traditional scenarios.
Step 2
Definition of conversion - greenfield approach or conversion?
Many SAP ERP users are planning to migrate in the coming years.
To ensure a successful transition to SAP S/4HANA, it makes sense to start addressing this issue now. Depending on your company’s strategic direction, the question arises as to whether a greenfield approach or a conversion of existing systems is the right path to take. Increasingly, this decision is also being considered in the context of the future operating model—for example, whether SAP S/4HANA should continue to be operated on-premises or, in the future, also in a cloud-based scenario.
Re-implementation with the Greenfield Approach
With the greenfield approach, the new SAP S/4HANA system is implemented in parallel with your existing ERP system.
This approach gives companies the opportunity to fundamentally reevaluate and redesign existing processes in order to fully leverage the potential of SAP S/4HANA. Access to best-practice models supports the design of innovative processes and increases efficiency during implementation. On the day of the system migration, all master and transaction data, as well as all open documents, are transferred to the SAP S/4HANA system. Particularly in a greenfield approach, it is often also assessed whether standardized processes can be optimally utilized in a cloud-based environment.
System takeover with a conversion
Conversion is an alternative approach to migrating to SAP S/4HANA. If you want to retain your proven processes and workflows, converting your existing SAP ERP system is a suitable option.
This approach is particularly useful when:
- extensive Z-developments are in use
- multiple branches access the existing system
- historical data plays a key role
During the pre-project phase, your system (Z-developments, add-ons, and data) will be checked for compatibility to ensure that your system landscape is optimally prepared.
On go-live, all data—including historical records—will be fully converted.
At the same time, a conversion can also serve as a starting point for a phased transition—for example, toward a modern, cloud-based operating model.
Which path suits your company?
Regardless of which strategic approach is right for your business, we’ll guide you through your journey to SAP S/4HANA.
Together, we’ll start by exploring initial ideas, define the next steps, and begin working on the most important tasks in the preparation phase.
These so-called “preliminary projects,” which can be launched within the existing ERP system, are essential. They:
- help improve data quality by cleaning the data
- support the conceptual direction, as valuable insights can be derived at an early stage
- enable sound planning of time and resources
As simple as it may sound, the “Road to S/4HANA” also begins with the first step.
Let’s take this step together.
Step 3
Pre-projects for SAP S/4HANA
Conducting preliminary projects early on is a key factor in ensuring a smooth migration to SAP S/4HANA. These projects establish the necessary technical and business prerequisites while also providing valuable insights for further project planning. Regardless of which transformation approach or future operating model is chosen, these initiatives form the foundation for a stable and future-proof system landscape.
Conversion to Unicode
The transition to SAP S/4HANA requires, among other things, migrating your SAP system to Unicode. This is an international standard for the uniform encoding of scripts and character sets.
In practice, this means that customer-specific programs, interfaces, and extensions, in particular, must be checked for potential incompatibilities and adapted accordingly.
To assist with this, SAP provides the UCCHECK transaction, a tool that can be used to identify affected objects.
The Unicode conversion should be performed as early as possible to ensure that all subsequent developments and customizations are based on this foundation.
Business Partner/Business Partner
In SAP S/4HANA, the business partner serves as the central master record, through which various business relationships—such as customer or supplier—are represented using business partner roles.
As part of the migration, existing customer and supplier master records will be converted into business partners and linked to one another. In this context, master data cleansing is often advisable or necessary.
We recommend performing the business partner conversion close to the actual migration date. The reason for this is that full production use in SAP ERP is limited due to functional restrictions (e.g., in transaction BP), and the use of the CVI (Customer-Vendor Integration) interface should be kept to a minimum.
New General Ledger | New GL
With SAP S/4HANA, the new general ledger is mandatory and can be implemented either as part of a preliminary project or directly during the migration.
Among other things, New GL enables the parallel mapping of different accounting regulations across various ledgers without the need for complex account structures.
It also serves as the foundation for additional functions such as document splitting, as well as modern reporting and analysis applications.
Do you have any questions?
Our colleague Klaus Augner is always available to answer any questions you may have.
Head of Sales
Webinars for your Road to S/4HANA
Our experts explain in detail what changes when switching to SAP S/4 HANA and which innovations and functions may be of interest to you. The webinars are relevant for IT, business and key users.
You can view past webinars on individual topics or subject areas as well as register for upcoming ones.
