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 much should we budget specifically for subscription-migration risk mitigation (QA, parallel-run, customer support surge) as its own line item separate from the core platform migration budget?

Subscription-migration risk mitigation deserves its own budget line, sized from five jobs rather than a percentage, because Deploi found no published benchmark that sets one. Fund a cutover check while the old app's billing is paused, as Shopify strongly recommends (Shopify developer docs, October 2026), then reconciliation, a delta sync, a rollback rehearsal and support cover through two billing cycles.

right-arrow

How do B2B recurring/replenishment orders (distinct from consumer subscriptions) migrate their contract-level scheduling data to Shopify?

Shopify business-to-business (B2B) has no destination object for a recurring replenishment schedule, so the schedule is rebuilt, not migrated. Shopify's developer docs say "B2B doesn't support purchase options, such as subscriptions, pre-orders, and try before you buy" (shopify.dev, October 2026). Shopify also lists Subscriptions among features that aren't compatible with B2B (Shopify Help Center, October 2026).

right-arrow

Does draft-order and quote data (common in B2B sales-rep-assisted workflows) migrate to Shopify's draft order model cleanly?

Only open quotes migrate, as Shopify draft orders; closed quotes don't migrate as quotes. A business-to-business (B2B) import needs the company, location, contact and products in Shopify first, plus the buyer's role at that location, because otherwise "an error is returned" (shopify.dev, October 2026). Sales rep ownership moves to staff assigned to each company location (Shopify Help Center, October 2026).

right-arrow

Do custom payment-term agreements (e.g., net-45 negotiated for one specific account) migrate correctly to Shopify B2B's payment-terms feature, or default to standard terms?

Net 45 migrates exactly, because net 45 is one of Shopify's six net payment terms for business-to-business (B2B) accounts (Shopify Help Center, October 2026). A term outside the list doesn't fall back to a standard term. Unless you map it, the company location keeps Shopify's default, No payment terms, and the buyer pays at checkout.

right-arrow

How do we decide whether to migrate ALL subscribers at once versus staggering the cutover by cohort (e.g., newest subscribers first, as a lower-risk test group)?

Cohort-staggered cutover beats migrating everyone at once above roughly 2,000 subscribers (Deploi practice); start with newest subscribers on cards your current processor holds. Check the destination first. Shopify Subscriptions skips contract rows it already imported (Shopify Help Center, October 2026), so one cohort file can follow another. Skio's documented process copies subscribers on one migration date (Skio Help Center).

right-arrow

How do we communicate a subscription-platform migration to active subscribers so they don't think their subscription was cancelled or their payment failed?

A subscription migration needs four messages, starting 14 days before cutover, because unexplained changes read as a cancellation (Deploi practice). Add a cutover portal note, a card prompt only where a card failed or did not transfer, and a first-charge confirmation. For a card that exists but fails, Shopify's customerPaymentMethodSendUpdateEmail emails a secure update link (Shopify developer docs, October 2026).

right-arrow