Table of Contents

How to upgrade SAP commerce

Here are some recommendations to make your upgrades as smooth as possible.

Planning

Please take your time to update and test the new Hybris version. In average the update takes an effort of 2 days of development and many days of testing. Try not to be interrupted by other work items.

What Hybris version to use a target version?

Never update to the last Hybris release as it may be buggy and not stable for production. If there isn't any critical fix or feature that you need, update to the third last version with the highest patch level. For example: If the last version is 6.7.0.15, update to version 6.5.0.23.

If there are more than 4 releases between your current version and your target one, update the hybris version slowly with steps of 3-4 releases. For example: if your target version is 6.7 and your current one is 6.2, update first to 6.5 and then to 6.7.

Avoid SAP commerce 6.4. This version seems to have threading bugs and the update running system may block for hours.

Preparation to have less surprises

Deprecation of standard extensions

Please read the section End-of-Life (EOL) Announcements to see if any of the extensions which your system depends on was deprecated by Hybris. You have 18 months to migrate to an alternative extension. Please inform the dev team about the deprecation, so less features are implemented on deprecated extensions or technologies but wait until Hybris offers an alternative with the same features as the old one. This may happen a few months before the deadline.

Make your custom code compatible with the target version

Removal of unused code and deprecated extensions

Testing

Deployment in production

– Based on SAP commerce 6.4