CX Works

A single portal for curated, field-tested and SAP-verified expertise for your SAP C/4HANA suite. Whether it's a new implementation, adding new features, or getting additional value from an existing deployment, get it here, at CX Works.

Migrate to SAP Commerce Cloud



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.

Preparation

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. 

Responsibilities

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

R


A

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
A
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 R I
UAT Issue Fixing R
A
Go Live R I

A

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. The following section has some of the most common questions and answers, with the corresponding rational. This section prepares you to scope the Commerce Cloud migration adequately.

Which version of SAP Commerce runtime are you currently running?

As previously mentioned in this article, SAP Commerce Cloud in the Public Cloud does not support all versions of the SAP Commerce runtime ("hybris platform"). See this page in the product documentation for the currently supported versions. An upgrade of your SAP Commerce runtime may take weeks or months, depending on a variety of factors including the version gap and the level of customizations.  You will need to make sure you tackle the upgrade project before the migration.

See the article Migrate to SAP Commerce Cloud: Project Planning Considerations for more detailed options.


Do you require the data center to be compliant for PCI-DSS 3.2?

Currently, SAP Commerce Cloud in the Public Cloud is not certified for PCI-DSS 3.2. If this is blocking your project you should consult your SAP representative to determine the status of the certification.

Note: Check your regional Supplemental Terms and Conditions for SAP Commerce Cloud if storing of PCI-DSS 3.2 relevant data is allowed.

Do you use Synchronous Order Management (SOM) with SAP ECC/S4HANA?

The APIs required for SOM are supported only for migrating customers and till November 2021. If your current commerce solution is utilizing SOM you should consider migrating to Asynchronous Order Management (AOM) prior to your migration to SAP Commerce Cloud in the Public Cloud. If not, you will technically be able to continue using SOM after moving to SAP Commerce Cloud in the Public Cloud, but as per this page of our product documentation SOM with SAP Commerce Cloud in the Public Cloud will not be supported by SAP. If you have doubts, please contact SAP CX Services for further assistance.

Which region/data centre do you target for SAP Commerce Cloud?

SAP Commerce Cloud is constantly re-evaluating the demand to consider additional data centers to host your solution. If you want to know the availability and location of the data centers please consult https://www.sap.com/about/trust-center/cloud-service-status.html#sap-commerce-cloud. If you have specific data protection laws and regulations that affect the physical position of the data center, you need to make sure SAP Commerce Cloud offers a data center in a required region.

Is your installation heavily customized?

SAP Commerce Cloud is a PaaS solution, wrapping the previously SAP Commerce runtime to maximize your customer experience. See SAP Commerce Cloud Architecture for more on the solution architecture of SAP Commerce Cloud in the Public Cloud. A migration can be a great opportunity to reassess your solution architecture to identify to what extent your code base and infrastructure setup vary from the recommended practices. Make sure to consider the compatibility of all customization not officially referenced in the product documentation for compatibility and, if required, develop a mitigation plan.

What kind of deployment model does your SAP Commerce application use?

SAP Commerce on Premise and on SAP Infrastructure can be deployed in various ways: multi-site strategy, multi-brand strategy, multi-tenancy strategy, etc. Based on how your application is deployed, you might need to redesign part of it based on following observations about SAP Commerce Cloud:

  • There is a one to one relationship between a Commerce Cloud in the Public Cloud subscription and code base.
  • One subscription might contain multiple productions zones sitting in different data centers (without active-active database replication)
  • There is limited support for multi-tenancy

If you have doubts, consult your SAP representatives to elaborate on how to deploy your solution to maximize your SAP Commerce Cloud experience.

Do you apply build customizations?

SAP Commerce on premise or on SAP Infrastructure allows to customize the build process in different ways:

  • ant customize
  • platform enhancements
  • web-server changes

SAP Commerce Cloud in the Public Cloud leverages the concept of a PaaS-solution and comes with its own build chain (see Getting Started with SAP Commerce Cloud). You are encouraged to use your migration project to reconsider any existing build customizations. If you have any you should be trying to replace them with out-of-the-box features. Each build customization should be assessed against the compatibility with SAP Commerce Cloud in order to ensure a smooth migration to Commerce Cloud leveraging the offered tooling.

Is your code available in Git source code repository accessible by public internet?

SAP Commerce Cloud will pull your source code from a Git-based source code repository accessible on the public internet. The repository will still be secure, by allowing only login to authorized and authenticated sources. Please make sure you follow the guidelines described on this page of the product documentation.

Do you integrate with a content delivery network (CDN) solution or use external web acceleration tools?

SAP Commerce Cloud includes some web acceleration by default, and it is recommended to test your application on the new infrastructure before introducing additional tooling. If, for example, you would like bring your self-managed Content Delivery Network appliance you can do so by following the recommendations in the "Content Delivery Network" section of our article on SAP Commerce Cloud Architecture.

Are you using a search engine different than SAP Commerce Cloud Solr?

In case you make use of a custom search engine (e.g. Elastic Search, Algolia, ...) or you have a heavily customized Solr, you may want to re-evaluate your solution against the Solr Cloud offering of SAP Commerce Cloud (see more in our article Search and Navigation in SAP Commerce Cloud - Solr Infrastructure). Whenever possible, we recommend to leverage the standard product capabilities of SAP Commerce Cloud.

Do you use any integrated software that needs to be hosted on the same infrastructure as the SAP Commerce application (e.g. SAP Commerce Cloud on SAP Infrastructure satellite servers)?

SAP Commerce Cloud is running on a containerized predefined setup. Any third party software requiring infrastructure cannot be deployed or managed through SAP, see more details in the "Third Party Software Applications" section of SAP Commerce Cloud Architecture. After moving to SAP Commerce Cloud in the Public Cloud, you should consider all of these components as regular integrations. Therefore, you will need to go through a diligence check to determine if the infrastructure architecture does fulfill your non-functional requirements (e.g. In-Memory caching server).

Any 3rd party server/software/lib required for build/run-time? 

Similarly to the previous question, SAP Commerce Cloud does not allow you to install any third party library / software on the operating system other than what is shipped with the standard application. 

Do you require a VPN-Tunnel for any kind of data integration or office-to-office?

In case you require a VPN tunnel please make sure you visit Setting Up a VPN for SAP Commerce Cloud to learn how to setup up a VPN tunnel for your SAP Commerce Cloud in the Public Cloud solution. Establishing such communications is a team effort between you, your Implementation Partner and SAP. As such, it needs to be collectively agreed and worked upon. Make sure to allow for the necessary time and resources for this setup in your project planning.

Do you make use of SMTP server?

SAP Commerce Cloud does not currently ship with an SMTP-server or service, but a list of possible solutions is covered in the article Integrating an Email Service with SAP Commerce Cloud. Design your mail sending strategy on SAP Commerce Cloud appropriately.

Do you plan on using hot folders for data integration?

Make sure your in place hot folders/NFS/sFTP based integrations can leverage the newly designed Cloud hot folders, see more information to support your project's solutioning in the article Get the Most out of Your Cloud Hot Folders and Azure Blob Storage.

Do you make use of integration components (e.g. SAP Commerce Cloud, data hub)?

SAP Commerce Cloud supports many types of integrations as covered in Integration Options for SAP Commerce Cloud. Any middleware that needs to be integrated into SAP Commerce Cloud requires a dedicated focus as part of the migration. For each of your current integration a migration of its configuration and code needs to be appropriately planned. Enough time for integration testing should be given in your migration project plan.

Are load tests scripts available for the solution?

Migrating an existing, stable and optimized SAP Commerce application to SAP Commerce Cloud in the Public Cloud does not guarantee you will need the same optimizations to properly leverage the new horizontal scaling model and resource matrix. Hence, we recommend that any migration goes through a thorough performance and load test exercise prior to cut over. If you don't have any test at hand or integrated in your existing development processes, the migration project is a great chance to start.


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

Planning

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

Delivery

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

Deployment

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

Conclusion

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 sapcx-services@sap.com.