Salesforce Commerce Cloud to Shopify Migration

Three to six months for most enterprise stores: three to four weeks for the data map and the fit verdict, two to four months for the build, the imports and the integrations, and a cutover window at the end. Several brands or locales, a large cartridge estate or a heavy ERP integration run longer, and the data map says how long before you commit.

Not if the redirects are done properly, and that is most of the work. Every old URL, including category pages, filtered listings and content pages across every locale, is mapped to its Shopify address and imported as a 301 redirect; Shopify allows 100,000 redirects on a standard plan and 20,000,000 on Plus. Structured data is checked on the new templates and rankings are watched for weeks after cutover. Our failed migration recovery page describes what happens when this step is skipped.

No. Shopify cannot import passwords from another platform, so each customer is invited to set a new one. We time the invitations for launch, write them in your voice and keep the old store reachable for support during the switch.

Yes, through the Admin API rather than the CSV import, which takes customers but not their orders. Orders are created as imported orders, so no confirmation emails go out and no stock moves. Customers see their past orders in their new account.

Each cartridge on the path is decided before the build: kept as an app from the App Store, rebuilt as a Shopify Function or a custom app, replaced by a theme setting, or dropped. Custom apps that use Function APIs need a Shopify Plus plan, which for a store of this size is the plan in question anyway.

For a store coming off Salesforce Commerce Cloud, almost always. Custom apps with Function APIs, the largest redirect counts and the deepest checkout customisation are Plus features. B2B is available on Basic, Grow, Advanced and Plus, and public apps with Functions run on any plan. The fit verdict names the plan the store actually needs. We do not quote Shopify's prices here because they change.

Rebuilt rather than copied. Campaigns and promotion rules are mapped one by one to Shopify discounts, and the ones Shopify's discount types cannot express are written as Shopify Functions. Scripts were deprecated on 30 June 2026 and checkout.liquid is unsupported for the checkout steps, so Functions and checkout extensions are the only route, and the data map lists every rule before the build starts.

A Shopify product holds up to 2,048 variants. Base products become products and variation products become variants; variation groups, product sets and bundles are remodelled in the data map, since Shopify has no direct equivalent for each. If the catalog cannot be made to fit without losing sales, that is a reason to stay, and we say so.

Individually, after the data map, which is the first deliverable and the one that tells us the size of the catalog, the number of cartridges to rebuild, the brands and locales in play and the integrations behind the store. Nothing on this site carries a price list because no two estates arrive in the same state.

No. The Salesforce Commerce Cloud store keeps trading until the Shopify store has passed every test, and the switch is a DNS change in a quiet window with the old store kept warm for rollback. Orders placed in the gap are reconciled by hand.

Estates that need one platform behind dozens of brand sites, stores whose order management is deeply custom, and B2B businesses that live on contract pricing, approval chains and quoting. Shopify's B2B features and Markets have narrowed those gaps, not closed them. For those stores the migration hub sets out the other destinations, and staying is one of them.

Each is re-pointed to Shopify's Admin and Storefront APIs, through an App Store integration where one exists and through a custom app where it does not. ERP, order management, PIM, email and reviews are mapped in the data map, and analytics is set up before launch so the first week's numbers compare with the last week on the old platform.

Yes. Shopify's Hydrogen framework on Oxygen hosting, with the Storefront API and the Customer Account API behind it, is the route for a store that came from a PWA Kit storefront. Shopify's own guidance is that a headless storefront costs more to build and run than a theme, so the fit verdict says whether it pays for your store.

Shopify Markets lets one store set currency, language, pricing, domains, product availability and taxes per market, which covers most country setups. Several brands usually mean several Shopify stores sharing apps and integrations. The data map lays out which it is for your estate before the build.