CX Works

CX Works brings the most relevant leading practices to you.
It is a single portal of curated, field-tested and SAP-verified expertise for SAP Customer Experience solutions

Migrate to SAP Commerce Cloud: Project Planning Considerations

9 min read

Migrate to SAP Commerce Cloud: Project Planning Considerations

This article provides guidance to support your migration project planning. If haven't already done so we recommend you begin with our article Migrate to SAP Commerce Cloud, which covers many of the fundamentals of migrating your solution to SAP Commerce Cloud in the Public Cloud.

Table of Contents


Milestones planning 

Below you can find an example of a milestone plan for an SAP Commerce Cloud migration.

Please notice that the duration expressed below in weeks is only an example; each milestone's duration will depend on the complexity of the activities, the number of developers assigned and on the degree of parallelization of tasks. 

In this example, three environments are considered: development (DEV), staging (STG) and production (PROD). However, additional environments are available on demand and can extend your project's scope, depending on your SAP Commerce Cloud contract.

Milestones Description

Must-do's and highlights of the above milestones include the following:

Milestone Key activities and considerations Helpful Links
  • Define details of your migration: for example, what detailed solution to adopt for each of the necessary code adaptations
  • Ensure the project prerequisites are met: for example, that the necessary resources from each party are planned to be available at the right time
  • Detail out and finalize project planning
  • If you require a direct database migration and media folder upload, involve SAP Consulting to plan for the delivery of the Data and Media Migration service
  • If you require additional support to identify all the necessary project activities, you can involve SAP Consulting for the delivery of the Migration Guidance service

Migrating to SAP Commerce Cloud: Data and Media Migration

Migration assessment service
  • Provide an in depth input to your project planning with an accurate view of your system in perspective of the upcoming migration to SAP Commerce Cloud

Commerce Cloud Migration Assessment Service Info Sheet

Environments setup
  • Get access to the SAP Cloud Portal (comes with a valid subscription)
  • Connect your GIT code repository to the Cloud Portal and create the manifest configuration
  • Build, deploy and execute smoke tests in DEV environment

Getting Started with SAP Commerce Cloud

Build and Deploy Your First SAP Commerce Cloud Project

Code Repository Setup

Adding a Build Manifest to your Code Repository

Code adaptations
  • Implement and test the needed code changes to adjust to the new infrastructure setup
See Code Adaptations
Data and media migration
  • SAP activity aimed at migrating the source database and media folders to the new environment
  • After this service, a system update and Solr index will be necessary
Migrating to SAP Commerce Cloud: Data and Media Migration
Lift & shift
  • Configure endpoints
  • Configure certificates
  • Configure IP Filter sets
  • Configure redirects
  • Configure static files
  • Third parties reconfiguration to the new system
  • Optional configuration of the VPN setup (if needed)

Cloud Portal

Setting Up a VPN for SAP Commerce Cloud

QA Testing
  • Light testing phase carried on by the implementation team
  • Ensure the newly configured system is working as expected

Code promotion and setup
  • Promote the code to the next environment
  • Setup the target environment and perform a build and deploy smoke testing
  • Adjust the manifest configuration for this environment if necessary
  • Cloud Readiness Check performed by SAP
Implement Continuous Delivery with SAP Commerce Cloud
Performance testing
  • Validate the performances of your application
  • A temporary change of STG sizing can be requested to test in a more production-like environment
  • Test the performance to ensure both:
    • The introduced code changes are not introducing a performance degradation,
    • The performances of the application at peak and average are satisfying the expectations.
  • NFRs could be collected from the existing application to ensure that the application in SAP Commerce Cloud performs as well or better than the original system
  • Ensure the results of the performance testing are shared with the Customer and are signed off before moving to the next stage

Managing Performance in an SAP Commerce Cloud Project

See "Performance Benchmarking" section of Migrate to SAP Commerce Cloud: Technical Considerations

  • User Acceptance Testing: ensure the Customer is satisfied with the system before proceeding
  • Ensure the UAT phase is documented (in terms of bugs found and their resolution status) and that it is signed off by the required stakeholders

Pre-cutover activities
  • Configure the PROD system for the go live
  • SAP to prepare the data and media migration activities for the go live
  • Prepare the thirds parties for the new PROD reconfiguration
Migrating to SAP Commerce Cloud: Data and Media Migration
Go live
  • SAP to migrate the data and media
  • Reconfigure thirds parties to point to the new system
  • Test the PROD system
  • Go/no go decision
Go Live Readiness for SAP Commerce Cloud
Post-cutover activities
  • Post go live support

To understand the migration process in more detail, please consult the following video: SAP Commerce Cloud: Migration Strategies

Strategic Planning

A default setup in SAP Commerce Cloud has three environments: development, staging and production. In case you have more than those to migrate, you can request additional environments in SAP Commerce Cloud. When it comes to project planning, you should also consider how you might parallelize activities on some of these environments. Consider the following while planning the dependencies:

  1. Define how many environments have to be migrated
  2. Define how one environment differs from another (e.g. DEV1 and DEV2 might be an exact copy incl. database. Therefore you might consider migrating the first environments and then using a snapshot, rather than performing two separate data migrations)
  3. Define quality gates (e.g. DEV1 and DEV2 to be closed off before STG1 is going to be migrated)
  4. Define critical path for sign-off (e.g. DEV1, STG2 (UAT), PRD1)
  5. Consider doing parallel development activities (by when will the development teams start to use development infrastructure e.g. after STG1 UAT development cycles will be stated on DEV1)

The diagram below shows an example of parallelized activities in several environments to a very high-level, with the following considerations:

  • The environments in scope from lower to higher are: DEV1, DEV2, STG1, STG2 and PRD1
  • DEV1 and DEV2 are identical, used for different scopes
  • DEV1, DEV2 and STG1 have no dependencies on each other
  • STG1 is the integration testing environment
  • It is mandatory that STG1 is fully tested before STG2 can be tested
  • STG2 has a similar configuration to STG1, with some amendments
  • STG2 is the environment dedicated to UAT
  • A successful UAT is the mandatory quality gate before the PRD1 go live


This article provided you with the resources to understand how you can embark on a migration to the new SAP Commerce Cloud. You should now be familiar with the overall approach for migrating your commerce solution, the steps you can take on your own (or with a partner) as well as the steps that require SAP involvement. Although the article tries to answer many of the questions we are asked, there will always be specific scenarios that may need more clarification. If this is the case or you are interested in starting a migration, please consult with your Account Executive, Customer Engagement Executive or reach out to