Build & Migrate
Salesforce Commerce Cloud to Shopify Migration
Enterprise scale, without the licence.
(opens in a new tab) Salesforce Commerce Cloud carries enterprise scale and an enterprise licensing bill to match, usually a percentage of GMV before a line of custom cartridge code is written. We move that scale onto Shopify Plus: every product, customer and order carried across, every custom cartridge mapped to a native Plus feature or rebuilt properly, and every ranking URL redirected before launch.
The brands we build, and the two we run ourselves.
Certified, not badge-only Most of an SFCC migration is deciding what not to carry across.
The two platforms comparedAnyone can export products. What decides whether the store works afterwards is what you do with the cartridges nobody has opened in four years, and the URLs that earned your rankings.
All migrationsSalesforce to Shopify migration
How we migrate a Salesforce Commerce Cloud store to Shopify
The crawl and the cartridge audit happen before anything moves. That ordering is the whole difference between a migration that protects what the store earned and one that finds the damage afterwards.
-
Audit and Crawl
We map the current Salesforce Commerce Cloud install in full: every cartridge, the personalisation logic, and every indexed URL. The crawl is the part most enterprise migrations skip, and it is the part that protects your rankings.
-
Migration Plan and Redirect Map
A written plan with the catalogue mapping, the cartridge-to-Plus mapping and the full redirect map, signed off before anything moves. Disagreements are cheap at this stage and expensive after launch.
-
Build and Migrate on Staging
Data migrated, the Shopify Plus store built, integrations connected and redirects implemented, all on staging first. You click through the real store with your real catalogue before anyone commits to a date.
-
Launch and Monitor
Pre-launch QA across real devices, managed go-live, then monitoring of rankings, redirect hits and errors through the weeks that follow, with a named person to call.
Salesforce Commerce Cloud migration
Why enterprise brands move off Salesforce Commerce Cloud
Salesforce Commerce Cloud carries enterprise scale and an enterprise licensing bill: usually a percentage of GMV, before a line of custom cartridge code is written. Shopify Plus carries the same scale, the same B2B capability and the same personalisation depth, without the licence structure or the developer overhead SFCC demands for routine changes.
We move UK and US enterprise brands off Salesforce Commerce Cloud onto Shopify Plus, mapping every custom cartridge to a native answer before anything moves and rebuilding what is genuinely bespoke rather than porting complexity you were only maintaining. Company accounts and negotiated pricing move onto Plus B2B natively.
Migrating suits a Salesforce store where the licensing cost and the cartridge maintenance burden have outgrown what the platform is actually delivering. If your current SFCC build is stable, well resourced and converting, moving for cost alone still needs the numbers run properly, which is the first thing we do.
- Custom SFCC cartridges mapped to native Shopify Plus features or rebuilt where genuinely bespoke
- Zero data loss: products, customers, order history and content all transferred
- Every old URL, including SFCC's own structure, redirected to its Shopify equivalent before launch
- The current store keeps trading throughout, with no maintenance-mode window
Salesforce Commerce Cloud features
What a Salesforce to Shopify Plus migration includes
Not a feature grid. Three questions: what happens to the custom code, what the catalogue becomes, and how the store keeps what it has already earned.
What the custom code becomes
Cartridge and Custom Code Audit
A Salesforce Commerce Cloud store usually carries custom cartridges built for logic that had no platform answer at the time. We audit each one, map it to a native Shopify Plus feature where one now exists, and rebuild what is genuinely bespoke rather than porting complexity you were only maintaining.
Integrations and Custom Functionality
ERP, OMS, PIM and payment integrations reconnected and tested against real orders before go-live. Where bespoke Salesforce functionality is genuinely load-bearing, our developers rebuild it natively on Plus. Where a native feature now does the job better, we say so instead of billing to recreate it.
What the catalogue becomes
Enterprise Catalogue and Personalisation
SFCC catalogues carry structures built for scale: large SKU counts, complex pricing rules and personalisation logic. We map that onto Shopify Plus's native catalogue, Functions and Markets, and flag anywhere the mapping genuinely changes behaviour before it happens rather than after.
B2B and Company Accounts
Where a Salesforce store runs B2B storefronts, company accounts or negotiated pricing, we move that onto Shopify Plus's native B2B rather than an app stack trying to replicate what SFCC did as standard.
What you have already earned
SEO Preservation
Salesforce Commerce Cloud's URL structure and its OCAPI-driven pages rarely match Shopify's, so the redirect map is what protects rankings that took years and a real budget to earn. Every indexed URL is crawled, mapped and given a 301 before launch, with a before-and-after crawl comparison so nothing is lost quietly.
Launch and the Weeks After
Managed go-live with the team on hand, then close monitoring of rankings, redirects and error logs through the period where migration problems actually surface. A migration of this scale is not finished on launch day, and pricing it as though it is helps nobody.
Decide
Before anything moves, the honest question is whether it should. Most of the money in a migration of this size is lost or saved here.
Salesforce Commerce Cloud migration
The licence is rarely the number that decides it
A percentage of GMV is the figure that starts the conversation and almost never the one that settles it. The cost that compounds is the developer time between wanting a change and having it: a cartridge to touch, a release to schedule, a window to wait for.
So we cost both sides against your own store, and count the routine changes your team would make themselves on Plus. If staying is the better commercial call for the next two years, we will say so, and you will have the numbers either way.
What changes, line by line
What you are actually comparing
Both platforms are built for scale, and on capability the gap is narrower than the licensing gap suggests. Only the first line below is about price. The rest are about who can make a change, and how long it takes.
| Capability | Salesforce Commerce Cloud | Shopify Plus |
|---|---|---|
| Licence | Usually a percentage of GMV | A platform fee, plus payment processing |
| Custom logic | Cartridges, written and maintained by developers | Native features and Functions first, bespoke code where it is earned |
| A routine change | A developer ticket, most of the time | Usually your own team, in the admin |
| Upgrades | Scheduled, and a project every time | Continuous, and not your project |
| B2B | Native: storefronts, company accounts, negotiated pricing | Native on Plus: company accounts, price lists, payment terms |
| Multi-region selling | Sites and locales configured per region | Markets: per-market pricing, domains and catalogues |
| Checkout | Yours to extend and yours to maintain | Built in, and extendable on Plus |
Migrate
The mapping, the rebuild and the redirects. Everything that decides whether the store you land on is better than the one you left.
B2B and company accounts
Trade buyers keep their prices, their terms and their logins
Where a Salesforce store runs B2B storefronts, company accounts and negotiated pricing, that is the part the business cannot afford to get wrong. It moves onto Shopify Plus native B2B: companies, locations, per-buyer price lists and payment terms, rather than an app stack reproducing what SFCC did as standard.
Trade and retail catalogues are separated properly, and every account is checked against its real price list on staging before anyone commits to a date.
Salesforce to Shopify migration
Rankings survive the move, or the move was not worth making
Salesforce Commerce Cloud URL structures and its OCAPI-driven pages rarely match Shopify’s fixed product and collection paths, so the redirect map is the single biggest factor in whether a migration protects your rankings or quietly costs them. A store that has ranked for years has the most to lose on the day it moves.
Every indexed URL is crawled, mapped and given a 301 before launch, then compared crawl to crawl afterwards, so a page that went missing is found by us rather than by your traffic graph six weeks later.
Before you commit
What usually goes wrong
Five failures account for most of the damage an enterprise migration does, and none of them is exotic. Each is cheap to prevent and expensive to find afterwards, which is why the audit comes first.
The cartridge list is taken from the documentation
Documentation records what was planned. A running SFCC install carries cartridges that were patched, forked or left switched on years after the reason for them went away. The inventory has to come from the instance, not the wiki describing it.
The redirect map is built from the sitemap
A sitemap says what you want indexed, not what Google actually has. We crawl the live store and pull Search Console’s own list beside it, because the pages earning the most are often the ones nobody remembers building.
Personalisation is treated as content
Years of segment rules encode commercial decisions nobody has revisited. Migrating them intact is the fastest route, and it hands the new store rules written for a catalogue you no longer sell.
The password reset lands as a surprise
Passwords cannot move between platforms, for security reasons, so every customer is invited to set a new one. Timed and worded with you, it reads as part of the launch. Sent cold, it reads as a phishing email.
Salesforce is switched off too early
It usually holds the only copy of something nobody thought to export, and on an enterprise contract the instinct to stop paying for it is strong. Keep it readable for a while after cutover.
The problems that matter rarely appear on launch day. They appear when Google recrawls, and when a trade account places its first order against a price list that moved across in a different shape. So the same developers stay on it.
Support after launchHow we work with you
Audit first, decide after
A crawl, a cartridge inventory and a catalogue mapping, priced on its own. You end up with a written migration plan and a redirect map you own, whoever eventually does the work.
Fixed feeFixed-scope migration
The plan signed off, then the build, the data, the integrations and the redirects to an agreed scope and date. The people who quoted it are the people on it.
ProjectMigration, then a retainer
Launch is where a migration starts being judged. The same developers stay on for monitoring, the fixes that surface in the first weeks, and the next round of work.
MonthlyReviews on the Shopify Partner Directory
Merchants, in their own words.
-
From start to finish, they were incredibly easy to work with. They understood the brief perfectly and delivered to a very high standard. Communication was excellent throughout, with quick and clear responses to any questions I had.
Tacky And Upsetting Store build or redesign · April 2026
-
The things [the team] have put in place and recommended for us have paid immediate dividend. We wish we had come in contact with [them] sooner.
ARTMARTIAL Store build or redesign · April 2026
-
I can’t recommend [the team] enough, [they] helped us with everything from product design, supplier communication to website building and SEO. We were able to build a brand off the back of all [their] information and help.
Reveliér Studios Business strategy guidance · April 2026
Keep reading
Everything around a migration
Other platforms
What comes with it
Read before you decide
Partners
Tools we have already run on our own stores.
The apps around a Shopify store decide as much as the theme does, and choosing between thousands of them is most of the work. We are a Shopify Plus Partner and we integrate the tools that sit around the platform. Every one of them runs on our own two stores before it reaches a client, so the recommendation you get comes from having paid for the thing and lived with it. When a brand already runs a stack that works, we integrate with it rather than rebuilding it to suit us.
How we use them
Straight answers
Will we lose our Google rankings when we migrate from Salesforce Commerce Cloud?
Not if the redirects are handled properly. We map every indexed URL, including SFCC's own structure and any OCAPI-driven pages, to its new equivalent before launch and verify them on the live domain afterwards.
Do we need Shopify Plus, or does standard Shopify cover this?
Almost always Plus. Salesforce Commerce Cloud is built for enterprise scale, and the features that scale actually needs, B2B, Functions, Markets and checkout extensibility, sit on Plus rather than standard Shopify.
What happens to our custom SFCC cartridges?
Each one is audited individually. Where a native Shopify Plus feature or Function now does the job, we move to it. Where the functionality is genuinely bespoke, our developers rebuild it natively.
Can you migrate a B2B storefront with negotiated pricing?
Yes. Company accounts, price lists and payment terms move onto Shopify Plus's native B2B, rather than an app stack trying to replicate what Salesforce did as standard.
How much downtime does the migration cause?
None your customers will see. We build and test on a separate Shopify Plus store, then switch the domain once everything passes.
Do you migrate US Salesforce Commerce Cloud stores from the UK?
Yes. We run migrations for US brands out of London, and the time difference helps: work done here overnight lands before your team starts the day.
Is this the right thing to buy from us?
Worth a conversation
- The licence is a percentage of GMV and the store has outgrown what it buys
- Routine merchandising changes need a developer and a release window
- Cartridges are maintained by people who did not write them
- B2B and retail are fighting each other inside one install
Probably not this, yet
- SFCC is stable, well resourced and not in your way
- Your contract has years left and no break clause worth using
- You want a redesign rather than a replatform
- You need someone to keep Salesforce running, which we do not sell
Tell us what the store needs to do
Send the store URL and what is in the way. We reply personally, and if the honest answer is that you do not need this yet, that is the reply you get.
Stores we build and grow
Migrate Salesforce to Shopify Plus
Talk to the people who would do the migration.
Send us the store. We will come back with what the cartridge audit looks like, what the redirect map involves, and whether moving is the right call at all.
UK and US brands buy this from the same senior team, and the American day is covered from the start of it rather than the end. How we work with US brands.
Get in touch