Migrations & Replatforming
Powered by Deploi
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 a separate budget line at roughly 25 to 40% of the scripted migration cost. Deploi scopes a scripted subscription migration at $15,000 to $40,000 (Deploi estimate, illustrative), which puts the mitigation line near $5,000 to $15,000. That money buys a 2 to 4 week parallel billing run, a reconciliation pass, and support capacity through the first two billing cycles.
How do B2B recurring/replenishment orders (distinct from consumer subscriptions) migrate their contract-level scheduling data to Shopify?
Shopify B2B has no destination object for a recurring replenishment schedule. Shopify states that "B2B doesn't support purchase options, such as subscriptions, pre-orders, and try before you buy", and a selling plan on a B2B order returns the error "Only one-time purchase is available for B2B orders" (per shopify.dev and Shopify Community, September 2026). B2B replenishment gets rebuilt, not migrated.
Does draft-order and quote data (common in B2B sales-rep-assisted workflows) migrate to Shopify's draft order model cleanly?
Open quotes migrate as Shopify draft orders; closed quotes do not migrate at all. Shopify's B2B import path requires every company, company location and company contact to exist first, and returns an error if the customer has no role assignment at that location (per shopify.dev, September 2026). No field carries sales-rep attribution.
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 is a native Shopify payment term, not an exception. Shopify's payment terms templates cover net 7, net 15, net 30, net 45, net 60 and net 90, plus due on fulfillment and fixed date for draft orders (per Shopify Help Center, September 2026). Terms outside that list need a Payment Customization function or an app.
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 a big-bang migration above roughly 2,000 active subscribers, and the right first cohort is newest subscribers on cards held by your current processor. Newest subscribers carry the freshest payment credentials and the lowest tenure-weighted LTV, so a failed transfer costs least there. Below about 2,000 contracts, a single-window migration with a parallel billing run is simpler and cheaper.
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 subscriber messages to avoid reading as a cancellation: a notice 14 days before cutover, a portal-change note on cutover day, a payment-update prompt wherever a card did not transfer, and a confirmation on the first charge day (Deploi practice, not a Shopify requirement). Shopify's customerPaymentMethodSendUpdateEmail mutation sends the secure update link (per shopify.dev, September 2026).