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

How do split shipments and partial fulfillments in historical order data migrate to Shopify's fulfillment-order model without breaking the audit trail?

Split shipments migrate as one fulfillment per shipment, not as the original fulfillment orders. Shopify creates fulfillment orders itself, and "It is not possible to manually create fulfillment orders" (shopify.dev, October 2026). Each fulfillment keeps its quantities and tracking but is dated at import, so add a fulfillment event to carry the original ship or delivery date (shopify.dev, October 2026).

right-arrow

How do serial numbers, lot numbers, or expiration-date tracking (common in specific verticals) migrate to Shopify's inventory model from a platform with native support for them?

Serial numbers, lot numbers and expiry dates have no field in Shopify's inventory model, so they move to an app, an upstream system or, for coarse expiry, the variant itself. An inventory item "holds the stock keeping unit (SKU), whether quantities are tracked, shipping requirements, and customs information" (Shopify developer docs, October 2026). Name the system that owns traceability first.

right-arrow

How do we communicate a subscription-platform migration to high-LTV, long-tenured subscribers specifically, versus the general subscriber base?

Long-tenured, high lifetime value (LTV) subscribers need a named-sender note 10 to 14 days before the migration cutover, instead of the general base's heads-up (Deploi practice). The note confirms price, cadence and next charge date are unchanged. It also explains any new sign-in, because Shopify's customer accounts, for one, use an emailed 6-digit code (Shopify Help Center, October 2026).

right-arrow

What questions should we ask a migration agency specifically about their subscription-migration track record before trusting them with an active subscriber base?

Test a migration agency's track record with 3 questions about its last 3 subscription migrations: how many subscribers moved to which platforms, what payment-method transfer rate it achieved, and where the cards were vaulted. Vague answers are disqualifying. Card location matters because Shopify migrates payment methods from four processors: Stripe, Braintree, PayPal Express and Authorize.net (Shopify Help Center, October 2026).

right-arrow

How do customer referral-program records (who referred whom, referral rewards owed) migrate as customer metadata during a platform switch?

Referral records don't migrate into Shopify as customer metadata, because Shopify has no referral object: its customer import has no referral column (Shopify Help Center, October 2026). Who referred whom stays in the referral app, and rewards owed are a liability on your books. Export the ledger before cancelling the app, then honor, convert or pay out each reward.

right-arrow

How do customer support ticket history and case notes (from the old helpdesk) get linked to migrated customer records in the new Gorgias/Zendesk-Shopify setup?

Helpdesk history links to migrated Shopify customers by email address, not customer ID, so an email changed in migration orphans tickets. Gorgias links tickets "by the contact email address" (Gorgias Help Center, October 2026), and its shipping-address phone match is off by default (Gorgias Help Center). Zendesk matches the requester's email or phone (Zendesk Help, October 2026).

right-arrow