Migrating From Salesforce Commerce Cloud to Shopify: What to Expect

If you run an established brand on Salesforce Commerce Cloud (many teams still call it Demandware), you probably already know why you are reading this. The platform works. It also costs a great deal, every change goes through a specialist partner, and your team cannot ship a homepage update without raising a ticket. A Salesforce Commerce Cloud to Shopify migration is one of the harder replatforms we scope, so this is the honest version rather than the sales version.

It is a low volume search for a reason. The brands asking the question are large, the stakes are high, and most of the content written for them skips the awkward parts. This piece covers them.

Why brands leave Salesforce Commerce Cloud

It is rarely one thing. The usual pattern is a build that has grown for six or eight years, a licence tied to a percentage of gross merchandise value (typically quoted somewhere in the 1-3% range), and an agency bill on top that covers cartridge maintenance, releases and a long queue of 'small' changes. Shopify's own commissioned study, run by an independent consultancy between November 2023 and February 2024, put Shopify's total cost of ownership 35% below SFCC. Treat that as a vendor number. It still matches what we see in practice: the licence is not the expensive part, the dependency is.

Release velocity is the other driver. On SFCC, a promotion rule, a content slot change or a checkout tweak is a project with a sprint, a test cycle and a deployment window. On Shopify, your merchandising team does most of it in the admin. That shift is the real reason to move. If you migrate and keep working the same way, you have paid a lot of money to change logos.

What migrates cleanly from SFCC to Shopify

Catalogue and price books map reasonably well. Products, variants, images, categories and most attributes land as Shopify products, variants, collections and metafields. Multiple price books become Shopify Markets pricing or B2B price lists. Expect a mapping exercise and some flattening of deep attribute hierarchies, but this part is well understood.

Customer records migrate: names, addresses, order totals, tags and marketing consent. Historic orders can be imported for reference, though they arrive as archived records rather than live transactions. SEO metadata, content pages and blog posts move over with some cleanup.

What needs rebuilding rather than porting

Promotions and campaign logic are the first thing to stop assuming. The SFCC promotion engine supports stacking, qualifiers, exclusions and scheduling in ways Shopify's native discounts do not replicate one for one. Document every live promotion with its rules, then decide which become Shopify discounts, which need a Shopify Function (custom builds require Plus), and which you can retire. Most brands find a good share of their promotions are no longer used at all.

Content assets and slots have no direct equivalent. Shopify's theme sections and metaobjects are the nearest fit, and they are good, but the modelling is different. Plan a content migration, not a content copy.

Customer passwords do not migrate. Shopify does not accept imported password hashes, so every customer either receives an account invite or logs in through Shopify's newer customer accounts, which use a one-time email code instead of a password. Decide this early and write the customer communication alongside the data plan, not the week before launch.

Then three decisions that each deserve their own meeting: order history (how far back, and whether it needs to be visible in the customer's account), subscriptions (which app, and how to move billing without double charging anyone), and loyalty (whether points balances migrate, and what the provider supports). None of these are hard. All of them get missed.

B2B and multi-site setups

If your SFCC estate runs several storefronts across markets or brands, this is where the scoping effort goes. Shopify Markets handles currency, language and local pricing within one store. Separate brands usually mean separate stores under one Plus organisation, with shared apps and an integration layer between them. B2B catalogues, company accounts and payment terms are supported natively on Plus, but your existing account hierarchies and contract pricing need a full mapping. We covered the detail in what Shopify B2B actually involves.

The re-plumbing people underestimate

The storefront is the visible part. The expensive part is everything behind it.

ERP: the order, inventory and customer sync has to be rebuilt against Shopify's APIs or routed through middleware. Our comparison of Shopify ERP integrations covers the main options.OMS: if an order management system sits between SFCC and the warehouse, decide whether it stays, moves into Shopify, or gets replaced.PIM: product data flows change direction. The PIM should feed Shopify, and the mapping built for the SFCC export is rarely reusable.Tax engines: Avalara, Vertex and similar connect to Shopify, but configuration is not portable. UK VAT, EU OSS and US nexus rules all need re-verifying.Search and merchandising: Einstein search rules and sorting logic do not move. Pick a search app early, because it shapes how your collection pages work.

Every one of these needs an owner on your side. The integration work is also where the timeline slips, because it depends on third parties who are not on your project plan.

SEO preservation and redirects at scale

On a large catalogue the redirect map is a project in itself. SFCC URL structures rarely match Shopify's product and collection patterns, so every product, category, content and campaign landing URL needs a mapped destination. Shopify allows up to 100,000 redirects on standard plans and 20 million on Plus, according to Shopify's URL redirect documentation, so capacity is not the issue. Accuracy is. Crawl the old site, export the top pages from Search Console, build the map in bulk, and test it before launch rather than after.

We wrote a full guide to preserving SEO when you replatform to Shopify. The short version: expect some volatility for 4-8 weeks, and treat a sustained drop beyond that as a bug to find, not a cost to accept.

Timeline, team shape and phasing for an enterprise Shopify migration

For a single-market brand with a clean catalogue, 4-6 months from scoping to launch is realistic. Multi-brand or multi-market estates with ERP, OMS and PIM in the mix run 6-12 months. Anyone quoting less for the second case has not seen your integrations yet. Our guide to Shopify migration costs gives ranges. For an SFCC exit, the integration and data work is usually a larger share of the budget than the storefront build.

Team shape on your side: a project owner with decision authority, a data owner who knows the catalogue, and named contacts at each integration vendor. On the agency side, you want senior people who have done this before. It is not a job for a team learning on your account.

Phasing is the biggest structural choice.

Single cutover: one launch date for everything. Simplest to communicate, highest risk on the day, and the only option if your integrations cannot run against two platforms at once.Market by market: launch a smaller market first to prove the integrations and the redirect approach, then move the main market. Adds a few weeks, removes most of the unknowns.Brand by brand: for multi-brand groups, move the smallest brand first. Same logic, same trade-off.

We usually recommend the phased route when the estate allows it. The extra time costs less than a bad launch on your largest storefront.

Be honest about cost and risk

A Salesforce Commerce Cloud to Shopify migration is a large project with a real failure mode. Done badly, you lose rankings, lose customer accounts, and spend the first quarter firefighting integrations. Done well, your team ships weekly instead of quarterly and your running costs drop materially.

The platform saving is real. The bigger return comes from a team that can finally change the site without raising a project.

Once you are on Shopify, the question changes. Most brands that complete a migration discover they never had a traffic problem. They had a conversion problem, hidden behind a platform that made testing too expensive to bother with. That is where our Conversion Growth Retainer picks up.

If you are weighing up an SFCC exit, we scope these projects from Glasgow for brands across the UK and internationally, with a senior team and no outsourcing. Our Shopify migration services page explains how we approach it, or get in touch and we will give you a straight answer on whether the move makes sense for your estate.