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

9 min read

Migrate to SAP Commerce Cloud

In this set of articles we provide a breakdown of the recommended approach to migrate to SAP Commerce Cloud in the Public Cloud and provide answers to common technical design questions raised in previous migration projects. The contents of these can be applied to migrations of either on-premise versions of SAP Commerce or SAP Commerce Cloud on SAP Infrastructure.

Table of Contents

Migration Services and Qualification

If you're interested in migrating your existing solution to SAP Commerce Cloud in the Public Cloud, please consult with your Account Executive or Customer Engagement Executive for more information. SAP offers a variety of migration services to assist you, including services to assess if you are qualified to migrate, identify any potential issues, and provide a high-level estimate for a migration project. Similar services may also be offered by your System Integrator/Partner and are supported by SAP.


A migration project is defined as the movement of an existing SAP Commerce implementation–on-premises or on SAP Infrastructure–to SAP Commerce Cloud in the Public Cloud. It is important to note SAP Commerce Cloud does not support all versions of the SAP Commerce runtime. For some migrations there may be a pre-requisite upgrade required to a compatible version. If you aren't on a compatible version consider reviewing our content on upgrading your SAP Commerce runtime at Upgrading your SAP Commerce Solution

The migration project delivery can be executed by SAP or by your preferred System Integrator/Partner: this article focuses on the latter case. It is important to notice that, in cases which require a direct database-to-database migration of the data, or in cases when you want to upload an already-existing media folder straight to the media storage on SAP Commerce Cloud (without uploading the data in the commerce interfaces), these activities require the mandatory involvement of SAP. This is due to security and privacy regulations of the public infrastructure. For more information, please refer to Migrating to SAP Commerce Cloud: Data and Media Migration.

It is also important to note that SAP Commerce Cloud on Public Infrastructure runs a different concept for infrastructure orchestration: containerized pods with a standard specified size versus custom virtual machines (see Getting Started with SAP Commerce Cloud). The scaling feature also allows for average usage sizing rather than the typical peak usage sizing which is common for the on-premise hosted installations. Because of these differences, it is important to run your project on the Cloud through thorough performance validation to validate the code performs efficiently on the new sizing principles, both at average and peak times. 

Migration supporting packages

In order to provide you with the best chances of success, SAP provides a full offering of services that will benefit your migration project. 

Service Package 1: Migration Assessment

Assess your existing SAP Commerce project (either on premise or on SAP Infrastructure) to validate your solution readiness and identify potential challenges of migrating to SAP Commerce Cloud in the Public Cloud.

For more details please see the Info sheet.

Service Package 2: Data and Media Migration Service

Perform a database-to-database migration from your existing on premise of SAP Commerce Cloud on SAP Infrastructure database to your SAP Commerce Cloud on Public Infrastructure database, and a direct media copy from your existing media folders to the Media Blob Storage of SAP Commerce Cloud. More details of this package are covered in our article Migrating to SAP Commerce Cloud: Data and Media Migration.

Additionally, you can review the Info sheet.

Service Package 3: Cloud Readiness Check

This package comes included with your SAP Commerce Cloud subscription, and is delivered during your project's implementation to ensure your project passes the mandatory quality gates for deploying an SAP Commerce Cloud solution. 

For more details please consult the Info sheet.

Service Package 4: Migration Guidance Service

The service provides a custom-tailored package to support your migration project from the beginning to the end, including cutover support, if needed. 

Please contact your SAP representative for more information about this service. 


This table highlights the different stakeholders in the migration project and who should be responsible for each activity. 

Activity Responsible
Customer SAP Partner
Migration Analysis



Service package 1: Migration Assessment (optional) R A
Project Planning and Management R I A
Project Delivery (environments setup, code adaptations, lift & shift, build & deploy) R
Service Package 2: Data and Media Migration Service R A
Performance Validation R I A
Service Package 3: Cloud Readiness Check R A
Service Package 4: Migration Guidance Service (optional service) R A
UAT Issue Fixing R
Go Live R I


The diagram below offers a further level of detail.

Known Blockers and Risks 

Prior to a migration we suggest you to evaluate and challenge your current solution design and infrastructure setup against SAP Commerce Cloud in the Public Cloud.

Please refer to the Checklist for Succeeding with SAP Commerce Cloud and SAP Commerce Cloud Architecture for further detailed information.

Consult SAP Consulting Experts to assess your solution by choosing the Migration Assessment Service.

Code Freeze options

A migration project for SAP Commerce Cloud could take up to several months. During this time, there is often an expectation that code can be deployed to the existing site in parallel to migration activities. At some point, no more changes will be allowed in order to align the code. However, when and how you freeze the code can have varying levels of impact on both business-as-usual operations and the ability to deliver a migration. Learn more about different code freeze options available to consider for use with your migration project. M


For your planning consideration please refer to the article Migrate to SAP Commerce Cloud: Project Planning Considerations.


Please refer to the article Migrate to SAP Commerce Cloud: Technical Considerations for the list of technical considerations to support your migration project. 


SAP Commerce Cloud migration involves migrating your development environment first, to pass through the intermediate staging and quality layers, and finishing up with your production environment. As each environment is being migrated, it is helpful to keep an activity log of what was done to setup and configure them. Ultimately, this methodical approach helps build your go live checklist as you migrate one environment to the next. The resulting list will form the foundation of your go-live plan. The final go-live plan should be reviewed by every member with a participating role for go live. Each step of the plan should be reviewed by all for accuracy and completeness. Furthermore, the plan should be tested until trusted. Every participating member should also be fully aware of not just the plan but also the schedule.  

Being ready to take your site live, is not just about ensuring you can deploy your code into production: the Go Live Readiness for SAP Commerce Cloud walks you through additional considerations like addressing the readiness of your team and providing a sample go live checklist. G


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 asked by customers, 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