Modernize SAP Commerce without losing control of delivery.
Assessment, remediation, migration, validation, go-live and stabilization — a phased path through JDK 21, Spring and Jakarta namespace changes.
Why upgrades stall
The platform is several versions behind and the effort has never been sized properly. Custom extensions were built against internals, so every upgrade attempt turns into a rewrite discussion. The business will not accept a delivery freeze, so the upgrade never gets a slot. There is no reliable regression coverage, so nobody can prove the upgrade is safe to release.
What an upgrade engagement covers
Upgrade assessment: Version gap analysis, customisation inventory, dependency and add-on review, and a costed plan. Code modernisation: Refactoring custom extensions away from deprecated APIs and internal dependencies. Framework migration: JDK, Spring and Jakarta EE namespace changes, library alignment and build fixes. CCV2 migration: Moving on-premise or CCV1 workloads onto CCV2 with manifest, environment and pipeline setup. Regression safety net: Automated test coverage on critical journeys before the upgrade branch is merged. Cutover & validation: Rehearsed cutover, data validation, performance comparison and rollback plan.
Technical areas we handle
Version jumps: Older Hybris releases through to current SAP Commerce Cloud, including multi-step upgrade paths. Deprecated API removal: Replacing removed and deprecated platform APIs across custom extensions. Data model migration: Type system changes, ImpEx updates and data corrections applied safely. Add-on strategy: Deciding which add-ons to keep, replace or retire before the upgrade. Build & pipeline: CCV2 manifest, build performance, environment properties and deployment automation. Performance re-baselining: Comparing key journeys before and after so regressions are visible, not anecdotal.
How we run an upgrade
Run an assessment first — no upgrade plan is credible before the customisation footprint is known. Agree a target version and a sequencing that fits your release calendar. Build regression coverage on the journeys that must not break. Upgrade on a parallel branch kept continuously merged with ongoing delivery. Rehearse cutover in a production-like environment before the real one. Validate performance and stability after go-live, with a defined support window.
Upgrade questions
How long does an SAP Commerce upgrade take? It depends almost entirely on customisation depth and version distance, so we size it with an assessment rather than a generic estimate. The assessment itself is short and produces a costed, sequenced plan. Can we keep delivering features during the upgrade? Yes. We run the upgrade on a parallel branch that stays continuously merged with your mainline, so feature delivery does not freeze. Do you upgrade older Hybris versions? Yes, including multi-step upgrade paths from older Hybris releases up to a current SAP Commerce Cloud version. What about migrating to CCV2? We cover manifest and environment definition, build and deployment pipelines, properties and secrets governance, plus data and content migration with a rehearsed cutover.