The SFCC migration is rarely about capability. It's about the invoice at renewal. Salesforce Commerce Cloud's revenue-share pricing punishes the brands that make it work hardest, and the implementation costs sit on top. Capable platforms are easy to migrate away from when the maths stops working. Here's the playbook for a clean exit.
Why brands actually leave Salesforce Commerce Cloud
The conversation almost always starts at renewal. SFCC's commercial model is based on a percentage of gross merchandise value, with floor minimums and tiered pricing. Brands signing 3-year deals lock in a rate. When the deal comes up for renewal, the rate is renegotiated, and the new number is usually a step change.
For brands that have grown 2x or 3x over the contract term, the renewal quote can be 1.5 to 2x the previous spend. That's the trigger.
The cost story is bigger than the licence number. SFCC implementations almost always involve a system integrator partner: Cognizant, Wipro, Accenture, Publicis Sapient, Cap Gemini, Astound. Annual partner spend on a mid-market SFCC store usually runs $400K to $1.5M depending on velocity. Most of that gets absorbed into Shopify Plus build costs of $80K to $250K and ongoing partner retainers of $150K to $400K. The TCO delta is significant.
The capability gaps are real but not usually decisive. SFCC has Einstein recommendations, deep B2C/B2B architecture, and a strong international story. Shopify Plus has caught up on every front that matters for $20M to $250M brands, and is materially better on velocity, app ecosystem, and developer talent availability.
What "the SFCC stack" actually means
A typical mid-market SFCC store has accumulated layers over multiple implementation cycles. The migration is partly a translation exercise, partly a chance to retire what no longer matters.
Cartridges. SFCC's unit of custom code. A typical mid-market store has 30 to 100 cartridges installed - some custom, some from the Salesforce LINK marketplace. Cartridges replace, extend, or add functionality. Migration means each cartridge gets evaluated: native Shopify replacement, Shopify app, custom Shopify Function, or retired entirely. Most stores end up retiring 40 to 70% of cartridges.
ISML templates. SFCC's templating language. Equivalent to Liquid on Shopify but with a different syntax and data model. Templates don't migrate. The front-end gets rebuilt either as a classic Shopify Plus theme or headless.
Page Designer. SFCC's visual page builder. Maps to Shopify's Online Store 2.0 sections or a headless CMS approach with Sanity or Contentful. Pages need to be rebuilt because the underlying structure is different.
Business Manager. SFCC's admin interface. Replaced by Shopify admin. Workflow differences here usually surface during user training, not technical migration.
OCAPI/SCAPI. SFCC's APIs. Used for integrations and headless front-ends. Replaced by Shopify's Storefront API, Admin API, and Functions for integration work.
The migration decision tree starts with the cartridge audit. The audit determines roughly half the project scope.
The integration problem
Integration depth is the hardest part of an SFCC migration. SFCC tends to attract enterprise customers, and enterprise customers tend to have integrated systems: ERP, OMS, PIM, WMS, payment platforms, tax engines, customer service tools, and bespoke connectors built years ago that nobody wants to touch.
SFCC's integration patterns usually fall into three categories:
Direct cartridge integrations. Pre-built connectors from LINK or custom-built cartridges that talk directly to SAP, Oracle, Microsoft Dynamics, or NetSuite. These don't translate to Shopify directly. The connection logic needs to be rebuilt against Shopify's APIs, often through a middleware layer (Boomi, Workato, MuleSoft, Celigo).
Middleware-routed integrations. Many SFCC stores already have middleware in place. The good news is the middleware can usually be repointed at Shopify with mapping changes rather than full rebuilds. The bad news is the mapping changes are non-trivial because the data shapes differ.
Custom event-driven flows. Webhooks, message queues, and async processes that fire on order, customer, or product events. These need to be rebuilt against Shopify's webhook system and API patterns. Reliable, but it's redesign work, not lift-and-shift.
A typical SFCC migration includes 4 to 12 integration workstreams running in parallel. Each one is its own project. Underestimating this layer is the most common reason SFCC migrations slip.
What changes at the data layer
SFCC's data model is closer to Shopify than Magento's EAV but not as clean as BigCommerce's. The translation is documented in a catalog mapping before any data moves.
Master and variation products. SFCC's master/variation product model maps to Shopify's product/variant model. Most master products with their variations migrate cleanly. SFCC's product sets (collections of products sold together) usually become Shopify product bundles via apps or custom development.
Product attributes. SFCC stores attributes against products and variants. These map to Shopify product fields, variant options, tags, or metafields depending on use. Custom attributes specific to filtering or search become metafields with defined schemas.
Catalogues. SFCC's catalogues (master and storefront) are the source-of-truth for assortment per site. On Shopify, this maps to collections, with separate logic for what's published per Market or store.
Inventory lists. SFCC's inventory lists tied to specific sites become Shopify inventory locations. Multi-warehouse setups need explicit mapping during the migration design phase.
Customers and orders. Customer profiles, addresses, and order history migrate. Passwords don't (see customer account migration). Order metadata from cartridges or custom OMS flows gets reviewed during migration: what stays in Shopify, what stays in the OMS, what becomes a metafield.
Multi-site realms
Many SFCC implementations run multiple sites under one realm: different brands, different regions, different B2C and B2B fronts. The migration needs to decide what each site becomes on Shopify before catalogue work starts.
Three common patterns:
Single store with Markets. Best for brands where sites differ by region or currency but share product catalogue. One Shopify store, multiple Markets, localised pricing and content.
Multiple Shopify stores. Best for genuinely separate brands or business units that share infrastructure on SFCC for cost reasons. Each becomes its own Shopify Plus store.
Hybrid. B2C runs in one configuration, B2B runs in another. Sometimes B2B becomes a separate store on Shopify Plus. Sometimes it stays in the same store using native Plus B2B features. Decision driven by sales team workflow and pricing complexity.
The decision affects everything downstream: catalogue mapping, redirect strategy, integration architecture, and reporting setup.
The SEO conversation
SFCC URL structures are configurable per site. Some stores use /product-name.html style. Others use /category/product-name. Some use site IDs in the path. The first task in SEO planning is documenting exactly what the live URL structure is.
Shopify's URL structure is fixed: /products/handle, /collections/handle, /blogs/blog-name/article-handle, /pages/handle. The 301 redirect map is what bridges old to new.
For mid-market SFCC stores the redirect map is usually 10,000 to 100,000 URLs because SFCC's category and faceted navigation generate large URL surfaces. We crawl the live site, pull Google Search Console data, and pull existing redirect rules into a source-of-truth spreadsheet before mapping destinations.
Multi-site realms add complexity because each site has its own URL space. The redirect strategy needs to account for which old site each URL belonged to and where it lands on the new Shopify setup.
What we won't do
A few principles that keep the project clean.
We don't migrate cartridges you no longer use. A cartridge audit usually shows 30 to 50% of installed cartridges have no real impact. Migration is the moment to retire them.
We don't replicate cartridge logic that's better as native Shopify. If a cartridge was a workaround for something Shopify Plus does natively, we use the native feature. The cost of replicating workarounds is technical debt on day one.
We don't ship without integration sign-off. Every integration is rehearsed end-to-end on the migration sandbox before go-live. ERP, OMS, PIM, and payment integrations all run against staging endpoints with sample data.
We don't ship without 1:1 data reconciliation. Product count matches. Customer count matches. Order count matches per site, per Market, per brand. If anything doesn't reconcile, we don't launch.
We don't sign off on a redirect map we haven't tested. Every URL gets crawled. Every redirect gets verified.
Where to start
If you're considering a Salesforce Commerce Cloud to Shopify Plus migration, the first step is a discovery audit. We document your cartridges, integrations, multi-site structure, catalogue depth, and redirect surface area, then return a build spec, a risk register, and a fixed-price Phase 1 quote.
The dedicated Salesforce Commerce Cloud to Shopify Plus migration page has more detail on our process, what's included, and how the timeline maps to your specific setup.
For broader context on Shopify Plus migrations across all source platforms, see the complete migration guide. For the operational decisions that come post-migration, why your Shopify Plus store needs an operations strategy covers the layer that determines whether the new platform actually pays back.
Frequently asked questions
Why do brands leave Salesforce Commerce Cloud?
The conversation almost always starts at renewal. Salesforce Commerce Cloud uses a revenue-share pricing model that scales with GMV. For brands above $25M revenue, the percentage-of-revenue cost can exceed $300K to $500K per year, which becomes significant compared to Shopify Plus published pricing. The other driver is implementation cost: SFCC builds and changes typically run 1.5 to 3x more expensive than equivalent Shopify Plus work.
How long does a Salesforce Commerce Cloud to Shopify Plus migration take?
Most SFCC migrations run 14 to 22 weeks, longer than other platforms because integration depth is heavier. SFCC brands typically have deeper Salesforce CRM integration, more cartridges, and more custom B2B workflows. Brands above $50M revenue or with extensive omnichannel setups push toward 22 to 28 weeks.
What are SFCC cartridges and how do they translate?
Cartridges are SFCC's extension system, similar to Magento extensions or Shopify apps. Each active cartridge gets audited and mapped to either a Shopify app, native Shopify capability, or custom rebuild. Brand-built cartridges (custom logic specific to your business) are the most complex translation work because they often contain bespoke business rules nobody fully documented.
Will my Salesforce CRM integration survive migration?
The Salesforce CRM connection migrates, but the architecture changes. SFCC has native bi-directional Salesforce sync. Shopify Plus integrates with Salesforce through middleware (MuleSoft, Workato, Boomi) or direct API connectors. The data flows the same way but the integration layer is different. Plan a 4 to 8 week Salesforce integration workstream parallel to the main migration.
How does SFCC B2B translate to Shopify B2B?
SFCC uses customer groups, price books, and account hierarchies for B2B. Shopify B2B uses companies, locations, and catalogues. The mapping is workable: customer groups become catalogues, account hierarchies become company structures, price books become catalogue pricing rules. The translation work is significant because SFCC B2B usually has years of custom workflow logic that needs explicit rebuilding.
How much does a Salesforce Commerce Cloud to Shopify Plus migration cost?
Build costs typically range from $180K to $400K for mid-market brands, with most landing in the $200K to $300K range. SFCC migrations cost more than other platforms because integration depth, B2B complexity, and cartridge translation all add scope. Total year-one investment including post-launch retainer and apps usually lands at $400K to $900K. The migration usually pays back in 18 to 24 months through reduced licence fees and lower implementation costs.
What about SFCC's Einstein AI features?
SFCC's Einstein recommendations, Einstein Search, and Einstein Personalisation don't have direct Shopify equivalents. The replacement strategy uses Shopify's native recommendations (good for most cases), Algolia or Klevu for AI-powered search, and personalisation tools like Nosto, Klaviyo predictive analytics, or Rebuy for product recommendations. The combined replacement stack costs less than Einstein and gives you better data ownership.
Can I migrate just B2C and keep B2B on SFCC?
Technically yes, but it's rarely worth it. Running two platforms doubles operational overhead, integration complexity, and ongoing licence costs. Brands sometimes do this when B2B revenue is small (under 10% of mix) or B2B has unique requirements. For brands with meaningful B2B revenue (above 20% of mix), migrating both is almost always the right call.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Salesforce Commerce Cloud migrations are the longest of any major source platform. Plan for 14 to 22 weeks. Integration depth and cartridge complexity are what stretch the timeline.
- The cost driver is SFCC's revenue-share pricing model. At scale, the licence becomes a percentage of GMV that compounds. Brands often discover the move pays for itself in 12 to 18 months.
- ISML templates, cartridges, and Page Designer don't migrate. The front-end gets rebuilt. Most brands use the migration as the moment to evaluate headless.
- Integration depth is usually the hardest part. ERP, OMS, and PIM connections that were built into SFCC over years need to be re-architected against Shopify's APIs.
- Multi-site SFCC realms (different brands or regions on one instance) need careful planning. Some land on Shopify Markets. Some become separate stores.
