Often, the most crucial and critical part of any cloud migration project is the cutover process. Getting the cutover right is half the battle won. So what actually is cutover, what needs to be planned and how do we plan it better. Read on to find out more about this.
Cutover is a general IT term used to refer to activities that have to be performed from switching over from an old system to the new one. In the context of SuccessFactors Employee Central implementation, the 'cutover' encompasses a broad list of activities starting with setting up the productive instance's provisioning settings, loading data model XMLs, enabling diverse configuration in the productive instance, loading certificates to name just a few. The actual master data (employee and organizational data) come at a later point in time of cutover which is the focus of the document. The cutover focuses on the migration of the master data from SAP ECC to Employee Central using Infoporter as a tool.
Making the Right Choice
To use either file transfer(CSV import files) or web services as a communication channel to migrate the master data using the Infoporter is an important decision. There are different parameters which are discussed in the document that drives the decision of whether to choose web service or file transfer. In general, we have noticed that web services mode of communication is generally being implemented by large scale implementations successfully considering that there are standard job scheduler reports to migrate large volumes of the dataset. The pros and cons of using these communication channels are discussed in detail in the implementation design principle document.
Planning the Cutover Process
A high-level cutover process overview is provided below to familiarise with the cutover activities that need to be planned and executed:
Preparation of SuccessFactors Employee Central System
Deploy the Employee Central System
Configure the Employee Central System
Load Foundation data
Load other configuration data relevant for Employee Central system
Start Data Freeze Period in Source System
Load Actual Organizational Master Data
Load Employee Master Data
Validation of Data Migration
Additional tasks in Employee Central before releasing for changes
End of Transaction Freeze Period
Data change to be enabled for a specific pilot user group
Preparation of Employee Central for Go-Live
Activate rules, permission and other such activities
Activate replication of Employee Central changes to SAP ECC
While you plan and execute the cutover process, it is equally important to optimize the transaction freeze period which entails another set of crucial activities that needs to be planned and accounted in the cutover. Some of these are data quality, cutover testing/simulations, cutover preparation, data migration initial load, cutover plan, point-of-no-return, operation modes, and Employee Central rules which are discussed in the Implementation Design Principle document in detail.
Figure 1. High-Level Overview of Cutover Activities Involved During the MasterData Movement
(PHR & QHR are the indicative names of the SAP ERP HCM systems; PHR for Productive SAP ERP system & QHR is the Test SAP ERP System)
We will look forward to hearing your feedback on the document and also see if there are other topics within cutover which are of interest and need more details.