From SAP Hybris to Commerce Cloud in 90 Days: A Migration Playbook

When we tell people we migrated Franke from SAP Hybris to SAP Commerce Cloud in 90 days, the first reaction is disbelief. Ninety days sounds aggressive for what most companies consider an 8-12 month project.

But we did it. And SAP recognised the project with a Quality Award for the efficiency and quality of delivery. This post shares the playbook — not the marketing version, but the actual methodology, timeline, and decisions that made it possible.

If you are facing the EoMM deadline in July 2026, this is directly applicable to your situation.

Why 90 days is achievable

A 90-day migration is not about cutting corners. It is about eliminating waste. Most long migration timelines are inflated by three things:

1. Analysis paralysis. Teams spend months documenting requirements that already exist in the running system.
2. 1:1 replication of unnecessary customisations. Moving code that is not needed on the target platform.
3. Sequential phases with handoff delays. Waiting for sign-offs, handovers, and context switches between teams.

Remove these, and the actual work — data migration, platform configuration, integration reconnection, and testing — fits into 90 days for a mid-size commerce platform.

The pre-migration phase (weeks -4 to 0)

The 90-day clock starts at kickoff. But 30 days of preparation before kickoff makes the difference between a controlled sprint and a chaotic scramble.

Platform audit (week -4 to -3)

We map everything in the current SAP Hybris instance:

• Custom extensions: Count them, classify them (still needed / replaceable / obsolete), estimate migration effort for each.
• Data models: Document custom types, relations, and attributes. Identify what maps directly to Commerce Cloud and what needs transformation.
• Integrations: List every inbound and outbound connection — ERP, PIM, CRM, payment, shipping, tax. Document protocols, data formats, and frequencies.
• Customisation hotspots: Identify the 20% of custom code that handles 80% of the business logic.

For Franke, this audit revealed that 35% of custom extensions were workarounds for on-prem limitations. We removed them from scope immediately, saving 3 weeks of migration effort.

Data profiling (week -3 to -2)

Before you touch the migration tools, understand your data:

• Profile every data entity for completeness, consistency, and quality
• Identify duplicates, orphaned records, and data that has not been accessed in 2+ years
• Define your data migration strategy: full historical migration vs. rolling window vs. fresh start for non-essential data
• Build and test your ETL pipeline with a small sample set

Environment setup (week -2 to -1)

• Provision SAP Commerce Cloud environments (development, staging, production)
• Configure CI/CD pipelines
• Set up monitoring and alerting
• Establish access for all team members

Team alignment (week -1)

• Finalise the backlog with prioritised work items
• Assign clear ownership for each workstream: platform, data, integrations, frontend, testing
• Agree on Definition of Done for each delivery increment
• Establish daily standups and weekly stakeholder demos

Sprint 1: Core platform (days 1-21)

The first three weeks focus on getting the core platform running on Commerce Cloud with your data models and base configuration.

What gets done

• Data model migration. Transfer custom types, enums, and relations to Commerce Cloud. Validate against the platform audit.
• Core business logic. Migrate the critical 20% of customisations identified in the audit. Cart calculation, pricing rules, promotion engine configuration, tax calculation.
• Base storefront. Deploy Composable Storefront with your product catalogue. No custom styling yet — functional correctness first.
• First data load. Run a full data migration to staging. Validate record counts, data integrity, and key business flows.

What does NOT get done

• Visual design refinements
• Non-critical integrations (analytics, review platforms, loyalty)
• Performance optimisation
• Edge-case business logic

Milestone at day 21

A working storefront on Commerce Cloud staging with real data, core business logic, and basic checkout flow. Stakeholders can browse products, add to cart, and complete an order. It does not look perfect. It works.

Sprint 2: Integrations and frontend (days 22-50)

With the core platform proven, sprint 2 reconnects the ecosystem and refines the experience.

Integration reconnection (days 22-36)

Work through integrations in order of business criticality:

1. ERP/order management: Order export, inventory sync, pricing updates
2. Payment provider: Reconnect payment gateway with Commerce Cloud’s payment extension
3. Shipping/logistics: Rate calculation, label generation, tracking updates
4. PIM/content: Product data feeds, media asset sync
5. CRM/CDP: Customer data synchronisation

For each integration:

• Validate the existing API contract still works
• Update endpoint URLs and authentication
• Run end-to-end tests with real data
• Document any behavioural differences

Frontend refinement (days 30-50)

In parallel with integration work:

• Apply brand styling to Composable Storefront
• Implement custom UI components identified in the audit
• Optimise for mobile (responsive layouts, touch interactions)
• Implement SEO requirements (meta tags, structured data, URL redirects from old paths)

Milestone at day 50

A fully integrated Commerce Cloud deployment with all critical integrations live, brand-consistent frontend, and end-to-end order flow working from browse to fulfilment.

Sprint 3: Hardening and go-live (days 51-90)

The final phase is about confidence. You already have a working system. Now you prove it is production-ready.

Performance testing (days 51-60)

• Load test with realistic traffic patterns (peak day simulation)
• Identify and resolve bottlenecks
• Validate auto-scaling behaviour
• Benchmark page load times against targets

User acceptance testing (days 55-70)

• Business users test every critical flow: search, browse, cart, checkout, order tracking, returns
• Test with real customer accounts and real product data
• Verify all integrations under realistic conditions
• Document and resolve all P1 and P2 issues

Data migration dress rehearsal (days 65-75)

• Run the full data migration pipeline end-to-end
• Measure elapsed time — this defines your cutover window
• Validate delta migration for data created between the dress rehearsal and go-live
• Test rollback procedures

Go-live preparation (days 75-85)

• Create the go-live runbook: step-by-step actions, owners, timing, rollback triggers
• Configure DNS and CDN
• Set up URL redirects from old paths to new
• Brief the support team
• Communicate the maintenance window to stakeholders

Go-live and stabilisation (days 85-90)

• Execute the go-live runbook
• Run delta data migration
• Switch DNS
• Monitor for 48 hours with the full team on standby
• Resolve any post-go-live issues

What made the Franke migration succeed

Looking back at the project, five factors made the 90-day timeline possible:

1. Ruthless scope management. We did not migrate everything. We migrated what the business needed. The 35% of unnecessary customisations stayed behind.

2. Parallel workstreams. Platform, data, integrations, and frontend ran in parallel with daily sync points. No sequential handoffs.

3. Early data investment. Data profiling started before kickoff. By day 1, we knew exactly what we were migrating and what we were leaving behind.

4. Iterative delivery with weekly demos. Stakeholders saw progress every week. Issues surfaced early. Course corrections happened in days, not months.

5. Experienced team. Our team had done this before. We knew the SAP Commerce Cloud platform, the migration patterns, and the common pitfalls. That experience compressed the learning curve to near zero.

The SAP Quality Award recognition

SAP awarded the Franke migration a Quality Award — their recognition for projects that demonstrate excellence in methodology, stakeholder engagement, and delivery quality. For us, it validated that speed and quality are not opposites. A focused, well-planned migration delivers both.

Your 90-day timeline starts with day -30

The playbook works. We have proven it. But the 90-day clock only starts ticking once preparation is complete. If you are facing the July 2026 EoMM deadline, the math is straightforward:

• 30 days preparation + 90 days migration = 120 days total
• To go live by July 2026, you need to start preparation by March 2026
• To go live comfortably with buffer, start by January 2026

The later you start, the more compressed the timeline becomes. And compressed timelines cost more.

Start your migration assessment

We will review your SAP Hybris instance, map your customisations, profile your data, and build a realistic 90-day plan tailored to your specific situation. No generic templates. A plan built on real experience from Franke and dozens of other SAP Commerce migrations.

Get in touch — let’s turn your EoMM deadline into a 90-day success story.