Shopify → Shopify Plus Migration Checklist | Bles Software

Published by Bles Software, a custom software and AI company based in Yehud-Monoson, Israel, building web apps, AI agents and API integrations for clients in Israel, the US, the UK and the EU.

A Shopify → Shopify Plus migration is less about moving platforms and more about recalibrating your commerce operating model around scale, governance, and extensibility. Shopify Plus brings organization-level administration, enterprise-grade features, B2B capabilities, and a modern checkout extensibility stack—but the migration has to protect revenue, preserve SEO equity, and control operational risk. This playbook provides a pragmatic, step-by-step framework for a Shopify Plus migration that emphasizes risk management, cutover strategy, downtime control, QA, and contingency planning. It also quantifies typical effort ranges so you can plan resourcing and timelines with confidence.

If you want help shaping scope and deriving a precise estimate, speak with our team via /services/migrations.

Outcomes and Intent: Define Why You’re Migrating

Before any technical activity, document the business intent of your shopify plus migration and the acceptance criteria that make it successful. Typical drivers include consolidating multiple storefronts under Organization Admin, enabling B2B features (company profiles, price lists, and payment terms), adopting Checkout Extensibility and Shopify Functions, improving governance with SSO/SCIM, and leveraging Shopify Markets for geographies and currencies. Clarify whether you are replatforming like-for-like to mitigate risk, or using the migration as a modernization program (new theme, new information architecture, new integrations). Write down what “good” looks like in terms of traffic loss tolerance, conversion impact, and operational continuity.

At this point, also perform a structured risk assessment. Call out hard constraints (no password migration; potential subscription re-consent; payment token portability limitations), high-variance tasks (custom apps, ERP/WMS integrations), and SEO risk. Define a maximum acceptable downtime or degradation window for cutover and the business events you must avoid (e.g., peak sale moments, fiscal close). This becomes your baseline for phasing and go/no-go decisions.

Assumptions and Constraints: What Changes on Plus

Moving from Shopify to Shopify Plus is familiar but not identical. Key differences shape the plan. Checkout customization moves from checkout.liquid to Checkout Extensibility with UI extensions and Shopify Functions; Shopify Scripts are replaced by Functions for discounts, shipping, and payment logic. Organization-level features introduce new permission models, store management, and SSO. Plus unlocks B2B on Shopify with company-level catalogs and payment terms. Markets and multi-currency management allow consolidation of localized experiences without necessarily spinning up additional expansion stores.

Not everything is migratable. Customer passwords cannot be transferred; you will need to plan an account invite campaign. Payment tokens are managed by gateways and are generally not portable between stores; subscriptions may require re-authorization or a gateway-facilitated vault migration. Existing order histories can be imported for reference and reporting, but will not be reconnected to legacy gateways or fraud analyses in the same way. Some apps may be redundant on Plus; others may not be compatible with the modern checkout. Document these realities early and align stakeholders to the expected user experience changes.

Phase 0: Discovery and Scope Definition

Inventory your current estate. Catalog products, variants, collections (manual and automated), tags and metafields, blogs and pages, files, discounts and gift cards, tax and shipping profiles, Markets and currencies, locations and inventory policies, and any B2B data structures. Map every integration and app: ERP, WMS, CRM, ESP, returns, 3PL, payment gateways, subscription platforms, search/merchandising, analytics, and consent/cookie management. Note how integrations connect (REST/GraphQL API, webhooks, middleware), their rate limits, and dependencies. Identify the key personas who must sign off: commercial, operations, finance, legal, and customer support.

Finally, set measurable objectives: SEO traffic retention thresholds, conversion targets, average page load budgets, customer service ticket projections, and a timeline with a hard launch window. Success metrics will guide tradeoffs throughout the migration.

Phase 1: Target Architecture and Store Design

Design the end state before moving data. Start with organization topology: determine whether you will use a single store with Shopify Markets for multi-currency/locale or multiple expansion stores for unique catalogs, content, taxes, or operational separations. Decide whether you will adopt B2B on Shopify and if so, which stores will enable it, how catalogs and price lists will be modeled, and how customer/company hierarchies will map.

Choose your storefront approach. For most merchants, a modern Online Store 2.0 theme with app blocks and section schema provides flexibility with low operational burden. If SEO authority rests on your current theme, consider a like-for-like rebuild on OS 2.0 to pick up performance and IA improvements with minimal disruption. Headless storefronts (Hydrogen/Remix or other frameworks) can be considered for unique experiences, but they add complexity, especially around checkout and core vitals; evaluate carefully during a migration. Establish a design system and performance budgets early to avoid late surprises.

For checkout, plan for Checkout Extensibility from day one. Inventory any Scripts and recreate them with Shopify Functions, or replace with native Plus capabilities. Evaluate checkout UI extensions for upsells, address validation, and payment wallet surfacing. Choose payment gateways with vaulting and local method coverage aligned to your Markets strategy. Define tax strategy using Shopify Tax, Avalara, or third-party services; confirm that your chosen approach supports your jurisdictions and product taxability.

Phase 2: Delivery Plan and Schedule

Translate the architecture into a delivery plan with phases, gates, and decision points. Use a pre-production Plus store as your testbed. Establish three environments: development (theme branches and scripts/functions in dev mode), staging/prep store for full-stack UAT, and production. Schedule the project in waves: build and configure, initial data load, integration rewiring, theme QA, pilot UAT, hardening and performance tuning, content freeze and delta data loads, cutover rehearsal, and launch.

Back into the launch window by setting milestones for SEO validation, payment gateway approvals, and app vendor readiness. Book time with third parties like your ERP and CRM teams, your gateway account managers, and logistics providers. If you depend on Salesforce for CRM, ensure your customer and order sync is scoped and tested; if you need implementation help, see /integrations/salesforce. Build contingency into the calendar for gateway underwriting and app review cycles which can take days to weeks.

Data and Content Migration Plan

Define the migration units and sequencing. Products and variants, including option sets, SKUs, pricing, inventory policies, and metafields, should be migrated first to unlock theme development and merchandising. Collections and navigation come next, keeping handles and URL structure stable wherever possible to preserve SEO. Blogs, pages, and files should be brought over with careful internal link checks. Discounts and gift cards require special handling; ensure codes, start/end dates, and usage limits migrate faithfully.

Customer records can be moved, but passwords cannot; plan a campaign for account invites at cutover. Tag and metafield mapping should be audited to avoid breaking personalization or automation flows. Orders can be imported for historical reference; decide how far back to go based on reporting needs and API cost. Remember that legacy order imports won’t replicate gateway transactions or fraud scores and are typically marked as archived; preserve original order IDs in a metafield to maintain reporting continuity.

Implement migration using the Admin GraphQL API for throughput and Matrixify or similar tooling for bulk operations where appropriate. Establish idempotent scripts and maintain mapping files for legacy IDs to new record IDs. Plan for rate-limit aware batching, exponential backoff, and checkpointing. Run an initial full load, validate, then run delta syncs for changes during the build window. Days before launch, enforce a content freeze on mutable resources (navigation, themes, CMS) and shift to scheduled delta jobs to minimize drift.

Checkout, Payments, Taxes, and Shipping

Checkout is mission-critical and the biggest difference between Shopify and Shopify Plus. Rebuild scripts as Functions and audit parity to confirm discount logic, shipping rules, and payment method gating function as expected. Adopt Checkout UI extensions for any on-page enhancements; avoid brittle DOM manipulations since checkout.liquid is not supported on new Plus stores. Validate that your payment gateway accounts are approved in the new store, including 3DS and local payment methods. Tokens generally cannot be ported; customers will re-enter payment information on their first purchase.

Subscription migration requires special attention. If you are moving from an app with vaulted tokens, coordinate with the provider on supported migration pathways. In many cases, you’ll need to run a re-consent flow that gracefully reactivates subscriptions on the new store. Message customers clearly and offer incentives to minimize churn.

Tax and shipping configurations must mirror your current operational reality while taking advantage of Plus capabilities. Confirm that tax jurisdictions, product exemptions, and shipping rate calculations match live expectations. If you use external tax engines, validate the integration end-to-end in staging and production with test orders. For shipping, re-create profiles, zones, and carrier-calculated rates; ensure that locations and inventory policies align so the correct rates present at checkout.

Integrations and Apps

Document every app and integration and decide whether to retire, replace, or reimplement. Many Plus-native features can replace apps: Functions can replace some discount logic; Flow can automate; B2B can replace bespoke wholesale portals. For retained apps, confirm Plus compatibility and whether a store switch requires vendor intervention to transfer licenses or data.

For direct integrations (ERP, WMS, PIM, CRM, ESP, 3PL, returns), update API credentials, webhooks, and endpoints to the new store. Validate rate limits and retry policies, especially during launch week when event volume spikes. For Salesforce or other CRMs, ensure bi-directional sync for customer attributes, preferences, and consent is aligned to your privacy model; if you need help, see /integrations/salesforce. Instrument logging and alerting for all middleware so that failures during cutover are immediately visible and recoverable.

Security, Access, and Compliance

Shopify Plus supports SAML SSO and SCIM provisioning for Organization Admin. Integrate identity early to enforce least-privilege roles across stores and environments. Define a credential rotation policy for API keys and webhook secrets. Confirm that data handling for the migration complies with GDPR/CCPA and your internal privacy policies, including secure handling and disposal of migration exports. For B2B, ensure PO numbers, tax exemptions, and terms are handled securely and auditable.

If you use Multipass or external SSO to bring customers into Shopify accounts, validate flows with the new Customer Accounts experience and consider moving to Shopify’s modern customer authentication patterns where feasible.

SEO and Analytics Preservation

SEO continuity hinges on URL stability, metadata parity, and redirect hygiene. Maintain existing handles and collections where possible. When changes are unavoidable, build a complete 301 redirect map and test it exhaustively. Validate canonical tags, hreflang for Markets, and robots directives. Regenerate sitemaps and submit them after launch, but only once DNS is authoritative.

Analytics must remain consistent for trend analysis. Audit GA4, server-side tracking if applicable, Meta Pixel, and other tags in both theme templates and checkout. Ensure enhanced ecommerce events are fired in parity to your current store. Reconcile any changes in cookie consent and CMP behavior; confirm that tags respect consent on both the storefront and checkout.

QA Strategy and Validation

Treat the migration like a release program with structured QA. Build test plans covering catalog integrity, pricing rules, discount application, shipping and tax calculation, customer account creation and login, guest checkout, payment methods, gift cards, returns, and refunds. Include negative tests for edge cases such as oversized carts, split shipments across locations, and B2B payment terms. Validate performance with Lighthouse and Core Web Vitals budgets; optimize theme assets, images, and critical CSS. Conduct accessibility audits to WCAG 2.2 AA using automated tools and manual checks.

Data validation is critical. Reconcile product counts, variant counts, inventory levels by location, discount codes, and customer records between the source and target. Sample order history imports to confirm totals and line items align with legacy records within acceptable tolerances. Run end-to-end integration tests by posting orders and verifying they reach downstream systems correctly.

Cutover Strategy and Downtime Control

Cutover is a controlled changeover from old to new with the least possible risk. Start by lowering DNS TTL 48–72 hours before launch. Plan a content freeze window and a final delta sync. Use a staged cutover: password-protect the new store, run pre-launch smoke tests in production with test gateways, then switch traffic.

Inventory and order integrity require dual-run or careful timing. If your ERP controls inventory, consider temporarily pausing backflush updates from the old store during the switchover and re-enabling once the new store is authoritative. For high-volume merchants, a short checkout pause of 10–20 minutes may be acceptable if it dramatically reduces risk; if not, implement a dual-capture strategy that drains the old store quickly while enabling the new one, recognizing that you’ll need reconciliation logic for orders created during the overlap. For DNS, consider a progressive cutover by geography and monitor error rates and conversion in real time. Confirm payment gateway toggles are active in the new store and disabled in the old to avoid split settlement.

Prepare operational support: staff your war room with engineering, Shopify developers, integration owners, SEO, analytics, support, and finance. Implement real-time monitoring dashboards for traffic, add-to-cart, checkout errors, payment declines, and webhook failures. Assign clear roles for triage and decision-making.

Rollback Plan and Recovery

A credible rollback plan is essential. Define objective triggers that force rollback: sustained error rates above an agreed threshold, payment authorization failures beyond a defined percentage, or critical data corruption in orders. The rollback window should be timeboxed—often 60–120 minutes from the start of cutover—after which data divergence becomes costly.

If you must roll back, revert DNS to the old store, re-enable gateways on the old store, and disable checkout on the new one to prevent order straddling. Capture a complete log of orders processed on the new store during the rollback window and plan reconciliation into the old store via API or as manual fulfillment exceptions. After rollback, conduct a blameless incident review, fix root causes, and schedule a new launch attempt with the plan adjusted.

Effort and Timeline Ranges

Every shopify to shopify plus migration is different, but planning benefits from grounded ranges. The following scenarios assume a focused cross-functional team (solution architect, Shopify developer, data engineer, integration engineer, QA, SEO) and a like-for-like migration unless stated.

These ranges compress with excellent documentation and vendor responsiveness and expand when app replacements, design changes, or data quality remediation enter the scope. For a precise estimate calibrated to your constraints, start a scoping discussion at /services/migrations.

Roles, Ownership, and Governance

Successful delivery hinges on clear ownership. A migration program manager orchestrates the plan and risk log. A solutions architect owns the target design, cutover strategy, and non-functional requirements. Shopify developers build the theme, Functions, and checkout extensions. A data engineer owns extracts, transforms, and loads with mapping and idempotency. Integration engineers rewire external systems and harden webhooks. QA engineers manage test plans, data reconciliation, and performance testing. SEO and analytics specialists maintain discoverability and measurement continuity. Legal/privacy ensure compliance, and support teams prepare macros and processes for launch week.

Governance should include weekly steering with executive stakeholders, a working group cadence for blockers, and documented go/no-go criteria prior to launch.

Communication and Change Management

Proactive communication reduces risk. Internally, publish a migration brief, environment access details, and a runbook including contacts and escalation paths. Hold a dry-run cutover rehearsal to align everyone on timings. Externally, prepare customer communications for any account reactivation, subscription re-consent, or minor changes in checkout behavior. Update help center articles and support scripts. Close to launch, deploy a subtle maintenance banner if you anticipate a brief checkout pause; set clear expectations and timelines.

Checklist Summary

Use this condensed checklist as a final readiness scan before cutover.

  1. Intent and success metrics approved; risk register and go/no-go criteria documented.
  2. Target architecture finalized: org structure, Markets vs expansion stores, B2B scope, checkout extensibility plan.
  3. Theme rebuilt and performance-tested; Functions and checkout extensions validated.
  4. Data migration executed with mapping files; delta plan rehearsed; content freeze scheduled.
  5. Integrations rewired; credentials rotated; webhooks tested; monitoring enabled.
  6. Payments, taxes, and shipping configured and tested; gateways approved in production.
  7. SEO and redirects validated; analytics parity confirmed; consent flows audited.
  8. Access and security established via SSO/SCIM; roles and least-privilege enforced.
  9. Cutover runbook rehearsed; DNS TTL lowered; war room staffed; rollback plan timeboxed.
  10. Customer comms, support macros, and post-launch hypercare plan ready.

Next Steps

A well-structured Shopify Plus migration protects revenue, avoids SEO regression, and unlocks the enterprise controls you need to grow. The right plan starts with your objectives and constraints, then moves through design, build, validation, and a disciplined cutover. To discuss your scope and receive a precise estimate with a delivery plan customized to your stack, get in touch at /services/migrations.

FAQ

Do we need multiple stores on Shopify Plus, or can we consolidate with Markets?

It depends on catalog, operational, and legal requirements. Shopify Markets enables multi-currency, pricing, and localized content in a single store, which reduces complexity and centralizes governance. Choose expansion stores when catalogs differ materially, tax and legal rules diverge significantly, or when operational separation is necessary (e.g., separate warehouses or teams). Many merchants adopt a hybrid: a core global store with Markets plus one or two expansion stores for outliers.

Can we migrate customer passwords and payment tokens?

Customer passwords cannot be migrated between Shopify stores for security reasons. Plan a customer account invite campaign at cutover. Payment tokens are held by gateways and usually cannot be ported across stores; customers will re-enter payment details on their next purchase. Some subscription platforms and gateways support limited vault migrations under strict conditions, but those require early coordination with the providers and are not guaranteed.

What changes in checkout when we move to Shopify Plus?

Plus uses Checkout Extensibility with UI extensions and Shopify Functions for core logic like discounts and shipping. checkout.liquid is not supported for new Plus stores, and Shopify Scripts are replaced by Functions. The result is more robust, upgrade-safe customizations with clearer governance. Plan to rebuild any legacy checkout logic and test parity thoroughly.

How do we avoid SEO traffic loss during migration?

Maintain URL handles and structure wherever possible. For changed paths, implement comprehensive 301 redirects and verify them. Preserve metadata, canonical tags, hreflang for Markets, and robots rules. Delay sitemap submission until DNS has fully propagated. Monitor crawl errors, 404s, and rankings post-launch, and fix redirect gaps quickly. A like-for-like theme migration reduces SEO risk; redesigns should be validated with pre/post benchmarks.

Can we migrate historical orders, and will reports match?

You can import historical orders for reference and reporting, but they won’t be linked to original gateway transactions, and some statuses won’t carry over identically. Reports should match within reason if you maintain source order IDs in a metafield and adjust analytics to account for the new store. Decide how far back to import based on reporting and customer service needs, balancing API cost and utility.

What is a realistic downtime expectation at cutover?

With sound planning, most Shopify Plus migrations can be executed with near-zero downtime. A brief checkout pause (10–20 minutes) during DNS switch and gateway toggling reduces risk but isn’t strictly required. If you must avoid any interrupt, design for a progressive DNS cutover and dual-run inventory/order handling, and budget effort for reconciliation. Always timebox your rollback decision window to limit data divergence.

How do we handle subscriptions during migration?

Subscriptions are the trickiest part of a shopify plus migration. Inventory your subscription app and gateway, confirm support for migration paths, and plan for a re-consent flow if vault migration isn’t feasible. Communicate early and often with subscribers, provide clear steps, and offer incentives. Test end-to-end in staging, including proration, renewals, and cancellation flows.

What team do we need to deliver this migration?

At minimum, you need a program manager, a solutions architect, a Shopify developer experienced with OS 2.0 and Checkout Extensibility, a data engineer for ETL, an integration engineer for external systems, and QA/SEO specialists. For complex scenarios, add a performance engineer and security/privacy lead. If you don’t have these in-house, our team delivers end-to-end programs; start a scope conversation at /services/migrations.

More Migration Playbooks from Bles Software