# Salesforce Commerce Cloud to Shopify, every cartridge accounted for.

> We plan and run moves from Salesforce Commerce Cloud (SFCC) to Shopify Plus. A fixed-fee Migration Blueprint comes first: it maps your cartridges, Business Manager data, Salesforce integrations and every URL, and prices the integration, data and SEO work in phases before anyone commits to a build.

Migrations to Shopify · Salesforce Commerce Cloud to Shopify

- **Starts with:** A fixed-fee Migration Blueprint
- **Typical build:** Phased, each phase priced before it starts
- **You own:** The code, the integration map and the documentation

## When should an SFCC brand move to Shopify?
- Small storefront changes wait for a specialist SFCC developer or an agency sprint.
- Licence and specialist costs weigh on every roadmap decision.
- Custom cartridges carry business logic nobody on the current team wrote.
- Merchandisers work around Business Manager rather than in it.
- You want wholesale and retail on the same platform, run by the same team.

## How does an SFCC to Shopify migration run?
1. **Audit cartridges and integrations** — Each cartridge, job and Salesforce integration, plus data quality and a rankings baseline.
2. **Map data and URLs** — Price books, promotions, content slots and every URL mapped to their Shopify equivalents.
3. **Build the storefront** — A theme or headless storefront; cartridge logic moved to apps and Functions.
4. **Rehearse the move** — Repeatable loads from SFCC exports, reconciled counts and redirects tested end to end.
5. **Cut over and watch** — A staged switch timed to your trading calendar, then orders and integrations watched.

## Your SFCC estate, mapped to Shopify
- A cartridge inventory, each with its Shopify replacement
- Price books and promotions mapped to Shopify pricing and discounts
- Content slots and assets moved to sections or Sanity
- Each Salesforce integration, specified against Shopify’s APIs
- Sites and locales mapped to Shopify Markets or stores
- Every URL mapped, with a tested redirect plan
- A customer activation plan, since passwords cannot move

## What usually goes wrong
- **Rebuilding every cartridge as a custom app** — Many already exist as Shopify apps or native features.
- **Copying Business Manager promotions rule for rule** — Shopify discounts work differently; redesign them, then test each.
- **Losing locale URLs in the redirect map** — Each site and locale path needs its own redirects.
- **Forgetting what Service and Marketing Cloud expect** — Each connection needs a contract against Shopify’s APIs before cutover.

## Questions
### Can Shopify Plus handle what our cartridges do today?

Cartridge logic usually lands in an existing Shopify app, a Shopify Function for cart and checkout rules, or a custom app for anything specific to your business. The Blueprint lists every cartridge and where it goes.

### Can we keep Salesforce Service Cloud or Marketing Cloud?

Yes, if they still earn their place. Shopify exposes orders, customers and products through its APIs and webhooks, so those connections are rebuilt against it. The Blueprint specifies each contract: what moves, how often and which system owns the record.

### Our SFCC storefront is headless. Should Shopify be headless too?

Not necessarily. Headless earns its cost when a theme cannot carry the experience. Then it is Hydrogen on Oxygen, or Next.js with Shopify’s Hydrogen library on Vercel when the storefront is one surface among several. The Blueprint recommends one, with reasons.

### What happens to our SEO when we leave SFCC?

We crawl the site before anything moves and record rankings for the pages that earn traffic. Every SFCC URL, including each site and locale path, gets a redirect to its Shopify equivalent. We crawl again after launch and fix what the crawl finds.

### How is an SFCC migration priced?

In phases, at fixed fees. The Blueprint is a fixed fee of its own. It ends with each build phase scoped and priced, so you see the cost of the move before you commit. Changes are quoted in writing, never billed by the hour.

[Request a Migration Blueprint](https://www.studioantipodes.com/start-a-project)