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

Migrating to SAP Commerce Cloud: Data and Media Migration

10 min read

Data and Media Migration from On-Premise to SAP Commerce Cloud in the Public Cloud in a partner-led project

Looking to migrate your existing SAP Commerce project to SAP Commerce Cloud in the Public Cloud? This will require a lift and shift of configurations along with integrations, data, and media replication from the existing site infrastructure. In most cases, this will include a database change and a new way to save media. This article focuses on the procedure and required steps to perform the database and media migration. If you're wanting an overview of the entire migration procedure, please see our article "Migrate to SAP Commerce Cloud".

Table of Contents

Data and Media Migration

SAP offers a dedicated service called "Data and Media Migration Package" to set up and run data and media migration from your existing system (be it on-premise, on a different Cloud provider or on SAP Commerce Cloud with SAP infrastructure) to SAP Commerce Cloud in the Public Cloud. This package addresses the need to perform database-to-database migrations on your behalf since by moving to SAP Commerce Cloud, you agree to use a fully managed infrastructure. 

The package consists of the following four phases:

  1. Planning
  2. Establishing Secure Connectivity
  3. Data and Media Migration
  4. Post-Migration Activities

SAP Commerce Cloud on SAP Infrastructure Migration

This Data and Media Migration service is mandatory for any partner-led migration project where the data is migrated in a database-to-database fashion from an existing SAP Commerce Cloud on SAP Infrastructure. This is because only SAP has access to the infrastructure for SAP Commerce Cloud. If you engage SAP to deliver your migration project end-to-end, this service will already be part of the project scope.

Database and Blob Storage access on SAP Commerce in the Public Cloud is restricted to SAP and assigned on a need-to-have basis to a specific migration team. This restriction is in place for all of the environments provisioned in your subscription (Development, Stage, Production, or any other additionally purchased environments) because of the following:

  1. Information Security
  2. Networking Constraints
  3. Separation of Concerns for Operations

On-premise Migration

In case of migrations from an on-premise system (not previously hosted on SAP Infrastructure) the Data and Media Migration Service can still be requested, but it is not mandatory–the migration can be executed in a fully self-serviced manner by the Customer/Partner. The following are available to assist with migrating database and media: 

  1. Database migration: you can download and use the Commerce Migration Toolkit. Please note that:
    1. The toolkit is a Code Template only, so it is NOT supported by SAP Support.
    2. If you require help, SAP CX Services can be contacted. 
    3. The toolkit is a Code Template meant to give you guidance of how to execute the migration. If you wish to contribute and share back with SAP your improvements, please do so by following the guidance in the self-contained documentation.
  2. Media migration: please see Migrate to SAP Commerce Cloud: Migrate Media with AzCopy.


This package is delivered by SAP CX Services with the support of the SAP Cloud Operations & Support (COS) team to provide access to the necessary infrastructure. The service supports all the most common SAP Commerce database types and applies the migration-specific changes related to the data definition. 

Roles and Responsibilities

While the preferred implementation partner is responsible for all aspects of the migration project, SAP will focus on the migration of the database and media. 

Through the Data and Media Migration Package, SAP CX Services will:

  1. Align with your project plan about when the data and media migration needs to be executed for each of the in-scope environments.
  2. Provision the infrastructure for migration and establish the connectivity between your source SAP Commerce instance and the provisioned SAP Commerce Cloud instance.
  3. Run one migration for each of the defined environments. This will provide the target systems with database schema, data, and media.
  4. Ensure data and media are migrated correctly and in a timely manner.
  5. After a successful go-live, decommission the migration infrastructure.

Migration Concepts

The data and media are copied from your existing source to the target instance of SAP Commerce Cloud. The migration occurs in a like-for-like environment to ensure data segregation and security, that is, Development to Development, Stage to Stage, and Production to Production. 

The migration infrastructure in the diagram below is comprised of:

  • A migration service that will orchestrate the migration and provide the correct connectors for the source and target databases and media servers. Additionally, it will provide any necessary database translation services.
  • A migration server that performs heavy data copying.

In case the source system's database differs from the target's database in SAP Commerce Cloud, data transformation might be necessary. The package accounts for this. 

Databases that use a case-sensitive collation are not supported by SAP Commerce Cloud. For specific use cases a different collation can be requested by the Customer by opening a support ticket.

To ensure the data is copied correctly, the source and target databases must be on the same schema, meaning the same code version.

Migration Phases


Since data and media migration is an integral part of a migration project, it is critical that SAP resources can work seamlessly as part of the delivery project. This means that the identified team needs to be available to perform the data and media migration at specific points in the project's lifecycle. Careful planning needs to occur between SAP, the customer and their preferred implementation partner.

This phase also defines which environments will be involved in the data and media migration. The typical setup involves three environments (Development, Stage, and Production). However, every customer is different, and the need to migrate fewer or additional environments may exist. For example:

  • Some development environments might be re-initialized when deployed. Therefore, their data and media could be excluded from a particular migration project.
  • An additional environment could exist in the landscape containing important data to migrate (for example, a pre-production system with lots of test data).

For these reasons, it is crucial for the SAP activities to be aligned with the dates defined in the project plan. The activities to be planned for are:

  1. Establish the Connectivity: This needs to be set up for the first data migration to occur and requires you to have a valid subscription on SAP Commerce Cloud. This phase sees the interactions between your networking team, SAP CX Services, and SAP Cloud Operations & Support. Therefore, time should be set aside for it to ensure that all parties are aligned and the connectivity has been established successfully.
  2. Data and Media Migration: This needs to be planned for each in-scope environment and requires the code base to be migrated and deployed on the target environment. Since the data migration is a one-time procedure using the resources of the source and target databases intensively, the Production data and media migration needs to occur during the cutover phase.
  3. Post-execution: Decommissioning the resources used during the connectivity needs to occur. Typically, this occurs after a successful go-live. 

Last, but not least, the pre-requisites for the data and media migration are shared with the project to ensure they are delivered in time for the migration execution. 

Connectivity Using Dedicated VPN Tunnel

The Data and Media Migration Package comes with a dedicated VPN tunnel to secure and optimize the migration. The following principles are applied:

  1. Secure the transfer so no unauthorized person can hook, record, or steal your data before, during, or after the migration.
  2. Provide a 650 Mbps VPN throughput to ensure a reduced transfer time duration and a faster go-live.
  3. Support your networking team with the VPN setup.

To follow SAP's best practices, a dedicated VPN connection is provided with the following steps:

  1. SAP CX Services will work with SAP Cloud Operations & Support to provision the necessary infrastructure on SAP Commerce Cloud.
  2. SAP will issue you a form to share the VPN setup.
  3. You will then complete the form with the requested information (VPN endpoint, peer IP, and subnets that you want to use for the migration).
  4. SAP will set up the VPN infrastructure as part of the your SAP Commerce Cloud subscription and will document the SAP peer IP and the subnet in the form.
  5. The completed form will then be returned to you. 
  6. Your networking team will then establish the connection and provide SAP with the interested server IPs and ports table (database server and file server for each of the in-scope environments).
  7. SAP CX Services will check the outbound connectivity to the customer's servers.


If additional support is needed or in case of connectivity problems, SAP CX Services will organize troubleshooting call(s) between SAP Cloud Operations & Support and your networking team in charge.

Project-specific security constraints

In case adding a dedicated VPN tunnel is not possible in your project, reach out to your SAP CX Services team to discuss possible workarounds, risks, and action plans as part of the planning stage of this engagement.


The actual migration of data and media is defined as an iterative engagement, environment by environment. SAP CX Services will:

  1. Confirm the pre-requisites for the corresponding environment migration are met.
  2. Configure the data integration pipelines for the corresponding environment's database.
  3. Run the data migration.
  4. Verify copied data (with tables and rows count) to ensure that the copy was successful.
  5. Reconfigure the pipelines to migrate the media.
  6. Run the media migration.
  7. Verify copied media (through checksum) to ensure that the copy was successful.

The migration pipelines are designed as a one-time transfer. For the production environment, it must be executed during your planned cutover time. The typical cutover time is between two and six hours. 

Delta/Incremental Migration

In case you require your data load to be incremental or include any delta after go live, please reach out to SAP CX Services to see what options SAP can provide.


After your successful go-live, SAP CX Services will trigger the decommissioning of all migration-related resources.


This article introduced you to the fundamental steps of migrating your data and media into SAP Commerce Cloud in Public Infrastructure. Now, you know what you need to consider when planning your migration project. For more information on this service , please consult the SAP Commerce Cloud Data Migration Package information sheet.