Salesforce Commerce Cloud to Shopify Plus, Cartridge by Cartridge

Start with an inventory of every cartridge, scheduled job and promotion so you know what the store does today. Then export catalogs, price books, customers and orders from Business Manager or through OCAPI, rebuild the SFRA or SiteGenesis storefront as a Shopify theme, rewire integrations such as your ERP, and load a single-hop 301 for every old URL. SFCC stays live until the Shopify store passes test orders.

Yes. Salesforce acquired Demandware and renamed it Salesforce Commerce Cloud, and Salesforce's developer documentation now calls the platform B2C Commerce. The old name still shows up in URLs such as /on/demandware.store/ and in file and cartridge names. A Demandware to Shopify Plus migration and an SFCC to Shopify Plus migration are the same project.

SFCC fits large estates with many brands, sites and locales, deep use of other Salesforce clouds, and an in-house team that knows cartridges. Shopify Plus fits teams that want a published fee, page changes without code deploys, and an app store. Salesforce lists B2C Commerce Premium as contact for pricing with 100 sites and 3,500 price books; Shopify Plus lists $2,300 a month on a 3-year term.

It depends on what unified means for you. On SFCC the checkout is code you own and maintain in cartridges, which gives control but needs SFCC developers for every change. On Shopify Plus, checkout is changed through checkout extensions and Shopify Functions, and Shopify B2B runs inside the same store, so wholesale and consumer buyers share one checkout and one admin.

Shopify's Plus pricing page states 10K+ checkouts per minute with unlimited bandwidth, transactions and SKUs. That covers the platform. What we load-test before launch are the parts you add: apps calling outside services, custom Shopify Functions, and the ERP or order management link that has to absorb a burst of orders. Those tests run on a development store weeks before launch.

The shape is the same: export catalog, price lists, customers and orders, rebuild the storefront as a Shopify theme, reconnect integrations, and map every old URL to a single-hop 301. The export tools and URL formats differ, so we read them from your live sitemap and your admin exports during the audit, and quote after we have seen them.

It depends on how many sites and locales you run, the number of cartridges worth keeping, promotion complexity, and how many systems connect to the store. FactoryJet quotes a fixed price in writing after a short scoping call, priced per phase. You see a working demo on your own SFCC catalog before you sign, and support after launch is optional with no monthly minimum.

Shopify Plus lists $2,300 a month on a 3-year term, from $2,500 a month on a 1-year term, or a variable platform fee for more complex businesses. Salesforce lists its B2C Commerce editions as contact for pricing, so compare against your own contract. Payment fees sit on top of both; on Shopify, third-party transaction fees may apply if you do not use Shopify Payments.

Cartridges and ISML templates do not run on Shopify. We list every cartridge in your cartridge path and mark each one keep, replace or retire. Storefront features are rebuilt as Shopify theme sections, checkout logic as checkout extensions or Shopify Functions, and back-office logic as apps or integration code. Cartridges that no longer do anything useful are retired instead of rebuilt.

It changes the audit, not the destination. Salesforce describes SFRA as JavaScript controllers in a model-view-controller pattern with Bootstrap, which makes custom code easier to trace. SiteGenesis is the older storefront and usually carries more custom code. PWA Kit, which Salesforce launched in 2021 as an alternative to SFRA, is headless, so a move to a headless Shopify build is worth pricing alongside a theme build.

Business Manager jobs such as product feeds, inventory imports and order exports to your ERP stop when SFCC is switched off. Each one needs a new home: Shopify Flow for simple rules, an app for standard feeds, or integration code for ERP and order management flows. We list every job with its schedule and owner during the cartridge audit, so none is missed.

Two routes. Business Manager import and export covers catalogs, price books, inventory lists, customers and orders as files. For scripted pulls and the final top-up we use the Open Commerce API, whose Data API gives read and write access to system resources. Every OCAPI request needs a client ID, and Salesforce notes that data can be exported from Production and Development instances.

List price books and sale price books become Shopify product prices and compare-at prices. Country or currency price books become Shopify Markets pricing, and customer-group price books become Shopify B2B catalogs. Salesforce lists B2C Commerce Premium with 3,500 price books, and large estates rarely need them all, so we map each one and merge duplicates before import.

Simple promotions become Shopify automatic discounts or discount codes. Rules SFCC handles with qualifiers, exclusivity or stacking order are rebuilt as Shopify Functions. Existing coupon codes are exported and reloaded so printed and emailed codes keep working. Every rebuilt promotion is tested against sample baskets with known totals before launch, so the discount a shopper gets matches what SFCC gave.

Each SFCC master product becomes a Shopify product, each variation product becomes a variant, and variation attributes such as size and color become Shopify options. Shopify allows up to 2,048 variants and up to three options per product. A master with a fourth variation attribute is split into several products or has the extra attribute moved to a metafield.

Customers, addresses and past orders can move; passwords cannot. Customer lists come out of SFCC and load into Shopify by CSV or API, and historical orders load through the Shopify Order API. SFCC stores passwords as one-way hashes, so each customer sets a new password from an account invite email, which we send in batches after launch.

SFCC subscriptions usually run through a third-party cartridge, so the contracts export from that provider. On Shopify, subscriptions are a purchase option: the Shopify Subscriptions app supports plans that renew weekly, monthly or yearly and can import and export subscription contracts, or you can use a third-party app. Saved cards move only through a transfer arranged with your payment providers, so we start that early.

Yes. Leaving SFCC does not mean leaving Salesforce. Sales Cloud, Service Cloud and Marketing Cloud can keep receiving Shopify customers and orders through connector apps or integration middleware. Which one fits depends on your Salesforce objects and custom fields, so we map the data your Salesforce org expects today and confirm the connection method before we quote.

No. Moving off B2C Commerce only replaces the storefront and checkout. Your CRM records, service cases and marketing journeys stay in Salesforce. What changes is where the order and customer events come from: Shopify instead of SFCC. Journeys that fire on SFCC events are reconnected to the matching Shopify events before launch.

Yes. Your ERP and order management stay as they are, and the integration that fed them from SFCC is rebuilt to read from Shopify Plus. Orders, stock by location, prices and fulfilments flow through the new link. We test it with real test orders in your ERP sandbox before cutover, because that link is where most launch problems start.

Rankings can move for a few weeks after any platform change. What protects them is a complete redirect map. We collect every URL from your SFCC sitemaps, Search Console and backlink data for each site and locale, map each to its Shopify page, and load them as single-hop 301s before DNS changes. Shopify Plus allows up to 20,000,000 redirects.

SFCC URLs depend on your URL rules. SEO URLs often end in .html with a product ID, headless storefronts may use /p/ and /c/ paths, and pages without URL rules show /on/demandware.store/Sites-SiteID-Site/ paths. Shopify fixes products at /products/handle and collections at /collections/handle, so every pattern gets its own mapping rule and every exception is listed.

Each SFCC site becomes either a Shopify Market inside one store or a separate expansion store, decided in the audit. Locale prefixes become Markets subfolders. Shopify notes that URL redirects do not apply to all market subfolders automatically, so each locale gets its own set of redirects rather than one shared set for the default language.

SFCC stays live and untouched until DNS moves. The Shopify store, catalog and integrations are tested with real test orders first. We freeze catalog changes on SFCC, pull the final orders and customers created since the test import, then move DNS in a quiet hour. If a launch check fails, DNS points back to SFCC while we fix it.