Migrating from Salesforce to Shopify Plus means replacing Salesforce Commerce Cloud as the ecommerce platform while deliberately rebuilding, reconnecting, retaining, or retiring the systems and business rules around it.
The migration does not automatically remove Salesforce CRM, Service Cloud, Marketing Cloud, or Data 360. Many companies keep those products and connect them to Shopify Plus through APIs, middleware, events, or controlled data pipelines.
In this article, we explain how to assess platform fit, audit Salesforce Commerce Cloud, map data and pricing, retain Salesforce integrations, manage legacy systems, protect SEO, and control cutover risk. The goal is not to copy SFCC into Shopify Plus. The goal is to preserve valuable business outcomes while removing unnecessary platform complexity.
What Does Migrating from Salesforce to Shopify Plus Mean?
A Salesforce to Shopify migration usually refers to moving the storefront, catalog experience, cart, checkout, customer accounts, promotions, and commerce administration from Salesforce Commerce Cloud to Shopify Plus. The project also needs to address data, integrations, search, content, analytics, SEO, and operational workflows.
The phrase can create confusion because Salesforce sells several products. A company may retire Salesforce Commerce Cloud while continuing to use Sales Cloud for accounts and opportunities, Service Cloud for cases, Marketing Cloud for campaigns, or Data 360 for customer data.
Commerce replacement
Shopify Plus replaces SFCC as the customer-facing commerce platform and administration layer.
Salesforce retention
The business keeps selected Salesforce products and reconnects the data flows that still create value.
Back-office continuity
ERP, PIM, OMS, WMS, payments, tax, search, loyalty, fraud, and reporting systems continue supporting operations.
Important distinction: A Shopify Plus Salesforce integration connects systems after the move. It does not replace the data mapping, capability redesign, SEO work, testing, and cutover planning required to retire Salesforce Commerce Cloud.
When Does Migrating from Salesforce to Shopify Plus Make Sense?
Migrating from Salesforce to Shopify Plus can make sense when SFCC requires too much specialized development, slows routine releases, depends on difficult customizations, or creates an operating cost that no longer matches the value it produces.
Shopify Plus may also fit teams that want simpler storefront administration, faster merchandising changes, a large application ecosystem, and a clearer path for standard B2B or hybrid B2B and B2C experiences. The decision still depends on the company’s hardest workflows, not on platform popularity.
| Business condition | Shopify Plus may fit when | SFCC may still fit when |
|---|---|---|
| Release management | The team wants faster theme, content, campaign, and storefront changes | The company relies on deep custom development and accepts the supporting operating model |
| Customization | The business can redesign requirements around Shopify extensions, Functions, apps, and APIs | The business depends on specialized logic that Shopify cannot support without unacceptable compromise |
| B2B commerce | Companies, locations, catalogs, quantity rules, and integrations cover the core buying model | The organization needs highly specialized account, pricing, procurement, or approval behavior |
| Internal skills | The team wants broader access to Shopify developers, partners, and applications | The company maintains a capable SFCC team and gains enough value from that expertise |
| Architecture | The business can keep operational truth in ERP, PIM, OMS, CPQ, or Salesforce | The current SFCC architecture already supports growth without excessive workarounds |
Our platform comparison helps teams evaluate commerce options against pricing, account structures, integrations, administration, scalability, and real buyer workflows.
Decision principle: Choose Shopify Plus only after it passes the requirements that carry the most revenue, operational, compliance, and customer-trust risk.
Audit Salesforce Commerce Cloud Before Migration
Migrating from Salesforce to Shopify Plus starts with an SFCC audit. The audit should expose every capability, dependency, customization, scheduled job, data source, manual workaround, and operational exception that the current platform supports.
Teams should inspect the current SFRA or SiteGenesis implementation, cartridges, controllers, templates, custom objects, Business Manager jobs, OCAPI or SCAPI connections, search configuration, content assets, analytics, and third-party services.
Audit these areas
- Sites, domains, locales, currencies, and regional storefronts
- Products, catalogs, categories, variants, bundles, sets, and custom attributes
- Price books, promotions, coupons, eligibility rules, and exclusions
- Customer profiles, account structures, permissions, and authentication flows
- Orders, returns, exchanges, payments, tax, shipping, and fraud controls
- ERP, PIM, OMS, WMS, CRM, CPQ, loyalty, search, and marketing connections
- Content assets, media, landing pages, metadata, structured data, and redirects
- Scheduled jobs, manual processes, incident procedures, and reporting dependencies
Our replatform discovery process focuses on the assumptions that can change scope, cost, architecture, or launch risk before development starts.
In our replatforming post, we explain why teams should not treat a platform move as a lift-and-shift exercise. We frame replatforming as a strategic reset across ERP, product data, commerce, workflows, and customer experience.
Classify What Migrates, Rebuilds, Stays, or Retires
A Salesforce Commerce Cloud to Shopify migration should not copy every SFCC capability into a new technical form. The team should decide whether each capability still supports the target operating model.
| Disposition | Use it when | Example |
|---|---|---|
| Migrate | The data or content remains accurate and fits Shopify’s structure | Approved products, customers, content, SEO metadata, and selected order history |
| Transform | The information remains valuable but requires a new model | SFCC custom attributes mapped to metafields or metaobjects |
| Rebuild | The business outcome remains necessary but the SFCC implementation does not fit Shopify | Checkout validation rebuilt with Shopify Functions or extensions |
| Replace | A Shopify-native capability or application handles the need more effectively | Search, subscriptions, loyalty, reviews, or merchandising |
| Retain | An external system should continue owning the process or data | ERP inventory, CPQ pricing, CRM cases, or OMS fulfillment |
| Retire | The customization no longer supports a current requirement | Unused cartridges, duplicate feeds, outdated promotions, or manual exports |
High-risk capabilities need a proof of concept before the team approves the full build. These often include product configurators, advanced promotions, complex bundles, subscriptions, loyalty, ERP pricing, custom checkout steps, multi-site rules, returns, and account-specific purchasing controls.
Map Salesforce Commerce Cloud Data to Shopify Plus
Migrating from Salesforce to Shopify Plus requires more than exporting SFCC XML and importing Shopify CSV files. The platforms organize products, content, pricing, customer relationships, and commerce logic differently.
| SFCC object | Shopify destination | Migration approach | Main risk |
|---|---|---|---|
| Products and variations | Products, options, variants, metafields, and metaobjects | Transform the product model and preserve stable identifiers | Option conflicts, duplicate variants, or lost relationships |
| Catalogs and categories | Collections, navigation, search filters, and B2B catalogs | Rebuild around buyer discovery and account eligibility | Lost category context or incorrect product access |
| Price books | B2B catalogs, ERP or CPQ pricing, discounts, and Functions | Define pricing ownership before mapping | Contract mismatch, promotion conflict, or margin leakage |
| Customers | Customers, companies, locations, roles, and permissions | Clean duplicates and map account relationships | Incorrect account access or failed activation |
| Orders | Shopify orders, metafields, external archive, ERP, or OMS | Choose the history that supports service and reporting | Missing references, incomplete financial context, or support gaps |
| Content assets | Pages, articles, theme sections, files, metafields, and metaobjects | Clean markup and rebuild reusable content models | Broken media, styling debt, or lost metadata |
| SEO rules | Shopify URLs, metadata, redirects, canonicals, and structured data | Map each valuable legacy URL to the closest new destination | Traffic loss, redirect chains, or indexation errors |
Preserve stable SKUs, account IDs, product IDs, order references, and external keys unless the organization approves a documented identifier change across every connected system. Arbitrary cleanup can break ERP, OMS, PIM, support, reporting, and historical references.
Shopify currently supports up to 2,048 variants per product by default, but the number alone does not prove product-model fit. Teams should test options, media, inventory, merchandising, search, and administration against the real catalog. Shopify documents the current limit in its variant model.
Map SFCC Price Books to Shopify Plus B2B Catalogs
Salesforce Commerce Cloud price books can support layered pricing, currencies, promotions, and customer-specific rules. Shopify Plus uses B2B catalogs to control product availability and pricing for companies and company locations.
Shopify Plus currently allows unlimited B2B catalogs and direct catalog assignment to companies and locations. Catalogs can also support quantity rules and volume pricing. Teams should review Shopify’s current B2B catalogs and quantity pricing documentation before they finalize the mapping.
Pricing decisions to settle
- Which system calculates the final customer price?
- How do company and location assignments affect product access?
- How do fixed prices and percentage adjustments interact?
- How do quantity rules, volume breaks, packs, and units work?
- How do promotions interact with contracted prices?
- How does the architecture handle missing, stale, or slow ERP pricing?
- Which exceptions require a quote, sales review, or manual approval?
Our Shopify B2B analysis explains where native catalogs and company features fit and where ERP rules, account complexity, or specialized workflows need additional architecture.
Pricing warning: Do not validate pricing with one sample account. Test parent and branch companies, active and expired contracts, quantity breaks, currencies, promotions, credit restrictions, missing prices, and integration timeouts.
Can You Keep Salesforce After Moving to Shopify Plus?
Yes. Migrating from Salesforce to Shopify Plus does not require a company to abandon every Salesforce product. Shopify Plus can replace Commerce Cloud while Salesforce continues supporting sales, service, marketing, customer data, or account management.
| System | Possible responsibility after migration | Common data flow |
|---|---|---|
| Sales Cloud | Accounts, contacts, opportunities, and sales activity | Shopify customer and order events can update account context |
| Service Cloud | Cases, service history, support workflows, and customer issues | Shopify orders, returns, and customer activity can support case resolution |
| Marketing Cloud | Campaigns, segmentation, journeys, and communication orchestration | Shopify consent, customer, product, and order events can support campaigns |
| Data 360 | Customer-data ingestion, mapping, unification, and activation | Shopify data can enter Data 360 through supported connection methods |
| Shopify Plus | Commerce experience, catalog access, cart, checkout, orders, and storefront administration | Shopify sends and receives approved data through APIs, events, middleware, and connectors |
Salesforce currently offers a beta Shopify connector for Data 360 ingestion. The connector can support data streams, but it does not replace a complete Shopify Plus Salesforce integration architecture. Teams should review the official Shopify connector documentation and validate the beta status, supported objects, connection direction, security, and operating requirements.
The integration design should define ownership for accounts, contacts, customer profiles, consent, opportunities, cases, orders, returns, service history, and customer activity. It should also prevent circular updates and conflicting changes between systems.
What Happens to Legacy Systems During the Migration?
The legacy-system plan should classify every application, interface, job, archive, report, and data feed. Migrating from Salesforce to Shopify Plus often changes the commerce layer while ERP, PIM, OMS, WMS, CRM, tax, payments, fraud, loyalty, search, and reporting continue running.
| System decision | Use it when | Required action |
|---|---|---|
| Retain | The system remains the source of truth or supports a critical process | Define its ownership and target-state interface with Shopify |
| Reintegrate | The system stays, but the SFCC connection cannot continue | Build and test a new Shopify connection with monitoring and recovery |
| Run temporarily | The team needs the old and new environments during validation | Define synchronization, freeze rules, delta migration, and shutdown criteria |
| Archive | The business needs historical access but not active processing | Create searchable, secure access for service, finance, legal, or reporting teams |
| Replace | A new service offers a better fit for the future architecture | Migrate data, recreate required behavior, and retire the old connection |
| Retire | The system or job no longer supports a valid business need | Confirm dependencies, preserve required records, and remove access safely |
Our replatforming risks analysis covers the ERP, pricing, product-data, workflow, testing, and operational issues that often surface during a complex platform move.
We make a related point in our foundation post. Modern replatforming must connect buyer self-service with ERP, PIM, OMS, payments, customer workflows, and the systems that support long-term operations.
Rebuild SFCC Custom Logic With Shopify Plus
SFCC implementations often contain years of custom checkout, promotion, shipping, payment, validation, and merchandising logic. The Shopify Plus migration should preserve the required business outcome without recreating the old code line by line.
Shopify native
Use standard products, discounts, B2B catalogs, markets, customer accounts, shipping, payments, and administration where they fit.
Shopify Functions
Use backend logic for supported discount, payment, delivery, validation, bundle, and fulfillment behaviors.
Checkout extensions
Add approved checkout interface elements and workflows at Shopify-supported extension points.
Custom applications
Build specialized administration, buyer, integration, or workflow capabilities when native features do not fit.
Middleware
Coordinate transformations, routing, retries, monitoring, and synchronization across Shopify and enterprise systems.
Process redesign
Remove custom logic when the rule no longer creates enough value to justify its cost and risk.
Shopify ended support for Shopify Scripts on August 28, 2025 and directs merchants toward Shopify Functions. Teams should validate each use case against the current Shopify Functions capabilities and the available checkout extension points.
Architecture principle: Recreate the business outcome, approval rule, validation, or customer experience. Do not recreate the historical implementation unless the new platform genuinely needs it.
Build a Controlled Migration Pipeline
A reliable Salesforce Commerce Cloud to Shopify migration pipeline needs five stages: extract, transform, load, validate, and reconcile. Each stage should produce logs, measurable results, and recoverable errors.
1. Extract: Export products, catalogs, customers, orders, pricing, promotions, content, media, SEO rules, and reference data from approved sources.
2. Transform: Apply documented mappings, clean invalid records, preserve identifiers, and create the structures Shopify requires.
3. Load: Use suitable Shopify APIs, bulk operations, files, applications, or integration tools for each data type.
4. Validate: Compare counts, relationships, prices, media, permissions, URLs, and business rules with approved acceptance criteria.
5. Reconcile: Investigate differences, retry failed records, approve exceptions, and confirm that source and target systems agree.
The pipeline should support repeatable runs without creating duplicates. It should also preserve referential integrity across products, variants, companies, customers, locations, orders, catalogs, and external system keys.
Our migration checklist covers product data, pricing, accounts, integrations, search, testing, and operational controls that teams should settle before cutover.
Migration warning: A successful import only proves that Shopify accepted the record. The team still needs to prove that customers, administrators, connected systems, and downstream operations can use it correctly.
Protect SEO During the Salesforce to Shopify Migration
SEO risk grows when SFCC sites, locales, categories, products, content assets, and faceted pages move into a different URL structure. Teams need to map valuable URLs before they finalize Shopify navigation and content models.
- Crawl every production site and preserve URL, status, canonical, title, description, hreflang, structured data, and internal-link information.
- Map each valuable legacy URL to the closest relevant Shopify destination.
- Avoid redirect chains, broad homepage redirects, and mappings that ignore search intent.
- Review faceted navigation, parameterized pages, pagination, robots directives, and canonical behavior.
- Map languages, regions, currencies, domains, and hreflang rules into the Shopify Markets structure.
- Preserve useful product specifications, part numbers, technical terms, and internal links.
- Compare pre-launch and post-launch crawls before opening the new storefront to search engines.
- Monitor rankings, traffic, revenue, errors, and conversion by landing page after launch.
SEO warning: Do not wait until the final launch week to create redirects. URL decisions influence navigation, collections, content structure, markets, analytics, and the migration pipeline.
Choose a Big-Bang or Phased Cutover
Migrating from Salesforce to Shopify Plus does not follow one universal timeline. Site count, market count, catalog complexity, custom logic, ERP dependencies, B2B pricing, historical data, SEO footprint, and internal readiness determine the delivery path.
| Cutover model | Best fit | Main advantage | Main risk |
|---|---|---|---|
| Big-bang | One storefront, controlled complexity, stable integrations, and a manageable launch window | The team avoids a long period of dual operations | One launch concentrates data, SEO, integration, and customer risk |
| Market phase | Regional sites with separable teams, catalogs, domains, or operations | The first market proves the model before wider rollout | Regional differences can limit reuse |
| Brand phase | Multi-brand organizations with distinct storefronts or teams | Each brand can validate its own requirements | Shared systems may complicate sequencing |
| Customer phase | B2B programs with complex accounts, pricing, permissions, or adoption needs | Real customers can validate workflows before full migration | The business must manage parallel customer experiences temporarily |
| Capability phase | Programs that can separate product discovery, self-service, ordering, or account operations | The team can release value while reducing one risk at a time | Temporary integration and experience boundaries need careful design |
Our phased migration analysis helps teams compare launch concentration, parallel operations, customer trust, rollback options, and system dependencies.
Every cutover plan should define content and configuration freezes, delta imports, DNS changes, integration switching, payment validation, order reconciliation, customer communication, support coverage, rollback criteria, and decision authority.
Test the Complete Business Workflow
A successful page load or checkout does not prove that the migration works. Teams need to test the complete journey from product discovery through pricing, account access, checkout, payment, ERP acceptance, fulfillment, service, return, and reporting.
Use real operating scenarios
- B2B companies, locations, roles, catalogs, prices, terms, and purchase orders
- B2C and guest checkout where the business supports both models
- Promotions, exclusions, stacking rules, quantity breaks, and restricted products
- Payments, authorization, capture, refunds, partial refunds, and fraud review
- Tax, shipping, inventory, split fulfillment, backorders, and unavailable products
- ERP order acceptance, duplicate prevention, error queues, and manual recovery
- Salesforce account, case, customer, consent, and activity synchronization
- Returns, exchanges, cancellations, credits, and customer communication
- International domains, languages, currencies, duties, and market rules
- Performance, accessibility, analytics, structured data, redirects, and indexation
Our launch checklist covers customer accounts, pricing, ERP flows, payments, tax, search, SEO, support ownership, monitoring, and post-launch validation.
Launch principle: Test the exceptions that employees handle manually today. Those cases often reveal the architecture and process gaps that ideal test orders miss.
Salesforce to Shopify Plus Migration Readiness Checklist
Use this checklist before approving cutover for a Salesforce to Shopify Plus migration.
- We confirmed why Shopify Plus fits the target business and operating model.
- We completed the SFCC capability, customization, data, SEO, and integration audit.
- We classified every major capability as migrate, transform, rebuild, replace, retain, or retire.
- We proved high-risk requirements before approving the full implementation.
- We preserved stable business identifiers and documented every data transformation.
- We tested B2B catalogs, pricing, companies, locations, quantities, and exceptions with real accounts.
- We assigned ownership for Shopify, Salesforce, ERP, PIM, OMS, and every retained system.
- We validated the migration pipeline, failed-record process, delta import, and reconciliation.
- We tested redirects, metadata, structured data, markets, internal links, and indexation controls.
- We approved cutover, customer communication, support coverage, monitoring, and rollback criteria.
- We funded post-launch reconciliation, issue resolution, SEO monitoring, and continuous improvement.
Conclusion
Migrating from Salesforce to Shopify Plus succeeds when the team treats the project as a business and architecture change, not as a storefront copy. The migration must preserve valuable data and workflows while redesigning the capabilities that do not fit Shopify Plus.
Strong teams clarify platform fit, audit SFCC, test high-risk requirements, map data and pricing, retain the right Salesforce products, reconnect legacy systems, protect SEO, and choose a cutover model that operations can support.
Our Shopify Plus implementation work connects discovery, data migration, B2B catalogs, Salesforce integration, ERP workflows, custom development, SEO, testing, and cutover around measurable business outcomes.
