Preparing the Productive System in the Deploy Phase

Executing the Production Cutover

Objective

After completing this lesson, you will be able to execute the production cutover plan by validating system readiness, completing all cutover tasks, and obtaining formal go-live approval in accordance with SAP Activate leading practices.

The Deploy phase

Introduction

With the Realize phase complete and all configuration workbooks signed off, the project now enters the Deploy phase. This is the final stage before the organization transitions to live operations. The Deploy phase is where everything that was built, tested, and validated during the project is brought together to stand up the production system, confirm organizational readiness, and switch business operations to the new solution.

High level diagram of six phases of SAP Activate methodology with the Deploy phase highlighted.

The purpose of the Deploy phase is to set up the production system, confirm the customer organization readiness, and to switch business operations to the new system.

Key activities during the Deploy phase:

  • Execute transition and cutover plans, including organizational change management (OCM) plans
  • Complete all scheduled end-user training
  • Identify and document all issues encountered in the transition to the new solution
  • Monitor business process results and the production environment through hypercare
  • Establish ongoing support mechanism as applicable
  • Track and report on value delivery
  • Transition to support organization

Production Cutover

Moving to Production

Before cutover to production can begin, the following readiness conditions must be confirmed:

Implementation Phase Status

The Realize phase is complete, all configuration workbooks are signed off, and User Acceptance Testing (UAT) has been successfully executed.

System Configuration Complete Status

All SAP SuccessFactors modules are properly configured in the test environment and business processes have been validated through iterative testing.

Data Migration Validation Results

Master data and historical data have been successfully migrated and validated in the test environment before the production cutover.

Integration Testing Outcome

Integration testing with all third-party systems — including payroll, ERP, and SAP S/4HANA — has been completed successfully.

Production Cutover Planning

With readiness confirmed, the cutover plan defines how data and configurations will be moved to production:

Data Migration to Production

Execute data loads for integration data in the production environment following validated migration procedures.

Historical Data Requirements

Migrate historical employee data using the full employee-data testing procedures validated during Iteration 3 testing.

Data Validation Checkpoints

Perform production checks for integrations and validate data integrity using testing scripts.

Backup and Recovery Procedures

Implement backup strategies and ensure recovery procedures are in place before go-live.

Execute Cutover Tasks as per the Cutover Plan

Purpose

The purpose is to cut over to the productive system, obtain customer approval (sign-off), validate that the go-live acceptance criteria have been met, and confirm the successful go-live.

Procedure

  1. Execute the cutover to production, following the tasks defined in the cutover plan.
  2. Document the actual duration of each step to support future projects.
  3. Capture any variances to the plan along with the decision maker who approved the change.
  4. Cutover manager(s) should proactively notify task owners of upcoming tasks to ensure their availability.
  5. Regularly communicate status to stakeholders.
  6. Test and validate the systems after the cutover has finished.
  7. Obtain the production approval sign-off, which documents stakeholder agreement that cutover tasks have been successfully executed.

Procedure Note(s)

See the Accelerator section for related documentation.

Accelerators

Case Study: How Pinnacle Industries Executed the Production Cutover

With Realize phase sign-off obtained, Pinnacle Industries moved into production cutover. The project manager and cutover manager executed the cutover plan developed and rehearsed during the Realize phase.

Key Activities

  • Confirmed all four readiness conditions — signed-off configuration workbooks, validated system configuration, migrated and validated data for all 15,000 employees, and all 11 integrations tested and signed off
  • Executed the production data load, performed validation checkpoints using test scripts, and confirmed data integrity across all integrated systems
  • Ensured backup and recovery procedures were in place before proceeding
  • Proactively notified task owners, communicated status to all stakeholders, and documented actual durations and variances throughout the weekend
  • Completed post-cutover system validation and obtained formal production approval sign-off

Outcome

Pinnacle Industries completed production cutover with all data loads validated, all integrations confirmed operational, and formal go-live approval obtained — clearing the final gate before the system was released to the business.

Summary

  • The Deploy phase is the final transition from the project environment to live business operations — all Realize phase activities must be completed before it begins.
  • Four readiness conditions must be confirmed before cutover: implementation completion, system configuration, data migration validation, and integration testing.
  • The cutover plan is the execution blueprint — follow it step-by-step, document actual durations, and capture all variances with the approving decision-maker noted.
  • Data validation checkpoints are critical — validate data integrity in the test environment before moving anything into production.
  • Stakeholder communication must be continuous throughout cutover — proactive notification of task owners and regular status updates helps prevent delays and confusion.