A Shopify Plus migration for an enterprise brand comes down to five things: an inventory of everything the current store does, a clean data model for products, customers and orders, a plan to rebuild custom checkout and pricing logic on Shopify's current tools, a complete URL redirect map, and a rehearsed cutover with a rollback plan. Most failed replatforms don't fail on the theme. They fail because a pricing rule, an ERP feed or a set of high-traffic URLs was missed. Use the checklist below phase by phase. It's built around those risks.
- Start with an audit of integrations, custom logic and URLs, not with theme design.
- Import data in a fixed order: products first, then customers, then historical orders.
- Customer passwords can't be moved, so plan the account-invite email campaign as carefully as the launch itself.
- Shopify Scripts stopped running on June 30, 2026. Any discount, shipping or payment logic has to be rebuilt with Shopify Functions or apps.
- Redirect every old URL one-to-one with a permanent redirect and keep the redirects for at least a year.
- Run at least one full rehearsal of the cutover before the real one.
Phase 1: Audit Everything the Current Store Does
Enterprise stores do far more than the storefront shows. Over the years they collect custom pricing rules, B2B price lists, ERP and warehouse feeds, tax exceptions, loyalty integrations, marketing tags and one-off scripts someone wrote for a campaign in 2021. If it isn't written down before the project starts, it won't exist on the new store.
Build a single inventory document with an owner for each line:
- Integrations: ERP, PIM, OMS, WMS, CRM, ESP, reviews, search, loyalty, subscriptions, tax and fraud tools. For each one, note the direction of data, the frequency and who maintains it.
- Custom logic: tiered pricing, bundles, free-gift rules, shipping rules by region or weight, payment-method restrictions, B2B terms.
- Content: product pages, collections, landing pages, blog posts, policies, help-centre articles.
- URLs: a full crawl of the current site plus the top landing pages from analytics and Search Console over the last 12 months.
- Tracking: analytics, ad pixels, server-side events and consent tools.
This audit is also your budget. The number of integrations and custom rules drives cost much more than the number of templates. We broke this down in our guide to what an enterprise website really costs.
Phase 2: Map Your Data Model Before You Move a Single Row
Shopify has its own opinions about how products, variants, collections and metafields fit together. Legacy platforms like Magento, Salesforce Commerce Cloud or a custom build often store the same information very differently. Mapping that difference is where enterprise migrations quietly succeed or fail.
Products and catalog
Decide how each legacy attribute will live on Shopify. Will it be a variant option, a metafield, a metaobject or a tag? Products with many attributes need a clear rule so merchandisers can still filter and search. Pay special attention to products missing a variant option, because these often fail on import and need fixing at the source.
Customers
Customer records carry addresses, tags, tax-exempt status and marketing consent. Shopify's documentation is clear that you can't migrate customer passwords from another store using a CSV, so customers must be invited to set new passwords. Consent matters too: only import customers as email subscribers if they actually opted in on the old platform.
Orders and the import sequence
Historical orders keep account history and lifetime-value reporting intact. Import them in the right order so they link correctly:
| Step | Data | Why it goes here | Typical method at enterprise scale |
|---|---|---|---|
| 1 | Products, variants, metafields | Orders reference products, so they must exist first | Admin API bulk operations or a migration app |
| 2 | Customers | Orders reference customers | API or CSV with consent fields mapped |
| 3 | Historical orders | Need both products and customers to link correctly | API import with staff order notifications turned off |
| 4 | Gift cards and store credit | Liabilities finance must reconcile | API, reconciled against the old balance report |
| 5 | Pages, blogs, policies | No dependencies, but feeds the redirect map | API or manual for low volumes |
Phase 3: Rebuild Checkout, Pricing and Promotions on Current Tools
This is the phase where many Shopify Plus checklists online are already out of date. Shopify announced that Shopify Scripts would stop executing on June 30, 2026, with Shopify Functions as the replacement for discount, shipping and payment logic. If you are moving from another platform, don't let anyone propose a Scripts-based solution. If you are consolidating older Shopify stores into Plus, audit every Script they used.
For each custom rule in your Phase 1 inventory, decide on one of three options:
- Native setting: automatic discounts, shipping profiles, B2B price lists and payment customizations often cover more than teams expect.
- App: a maintained app from the Shopify App Store, if its data handling and support terms pass your procurement review.
- Custom Function or app: for logic that is truly yours. Budget for testing, because pricing errors cost real money within minutes.
Checkout branding, extra fields and post-purchase steps are now built with checkout extensions in the checkout editor, separate from the theme. Treat checkout as its own workstream with its own test plan.
Phase 4: Protect SEO With a One-to-One Redirect Map
Shopify uses fixed URL patterns such as /products/ and /collections/, so almost every enterprise migration changes URLs. Google's guidance for site moves with URL changes is to use permanent server-side redirects, send each old URL straight to its final destination, and keep redirects for as long as possible, generally at least a year. It also warns that rankings can fluctuate for a few weeks or more while the site is recrawled.
A few Shopify-specific details matter here:
- Plus stores can hold up to 20 million URL redirects, so volume is rarely the limit. Accuracy is.
- Per Shopify's redirect documentation, a redirect only fires when the old URL is broken. If a live page still exists at that path, the redirect is ignored.
- Fixed paths such as
/productsand/collections/allcan't be used as redirect sources. - Import redirects by CSV and set them up before the domain moves, not after.
Avoid sending discontinued products to the homepage. Point them at the closest category or replacement product instead. Our step-by-step playbook for migrating without losing SEO covers the redirect map, crawl comparisons and Search Console monitoring in more detail.
Phase 5: Rehearse the Cutover, Then Launch
An enterprise cutover is an operations event, not a deploy. Write a runbook with times, owners and go/no-go checks, and rehearse it at least once on a staging store.
- Freeze catalog and pricing changes on the old platform 48–72 hours before launch.
- Run the final delta migration and reconcile counts: products, customers, open orders, gift-card balances.
- Place test orders with every payment method, plus refunds, cancellations and partial fulfilments.
- Confirm ERP, warehouse and tax feeds are processing live orders correctly.
- Lower DNS TTLs in advance, disconnect the domain from the old platform, then connect it to Shopify.
- Spot-check your top 100 URLs for correct redirects and the right status codes.
- Submit the new XML sitemap in Search Console.
- Keep the old platform available in read-only mode for a defined rollback window.
During the cutover, response time matters more than anything else. When we ran a large rebuild for a US home-improvement company, the client's review on Upwork mentioned exactly that: "No matter when I messaged him, he would usually get back to me." That kind of availability should be written into your launch plan, not left to chance.
Phase 6: The First 90 Days After Launch
Launch is the middle of the project, not the end. Plan for three stages of follow-up:
| Window | Focus | What to watch |
|---|---|---|
| Days 1–7 | Stability | Order errors, payment failures, integration queues, 404 logs, customer service tickets |
| Weeks 2–4 | Customers and SEO | Account-invite open rates, login issues, Search Console coverage, redirect gaps |
| Months 2–3 | Performance | Conversion rate by device, Core Web Vitals, app bloat, organic traffic trend versus the old site |
Send account invites in batches rather than all at once. Large sends from a new store can hurt email deliverability, and batches let customer service keep up with password questions.
For Mid-Sized and Small Businesses
The same checklist applies at a smaller scale, just with fewer moving parts. If you have a few hundred products and one or two integrations, you may not need Shopify Plus at all. Standard Shopify plans handle many growing brands well, and Plus starts at $2,300–$2,500 per month depending on term. Focus on the same three risks: a complete redirect map, a correct data import order and a clear plan for customer accounts. Those three protect most of your revenue and rankings, whatever your size.
The Bottom Line
A Shopify Plus migration goes smoothly when you treat it as a business-operations project with a storefront attached. Audit everything the old store does, map the data before moving it, rebuild custom logic on Shopify Functions rather than retired tools, redirect every URL one-to-one, and rehearse the cutover. If you want a developer who has done this and who works with you directly, with no account managers in between, see our Shopify and Shopify Plus development services or how our project process works. When you're ready to scope your migration, talk to us here.
Frequently Asked Questions
How long does a Shopify Plus migration take for an enterprise brand?
Most enterprise migrations take several months from audit to launch. The timeline depends mainly on the number of integrations, the amount of custom pricing and checkout logic, and how many teams must sign off. Catalog size matters less than people expect, because data imports can be automated.
Can we keep our customers' passwords when moving to Shopify Plus?
No. Shopify doesn't allow customer passwords to be imported from another platform. Customers are imported without passwords and receive an account invite to set a new one. Plan the invite emails, the timing and the customer service scripts before launch.
Will we lose SEO rankings when migrating to Shopify Plus?
Some short-term fluctuation is normal while Google recrawls the new URLs, and Google says it can take a few weeks or more on larger sites. Losses that last are usually caused by missing or incorrect redirects, removed content or a broken internal link structure. A complete one-to-one redirect map prevents most of them.
What replaced Shopify Scripts for custom discounts and shipping rules?
Shopify Functions. Shopify Scripts stopped running on June 30, 2026, and custom discount, shipping and payment logic is now built with Functions, native settings or apps that use them.
Should we migrate historical orders or start fresh?
For most enterprise brands, migrate them. Order history keeps customer accounts complete, supports returns and service questions, and keeps lifetime-value reporting accurate. Import orders after products and customers, and turn off staff order notifications during the import.
Do we need an agency to migrate to Shopify Plus?
Not necessarily. What you need is someone who owns the whole plan: audit, data mapping, custom logic, redirects and cutover. That can be an agency, an in-house team or an experienced independent developer working with your team directly. Check that whoever you pick has done a migration with integrations similar to yours.