For many companies today, it is a necessity to take full advantage of the many opportunities offered by digitization in their day-to-day business. This is the only way they can develop their company further and establish new business models. Only this way can they also secure or further expand competitive advantages in the long term. The necessary conditions for this change are created by modern IT landscapes such as the cloud-based real-time ERP suite SAP S/4HANA.

Actual status of existing ERP systems

ERP systems are the heart of many companies. Numerous data and business processes originate there. The larger a company is, the larger its ERP system usually is or will be. As a consequence, the systems become more and more complex. This not only reduces maintainability, but also efficiency, which in turn increases operating costs. In addition, it is often difficult to train new employees in historically grown systems due to unwieldy user interfaces and many processes that have been individualized over the years. If the performance of your ERP system is declining and new processes can only be implemented using costly workarounds, one should become alert. Because these are signs of outdated systems – and a need for a system change.

Greenfield, Brownfield, or Selective Data Transition – Pros and Cons

Choosing the right migration strategy is essential for the success of your transformation. After all, it sets the framework for your project and thus directly influences the adherence to time and budget targets. Overall, you can choose between three different migration methods to get to SAP S/4HANA:

1. Brownfield approach

In the brownfield approach, the existing overall system with all existing data and processes is migrated to SAP S/4HANA. This method is suitable if you are satisfied with your legacy system and the dataset is kept up to date. This is the case, for example, if the last transformation of existing systems (in the case of company acquisitions or sales) happened not too long ago. However, if you are not satisfied with the status regarding legacy data and processes, this can quickly become a cost driver for your migration. And without you ultimately benefiting from the desired added value of the new environment for your company.

2. Greenfield approach

With the greenfield approach, you start with a completely new S/4HANA installation. In this case, the system is set up independently of the legacy system and only the current data is migrated. The advantage of this is the possibility to start anew in terms of processes and data structure. The disadvantage: Historical customer and order data that is still needed could require a complex conversion project. This is because the data would have to be transferred almost manually. In addition, previous investments in the SAP ECC system are lost with the greenfield method. It is also a challenge for change management in the company.

3. Selective Data Transition

Between the two very opposing migration strategies, there is a third strategy called Selective Data Transition (SDT) - also known at Natuvion as the ALLFIELD™ approach. This is a hybrid of the brownfield and greenfield methods that combines their advantages and minimizes restrictions. It allows you to transfer all the data and processes you need while at the same time benefiting from technological innovations. In the Selective Data Transition, the existing SAP ECC system is transferred to SAP S/4HANA as a functionalshell. Subsequently, the required data is migrated and legacy data is archived or deleted. The Selective Data Transition is an ideal opportunity for you to check established processes and data for up-to-dateness and quality and, if necessary, update them with best practices from the new environment.

The three migration strategies at a glance

5 project phases to achieve your goal

1. Discover

In the first step, we work together with you to determine the relevant migration objects, the data usage, and volume, and the processes to be migrated, including all changes. Based on this, we give you a recommendation for the future system environment including the test- and production environment.

2. Prepare

We then set up the transformation environment and -software and create an action plan in which the responsibilities are recorded. For a smooth transition to live operation, we also recommend an appropriate test strategy.

3. Explore

In the next step, we coordinate the required technical processes for data migration individually for your project and define a security concept for the data protection architecture. At this point, the framework for the cutover - the concrete conversion of the system - is also defined.

4. Realize

In the penultimate step, we implement the procedure agreed with you. The transformation software is configured, the GRC rules are updated, and anonymization and pseudonymization functions are implemented within the framework of data protection. Subsequently, we perform data migration test cycles and you perform end-to-end process tests. Based on these tests, the migration rules and settings are adjusted.

5. Deploy / Run

In the final step, we work together with you to simulate the conversions to live operation in accordance with the cutover plan. This is controlled via agile processes and the entire system, including all GRC and data protection components, is finally tested. Due to the phased approach and intensive preparation, the go-live almost always runs smoothly.

Extensive experience and the right tools

From our years of experience and expertise, we have developed a repeatable, field-tested concept for transformation processes. This not only guarantees our customers more stability and a higher success rate in the project, but also creates cost advantages. Are you wondering how we achieve this?

The heart of our model and at the same time our distinguishing feature is the in-house Natuvion Data Conversion Suite (DCS). This is where we run our intelligent, cloud-based transformation software. With the Natuvion DCS, we accelerate and automate the activities of your transformation processes. For example, it supports your project team in integrated quality assurance through automated testing. In addition, the Natuvion DCS provides a tamper-proof audit trail of all activities for control purposes through your auditors.

Another success factor is the organization of our employees in functional teams according to business units and industries, e.g. for HCM/Payroll or Utilities. In this way, you benefit from our experts' deep and established understanding of your individual requirements for data structures and process modeling.

And we are also officially part of the SAP transformation elite: As one of only four companies worldwide, we have been part of the Selective Data Transition Engagement (SDTE) Community since 2018. In this working group, we jointly define best practices for the transformation to SAP S/4HANA. Our collaboration with SAP product management and the SAP teams is very close.