Your Salesforce Commerce Cloud contract renewal is coming up. The number on the proposal is higher than last year. Again. And somewhere in your finance team, somebody is doing the maths on what 1% of gross merchandise value actually means when revenue grows 30%.
Here is the uncomfortable truth about SFCC: the platform's pricing model punishes growth. The more successful you become, the more you pay, and the gap between what you pay and what you receive has been widening since 2023. Meanwhile, the developer who understands your ISML templates and custom cartridges is fielding calls from three recruiters a week.
This is the dedicated SFCC-to-Shopify Plus migration guide. Not the generic "why you should consider replatforming" pitch. The specific architecture decisions, data migration traps, and timeline realities for brands leaving Salesforce Commerce Cloud in 2026.
The SFCC Cost Problem Is Structural
Salesforce Commerce Cloud charges on a revenue-share model, typically 1-3% of GMV. For context, here is what that looks like at different scales:
| Annual GMV | SFCC platform fees (1-2% GMV) | Shopify Plus annual cost | Annual savings |
|---|---|---|---|
| $10M | $100,000-$200,000 | $30,000-$48,000 | $52,000-$170,000 |
| $30M | $300,000-$600,000 | $48,000-$84,000 | $216,000-$552,000 |
| $75M | $750,000-$1,500,000 | $84,000-$180,000 | $570,000-$1,380,000 |
| $100M+ | $1,000,000-$3,000,000 | $180,000-$300,000 | $700,000-$2,700,000 |
Shopify Plus pricing moved to a variable model in 2024, but even at scale, the three-year TCO comparison is stark. Brands migrating from SFCC consistently see a 3-5x reduction in platform costs alone. When you add the developer cost differential, the gap widens further.
The developer talent crisis is real
Certified SFCC developers command $100-$180/hour domestically (AU/US/UK). The talent pool is shrinking because younger developers are choosing React, Node.js, and frameworks with larger communities. Shopify's developer ecosystem is 10-15x larger than SFCC's, which means faster hiring, lower rates, and more competition among agencies for your business.
Your current SFCC implementation partner knows this, which is why they are not exactly rushing to recommend migration. Their business model depends on the scarcity of their skills.
What Makes SFCC Migration Different
If you have read our general migration guide, you know the broad strokes. But SFCC has specific architectural patterns that create unique migration challenges. Ignore them and you will blow your timeline.
SFRA and PWA Kit: two codebases, two problems
If your store is on the Storefront Reference Architecture (SFRA), you are dealing with ISML templates, Node.js controllers, and a proprietary content slot system. If Salesforce moved you onto their PWA Kit (the React-based headless option), you have a different stack entirely. Either way, the code has zero portability. None of it comes with you to Shopify.
The migration is not a code port. It is a complete rebuild of the frontend with logic re-implementation. Accept this early and your planning gets honest.
Price books and customer groups
SFCC's price book architecture is one of its genuine strengths. Multi-currency price books, customer-group-specific pricing, promotional price overlays. Shopify Plus handles this differently: Markets for multi-currency, B2B catalogues for customer-specific pricing, and Shopify Functions for dynamic discounting.
The mapping is not one-to-one. It requires architectural decisions about which pricing rules move to Markets, which become B2B catalogue entries, and which become custom Shopify Functions. Get this wrong and your merchandising team will spend launch week manually fixing prices.
Content slots and page designer
SFCC's Page Designer and content slot system is how your marketing team manages campaigns and landing pages. Shopify's equivalent is Sections Everywhere with the Online Store Editor, plus metaobjects for structured content. The migration path requires rebuilding your content architecture and retraining your content team on a fundamentally different editing paradigm.
Order management system integration
Many SFCC stores use Salesforce Order Management (SOM) as their OMS. If you are leaving SFCC but staying on SOM, you need a custom integration between Shopify Plus and Salesforce OMS. If you are leaving the Salesforce ecosystem entirely, you need a new OMS strategy. We typically recommend evaluating Shopify's native order management, Brightpearl, or ShipHero before assuming you need the complexity of a standalone OMS.
The Migration Architecture for SFCC
Phase 1: SFCC audit and data mapping (4-6 weeks)
- Price book extraction: Export all price books, promotional pricing rules, and customer-group-specific pricing. Map each to its Shopify equivalent (Markets, B2B catalogues, or Shopify Functions).
- Content inventory: Catalogue every Page Designer page, content slot, and content asset. Determine which migrate to Shopify sections, which become metaobjects, and which can be simplified.
- Integration map: Document every SFCC cartridge integration (payment gateways, ERP connectors, marketing tools, analytics). Each needs a Shopify equivalent or custom app build.
- Custom business logic: Identify every controller, hook, and script that implements custom business rules. These become Shopify Functions, custom apps, or theme logic.
- SEO audit: Map every indexed URL from the SFCC URL structure to the Shopify structure. SFCC URLs follow patterns like
/s/SiteID/category/subcategorythat do not have Shopify equivalents.
Phase 2: Platform build (10-16 weeks)
- Theme development or headless frontend (Hydrogen) depending on customisation requirements
- Shopify Functions development for complex pricing, shipping, and payment logic
- Integration rebuilds (ERP, OMS, PIM, marketing automation)
- B2B configuration for customer-group-specific pricing and wholesale channels
- Markets configuration for multi-currency and international selling
- Custom app development for any SFCC cartridge functionality that does not have a Shopify equivalent
Phase 3: Data migration (3-5 weeks)
- Product catalogue migration with price book mapping to Markets/B2B catalogues
- Customer data migration (accounts, addresses, order history, loyalty data)
- Content migration (Page Designer pages to Shopify sections)
- Multiple test migrations with data validation scripts before final cutover
Phase 4: Cutover and hypercare (1-2 weeks)
DNS switch during a planned window, typically sub-2-hour downtime. Both platforms run in parallel for 48-72 hours with order routing to catch edge cases. Integration health monitoring runs continuously through the first 30 days.
The Build-and-Forget Trap
You left SFCC because the platform was not keeping pace with your business. A traditional agency migration puts you on Shopify Plus, hands you a login, and leaves you with a new platform that starts depreciating the moment it launches. That is the same cycle that made you leave SFCC.
Our migrations launch into a living ecosystem. The difference is fundamental:
| Post-migration | Traditional agency | Living ecosystem (Sonder) |
|---|---|---|
| Monitoring | 30-day warranty, then silence | AI monitors performance, integration health, conversion, and security continuously. Anomalies surface in real-time, not monthly reports. |
| Integration health | ERP sync breaks silently at 2am. You find out when orders stop shipping. | Every integration endpoint monitored. Failed syncs flagged within minutes. Schema drift caught before it corrupts data. |
| Platform updates | You read the Shopify changelog yourself | Every Shopify release evaluated against your store. Relevant features implemented proactively. Your store appreciates instead of stagnating. |
| Conversion optimisation | Not included | AI surfaces checkout drop-off spikes and mobile UX regressions. Human experts action the insights weekly. Your conversion rate climbs, not decays. |
| Client visibility | Monthly PDF (maybe) | Real-time dashboard: site health score, optimisations shipped this week, measurable ROI of every change. |
A living ecosystem migration is not a project with a start and end date. It is an ongoing relationship where your Shopify Plus store gets better every week. Think of it as moving from a platform that taxed your growth to a system that compounds it.
Investment Ranges for SFCC Migration
SFCC migrations run higher than Magento or BigCommerce migrations because the architecture is more complex and the integration surface area is larger. Here are realistic ranges:
| Brand profile | Migration scope | Investment range | Timeline |
|---|---|---|---|
| $10M-$25M GMV, DTC primary | SFRA to Shopify Plus theme, 2-3 integrations, standard checkout | $150,000-$220,000 | 16-22 weeks |
| $25M-$60M GMV, DTC + B2B | Complex build, ERP + OMS, custom checkout, B2B catalogues, multi-market | $220,000-$380,000 | 22-30 weeks |
| $60M-$100M+ GMV, multi-brand/global | Headless or multi-entity, multiple ERPs, custom apps, global markets | $380,000-$550,000+ | 28-40 weeks |
These include 12 months of living ecosystem management. The ongoing retainer after year one runs $10,000-$20,000/month depending on integration count and store complexity.
The ROI case writes itself when you compare these one-time investments against the annual SFCC platform fees from the table above. Most brands achieve full payback within 12-16 months purely through platform cost reduction, before accounting for improved conversion rates and developer cost savings.
When NOT to Leave SFCC
We will talk ourselves out of a project when the maths do not work. You should consider staying on SFCC if:
- You are deeply embedded in the Salesforce ecosystem: If you use Marketing Cloud, Service Cloud, and Commerce Cloud as an integrated suite, and the data flows between them are the foundation of your customer experience, the migration scope expands significantly. The platform savings may not justify the integration rebuild cost.
- Your contract has 18+ months remaining: Breaking a Salesforce contract early usually involves paying the remaining term. Time your migration to align with your renewal date.
- You have fewer than 6 months of runway: SFCC migrations take 16-40 weeks. If you need the new platform live for a specific date (Black Friday, a major product launch), work backwards from that date and add a 4-week buffer. If the maths does not work, wait for the next window.
- Your business requires a true marketplace: Multi-vendor marketplace functionality with independent seller payouts is not native to Shopify Plus. If that is your model, SFCC (or a dedicated marketplace platform) may still be the better fit.
The SFCC Exit Checklist
If you are moving forward, here is what to prepare before your first call with any agency:
- Current SFCC contract terms: Renewal date, exit clauses, GMV tier, and any penalties for early termination.
- Integration inventory: A list of every system connected to SFCC (ERP, OMS, PIM, CRM, marketing automation, analytics, payments).
- Cartridge audit: Which cartridges are installed, which are actively used, and which are abandoned. We see an average of 8-12 cartridges per SFCC store; typically 3-4 are unused.
- Annual platform spend: Full TCO including SFCC fees, hosting, development retainer, and ad-hoc project costs over the last 24 months.
- Revenue trajectory: Current GMV and projected growth. This determines whether the SFCC cost penalty accelerates or stabilises.
Bring these to the conversation and you will get an honest assessment within a week. Without them, any agency quoting you a migration price is guessing.
Next Steps
If you are a brand doing $10M+ on Salesforce Commerce Cloud and the renewal numbers are making your CFO nervous, we should talk. We will audit your current SFCC TCO, model the Shopify Plus alternative including migration cost, and give you a straight answer on whether the move makes financial sense for your specific situation.
No pitch. No pressure. If staying on SFCC is the right call for your business, we will tell you that too.