Salesforce Commerce Cloud to Shopify Migration

First, What You're Actually Migrating

This guide is for teams that have already decided to move from Salesforce Commerce Cloud (SFCC) to Shopify and now need an execution plan. If you're still weighing whether to replatform, or which enterprise platform to choose, that's a different question. Coming from a different platform entirely? Our platform-by-platform migration guide covers WooCommerce, Wix, Magento and more.

The instinct with an SFCC migration is to picture it as exporting one database and importing it into another. It isn't. SFCC stores are built on custom cartridge code, controllers and pipelines that have no counterpart on Shopify, so the real work is re-implementing behavior, not shuttling rows. That reframing — rebuild, not transfer — is what separates a smooth cutover from a scramble. It's also why brands that make the move tend to describe it as a step up, not a lateral port:

The Naming: Demandware, B2C Commerce, Agentforce

The platform you're leaving goes by several names, and knowing which is which saves confusion during research. Demandware was acquired by Salesforce in 2016 and became Salesforce Commerce Cloud. Salesforce now markets the line as Agentforce Commerce, while its developer documentation still refers to the platform as B2C Commerce. On the storefront side, the architecture evolved from SFRA to the Composable Storefront (PWA Kit), and — per a third-party SFCC reference — a newer generation called Storefront Next. One more distinction: Salesforce B2B Commerce is a separate product with its own data model, and this guide does not cover it.

SFCC → Shopify: What Maps to What

The most useful way to scope an SFCC move is to lay each concept next to its Shopify counterpart and mark how it gets there — imported, re-created by configuration, or rebuilt in code. The map below is the honest picture.

Shopify capabilities from Shopify Help Center and shopify.dev; SFCC concepts from Salesforce developer documentation. Verified July 2026.

On the platform you gain in return, teams that move off SFCC consistently point to how much arrives built in — and how that frees engineering time that used to go into maintaining basics:

Cartridges, Controllers & Pipelines

A cartridge is SFCC's mechanism for packaging code and data, and SFRA runs on controllers with pipelines as a legacy fallback. On Shopify that logic splits by type: discount, shipping and validation rules become Shopify Functions; storefront behavior becomes theme code or apps; scheduled jobs become webhook-driven services. The nuance worth planning for is that one cartridge rarely maps to one Shopify object — a single custom checkout cartridge can fan out into a Function, an app and a theme change. Where the storefront code lands also depends on the Liquid-versus-headless choice below.

Reconnecting Your Back Office

The nuance here is the shift in event model. SFCC drives back-office sync through scheduled jobs and pipelines; Shopify drives it through webhooks and API calls, which are event- rather than batch-oriented. So an ERP, OMS or PIM link isn't just re-pointed — its triggering logic is re-thought around near-real-time events. Scope each connection as its own small project with its own testing: list every system that talks to your store today, and decide how each one will talk to Shopify tomorrow.

Your Custom Checkout

Custom SFCC checkout logic is re-created through Shopify Checkout Extensibility, and the nuance is plan-gating. You add checkout apps through the checkout and accounts editor; on Basic and up they extend the thank-you and order-status pages, while Shopify Plus additionally unlocks the information, shipping and payment pages plus the Checkout Branding API. So how much of your SFCC checkout you can rebuild depends on your Shopify plan — map that before you assume parity, and use the move to shed customizations that never earned their keep.

Multi-Site Realms & B2B

SFCC realms and multi-site setups become one of two Shopify shapes: multiple regions, currencies and languages run from a single store with Shopify Markets, or genuinely separate brands and catalogs run as multiple stores. Shopify frames Markets as “sell to multiple markets, all from a single store,” which replaces many realm configurations — but when the separation is real, several stores is the honest answer. That trade-off carries cost and operational consequences, covered in our guide to running multiple Shopify stores.

If wholesale is part of the picture, SFCC customer groups map to Shopify customer segments and B2B. B2B is available on the Basic, Grow, Advanced and Plus plans, but the heavy-duty pieces — unlimited catalogs and assigning price lists directly to companies — are Plus-only. When B2B is core to your store, plan those features deliberately; our deep dive on B2B on Shopify Plus covers what native B2B does and doesn't replace.

What Doesn't Move Automatically

A migration tool moves data. Everything below is either rebuilt by hand or handled by a deliberate workaround — none of it rides along with a catalog export, so scope it explicitly.

How Complex Is Your Migration?

You've seen what maps cleanly and what gets rebuilt. Now size your own move. Answer five quick questions about your cartridges, custom logic, B2B footprint, catalog and integrations, and this quiz places your migration on a complexity scale — from a lean, tool-driven move to a full agency-led program. There's no wrong route here; each one points you at the execution approach that fits your store.

Your route isn't the whole story — the Timeline and Cost sections below turn it into real weeks and dollar ranges. But first, now that you know your complexity, do a quick timing check: is this the right moment to move?

Before You Commit: When to Pause

You've decided to move and you've sized the job — the last gut check is timing. The most common reasons to pause are practical: you're mid-contract with a long exit-notice window, you're inside a peak-sales period, or your store leans on deep SFCC-native logic with no clean Shopify path yet. A real forcing function — a contract renewal deadline, a platform end-of-life announcement, or a capability you're blocked on — is what makes the timing right. Check the contract terms early; the exit-notice window is a fact you want before you plan anything, and it often decides the calendar more than any technical detail.

And if what you're actually weighing is whether Shopify Plus is the right enterprise platform in the first place — the three-year total cost of ownership, how it compares to Adobe Commerce or SFCC, and the profiles where Plus loses — that's a decision, not an execution question. Our Shopify enterprise guide handles that side; this one assumes the decision is made.

With the timing settled, the rest of this guide is a straight execution run — starting with getting your data out.

Getting Your Data Off SFCC

SFCC's own export lives in Business Manager: Site Export writes your catalog to XML (coupons to CSV). Note that Site Import/Export moves site configuration between instances, not your live product and customer data — that's a separate mechanism you don't rely on for the migration itself. From there, four routes carry data into Shopify.

Store Migration app supported list: Shopify App Store, verified July 2026. Tool coverage from each vendor's own pages; confirm current support before you buy.

Whichever route you choose, run a test migration first and validate the results on sample products before the full run. The walkthrough below shows an automated Salesforce-Commerce-to-Shopify move end to end, so you can see the flow before you start.

Historical Orders & the 60-Day Limit

Historical orders import as records through Shopify's Admin API, and you can suppress customer notifications so shoppers aren't emailed about years-old orders. One point that trips teams up: the Order resource returns only the last 60 days of orders by default. That's a read default you filter around, not a cap on importing history — your migration tool or ETL backfills older orders as records. Plan how you'll handle refunds and fulfillment for pre-migration orders, since those imported records aren't live transactions.

Customer Passwords

Passwords are encrypted outside the platform and cannot be migrated by any tool — this applies to every source platform, SFCC included. The fix is built in: after you import customers, trigger Shopify's account-invite email on launch day so shoppers set a new password on first login. Order history stays attached to each record, so accounts feel continuous once customers are back in. Expect a small login dip in week one and prepare a short support note explaining the reset.

Protecting Your SEO Through the Move

SFCC lets you shape storefront URLs; Shopify uses fixed paths — /products/<handle> for products and /collections/<handle> for collections. That means almost none of your old URLs survive unchanged, and each one needs a redirect. Here's how the common patterns map.

Shopify uses fixed /products/<handle> and /collections/<handle> paths. Patterns shown are generic examples of both platforms' structures.

Shopify lets you create up to 100,000 URL redirects on standard plans (20 million on Plus), imported in bulk by CSV. A few paths are reserved and can't be redirect targets, so keep them out of your map.

On rankings, be realistic: expect short-term fluctuation while Google re-crawls your new Shopify URLs — that's typical during any replatform. A complete 301 map, not luck, is what holds your equity through that window. Migrations that lose traffic almost always skipped or botched redirects.

Liquid or Headless: How You'll Rebuild the Storefront

Because your storefront is rebuilt, you get to choose how. Teams coming from PWA Kit or a Composable Storefront often assume they must stay headless, but that isn't the case — Shopify's native themes cover the majority of storefronts at a fraction of the cost. Here are the three honest paths.

Which path fits depends on your front-end requirements and the team maintaining it afterward. For the deeper trade-offs — the tech stack, scoping and what each approach really costs to build and run — our guide to custom Shopify development breaks down when headless earns its keep and when Liquid wins.

Timeline, Phases & the Team You Need

There's no single duration for an SFCC move, but the phases are consistent. Confirm your SFCC contract exit-notice window during discovery — it anchors the whole project, and you'll want to know it before you commit to a cutover date. Durations below are agency-observed ranges, not official Shopify data, and the higher-complexity setups from the quiz above sit at the top of every range.

Phase durations are agency-observed ranges, not official Shopify figures — timelines vary widely by store complexity. Use them for sequencing, not budgeting.

The speed gain after cutover is what teams notice most: work that took months of platform engineering on SFCC becomes routine on Shopify, because so much is built in.

What It Really Costs

There's no single price for an SFCC-to-Shopify move because most of the cost is labor: rebuilding cartridge logic, reconnecting integrations and validating data. Here's what each path realistically costs, using published Shopify-developer and Shopify-agency rate benchmarks.

Freelancer rates: Upwork Shopify-developer benchmarks. Agency rates and project minimums: Clutch Shopify directory. All observed 2026 — confirm current rates before budgeting.

If the answer is to hire it out, the harder skill is scoping the job and vetting whoever takes it. Our guide to hiring a Shopify developer covers the brief, the red flags and how to compare quotes so you don't overpay for the parts of the migration you could have scoped tighter.

Your Cutover Playbook

These steps apply to everyone: if you're running it in-house you'll do them yourself, and if you've hired help you'll supervise and sign off on each. If you're going headless, the storefront-build step looks different, but the sequence holds. One mechanic to plan for: between your main data dump and go-live, new orders and customers keep accumulating on SFCC — so budget a short content freeze plus a delta import to catch anything created in the gap. Tick each step off as you go; the checklist saves your progress on this device.

The Bottom Line

Salesforce Commerce Cloud and Shopify are both capable platforms; moving between them is a rebuild, not a rescue. The teams that come out ahead are the ones that scope the custom code and integrations honestly up front, pick the execution path that fits their complexity, and respect the two revenue-critical steps — the complete 301 redirect map and the final delta import before cutover. Get those right and the migration is a step up; rush them and it's an outage.

Frequently Asked Questions