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
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.
Must-do's and highlights of the above milestones include the following:
|Milestone||Key activities and considerations||Helpful Links|
|Migration assessment service||
||See Code Adaptations|
|Data and media migration||
||Migrating to SAP Commerce Cloud: Data and Media Migration|
|Lift & shift||
|Code promotion and setup||
||See "Performance Benchmarking" section of Migrate to SAP Commerce Cloud: Technical Considerations|
||Go Live Readiness for SAP Commerce Cloud|
To understand the migration process in more detail, please consult the following video: SAP Commerce Cloud: Migration Strategies
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:
- Define how many environments have to be migrated
- 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)
- Define quality gates (e.g. DEV1 and DEV2 to be closed off before STG1 is going to be migrated)
- Define critical path for sign-off (e.g. DEV1, STG2 (UAT), PRD1)
- 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 email@example.com.