Daniel Wellington cut $600,000 a year off platform spend by leaving Salesforce Commerce Cloud for Shopify Plus. Skullcandy did the same migration in 90 days and grew holiday revenue 45% year over year. The Conran Shop dropped total cost of ownership by 50% and lifted conversion by 54%. These are not outliers anymore. They are the pattern.

If you run a Salesforce Commerce Cloud store and you are thinking about Shopify, you are not alone. The trend is loud. The math is easy. The license savings alone usually pay for the migration within 18 months, according to Contra Collective's 2026 analysis.

What most replatforming guides skip is the part that actually breaks brands. Not the data move. The morning after launch, when "I can't log in" and "where is my order" tickets flood in, and the support team is buried before lunch. This guide covers the cost math, the platform differences, the 7-step migration playbook, and the support continuity chapter nobody writes.

Hear what AI support calls sound like for your store. Just paste your Shopify URL and get sample calls in under 20 seconds, no email required. Listen to demo calls for my store.

Why brands are leaving Salesforce Commerce Cloud

Three things drive almost every SFCC to Shopify migration: cost, agility, and the people problem.

Cost is the loudest reason. Salesforce Commerce Cloud charges roughly 1-3% of your gross merchandise value. On $10 million in annual revenue, that's $100,000 to $300,000 a year in platform fees alone, before development, hosting, or third-party integrations. At $150M, you're looking at $1.8M to $2.5M a year in licensing, with total platform spend often hitting $4M to $5M. Shopify Plus, all-in, typically lands 40 to 60% below the equivalent SFCC stack.

Agility is the second reason. SFCC features that should take days take months. The certified-developer pool is small, agency contracts are long, and release cycles are slow. Brands tell us the wait for changes that competitors ship in a sprint is the breaking point.

Then there's the people problem. SFCC's partner ecosystem is a fraction of Shopify's 8,000+ apps. Hiring an SFCC developer is harder and more expensive than hiring a Shopify dev. When your agency wants to renew at 1.4x last year's rate, you start checking the alternatives.

The proof is in the brand outcomes. According to Shopify's enterprise data migration guide:

• Daniel Wellington: cut license costs 50%, saved roughly $600,000 a year, launched 12 stores
• The Conran Shop: 50% TCO reduction, 54% conversion rate lift
• Skullcandy: 90-day migration, page load from 2.8s to 0.8s, 45% YoY holiday revenue, absorbed a 200% traffic spike without a performance issue
• CarBahn: organic traffic tripled in 30 days, AOV jumped by more than $200, page load dropped from 9 seconds to 1 second

Shopify also benchmarks its migrations as 36% faster than custom platforms, 56% less expensive than competitors, and 74% more likely to finish on time. Read those with a salt grain, since Shopify is the source. But the brand outcomes hold up across third-party G2 and Capterra reviews too. Salesforce B2C Commerce sits around 4.0/5 on G2, with the most-mentioned complaints being implementation cost, expensive certified developers, and slow integration cycles.

If you're on Shopify or about to be, Ringly.io handles the post-launch phone wave so your team doesn't drown in tickets. Try it free for 14 days.

SFCC vs Shopify Plus: what actually changes

Most of the replatforming pain comes from structural differences, not from the data move itself. Here's the side-by-side, based on real migrations we and our agency partners have shipped.

The variant ceiling matters. SFCC supports attribute groups that map cleanly to fashion, footwear, and configurable products. Shopify caps at 3 options. Brands selling shoes (size + width + color + material) need a workaround, usually a product-options app like Infinite Options or a metafield-based UI. Plan for the rebuild. The Vervaunt analysis on SFCC vs Shopify Plus covers this in detail.

Multi-store is a real planning question. Shopify Markets has closed most of the gap, but if you run dozens of country-specific storefronts with separate inventory pools, you might still want separate Shopify stores. That's a decision to make with your agency, not a default. See the Shopify Plus vs Commerce Cloud breakdown for the structural comparison.

Payments has a hidden cost. If you're locked into a multi-year Adyen contract on SFCC, you'll probably keep paying Adyen for 12+ months after launch while running Shopify Payments. Budget for the overlap.

What it actually costs to migrate

Cost has two layers: the new Shopify Plus subscription, and the one-time migration spend.

Shopify Plus 2026 pricing:

For a brand doing $5M/mo GMV on a 3-year term, monthly platform fee lands around $2,300 + ($4M × 0.25%) = $12,300/mo, or roughly $147K/year. Compare that to the SFCC equivalent at 1-3% of GMV: $600K to $1.8M a year. The delta is the easy part. See our full Shopify Plus pricing breakdown for the line-by-line math.

Migration spend (one-time):

Hidden costs nobody itemizes upfront:

• Adyen / gateway overlap: 6-12 months of double payment
• Theme rebuild: $25K-$80K depending on design ambition
• App stack rebuild: $50-$2,000/mo per app, plus implementation
• Parallel agency contracts: your SFCC agency stays on through cutover (and they'll charge for it)
• Training: your internal team needs 2-4 weeks of Shopify ramp
• Helpdesk + phone migration: rarely budgeted, always needed

Want to see what AI phone support costs vs the alternative? Start your free trial. Setup takes about an hour.

The 7-step Shopify migration playbook

Every migration we've watched ship cleanly followed roughly the same path. The brands that skipped steps got hurt. Here it is.

Step 1: Audit your SFCC stack

Before you spec anything new, document what's actually there.

• Inventory every customization: SAP (Storefront Application Package) cartridges, custom scripts, business rules, pricing logic
• Map every integration: ERP, OMS, helpdesk, payment, shipping, tax, email, loyalty, reviews
• Catalog every page template: homepage, PLP, PDP, cart, checkout, account, content
• List every custom data field: product attributes, customer fields, order metadata

You'll be surprised what's in there. Most SFCC stores have 20-40% of customizations that nobody can explain anymore.

Step 2: Decide what to keep and what to kill

This is where most brands save the most money. According to the Referral Candy migration guide, 30 to 40% of SFCC customizations don't need rebuilding. They were built for a specific 2019 use case nobody remembers.

For each customization, ask three questions:

• Does it drive revenue today? If yes, rebuild it. If no, kill it.
• Is there a Shopify app that does this natively? Use the app. Custom dev is a last resort.
• Can we live without it for 90 days post-launch? If yes, defer. Phase 2 backlog.

This single decision usually cuts 25-35% off the migration budget.

Step 3: Map your data

Pull every product, variant, customer, order, content page, redirect, and metadata field. Then map field-by-field to the Shopify schema.

• Products and variants: SFCC attribute groups -> Shopify options (max 3) + metafields. Variant count check (cap is 2048).
• Customers: emails, phone numbers, addresses, tags, segments, lifetime value
• Orders: order IDs, line items, fulfillment status, refunds, notes
• Content: blog posts, PLPs, marketing pages
• Redirects: URL-by-URL map (this is your SEO insurance)

If you're using LitExtension, Cart2Cart, or a similar tool, the heavy lift is bulk import. The cleanup, however, is manual. See our migration timeline guide for the realistic pace.

Step 4: Pick phased vs big-bang

Big-bang: one cutover day, everything switches at once. Simpler to coordinate. Riskier.

Phased: region-by-region, brand-by-brand, or category-by-category. Lower risk. Longer timeline.

The brands that ship clean cutovers in 90 days (like Skullcandy) do big-bang on a low-traffic week with a heavily rehearsed rollback plan. The brands that botch cutovers usually rushed big-bang into peak season. Don't migrate the eight weeks before Black Friday.

Step 5: Build, populate, integrate

This is the longest phase. Roughly 6-12 weeks for mid-complexity.

• Theme: pick Dawn or a premium theme as base; customize from there
• Apps: install your shortlist (10-15 typical), configure each
• Payments: Shopify Payments + backup gateway; Apple Pay, Google Pay, Shop Pay
• Helpdesk: install Gorgias, Richpanel, or Reamaze with Shopify integration (see Gorgias vs Richpanel for which fits your team)
• Phone: this is the orphan step. Plan it now. (More on this below.)
• Email/SMS: Klaviyo, Postscript, Attentive (most SFCC brands already have these)
• Tax: Avalara or Shopify Tax
• Shipping: ShipStation, Shippo, or ShipBob if 3PL
• Reviews, loyalty, search: depends on stack

Step 6: Test in staging, then test again

Build a full clone of the new store in a staging environment. Run end-to-end tests on:

• Checkout (with real payment methods, then refund)
• Account creation, password reset, login
• Order lookup and customer service flows
• Subscription billing if applicable
• B2B account flows
• All integrations (helpdesk, ERP, fulfillment, email)
• Mobile responsiveness across iOS and Android

The single most-skipped test: password reset emails actually arriving in customer inboxes. This is the #1 source of post-launch tickets.

Step 7: Cutover, redirect, monitor

The big day. Hour-by-hour plan, with named owners for each step.

• DNS switch: point the domain to Shopify
• 301 redirects: deploy the full URL map (every old URL -> closest new URL)
• Sitemap submission: submit new sitemap to Google Search Console and Bing Webmaster
• Monitor: traffic, error rates, checkout completion, support ticket volume, phone call volume
• War room: 24-72 hour coverage with dev, support, and ops in one room (or Slack channel)
• Rollback plan: documented and ready

The first 72 hours are where most things break. The first two weeks are where customer service gets tested.

Protecting your SEO through the migration

This is the easiest place to lose 30-40% of organic traffic if you don't do it right. The good news: it's also the most preventable.

Build the 301 redirect map BEFORE cutover, URL-by-URL. Don't redirect everything to the homepage (that destroys ranking signals). Map each old URL to the closest new URL.

• Product pages: old PDP URL -> new PDP URL
• Category pages: old PLP URL -> new collection URL
• Content pages: old slug -> new slug
• Blog posts: old URL -> new URL
• Custom pages: account, support, about

Preserve all canonical tags, meta titles, meta descriptions, and image alt text in the migration. These are years of optimization work. Don't lose them.

After cutover, submit the new XML sitemap to Google Search Console and monitor crawl errors daily for 60-90 days. Watch Search Console's "Pages" report for indexing drops. Crawl the new site with Screaming Frog and diff against your pre-migration crawl to catch broken redirects.

If you're using ecommerce SEO best practices on the new store, the typical pattern is a 2-4 week dip followed by full recovery, sometimes with a lift if the new site is faster (which it usually is).

The chapter nobody writes: support continuity through the cutover

This is the section that decides whether your migration looks clean or chaotic from the customer's side. And almost nobody plans for it.

The pattern is brutal. The morning after cutover, two ticket types flood in.

"I can't log in." Shopify forces a password reset for migrated accounts. The email lands in spam, gets ignored, or never delivers because the sending domain isn't authenticated yet. Customers hit "forgot password" two or three times. Then they call.

"Where is my order?" Pre-migration orders may not import, or they import with new order numbers. The customer sees their old order confirmation but can't find it in their new account. They call. This is the WISMO call (where is my order), and it dominates the queue. WISMO calls typically make up 30-50% of inbound support volume in a normal week. After a migration, they can hit 70%.

Three things break at cutover:

• Phone line routing: if you ran Service Cloud or Genesys, that doesn't follow. You need a new phone stack live on day one.
• Helpdesk integration: your new helpdesk (Gorgias / Richpanel / Reamaze) needs to be reading Shopify orders correctly from minute one
• Knowledge base accuracy: your KB articles probably reference old account flows, old order URLs, old return processes. Update them BEFORE launch.

The math is rough. A typical mid-market Shopify brand handles 200-500 inbound support contacts a day. After a migration, expect that to double or triple for 1-2 weeks. If your support team is 6 people, you're now drowning.

Most brands solve this badly. They hire temps (slow to ramp, expensive, don't know your product) or escalate everything to founders (burnout, bad CSAT). There's a better way.

Ringly.io is AI phone support for Shopify brands. Instead of hiring and training a phone team, the AI handles inbound calls 24/7: order status, returns, product questions, abandoned cart rescue. Across 50+ brands, the AI resolves 73% of calls autonomously at roughly $0.42 per resolved call. Plans start at $349/mo with a 65% resolution guarantee. Live in under an hour.

For a migration cutover, that means the phone wave gets absorbed without temps, without burning out your team, without watching CSAT collapse on launch week. Calls that need a human escalate cleanly to Gorgias, Richpanel, Reamaze, or whatever helpdesk you're moving to. Your team handles the complex tickets; the AI handles the volume.

Ready to see what AI phone support looks like for your store? Start your free trial. Setup takes about an hour.

Migration mistakes that kill the project

We've watched dozens of replatforms ship. The failures repeat.

• Rebuilding everything: 30-40% of SFCC customizations don't need to come over. Cut them.
• Skipping the redirect map: this is how you lose a third of your organic traffic in two weeks
• Big-bang in peak season: don't migrate the 8 weeks before BFCM. Don't migrate the 4 weeks before Valentine's. Pick a quiet stretch.
• Cutting the old agency too early: you need parallel coverage through cutover plus 4 weeks
• Forgetting phone and helpdesk: this is the support continuity gap that turns a clean technical launch into a CSAT crash
• Underestimating data cleanup: products with missing images, orphan SKUs, broken variants. Budget 2-3x your initial estimate.
• Treating training as optional: your internal team needs real Shopify ramp time before they're effective
• Skipping the rollback plan: hope is not a launch strategy

The Ringly Shopify migration partner guide has the agency-selection criteria we use, and the Shopify migration agency overview covers the right RFP questions.

Frequently asked questions

How long does an SFCC to Shopify migration take?

Most mid-market migrations take 8-16 weeks. Enterprise builds with B2B, headless, or multi-region setups run 4-6 months. Skullcandy did theirs in 90 days, but they ran a tight scope and a heavily rehearsed cutover.

Will I lose my SEO rankings?

Only if you skip the 301 redirect map. With proper URL-by-URL redirects, canonical preservation, and metadata migration, the typical pattern is a 2-4 week dip followed by full recovery. Without redirects, expect 30-40% traffic loss that takes months to claw back.

What about my product variants and attributes?

Shopify caps at 3 options per product and 2048 variants. SFCC's attribute groups don't map 1-to-1. Plan for metafields, product-options apps, or a different storefront pattern for highly configurable products like footwear or eyewear.

Is Shopify Plus cheaper than SFCC?

For most mid-market brands, yes. SFCC charges roughly 1-3% of GMV. Shopify Plus is $2,300-$2,500/mo flat up to ~$1M monthly GMV, then variable above. Brands typically report 40-60% all-in cost reduction across the full stack.

What happens to my customer service phones during the cutover?

This is the gap that catches most brands. If you ran Service Cloud or a separate phone vendor on SFCC, the routing doesn't follow. You need a new phone setup live on day one. Most brands underestimate the post-launch ticket spike (often 2-3x baseline for 1-2 weeks). Ringly.io handles inbound phone calls during the spike so your team isn't overwhelmed.

Can Shopify Plus handle B2B?

Yes. B2B is now a native Shopify Plus feature: company accounts, custom catalogs, PO workflows, net-30 terms. You don't need a separate B2B platform anymore.

Should we do a phased or big-bang launch?

Phased is safer (region-by-region or brand-by-brand). Big-bang is faster but riskier. If you do big-bang, do it on a low-traffic week with a fully rehearsed rollback plan and a 72-hour war room.

The cutover decision

The platform decision is the easy part. SFCC to Shopify Plus is the most common enterprise replatform in the market right now, and the brand outcomes (Daniel Wellington, Skullcandy, Conran Shop) speak for themselves. The math works.

What separates a clean cutover from a CSAT crash is the support continuity plan. The phone line, the helpdesk integration, the post-launch ticket spike. Plan for it before you sign the Shopify contract, not the morning after launch.

If you're migrating to Shopify and you want to keep phone support live without hiring a temp team, try Ringly.io free for 14 days. The AI handles 73% of calls autonomously, escalates the rest to whatever helpdesk you're moving to, and is live in under an hour.

Article by Ruben Boonzaaijer. Co-founder of Ringly.io. We build AI phone support for Shopify brands so they can scale support without hiring a phone team.