What to know before an SAP Commerce Cloud Migration

More and more SAP Hybris or Commerce customers are planning to migrate to SAP Commerce public cloud. So to help you benefit from our expertise in this area, we’re pleased to share our insights with you. We’ve executed many SAP Commerce Cloud migration projects, and we would like to share with you 10 points that you MUST KNOW before embarking on your SAP Commerce Cloud migration journey. 

Compatibility Check

First and foremost, you need to check the compatible version of SAP Commerce for cloud migration, especially if you’re running on-premise SAP or Hybris Commerce. You can check this on the sap help document (help.sap.com). You might have to upgrade your current Hybris or SAP Commerce to a compatible version before migrating to SAP Commerce Public Cloud.

Firewall Considerations

Is your current Commerce deployment integrating with your on-prem back-end systems (such as ERP or CRM) behind a firewall through a VPN tunnel? If so, pay special attention to how you will establish the VPN tunnel with SAP Commerce public cloud. There could be some limitations in the network protocols depending on your firewall, which could add unnecessary delays to your project timeline. We can’t overemphasize the importance of this step!

SAP Commerce Integrations

Make a list of all integration touchpoints with your SAP Commerce system. Develop a plan to integrate all those with SAP Commerce Public Cloud or CCv2. This is an extremely important step. Please set aside time to validate and test all the integration scenarios, and don’t cut corners on your integration testing timeline.

Hotfolders Compatibility

Have you implemented hotfolders like most SAP Hybris Commerce customers? You need to allocate some extra time to make your hotfolders public-cloud compatible. Using any middleware to place the files in a hotfolder with an on-prem location? Please check if your middleware is capable of keeping the files in Microsoft Azure Blob storage. 

SMTP Storage

You need to get your own SMTP service for all the emails. Especially if you’re using an SMTP relay of SAP Commerce Cloud on SAP infrastructure (aka CCV1 or Commerce Cloud version one), With SAP Commerce Public Cloud version (Commerce Cloud Version Two or CCV2), in-built SMTP service is not available. For all the email backup from your current SMTP relay, you need to talk to SAP. They can assist you with the backup process.

Database Migration

SAP will help you with database migration to SAP Commerce Cloud. However, it is recommended that you cleanup your database before the lift and shift. Otherwise you’ll hit snags moving your database to SAP Commerce public cloud or SAP Hybris. This goes a long way in improving your site performance. If you’re running your current SAP Commerce on HANA database (as will most likely be the case if you’re running CCv1), and you’ve written a lot of complex database queries, make sure you maintain extra time in your project to modify those queries for the Microsoft Azure cloud SQL. Most of your current SQL queries from HANA should work in Microsoft Azure Cloud. However you could have some trouble spots as per your complexity that might require some attention. 

Datahub Middlewear

As you probably know, SAP recommends SAP Cloud Platform Integration for all SAP integrations. Using Datahub as your middleware for SAP Commerce? Evaluate what would it take to migrate to SAP CPI from Datahub. We have encountered few challenges with moving Datahub to public cloud. If you can migrate to CPI, you will be set for the future. 

Kibana & Dynatrace Training

SAP Commerce Cloud version one – or CCV1 – uses Splunk for Application Management. However, SAP Commerce in Public Cloud or CCV2 uses Kibana, a much better tool. Also SAP Commerce in public cloud includes Dynatrace for application monitoring. It will be very beneficial if you get your application team members trained on both Kibana and Dynatrace.

CI/CD Scripts

If you’re currently using Continuous Integration and Continuous Deployment scripts to automate your deployment process, please be aware that you will need to rewrite your CI/CD scripts. This is to make them work with SAP Commerce Public Cloud. 

Test, Test, Test!

Last – but not least – in fact the most important step; test thoroughly! We can’t stress enough the importance of repeated testing. Please make sure that you plan enough time to fully test your application in SAP Commerce Public Cloud. 

Thank you for reading. It’s our sincere hope that you can easily migrate to SAP Commerce Public Cloud! Please do not hesitate to reach out to #teamasar if you have any questions or need any help. Or leave any comments and questions below. Standby till our next article. Thank you!

Share Article

Share on facebook
Share on twitter
Share on google
Share on linkedin

Recent Topics