Salesforce Commerce Cloud migration
OUXP moves Salesforce Commerce Cloud (SFCC) stores to Shopify Plus for enterprise teams tired of revenue-based license fees and of waiting on specialists for every change. We rebuild your cartridge logic as Shopify apps and Functions, map your sites and locales to Shopify Markets, keep Salesforce CRM and Marketing Cloud connected where you need them and protect rankings with a per-pattern 301 map – at a price fixed in writing before work starts.
SFCC is a capable enterprise platform, and Salesforce runs the infrastructure. What teams leave is the operating model: license fees that rise with revenue, and a release process that sends most changes through specialists.
01
SFCC is typically licensed as a share of gross merchandise value – commonly estimated at 1–3%. Salesforce lists every B2C Commerce edition as “Contact for pricing”, so treat this as an estimate; your contract has the real number.
02
Templates, controllers and business rules live in custom cartridges, so even small storefront changes usually go through a systems integrator or specialist SFCC developers.
03
Code ships as versioned cartridges, and data and content move from staging to production by replication. Planned releases run well; quick campaign changes and experiments feel slow.
04
Salesforce still supports SiteGenesis but stopped feature work on it years ago. Moving to SFRA, the Composable Storefront or Storefront Next (generally available since June 2026) is a rebuild in its own right – which is why many teams price it against leaving.
05
The Composable Storefront (PWA Kit) and Storefront Next add a React front end to build and maintain on top of B2C Commerce – two codebases, two release cycles, one more set of specialists.
06
SFCC runs on contract terms. Start an enterprise migration 6–9 months before renewal, or you pay for both platforms while the new store is built.
Both are enterprise SaaS platforms with hosting included. The differences are cost structure, who can make changes and how fast those changes ship.
| Criteria | Salesforce Commerce Cloud | Shopify Plus |
|---|---|---|
| Hosting and infrastructure | Included Managed by Salesforce | Included Managed by Shopify |
| Pricing model | Revenue share A share of GMV, commonly estimated at 1–3% | Flat fee From $2,300/month on a three-year term, or $2,500/month on a one-year term; high-volume stores move to a revenue-based variable fee |
| Who makes changes | Specialists SFCC developers or a systems integrator | Wide talent pool A large market of Shopify developers and agencies |
| Release process | Scheduled Code versions, then staging-to-production replication | Continuous Theme and app deploys; the platform updates itself |
| Server-side customization | Full code access Cartridges, hooks and controllers | Extensible Shopify Functions for discount, shipping and payment logic, checkout UI extensions and custom apps |
| Multiple sites and regions | Built in Many sites in one realm, sharing a master catalog | Built in Shopify Markets in one store, plus 9 expansion stores included (one brand per contract) |
| Salesforce CRM and Marketing Cloud | Native Salesforce-built connectors | Via integration Middleware such as MuleSoft, or a custom app |
| Extensions | Via cartridge Merged into your codebase | Via app Updated by each app’s vendor |
| Built-in AI | Einstein recommendations and search, plus Agentforce agents | Shopify Magic, Sidekick and Agentic Storefronts, plus apps |
Broad comparison; details vary by project. Shopify pricing and platform facts as of October 2026; SFCC license rates are industry estimates – Salesforce doesn’t publish them.
When staying on SFCC is the right call
Stay if your sales and service teams depend on SFCC’s built-in links to Sales, Service and Marketing Cloud, if you run many brands and regions with an in-house SFCC team that ships well, or if Einstein personalization on your Salesforce data drives your merchandising. If that describes your business, the free migration assessment says so.
10–24+ weeks – usually the longest engagements we run, because SFCC stores carry years of cartridge logic, enterprise integrations and often several sites. Where your project lands depends less on catalog size than on the factors below.
Running several sites? Multi-site realms can move in phases – one site or region first, then the rest on the same foundation – which spreads cost and risk across several launches.
Typically $80,000–$250,000+. The free assessment gives you a band without store access; the fixed price follows a deeper review with read-only access under NDA and is agreed in writing before work starts.
Data moves with its history. Cartridges and custom code can’t transfer between platforms, so they are rebuilt, replaced by an app or retired. Discovery inventories every site, catalog, price book, cartridge and integration, and you sign off the list before the build starts.
Internal IDs don’t carry over between platforms; the relationships do – each order with its customer and products, each master product with its variants and images. SFCC order and customer numbers that support, finance or Salesforce CRM rely on are kept for reference.
Passwords can’t move – Shopify can’t read SFCC’s password hashes – so returning customers sign in with an emailed one-time code through Shopify’s customer accounts; the older password-based accounts are no longer offered to new stores. Stored payment details, active subscriptions and data held in third-party cartridges – loyalty points, wishlists – are investigated in discovery, never assumed.
Moving data is the easy part. These five problems decide whether an SFCC migration lands on time, so we scope each one before quoting – not halfway through the build.
How we solve it
SFRA and SiteGenesis stores keep pricing rules, checkout steps, integrations and order handling in custom cartridges, hooks and controllers, often layered over years by different teams. We audit the code itself, not just the storefront: every cartridge on the cartridge path, every hook and every scheduled job. Each behavior is then rebuilt as a Shopify Function, a checkout UI extension or a custom app, replaced by an existing app, or retired – and you approve that list before anything is built.
How we solve it
One SFCC realm can run many sites – countries, brands, outlet stores – from a shared master catalog. On Shopify, most regions become Markets inside one store, each with its own currency, language, domain or subfolder and pricing; regions that need separate inventory, operations or checkout rules become expansion stores (Plus includes 9, more cost extra), and because Shopify sells Plus as one brand per contract, a separate brand needs its own Plus contract. We settle that structure with you before mapping any data, because it shapes catalogs, URLs and integrations.
How we solve it
SFCC master products can carry many variation attributes, and price books set list, sale and currency prices per site. Shopify allows up to 2,048 variants per product but only three options, and keeps one base price per variant that Markets and B2B catalogs adjust. We restructure products with more than three options, move descriptive attributes to metafields and translate each price book into market pricing, compare-at prices or B2B catalogs – with a map you approve before any data moves.
How we solve it
SFCC campaigns combine promotions, coupons, customer groups and source codes, and many checkouts carry custom steps in their controllers. On Shopify Plus you don’t own the checkout code: discount, shipping and payment rules are rebuilt as Shopify Functions, and added fields and content as checkout UI extensions. Source codes and customer-group pricing have no one-to-one equivalent, so each becomes a discount, a customer segment or a catalog – itemized at discovery, never discovered mid-build.
How we solve it
SFCC URLs carry locale prefixes, category paths and, on older builds, /on/demandware.store/ controller URLs that may still be indexed. Shopify uses fixed /products/, /collections/ and /pages/ paths, with Markets adding language or country subfolders. We export the full URL set for every site and locale, build a per-pattern 301 map, carry over titles, meta descriptions and canonicals, and rebuild hreflang for the new structure – automatic within Markets, added in the theme across expansion stores.
Leaving SFCC doesn’t mean leaving Salesforce. Many brands keep Salesforce CRM and Marketing Cloud and connect them to Shopify. We decide first which system owns customers, orders and inventory, then build the integrations around that decision.
| Salesforce product | After the move to Shopify Plus |
|---|---|
| Sales Cloud and Service Cloud | Stay. Shopify customers and orders sync to Salesforce through middleware or a custom app, so sales and service teams keep the full order history. |
| Marketing Cloud | Stays, fed with Shopify customer and order events – or moves to Klaviyo for Shopify if you were planning to replace it anyway. |
| Salesforce Order Management | Stays and receives Shopify orders through an integration, or gives way to Shopify’s order routing with your ERP or WMS. The choice depends on where your order logic lives today. |
| MuleSoft | Stays as your integration layer; MuleSoft publishes a Shopify connector. |
| Salesforce B2B Commerce | Can move to Shopify’s B2B: company accounts, catalogs, payment terms and quotes are on every paid plan since April 2, 2026, and Plus adds unlimited company-specific catalogs, deposits and custom Shopify Functions for B2B pricing and checkout rules. |
| B2C Commerce (SFCC) | Retired after cutover, once redirects and order flows are verified on Shopify Plus. |
Common paths, not a fixed plan. Salesforce, middleware and app licenses you keep are billed by their vendors and are not part of the migration price.
Every cartridge is replaced by an app, rebuilt as custom code or retired because Shopify covers it natively. These are the most common mappings, from payment, PIM, email and shipping connectors to custom code; your full list comes from the cartridge audit in discovery.
| On SFCC | On Shopify Plus |
|---|---|
| Payment cartridges (Adyen, Stripe, Authorize.Net) | Shopify Payments with Shop Pay, Apple Pay and Google Pay, plus PayPal, Klarna or Affirm; other gateways where they support Shopify |
| Tax cartridges such as Avalara | Shopify Tax, or Avalara’s Shopify integration |
| Shipping and fulfillment (ShipStation, EasyPost, Flexport, 3PLs) | The providers’ Shopify integrations where they offer one, or Admin API middleware for custom 3PL feeds |
| Ratings and reviews (Bazaarvoice, PowerReviews, Yotpo) | The same vendors’ Shopify apps, or Okendo or Judge.me, with review history imported |
| Einstein search, Algolia or Bloomreach | Shopify Search & Discovery, or Algolia, Bloomreach or Klevu for Shopify |
| Einstein product recommendations | Shopify Search & Discovery recommendations, or Rebuy or Nosto |
| Email and SMS (Klaviyo, Iterable, Attentive) | The same vendors’ Shopify integrations, with lists, flows and events reconnected |
| Page Designer pages and content slots | Theme sections and blocks, with metaobjects for structured content |
| Custom objects | Metaobjects, or data held in a custom app |
| Scheduled jobs and import/export feeds | Shopify Flow, middleware schedules and Admin API bulk operations |
| ERP connectors (SAP, NetSuite, Dynamics) | MuleSoft, Celigo, Boomi or custom Admin API middleware |
| PIM (Akeneo, Salsify) | The PIM’s Shopify connector, or a custom sync into products and metafields |
| HubSpot or another non-Salesforce CRM | HubSpot’s Shopify integration, or a sync through middleware |
| Custom cartridges, hooks and controllers | Shopify Functions, checkout UI extensions and custom apps, itemized at discovery |
| Composable Storefront (PWA Kit) or Storefront Next | A Shopify theme, or Hydrogen if headless still pays for itself – see headless commerce |
Common mappings, not a fixed list. Apps and Shopify features as of October 2026; app subscriptions are billed by their vendors and are not part of the migration price. Using a payment gateway other than Shopify Payments adds a Shopify transaction fee, currently reported as 0.20%, on top of your processor’s fees.
Want this mapped for your store? The free assessment gives you an app and integration map, 2–3 risk flags and timeline and cost bands within 2 business days – no store access needed.
Before step 1, the free assessment gives you timeline and cost bands, and a deeper review with read-only access under NDA fixes the price and timeline in writing. Then seven steps, each with an output you can check before the next one starts. Your team’s time goes mainly into approving the maps, reviewing the build and signing off QA and the launch rehearsal.
Inventory sites, locales, catalogs, price books, cartridges, hooks, jobs, integrations and URLs – from Business Manager and the code.
Decide where everything goes: store and Markets structure, product and price-book map, cartridge map, integration plan and 301 map.
Theme, apps, Shopify Functions, checkout extensions and Salesforce integrations, in a separate development store.
Import a representative sample from SFCC exports, compare counts, totals, keys and links, then fix and repeat.
Test functionality, checkout, integrations, SEO and performance, take your team’s acceptance sign-off, then run the cutover end to end, including redirects, payments and order flow into Salesforce and your ERP.
Freeze changes, import the final delta of orders and customers, switch domains site by site and verify checkout.
Watch orders, integrations, rankings and Core Web Vitals, tune speed and conversion, then hand over to your team or to an OUXP retainer and maintenance plan.
Our engineers have worked on Magento, Adobe Commerce and Shopify Plus, so the audit starts in the code – cartridges, hooks and jobs – not in the storefront.
15+ years · 300+ projects delivered
Store structure, cartridge rebuilds and Salesforce integrations are scoped before we quote, so undocumented hooks and forgotten scheduled jobs are in the price, not found mid-build.
Fixed before work starts
If staying on SFCC, or waiting for your next renewal, makes more sense, the free assessment says so in writing – yours to keep or share with another agency.
Written assessment in 2 business days
AI tooling shortens the slow, repetitive parts of a migration, so engineer hours go to the decisions your cartridges and integrations need. A senior engineer reviews every AI-assisted change before it reaches your store.
Used for data mapping, test suites, code review and QA
Every migration prioritizes Core Web Vitals, page speed, technical SEO and conversion – tested in QA before launch, then watched and tuned after it.
Core Web Vitals checked before and after launch
Retainers from $2,500 a month cover fixes and ongoing Shopify Plus development – or a dedicated engineer – month to month with 30 days’ notice, plus an optional 24/7 emergency add-on.
First response within 30–60 minutes in business hours
What carries over to an SFCC move: wholesale pricing and two currencies run from one Shopify store, and the most complicated work delivered on a large Shopify Plus store.
Thousands of SKUs, wholesale pricing and CAD/USD selling in one storefront
A multi-brand supplier selling to contractors and municipalities in Canada and the US needed wholesale account pricing and two currencies without slowing a deep catalog.
“We are large shopify plus store and Sean managed to deliver our most complicated tasks.”
Reviews sometimes name our engineers – everyone named is part of the OUXP team.
Something else on your mind? Ask an engineer – first response within 30–60 minutes in business hours.
10–24+ weeks, which makes SFCC our longest migrations. Single-site stores with a catalog that fits Shopify’s product model sit near the lower end. Multi-site realms, heavy cartridge logic, order flows through Salesforce Order Management or an ERP, and a Composable Storefront or Storefront Next front end push projects to 24 weeks or more. The free migration assessment places your store in that range, and a fixed timeline with milestones is agreed before work starts.
Most SFCC migrations cost $80,000–$250,000+. The number of sites and markets, custom cartridge logic, the Salesforce clouds that stay connected and design scope move the price more than catalog size. The free assessment gives you a cost band without store access; the fixed price follows a deeper review with read-only access under NDA and is agreed in writing before work starts. SEO preservation is always included.
Yes – leaving SFCC doesn’t mean leaving Salesforce. Sales Cloud, Service Cloud and Marketing Cloud can keep receiving customers, orders and events from Shopify through middleware such as MuleSoft or a custom app on Shopify’s Admin API. We decide first which system owns customers, orders and inventory, then build the sync, so service agents and marketers keep the data they rely on.
Each one is assessed in discovery from the code, not just the storefront. Most become Shopify Functions for discount, shipping and payment rules, checkout UI extensions or custom apps; others are replaced by an existing Shopify app; some are retired because Shopify covers them natively or you no longer need them. You approve the list before the build starts, so the rebuild is part of the fixed price.
Usually not. Shopify Markets runs several countries, currencies, languages and domains or subfolders from one store, with market-specific pricing. Regions that need their own inventory, operations or checkout rules can become expansion stores – Shopify Plus includes 9, and more cost extra. Shopify sells Plus as one brand per contract, so a separate brand needs its own Plus contract. We recommend a structure in discovery, because it shapes catalogs, URLs and integrations.
No. Planning can start any time; start the migration 6–9 months before your renewal date – that window holds the assessment, the fixed quote, the build and a launch away from peak trading. SFCC migrations take 10–24+ weeks, so starting then lets you cut over before renewal instead of paying for both platforms. The free assessment tells you whether an exit before renewal is realistic for your scope, or whether one more term on SFCC makes more sense.
Not when the move is planned for it, though no supplier can promise rankings stay exactly the same. We build a per-pattern 301 map covering every site and locale, including legacy demandware.store URLs, carry over titles, meta descriptions and canonicals, rebuild structured data and hreflang for the new market structure, submit the new XML sitemaps in Google Search Console for every domain, and monitor rankings and crawl errors after launch. SEO preservation is part of every migration.
Yes. Like SFCC, Shopify runs hosting, scaling and checkout for you, so moving adds no capacity work on your side – Black Friday included. What deserves testing is the part you own: theme performance, apps, and the integrations that fire on every order, such as the sync into Salesforce and your ERP. We test those before launch and watch them through your first peak.
Send your store URL and tell us about your sites and Salesforce stack. Within 2 business days an engineer sends a free written assessment: platform verdict, timeline band, cost band and the risks specific to your store – yours to keep whether or not you hire us.