Data & Customer Migration

Move customers, orders, subscriptions and B2B accounts to Shopify without duplicates, gaps or broken billing, and plan the subscriber cutover.

Common Questions

What order-level custom fields (gift messages, engraving instructions, delivery-date selections) need special handling during an order-history migration?

Engraving instructions and delivery-date selections need special handling; gift messages need only consistent keys. Shopify's example for an order's custom attributes is a "gift message, delivery instructions, or internal notes" (shopify.dev, October 2026). Engraving goes in line item properties, so each line keeps its own text. Delivery dates go in a date-type metafield, which Shopify validates (shopify.dev, October 2026).

right-arrow

Do return/RMA records and their approval history migrate cleanly to Shopify's returns model or a returns app like Loop/AfterShip?

Return merchandise authorization (RMA) records migrate only partly. A Shopify return needs a fulfilled line item "that hasn't yet been refunded" (shopify.dev, October 2026), so a refunded RMA can't become one. An open RMA can be recreated with its request date but no approval history (shopify.dev, October 2026). Loop and AfterShip document no history import (Loop Help Center, AfterShip's Returnly page, October 2026).

right-arrow

How do vendor/supplier records and purchase-order history migrate as data objects during a platform switch, given Shopify has no native supplier-management model?

Supplier records reach Shopify only by hand, and purchase order history doesn't reach it at all. Shopify now has native suppliers but no supplier import, and "Historical purchase orders can't be imported into Shopify" (Shopify Help Center, October 2026). Rekey suppliers, or load them into the app or enterprise resource planning (ERP) system that owns purchasing, and archive the history.

right-arrow

Does customer-specific product visibility (certain SKUs only shown to certain B2B accounts) migrate correctly to Shopify B2B's catalog-assignment model?

Customer-specific product visibility migrates correctly only for in-or-out rules. A Shopify business-to-business (B2B) catalog only includes or excludes products for its company locations (Shopify Help Center, October 2026). SuiteCommerce's view-only Disable Purchase levels have no catalog equivalent (Oracle NetSuite Help Center, October 2026). Below Shopify Plus, one account's own assortment uses one of 3 catalogs (Shopify Help Center, October 2026).

right-arrow

Does blended B2B/DTC customer data (one person who buys both wholesale and retail) migrate correctly without duplicating or misclassifying the account on Shopify?

Blended customer data migrates correctly, without duplicates, only when each person becomes one Shopify customer before any company link. One email belongs to one customer, who joins only one company (Shopify Help Center, October 2026). Signed in, that customer buys business-to-business (B2B); signed out, retail (Shopify Help Center, October 2026). Shopify won't merge B2B-linked profiles (Shopify Help Center, October 2026).

right-arrow

Is it ever the right call to pause new subscription sign-ups during a platform migration, or does that hurt growth more than the migration risk justifies?

Pausing new subscription sign-ups for a whole platform migration is the wrong default, so take the subscribe option down only for the hours around the billing cutover. Recharge's guide puts new subscribers on Recharge before the old data is exported (Recharge Help Center). Skio wants the store selling Skio subscriptions first: at least 24 to 36 hours by its migrations guide (Skio Help Center), about 24 by its overview (Skio Help Center, October 2026).

right-arrow