SAP GRC Migration from Standalone system to S/4 Embedded Systems

Embedded GRC architecture:

Thus, the customers who are on SAP GRC v1200, it is imperative to migrate to the embedded version. Wondering how it can be carried out?

To simplify, the SAP GRC migration is not similar to other products such as SAP S/4 HANA. It’s a Lift and Shift migration, which is the rehosting of the GRC application. This means that migration is accomplished without any changes rather than it is a copy of the master data, some part of the transactional data and the configurations and workflows in to a different SAP infrastructure. This approach involves “lifting” the data from the current system and “shifting” to a new environment or landscape.

There are various techniques to perform the GRC Migration. Let’s discuss them briefly.

1. Manual migration – In this approach, the configuration settings, Master data, common settings, etc., in the GRC standalone system are manually replicated in the GRC embedded system. The transaction data such as requests, mitigation controls, change logs etc., can’t be migrated to the new system. This process is completely a manual effort and is easier to migrate the data from one source system to the target system.
   
   Audit Recommendation: It is recommended to keep this system ALIVE for a few years to meet the audit requirements. Alternatively, the data can be exported into flat files or archived to meet the audit requirements. 
   
   
2. SAP Landscape Transformation Replication Server (SLT) – This is a powerful tool offered by the SAP that enables the real-time data migration without any downtime of any SAP application. This feature helps in the swift migration & replication of the data in the continuous flow. SAP SLT offers a high speed of data migration with millions of records in a short span of time. This tool is easy to configure and monitor. SLT has capabilities for customised migration requirements that can be easily replicated in the target system as per the client. This tool is expensive and requires specialised resources to perform the migration & replication of data. However, even SLT has some limitations on the transactional data migration which needs to be handled manually.
   
   
3. Data Management and Landscape Transformation (DMLT) – This solution is complex and requires specialised resources to monitor and manage DMLT. This solution has the ability of one-time data migration & system consolidation from the source system to the target system. DMLT is helpful in the large projects of migration & system transformations for the organization which has a presence across the globe.

Migration Approach:

A right approach helps the project go smoother. I recommend to adapt to an approach which best fits your organization. We followed the below mentioned approach in the projects that were handled by our team:

Select the right approach

Have a detailed assessment & planning

Evaluate the system

1. Detailed Assessment & Planning – Need to make the clear scope of the project of migration and analyse the current state of the system, data volume, and current customisations in the SAP GRC standalone system.  All the project stakeholders are involved in the migration planning.
   
   
2. System development– The target embedded system to should have the required hardware and software components for SAP GRC like “GRCFND_A”. Also, perform some basic configurations like setting up RFCs.
   
   
3. Migration Execution- You have to choose the tool or technique discussed above for migration that suits your requirements. Perform the initial steps of migration of data from the source system to the target system. Validate the migrated data to check accuracy and completeness.
   
   
4. Go-Live & Production support – The output of the migrated data from the standalone system to the embedded system needs to be checked it is working fine. The new system has to be observed in a such way that all data migrated is as per the scope defined initially. Provide post-go-live support to address any issues that arise.

The best practices for Data migration depend on the various aspects like the no.of systems, integrations, master data, configurations, enhancements and so on. The above approach have various capabilities to perform according to the exact requirements of the data migration project.

ToggleNow difference:

ToggleNow has the required expertise in migrating SAP GRC system from a standalone environment to an embedded environment. Additionally, ToggleNow offers a customized SAP GRC Migration tool that will move the configuration and master data quickly with the lift & shift approach. It has the capability of migrating some of the Transactional data as well from the source system to the target system.

This robust tool helps you to migrate and replicate the data by connecting the RFC connector and making a streamlined process for the migration leaving no scope for errors with the configuration and data migration. This approach provides fast, cost-effective, and reliable migration with benefits like cost savings, scalability, and speed.

Read an interesting case study on SAP GRC migration.

https://togglenow.com/assets/case-studies/Migrating-SAP-GRC-Access-Control-from-Standalone-to-S4-Embedded.pdf