SAP Commerce Upgrade: The Definitive Step-by-Step Guide

The Continuous Innovation of SAP Commerce Cloud, introduced with the 2211 release, brought about a significant change. Monthly update releases now include bug fixes, security updates, and potential new features, which customers can enable according to the Upgrade guide. SAP Commerce Cloud 2211 customers must adopt a current update release to ensure the software remains up-to-date.

Lastly, SAP provides update releases for SAP Commerce Cloud AddOns, including new features and innovations. SAP recommends that customers use a current update release to streamline upgrades and limit potential security and system issues.

On the way to the Continuous Innovation Strategy from SAP, customers are strongly advised to move to release 2211 as soon as possible. From the versions before the Continuous Innovation plan, only commerce releases 2105 and 2205 are still under SAP’s maintenance plan.

Release SAP Commerce Cloud 2105 ended its End of Mainstream Maintenance recently, on 19th August 2023. The last version before this strategy, SAP Commerce Cloud release 2205, will continue to be officially supported by SAP until the end of May 2024.

This is why SAP is strongly pushing for an SAP Commerce Upgrade to 2211 so that customers can be part of their continuous innovation plan and be constantly and seamlessly updated with functionalities, performance, and security upgrades.

The upgrade project of an SAP Commerce solution can vary greatly depending on several factors, including the number of customizations currently leveraged in the system and the version you are migrating from. Migrating from SAP Commerce 2105 will be simpler than an SAP Hybris upgrade from an older version, like 1808.

Upgrading from an old version might require an intermediate technical upgrade to an intermediate version, as the official SAP support guidelines suggest. At E-Turia, we have vast experience working on SAP Hybris upgrade projects, so you can feel free to contact us via the form at the bottom of this page to ask about your project and your commerce version or to set up a free consultation with us.

Now let’s dive into the steps required for a successful working plan of a project upgrade. This may seem complex, but you can ensure a seamless transition with a detailed roadmap.

This step can be done parallel to the previous one and focuses on revising the project’s technical documentation and integrations. E-Turia’s Architects and Senior Developers will run the project locally to ensure the correctness of the current solution and a deep project comprehension, including the modifications done throughout its lifetime.

During this phase, the different regression tests will be defined so that after the upgrade is completed, these tests can be executed to ensure a smooth change in the Commerce version minimizing potential regressions and risks. This is the basis for the latter successful hybris upgrade steps.

This stage is the most technical and will ultimately determine the success of your upgrade project. Here, E-Turia’s most experienced developers will implement the necessary adaptations to successfully run your current platform with all its functionalities on the new SAP Commerce release.

It can be subdivided into different tasks:

1. Defining the upgrade steps into different Commerce versions. If you upgrade from a very old SAP Hybris version, SAP recommends upgrading to an intermediate version before moving to the most recent one. If this is the case, the following steps will need to be done for all the mini upgrades, but please keep in mind that you need to be currently running an old version of hybris. Please contact us from the form at the end of this page if you have questions about your current version.
2. Technical analysis. Our team will evaluate the difference between the Out-Of-the-Box versions of Commerce given the current set of Commerce modules and AddOns used. Apart from carefully checking the official Release Notes from SAP, our team will do a complete diff on both codebases to ensure no code changes are left unidentified. This helps us locate the customized code’s potential conflicts and pain points. On top of the old SAP Commerce version, these leveraged areas will be our primary focus, considered the most risky parts of the project.
3. Old code fixes. Before adapting the old code to the newer SAP Commerce version, our team thoroughly reviews the main processes to ensure they are error-free and avoid confusion after the upgrade. We have seen many upgrade projects where the initial project state could be better, and some issues can lead to confusion after the commerce version change. The typical parts to review are things like an error-free initialization, clean synchronizations, a console free from error prompts during the place order, or a Solr indexing job.
4. Custom code adaptation. At this stage, the E-Turia team updates the custom code to run with the new Commerce version. Code is reviewed carefully, considering the technical changes and the regression tests identified earlier to ensure all preexisting functionalities work as they should.

• Improvements in the payment processes, such as:
  • Integration with BitPay to allow receiving payments in cryptocurrencies such as Bitcoin, Ethereum, or StableCoins.
  • Payment restrictions by B2BUnit
• Inclusion of new promotional types ready to be used.

Now we have the code upgraded to the desired SAP Commerce version, and it has successfully passed most tests in the development environment. We will deploy the code in the SAP Staging environment, allowing further testing with better-quality data and all the necessary connections to the systems with which SAP Commerce integrates.

This is also the time when our customers get involved. Depending on the needs and the version difference, the E-Turia team showcases a demo to our customers so that everyone can be familiarized with the new functionalities of the tool. Then, the system is ready for the customers’ UAT (User Acceptance Testing) to verify that the system works as expected and is prepared to move to production.

After the code has passed all the demands on the Staging Cloud environment, the code is ready to be deployed in production. The different strategies are evaluated for the Go Live to minimize the time the system is down and ensure a proper risk mitigation plan with the necessary backups.

Right after the Go Live, the E-Turia team will check this environment with the set of tests to ensure the system’s correctness and tweak any minor configuration if the system needs it.

In an SAP Commerce Upgrade project, it is a must for the implementation partner to offer a period of warranty to ensure the system works flawlessly as expected. At E-Turia, we usually work with post-go-live support of 30 days, where someone from our team is dedicated to the newly upgraded platform, allowing our customers to rest assured that the system will work as expected and that any possible concern will be instantly addressed.

1. Upgrading the SAP Commerce platform first with the old storefront. Once the system is stable with the new hybris version and no regressions, we can start working on the migration to Spartacus so that the risks are minimized (remember that both storefronts could coexist in the same Commerce instance).
2. Migrating the old hybris version to Spartacus first, then updating SAP Commerce to the new version. This option is not ideal in most cases as it would generally require more effort to adapt Spartacus to older versions than the old Storefront to a newer commerce version. However, for some specific requirements, this strategy might make sense.
3. Doing both the upgrade and the migration at once. This strategy might look faster as it is like option one but without the need to update the old storefront. We don’t generally recommend this strategy as it’s riskier, and you lose the old storefront environment in the new commerce version. It would be the equivalent of a traditional waterfall approach, while the first option would be agile development with multiple checkpoints and demos to lower the risks.

Our go-to option from E-Turia is option 1 in most cases: First, upgrading the SAP Commerce Cloud with the old Storefront, and after this is finished, start the Spartacus migration. However, each scenario is different. If you want us to evaluate your case for free, please get in touch with us in the form below.

Upgrading an SAP Commerce solution can take as little as two months. Each case is different and will depend on multiple factors, like how far apart the start and end versions are and the amount and code quality of the customizations performed on the platform.

At E-Turia, we can provide you with an upgrade project estimation length. Still, it will be more accurate after our team of certified experts analyzes your platform during the initial workshops and technical review of the project.

Platforms upgrading from SAP hybris versions, which are still supported, and have been leveraged using the best practices recommended by SAP, could be fully upgraded to the latest version in 2-3 months from the project’s kick-off. Testing times might vary depending on the number of functionalities used, but the upgrade project timeline would look something like this:

There are multiple advantages of a well-planned SAP Commerce Cloud Upgrade. Let’s dive into the benefits that your platform will obtain when migrating to the last SAP Commerce version.

Updating your SAP Commerce version ensures your system operates at its best, enhancing user experience and encouraging customer loyalty. Customers visiting online stores are much more likely to exit your store if it does not respond fast enough. Website performance is also crucial for the technical SEO metrics, helping your site rank higher on Google.

Upgrading to the latest SAP Commerce version often includes vital security patches that help protect your system from evolving threats. This is a critical aspect of risk management in the digital age. Bear in mind that when you migrate to a newer SAP Commerce Cloud version, you are updating the core of the SAP platform and benefiting from the dependent libraries and their updates.

A successful SAP Commerce Cloud upgrade gives you access to new and improved features. It’s an investment in staying ahead of the curve in a competitive industry and an opportunity to take advantage of new Out-of-the-Box features you might have yet to realize could be used in your online store. New features are added to the development pipeline of SAP considering the demand of worldwide customers using the platform, so it’s an excellent opportunity to include highly demanded features with minimal effort.

Upgraded versions are better supported by SAP, ensuring quicker resolution to potential issues. This support can significantly reduce system downtime and ensure seamless operations. Not to mention that with the Continuous Innovation strategy, your platform will receive constant updates from SAP after a successful upgrade to SAP Commerce 2211. Staying away from versions Ending Mainstream Maintenance is essential to avoid risks like severe security issues.

At E-Turia, we have helped many customers in several industries upgrade their SAP Commerce Platforms. As a trusted SAP Partner, we specialize in supporting businesses through their upgrade journey, ensuring a smooth and seamless transition, which has granted us a vast experience in the sector.

Our team of experts understands the intricacies of the SAP Commerce Cloud ecosystem. With our wealth of experience, we manage everything from planning to execution, ensuring your upgrade is successful, risk-minimized, and completed on time. We handle the details, so you can focus on what you do best – running your business.

Contact us below to embark on this journey together and propel your business toward digital excellence. Start your SAP Commerce upgrade today by scheduling a free consultation with us.