Salesforce Commerce Cloud → to Shopify

Salesforce Commerce Cloud to Shopify Plus: the enterprise replatform, done in phases

Salesforce Commerce Cloud, the platform many teams still call Demandware, runs some of the largest stores on the web, and the brands leaving it are not leaving because it cannot scale. They are leaving because of what it costs to run, how long changes take, and how much of the revenue share goes to the platform. This guide is how we move SFCC B2C sites to Shopify Plus: what comes out of Business Manager, how the integrations are rebuilt, and how the cutover is sequenced so trading never stops.

Why enterprise brands leave SFCC

• Total cost. Revenue-share licensing plus a system integrator on retainer plus a large internal team. Shopify Plus removes the first, shrinks the second and lets the third focus on selling.
• Speed of change. Cartridge development, code deployments and release windows mean a promotion change takes weeks. On Shopify it is a settings change.
• Front-end debt. SiteGenesis and SFRA storefronts accumulate years of customization. Rebuilding on Shopify’s theme architecture or Hydrogen resets that.
• Checkout. Shop Pay, checkout extensibility and Shopify’s conversion data are the strongest argument, and the one that shows up in the P and L first.

What comes out of Business Manager

Data	SFCC source	Shopify destination
Catalog: products, master and variation products, attributes, images, categories	Catalog export (XML) or OCAPI / SCAPI	Products, variants, options, metafields for attributes, collections for categories. Variation groups map to Shopify options within the three-option limit; larger structures are restructured in discovery.
Price books and promotions	Price book export, campaign and promotion definitions	Prices per Market, B2B price lists, and Shopify Functions or native discounts for promotions. Complex promotion logic is redesigned, not copied.
Inventory lists	Inventory export	Shopify locations. Multi-inventory-list setups map to locations and Markets.
Customers, addresses, customer groups	Customer export (XML)	Customers with tags or B2B companies. Passwords do not move; passwordless accounts are the standard answer.
Orders	Order export (XML) or OMS	Real orders with original numbers and transactions. Depth of history is a scope decision.
Content: Page Designer pages, content assets, slots	Library export	Rebuilt as theme sections and metaobjects.
Sites, locales, currencies	Site configuration	Shopify Markets, with Expansion Stores on Plus where a region needs its own catalog.
URLs	URL rules, aliases, Search Console	Redirect map covering the product and category URL rules, the legacy /s/SiteID/ and .html forms, and every alias.

The integrations

SFCC sites are rarely standalone. The work is in reconnecting the surrounding systems.

System	Typical approach on Shopify Plus
ERP (SAP, Oracle, NetSuite, Dynamics)	Shopify’s connectors where they exist, otherwise an iPaaS such as Celigo, Boomi or MuleSoft, which many SFCC customers already run.
OMS	Shopify Order Management or the existing OMS connected by API.
PIM	Direct connectors exist for Akeneo, Salsify and others.
Marketing Cloud, Service Cloud	Both connect to Shopify natively.
Tax, fraud, payments	Avalara or Vertex, Shopify’s fraud tooling or Signifyd, Shopify Payments plus regional gateways.
Search and personalization	Shopify search and discovery, or Algolia and similar where the site depends on them.

How we run it

1. Discovery. Sites, locales, catalogs, price books, promotions, integrations, custom cartridges, order volume and the URL inventory. A phased plan with a fixed price per phase.
2. Integration first. ERP, OMS and payment flows are built and tested against a Shopify development store before storefront design starts, because they are the schedule risk.
3. Storefront build on Shopify Plus: theme or Hydrogen, checkout extensibility, Markets, B2B where needed.
4. Data load of catalog, prices, inventory, customers and order history, reconciled against Business Manager counts.
5. Promotion redesign into Functions and native discounts, tested against last year’s campaign calendar.
6. Parallel run and UAT with finance and operations signing off on order, fulfillment and payment postings.
7. Redirects tested individually against the live domain.
8. Cutover by site or region where there are several, with hypercare for 30 days after each.

Timeline and cost

SFCC to Shopify Plus programs run 16 to 30 weeks depending on the number of sites and integrations. Storefront and migration work is quoted as a fixed price per phase after discovery, typically from $75,000 for a single-site B2C store to several hundred thousand for multi-site, multi-region programs with ERP and OMS integration; integration platform licensing is additional. Payment terms are 50 percent per phase to begin and 50 percent once that phase is live and you are fully satisfied with the figures.

SFCC catalog structure and where it lands

SFCC concept	Shopify equivalent	Notes
Master product with variation attributes and variants	Product with options and variants	Variation attributes become options. Masters with more than three attributes are restructured, usually by promoting one attribute to a separate product.
Variation groups	Products sharing a metafield, or combined listings on Plus	Combined listings reproduce the color-family page pattern.
Product sets and bundles	Shopify Bundles, or collections for shop-the-look sets	Bundles decrement component stock natively.
Product options (monogramming, gift wrap)	Line item properties or add-on products	Priced options become add-on products so they appear on the order correctly.
Shared master catalog and site catalogs	One catalog with publishing per Market	Site-specific assortments become market availability rules.
Category assignments and sorting rules	Collections with manual or automated membership and sort order	Dynamic category rules become automated collection conditions.
Image groups by view type	Product media with alt text, and variant images	Swatch images become variant images.
Custom attributes on products, customers and orders	Metafields with definitions	Every attribute in use is inventoried in discovery; unused ones are dropped.
Inventory lists per site	Locations and market inventory	Available-to-promise from the OMS is what flows to Shopify.

Content, Page Designer and the storefront

SFCC content lives in libraries as content assets, slots and, on newer sites, Page Designer pages and components. Shopify’s equivalent is theme sections and blocks for layout, metaobjects for structured content such as stores, lookbooks and designer bios, and pages and blogs for editorial. We inventory every content asset, retire the ones nobody has touched in two years, and rebuild the rest as sections or metaobject entries that the marketing team can edit without a release. For brands that want a fully custom front end, Hydrogen on Oxygen gives a React storefront with Shopify’s checkout, which is the closest analogue to a headless SFCC build. Most brands do not need it and a well-built theme is faster to launch and cheaper to run.

Common mistakes in SFCC replatforms

• Trying to reproduce every promotion rule. Most of them exist because someone built them once; the campaign calendar tells you which ones matter.
• Building the storefront before the ERP and OMS flows are proven, and finding the integration is the critical path with three weeks to launch.
• Migrating the full order history into Shopify. The OMS or data warehouse already has it; customers need the last year or two.
• Underestimating redirects. Large SFCC sites have hundreds of thousands of indexed URLs across locales, aliases and legacy forms, and the map has to be generated from data, not written by hand.
• Choosing headless by default. Hydrogen is excellent when it is needed and expensive when it is not.

Promotions and campaigns, translated

SFCC promotion type	Shopify equivalent
Percentage or amount off products, with qualifying product groups	Automatic or code discounts with collection conditions
Buy X get Y, bonus products	Buy X get Y discounts; free gift with purchase through a Cart Transform function where the gift must be added automatically
Tiered spend thresholds	Discount tiers by minimum purchase, or a Functions discount for complex ladders
Free or discounted shipping by basket or destination	Shipping discounts and shipping profile rules per market
Source-code and customer-group promotions	Segment-eligible discounts, B2B catalog pricing, UTM-triggered discounts through Flow
Coupons with usage limits and redemption codes	Discount codes with usage limits; bulk codes for one-per-customer campaigns
Campaigns with schedules and stacking rules	Scheduled discounts with combination settings; Launchpad on Plus for timed site-wide events

We rebuild the promotions that ran in the last twelve months, test each against the orders it produced, and retire the rest.

Customers, groups and B2B

SFCC customer groups drive pricing, promotion eligibility and content targeting. On Shopify, consumer groups become customer segments, which can be used for discount eligibility and marketing, and trade groups become B2B companies with catalogs, price lists and payment terms on Plus. Customer profiles export with addresses, preferences and custom attributes; the custom attributes become metafields so segmentation continues to work. Passwords do not move, and for a brand with a large account base the switch to passwordless customer accounts is worth making part of the launch communication rather than a surprise.

Timeline by phase

Phase	Weeks	Output
Discovery and architecture	1 to 4	Integration map, catalog restructure plan, promotion inventory, URL inventory, phased fixed-price proposal
Integration build and sandbox test	3 to 12	ERP, OMS, PIM, tax and payment flows proven on a development store
Storefront build	6 to 16	Theme or Hydrogen, checkout, Markets, B2B, content rebuilt
Data load and reconciliation	10 to 18	Catalog, prices, inventory, customers, recent orders reconciled to Business Manager
Parallel run, UAT, redirects	14 to 22	Finance and operations sign-off, every redirect tested
Cutover and hypercare	18 to 30	Region-by-region launch with 30 days of support each

What you get at handover

Each phase closes with its own package: the integration design and sandbox test logs for the ERP, OMS and payment flows; the catalog restructure map showing how every master, variation group and product set was translated; the promotion inventory with each rule’s fate; the reconciliation ledger against Business Manager counts; the redirect verification list, which on an SFCC site is usually the largest document in the set; and a recorded walkthrough of the Shopify admin for merchandising, marketing and operations teams separately, because each uses different parts of it. The hypercare log with every issue and its resolution is handed over at the end of each region’s 30 days.

Questions we settle in the survey

• Number of sites, locales and currencies, and whether each needs its own catalog or fulfillment.
• The systems around SFCC: ERP, OMS, PIM, tax, fraud, search, personalization, and who owns each integration.
• Whether the storefront is SiteGenesis, SFRA or headless, and how much custom cartridge code exists.
• The promotions that ran in the last year and which are contractual.
• Order volume and peak traffic, which shape the checkout and integration design.
• Whether the brand has an internal ecommerce engineering team that will own the Shopify build afterwards.

These answers set the phase boundaries and the fixed price for each, and they usually surface one or two integrations nobody had listed, which is the point of asking before the proposal rather than after. Where the answers are not known, discovery starts by finding them, with your system integrator in the room if you have one.

Frequently asked questions

Start with the migration survey and list your sites, locales and integrations. The Shopify Plus migration page covers the enterprise process, and the Adobe Commerce guide covers a comparable replatform.