SAP Commerce On-Prem vs. Cloud: The Real Cost of Waiting

Most SAP Commerce on-prem customers know they need to move. The question is not “if” but “when.” And behind that question hides the real trap: every month you delay, your total cost of ownership goes up — not down.

This post breaks down the real numbers. Not vendor marketing. Not theoretical models. Actual cost categories that we see across dozens of SAP Commerce projects.

The on-prem cost iceberg

Your SAP Commerce licence fee is the visible tip. Below the waterline sits everything that actually drains your budget.

Infrastructure costs

On-prem means you own the hardware, the hosting, the network, and the uptime. For a mid-size SAP Commerce deployment, that typically looks like:

• Hosting: CHF 8,000-15,000/month for production, staging, and development environments
• Monitoring and incident response: 1-2 FTEs dedicated to keeping the platform healthy
• Disaster recovery: Redundant infrastructure that sits idle 99% of the time

On SAP Commerce Cloud, infrastructure is included in the subscription. SAP manages hosting, scaling, patching, and uptime. You do not need a dedicated ops team for the commerce platform.

Security costs after EoMM

This is where the numbers get uncomfortable. After July 2026:

• SAP stops guaranteeing security patches for non-critical vulnerabilities
• You must either accept the risk or hire specialists to build and test custom patches
• Custom patching for a single critical vulnerability can cost CHF 20,000-50,000 per incident
• A data breach in the EU (GDPR) carries fines of up to 4% of annual global turnover

One mid-size retailer we spoke with estimated their post-EoMM security patching budget at CHF 120,000/year — and that covered only the known vulnerabilities.

Talent costs

The market for SAP Commerce on-prem developers peaked around 2020. Since then, the talent pool has been shrinking steadily.

• Day rates for on-prem specialists: CHF 1,400-1,800/day — trending upward
• Day rates for Commerce Cloud developers: CHF 1,200-1,600/day — stable, with a larger talent pool
• Recruitment cost: On-prem roles take 30-50% longer to fill than cloud equivalents

When you factor in onboarding, knowledge transfer, and the risk of a single developer holding critical platform knowledge, the talent premium alone can justify a migration.

Opportunity cost

This is the most underestimated line item. Every feature your business needs but cannot ship because the platform is frozen has a cost.

• A competitor launches same-day delivery integration. You cannot match it for 6 months.
• Your marketing team wants A/B testing on checkout flows. Your on-prem setup requires custom development.
• Mobile conversion rates are dropping. A modern PWA frontend would fix it, but your monolithic architecture makes it a 4-month project.

These are not hypothetical scenarios. We hear them from every SAP Commerce on-prem customer we talk to.

The Commerce Cloud TCO

SAP Commerce Cloud operates on a subscription model. The subscription includes:

• Managed infrastructure (production, staging, development)
• Automatic updates and security patches
• Built-in CDN and edge caching
• Elastic scaling for peak traffic
• SAP support with cloud-priority SLAs

For a comparable mid-size deployment, the total annual cost typically breaks down as:

These are indicative ranges based on our project experience. Your numbers will vary based on deployment size, customisation complexity, and region. But the pattern holds: on-prem after EoMM costs 40-60% more than Commerce Cloud for the same business outcome.

The compounding cost of delay

Every month you stay on-prem past EoMM, the gap widens. Here is why:

Month 1-6: Extended maintenance fees kick in. Your team spends extra hours on manual patching. No new features.

Month 7-12: First security incidents that would have been auto-patched on cloud. One or two key developers leave for cloud projects. Replacement hiring takes 3-4 months.

Month 13-24: The platform is now two major versions behind Commerce Cloud. Migration complexity increases by 20-30% compared to migrating at EoMM. Your competitors have shipped features you cannot match.

Month 25+: You are now in emergency mode. The migration is no longer optional — it is urgent. Rushed migrations cost 30-50% more than planned ones. Your negotiating position with implementation partners weakens because demand spikes.

The migration investment

A typical SAP Commerce on-prem to Commerce Cloud migration costs between CHF 250,000 and CHF 600,000, depending on:

• Number of storefronts and markets
• Customisation complexity
• Data volume and cleanup needs
• Integration count
• Internal team availability

That is a one-time investment. Compare it against the annual cost differential of CHF 200,000-500,000, and the migration pays for itself within 12-18 months.

We completed the Franke migration in 90 days and won an SAP Quality Award for the efficiency and quality of the delivery. That project proved fast migration is not just possible — it is the cost-optimal path.

What smart companies do

The companies that come out of EoMM strongest share three habits:

1. They start early. Not six months before the deadline. Twelve months before. Early starters choose their timeline instead of having it imposed.
2. They clean up before they move. Dead customisations, unused integrations, legacy data — all of it gets audited and removed before migration. This cuts migration cost by 15-25%.
3. They migrate iteratively. Not a big-bang cutover. Market by market, storefront by storefront. Each phase delivers value and reduces risk.

The bottom line

Staying on SAP Commerce on-prem after July 2026 is not a money-saving strategy. It is a money-losing one. The longer you wait, the more you pay — in licence fees, in talent premiums, in security risk, and in missed business opportunities.

The migration investment pays for itself. The question is whether you make that investment on your terms or under deadline pressure.

Talk to us — we will show you exactly what your migration would cost and how fast it can happen.