Best Practices for Migrating from Salesforce to Shopify Plus

Undertaking an ecommerce migration can feel like switching planes in the middle of a flight when you are moving from Salesforce Commerce Cloud (SFCC) to Shopify Plus.

There are lots of moving parts, deep integrations, and a ton of business logic baked into the stack. This ecommerce migration guide breaks it down step by step so it is easier to plan, execute, and launch with confidence.

Whether you are running B2C, B2B, or a hybrid model, the flow below will help you avoid common gotchas and keep your SEO, data, and custom logic intact.

1) Pre-Migration Audit (SFCC-Specific)

Before touching a single line of code, map the lay of the land. SFCC stores tend to be highly customized, often in ways that do not show on the surface.

You are not just copying files. You are moving business rules, pricing logic, integrations, and a lot of invisible operational detail.

What you are running today

• Pipelines or controllers, ISML templates, and custom scripts
• Catalog structure including categories, attributes, and variations
• Whether the site runs on SiteGenesis or SFRA, since that affects how templates map to a Shopify theme

What to export from Business Manager

• Products, categories, customers, and orders
• Promotions and price books
• SEO redirects and URL rules
• Content assets such as banners, HTML blocks, and media

What is connected

• ERP, OMS, or CRM through OCAPI or server-side scripts
• Payments, taxes, and shipping carriers
• Reviews, loyalty, subscriptions, search, and analytics tools

2) Data Model Mapping (SFCC → Shopify Plus)

This is where you translate how SFCC thinks into how Shopify operates. Get this right and the rest of the migration becomes much easier.

Products and variants

• SFCC catalog XML becomes Shopify products and variants
• Variant drivers such as Size and Color become product options
• Extra attributes move into metafields or tags
• Keep handles clean and consistent because they become your URLs

Price books and B2B

• SFCC price books are granular, while Shopify Plus handles B2B pricing through Price Lists
• Set up companies and locations, then assign the right price lists
• For retail pricing, use standard price and compare-at price where needed
• Promotions can move into Shopify Discounts or Shopify Functions

SEO

• Export SFCC SEO URL redirects and map them into Shopify redirect CSVs
• Preserve titles, meta descriptions, and structured data such as JSON-LD
• Keep slugs where possible, and redirect old URLs to new ones one-to-one if they change

Customers

• Export customers in XML or CSV format
• Passwords will not migrate because the hashing systems are different
• Plan a reactivation campaign with a clear reset password flow and, if appropriate, a small incentive

Orders

• Decide how much order history to migrate, often 12 to 24 months
• Map SFCC order_no into a Shopify metafield so support can search legacy orders
• Include payment status, fulfillment status, channel or source, taxes, shipping, and discounts

3) Build Your Migration Pipeline

This is where the ETL pipeline does the heavy lifting.

Step 1: Extract (Get your data out of SFCC)

You usually have two main escape hatches:

• Business Manager export jobs for products, categories, customers, and orders. This is the quickest way to pull clean chunks of data without custom code.
• SFCC OCAPI Data API for more control, automation, and bulk data pulls.

Do not forget media assets such as images, PDFs, and videos. These often live in SFCC’s content library, and exporting them early will save a lot of cleanup later.

Step 2: Transform (Make SFCC data talk to Shopify)

This is where you translate between two systems that structure data differently.

• Use Python or Node.js for XML and CSV parsing, then format for Shopify CSV or JSON flows
• Normalize SKUs by removing spaces and unusual characters
• Standardize option names such as Size and Color
• Clean product description HTML by removing unnecessary tags, inline styles, and scripts
• Map SFCC price books into Shopify Plus B2B Price Lists where needed
• Plan metafields in advance for custom product attributes

Step 3: Load (Bring it into Shopify safely)

• Shopify GraphQL Admin API is usually the best option for high-speed, high-volume imports
• Use bulk operations for catalogs larger than 10,000 products
• Batch imports carefully to stay within Shopify rate limits
• Keep detailed logs so failures are easy to retry

If your ERP is already the source of truth for inventory, it is often better to connect ERP to Shopify directly instead of importing static inventory from SFCC first.

4) SEO and Redirect Strategy

This is where many migrations lose momentum. A strong redirect plan protects rankings, preserves traffic, and reduces post-launch chaos.

Rebuild redirects in Shopify before launch

• Use one-to-one mapping wherever possible
• Avoid chained redirects such as old → temporary → new
• Prioritize high-traffic pages using analytics and Google Search Console

Check with a crawler

• Review status codes such as 200, 301, and 404
• Validate canonicals, hreflang, and schema
• Confirm important pages appear in Shopify’s refreshed sitemap

Monitor after launch

• Watch Google Search Console closely for the first 2 to 3 weeks
• Patch 404s quickly
• Submit important updated URLs for reindexing if needed

5) Checkout and Custom Logic

SFCC checkouts are often deeply customized. On Shopify Plus, the goal is not to recreate the same code line by line. The goal is to recreate the same business outcomes with better extension points.

Checkout UI Extensions and Functions

• Functions handle logic such as discounts, validation, bundles, buy X get Y, and minimum thresholds
• Checkout UI Extensions handle extra fields and custom UI touches
• Legacy Scripts may still exist in some environments, but Functions are the long-term direction

Payments, taxes, and shipping

• Map gateways and fraud tools carefully
• Recreate tax logic using Shopify Tax or your preferred provider
• Rebuild shipping rules, carrier rates, zones, or logic through Functions or apps as needed

B2B on Shopify specifics

• Net terms and PO fields
• Company-specific methods and minimum order amounts
• Price visibility rules and location-level differences

6) Integrations

Most SFCC stores rely on ERP and Salesforce CRM. Keep the flows, but change the pipes.

Common flows

• Shopify orders to Salesforce CRM opportunities or cases
• Two-way customer profile sync
• ERP inventory and price to Shopify
• Shopify to ERP for fulfillment, invoicing, and financials
• OMS returns and tracking to Shopify

Middleware that works

Celigo, MuleSoft, and Boomi are all options. The best choice is often the one your team already understands and can support long term.

Data ownership

• Define the system of record for inventory, pricing, customer data, and order status
• Avoid circular updates
• Set direction, frequency, and conflict rules clearly

7) Theme, Content, and UX

Your store will feel fresher on Shopify. Make the move count.

Theme

• Use a modern theme or build custom on Online Store 2.0
• Protect Core Web Vitals by compressing images, avoiding app bloat, and lazy-loading thoughtfully

Content

• Move blogs, pages, and media carefully
• Turn reusable blocks into sections and snippets
• Add JSON-LD for products, breadcrumbs, and articles

Navigation and filters

• SFCC categories typically become Shopify collections
• Use automated collections where possible so merchandising rules stay scalable
• Add stronger filters using the theme or an app when needed

Accessibility and mobile

• Check contrast, focus states, and keyboard navigation
• Test PDP and checkout experiences on low-end Android devices

8) Testing and Go-Live (Treat It Like a Product Launch)

No surprises on launch day. That is the goal.

Test matrix

• B2B and B2C price lists by customer group
• Promotions including stacking, exclusions, and scheduled windows
• Checkout flows for guest and logged-in users, domestic and international
• Taxes and shipping across key markets
• ERP inventory sync, order flow, and CRM sync
• Payments including auth, capture, refund, and partial refund
• Performance, accessibility, and structured data

Dry runs and freezes

• Run a full rehearsal on a staging store with a fresh data snapshot
• Freeze content a few hours before cutover
• Plan a delta sync for orders and inventory placed during the launch window

Launch checklist

• Redirects imported and tested
• Payment gateway live and tested with a real transaction
• DNS changed during a lower-traffic period
• SFCC kept in maintenance mode briefly as a fallback
• Google Search Console, analytics, errors, and uptime monitored for the first 72 hours

After launch

• Send account reactivation emails with password reset instructions
• Watch for 404s, cart issues, checkout problems, and support tickets

A Simple 9-Week Plan (Adjust as Needed)

• Weeks 1–2: Audit, architecture, data mapping, and integration planning
• Weeks 3–5: ETL scripts, theme build, and initial imports
• Weeks 6–7: ERP and CRM connections, Shopify Functions setup, and B2B price lists
• Week 8: QA, redirects, performance checks, and user acceptance testing
• Week 9: Freeze changes, run the final sync, launch, and monitor closely

If you have more regions, a very large catalog, or complex B2B requirements, give yourself extra testing time.

Final Takeaway

Similar to a BigCommerce to Shopify migration or a Magento to Shopify Plus migration, moving from Salesforce Commerce Cloud to Shopify Plus is a major step toward scalability and growth.

Whether it is a WordPress to Shopify migration, a Magento 1 to Shopify migration, or a Volusion to Shopify migration, partnering with an experienced Shopify Plus development company can help reduce risk and unlock the full potential of your new ecommerce platform.