Selective data transition is an alternative to the new implementation or system conversion approach and is relevant for companies moving from an existing SAP ERP solution to SAP S/4HANA.
As its name implies, this approach involves transferring data from one or more existing SAP ERP solutions to a new SAP S/4HANA solution.
Complex scenarios, such as consolidating multiple systems into a single SAP S/4HANA, require the involvement of SAP Services and Support and its specialized tools and services. Less complex business requirements indicate the use of SAP Business Transformation Center, which comes without additional subscriptions. In addition, some partners have their own tools and services. Note that this post focuses on selective data transition using SAP tools.
The data selectively transferred can include the following:
There are two common approaches for the target system creation within selective data transition: shell conversion and mix and match. In shell conversion, a shell copy of a production system is made without master data and transaction data and is converted to SAP S/4HANA. In mix and match, a new SAP S/4HANA install is created, and then elements of the configuration and ABAP repository are transported or manually transferred. Both scenarios require data migration to follow, including master data, balances, and open items. A comparison of the approaches is shown in this table.
The data is moved using Data Management and Landscape Transformation (DMLT) software and related services. For more than 10 years, DMLT tools and services have provided well-established solutions for organizational changes, acquisitions, divestitures, or harmonization of SAP landscapes. The software provides highly automated processes that move large amounts of data between SAP instances quickly. Similar software and services are provided by third-party vendors but fall outside of SAP’s support arrangements.
Next to DMLT and third-party vendors, the SAP Business Transformation Center offers standard SAP tooling for selective data transition approaches.
Selective data transition should be considered when organizations need to do the following:
The split and consolidation of SAP ERP instances is a large topic and won’t be covered in detail in this blog post. Instead, this post focuses on how selective data transition can be used to phase go-lives and accelerate projects. This may be required in SAP ERP solutions with large data volumes or with many users in multiple countries.
The starting point is to create a parallel SAP S/4HANA sandbox or development system. A new clean install of SAP S/4HANA can be used (mix-and-match approach). Alternatively, you can use DMLT tools to create a shell copy of an existing SAP ERP system (shell conversion). The shell contains the ABAP repository and configuration data without master data or transactional data. A system conversion is done to turn this into an SAP S/4HANA instance. The conversion process is simpler and faster without the master data and transactional data, and certain simplification items can be more easily implemented without business data.
DMLT or SAP Business Transformation Center are used for selective data migration of master and transactional data. If no historical transactions are required and only open transaction items are needed, the SAP S/4HANA migration cockpit (direct transfer scenario) may be the best option. DMLT allows a time slice of historical transactional data to be migrated.
Let’s consider an example project scenario using shell conversion. This assumes a two-stage project. The first stage is a technical transition followed by a second stage to implement business transformation innovations.
Let’s walk through the phases of the first (technical) stage, which is led by a technical team:
In the prepare phase of a selective data transition using shell conversion, you perform the following activities:
In the explore phase of selective data transition using shell conversion, you perform the following activities:
In the realize phase of selective data transition using shell conversion, you perform the following activities:
In the deploy phase of selective data transition using shell conversion, you perform the following activities:
After the technical transition stage is complete, a second project stage can be kicked off to implement business transformation innovations (e.g., adoption of SAP Fiori apps). The second stage is led by the business.
This approach is flexible and can be adjusted depending on your organization’s requirements, for example:
The following DMLT scenarios may be relevant in selective data transition. Scenarios 1 and 2 are used in our previous example.
In scenarios 2 to 4 with multiple source SAP ERP systems, the ABAP repository and configuration of the source systems must be compatible. These approaches require manual harmonization work in the source systems and target development system. Analysis tools that compare the source systems can identify the harmonization work required. The transformation can include data model conversion, Unicode conversion, and database changes to SAP HANA in one step. The project can take several months. Multiple test cycles are required in a dedicated sandbox system. SAP uses the test cycles to finalize configuration and generate programs to do the transfer.
Editor’s note: This post has been adapted from a section of the book SAP Activate: Project Management for SAP S/4HANA Cloud and SAP S/4HANA by Sven Denecken, Jan Musil, and Srivatsan Santhanam. Sven is the senior vice president and chief marketing and solutions officer for Industries & CX, SAP SE. He drives product marketing across SAP’s Industry & CX solutions, enabling customers’ digital transformation. Jan is the SAP Activate chief product owner at SAP. He leads a team of seasoned product managers responsible for SAP Activate, the innovation adoption framework aiding SAP customers and partners in deploying SAP solutions like SAP S/4HANA, SAP SuccessFactors, SAP Ariba, SAP Integrated Business Planning, and SAP Business Technology Platform. Srivatsan has been with SAP Labs, India, since 2004 where he is the head of the SAP Concur engineering product unit. He has two decades of industry experience and is one of the early pioneers and thought leaders in hybrid cloud/two-tier ERP landscapes within the SAP S/4HANA Cloud product space.
This post was originally published in 8/2021 and updated 3/2025.