Accelerator to Composable Storefront: A Practical Migration Guide
Janko Spasovski
SAP Commerce Developer, Spadoom AG
Migrating from Accelerator to the Composable Storefront isn’t a “version upgrade” — it’s a frontend replatforming project. You’re moving from server-side JSP templates to a headless Angular application. The backend stays, but the frontend is completely new. Teams that treat this as a simple upgrade underestimate the effort.
This guide covers the 10-step migration process, realistic timelines, and the mistakes that derail real migrations.
TL;DR: Migrating from Accelerator (JSP) to the Composable Storefront (Angular) takes 3–6 months for standard implementations. The backend and OCC APIs stay — the entire frontend is rebuilt. Global retail e-commerce reached $6.334 trillion in 2024 (eMarketer, 2024). A slow storefront migration directly impacts revenue.
Why Can’t You Just “Upgrade”?
Gartner has named SAP a Leader in Digital Commerce for 11 consecutive years (SAP News, 2025). Staying on the recommended frontend path means moving to the Composable Storefront.
Accelerator and the Composable Storefront are fundamentally different: server-side JSP vs client-side Angular, direct model calls vs OCC APIs, server sessions vs NgRx state. There’s no automated migration tool because the architectures share nothing at the frontend level.
What’s the Migration Process?
Mobile commerce reached $2.07 trillion in 2024 — 57% of total e-commerce (Oberlo, 2025). Your new storefront needs mobile performance from day one.
Step 1: Audit Accelerator customisations. Catalogue every custom JSP tag, controller, CSS, and JavaScript.
Step 2: Map to Composable Storefront equivalents. Most standard components have equivalents. Custom components need Angular rebuilds.
Step 3: Verify OCC API coverage. Custom features using direct service calls may need new OCC endpoints.
Step 4: Set up the Composable Storefront. Scaffold, configure backend connectivity, set up CMS mappings.
Step 5: Rebuild custom components. Prioritise by business impact — checkout customisations and B2B features first.
Step 6: Migrate CMS content. Remap content slots and components from Accelerator to Composable Storefront mappings.
Step 7: Configure SSR. Set up server-side rendering for SEO and performance.
Step 8: Theme and brand. Apply visual design — override styles, implement typography and colours.
Step 9: Test in parallel. Run both storefronts against the same backend. Compare functionality and conversions for 2–4 weeks.
Step 10: Cut over. Redirect traffic. Monitor closely for 2 weeks. Keep Accelerator as rollback.
What Are Realistic Timelines?
Thirty-nine per cent of B2B buyers are willing to spend $500K+ per online order (McKinsey, 2024). Migration timelines matter when transactions of that size flow through your storefront.
- Standard B2C (10-20 custom components): 3–4 months
- Heavy customisation (30+ components): 4–6 months
- B2B storefront: 5–7 months
- Multi-site, multi-language: 6–9 months
The biggest variable is custom component count.
What Are the Most Common Migration Mistakes?
Trying to replicate Accelerator exactly. Use migration as an opportunity to simplify.
Migrating everything at once. Move section by section — product listing, then cart/checkout, then B2B.
Ignoring OCC API gaps. Custom features using direct service calls need new backend work.
Underestimating Angular learning curve. Plan 4–8 weeks of training or hire Angular developers.
FAQ
Can I run both storefronts simultaneously?
Yes. Both run against the same backend. Route traffic by URL, domain, or percentage-based splitting.
Do my Accelerator customisations carry over?
No. All frontend code is rebuilt in Angular. Business logic stays in the backend via OCC APIs.
How do I handle SEO during migration?
Maintain URL structures or set up 301 redirects. Configure SSR from the start. Monitor Google Search Console closely.
What happens to my SmartEdit content?
CMS content persists in the backend. You remap component types to Angular components. Content itself doesn’t need recreation.
Should I upgrade Commerce Cloud and migrate the storefront at the same time?
Ideally no. Upgrade the backend first, validate stability, then migrate the storefront. Doing both doubles the risk.
Solutions for E-Commerce
See how SAP Commerce Cloud can work for your business.
Related Articles
SAP Composable Storefront: Architecture, Features, and How It Works
The Composable Storefront (formerly Spartacus) is SAP's headless frontend for Commerce Cloud. Here's how its architecture works and what each feature does.
SAP Composable Storefront: Pros, Cons, and When You Actually Need It
The Composable Storefront isn't automatic — it requires Angular expertise, changes your team structure, and adds frontend complexity. Here's when it's worth it.
Building a Composable Storefront: Prerequisites, Setup, and Common Pitfalls
Setting up the Composable Storefront isn't difficult — but the prerequisites and common mistakes aren't obvious. Here's the practical setup guide.