Migrations & Replatforming
Powered by Deploi
Common Questions
Does customer-specific product visibility (certain SKUs only shown to certain B2B accounts) migrate correctly to Shopify B2B's catalog-assignment model?
Per-account SKU visibility migrates as a binary, and the legacy models it comes from are three-state. SuiteCommerce Personalized Catalog Views offer Display Fully, Disable Purchase, and Disable Purchase and Hide Price (Oracle NetSuite docs, September 2026). Shopify catalogs offer in or out. A visible product the buyer cannot purchase has no native catalog equivalent.
Does blended B2B/DTC customer data (one person who buys both wholesale and retail) migrate correctly without duplicating or misclassifying the account on Shopify?
One person who buys both wholesale and retail stays one Shopify customer record. A customer can belong to only one company, a single email address can belong to only one customer, and the buying context follows whether that email is assigned to a company location (Shopify Help Center, September 2026). Two source logins must collapse into one.
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 during a platform migration is the wrong default for almost every mid-market merchant. Freeze the sign-up surface only for the hours around the actual billing cutover, not for the whole 60 to 90 day migration window (July 2026 research). A multi-week freeze costs compounding cohort growth to avoid a risk that rehearsal removes.
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.
Does a migration to Shopify ever cause a temporary drop in AI-answer-engine citation share even if traditional Google rankings hold steady?
A Shopify migration costs AI answer-engine citation share through two mechanisms that Google rankings never reveal: changed URLs break the links engines already cite, and every engine re-crawls on its own separate cycle. OpenAI runs a dedicated crawler, OAI-SearchBot, for ChatGPT search results (OpenAI developer docs, September 2026). No engine publishes a re-crawl interval. Budget one quarter.
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.