Legacy Customer Accounts on Shopify [506K-Store Study]

Shopify deprecated legacy customer accounts, but 40.9% of 506,321 classified stores still use them. We show where migration risk is highest.

StoreInspect Team
StoreInspect Team
April 16, 202610 min read

Legacy customer accounts on Shopify study

TL;DR

  • Shopify officially deprecated legacy customer accounts on February 26, 2026, but 207,334 of 506,321 classified stores in our dataset still use them.
  • That means 40.9% of classified Shopify stores still rely on the old account model, while 57.1% use the newer customer accounts experience.
  • Legacy usage is higher in more complex stores, not lower: 45.4% of Shopify Plus stores and 46.0% of paid-theme stores still run legacy accounts.
  • Among stores with 50K+ monthly traffic, legacy adoption rises to 46.3%. At that tier, the migration is rarely a simple settings change.
  • We found 45,873 high-complexity legacy stores that combine legacy accounts with 50K+ traffic, paid or custom themes, and 5+ apps.
  • The migration is not just about sign-in. Shopify says legacy account URLs redirect after upgrade, apps or Liquid customizations on account pages do not carry over automatically, and customer accounts are not compatible with pixels.
  • For agencies, theme developers, and app teams, the real opportunity is not "all legacy stores." It is the subset with mature stacks, paid themes, strong tracking setups, and existing Shopify Plus signals.

Legacy customer accounts on Shopify are deprecated, but they are far from gone. The official Shopify guidance explains how to upgrade, yet it does not answer the operational question agencies and app teams actually care about: how many stores still use legacy customer accounts, and what kind of stores are they?

We analyzed 506,321 Shopify stores with a classified account setup to answer that directly. The headline is simple: legacy customer accounts are still common, and they are disproportionately concentrated in more complex stores with paid themes, custom themes, deeper tech stacks, and stronger Shopify Plus upgrade signals.

How We Classified Customer Account Modes

We classify a store's account setup by checking public account entry points and storefront behavior. That includes whether /account/login resolves to a password-based login, an email one-time-code flow, a newer account subdomain flow, or a disabled account state.

MetricValue
Total stores in database528,527
Stores with classified account type506,321
Coverage of full database95.8%
Legacy accounts207,334
Customer accounts289,023
Accounts disabled9,964

What we can detect: storefront-visible account behavior, theme type, estimated traffic tier, detected apps, detected pixels, Shopify Plus signals, and lead-fit proxies.

What we cannot detect: backend-only identity systems, every app block configured inside the checkout and accounts editor, or whether a merchant has already rebuilt some legacy account functionality in a custom app.

For broader context on how these stores differ by maturity, compare this dataset with our Shopify store benchmarks, theme performance study, and tech stack by growth stage analysis.

Legacy Customer Accounts on Shopify Are Still Common

Shopify's February 26, 2026 changelog made the direction clear: legacy customer accounts are deprecated, no longer available to new stores, and no longer receive feature updates or technical support. But deprecation is not the same as disappearance.

Account typeStoresShare of classified stores
Customer accounts289,02357.1%
Legacy customer accounts207,33440.9%
Disabled accounts9,9642.0%

Two implications matter.

First, this is not a small long-tail cleanup problem. Four in ten classified Shopify stores still use legacy customer accounts.

Second, the migration window will not hit a random sample of stores. It will hit a large installed base that still includes serious operators using mature stacks with Klaviyo, Judge.me, Smile.io, Gorgias Chat, Rebuy, Google Analytics, Google Tag Manager, and Meta Pixel.

If you want the broader checkout-side deadline context, read our separate Shopify checkout migration guide. This post is specifically about the customer account layer.

Who Still Uses Legacy Customer Accounts on Shopify

The obvious assumption is that legacy accounts mostly survive on low-end stores that have not touched their setup in years. The data does not support that.

Legacy share rises with traffic

Traffic tierClassified storesLegacy storesLegacy share
Under 50K333,181127,16738.2%
50K-200K164,45076,00146.2%
200K-1M8,6454,14648.0%
1M-5M411843.9%
5M-20M4250.0%

Once stores cross 50K monthly traffic, legacy usage jumps from 38.2% to 46.2%. That is the opposite of what you would expect if legacy accounts were mostly a low-sophistication artifact.

This matters because the same traffic tiers also carry more paid media, more pixel complexity, and more customer-experience tooling.

Theme typeClassified storesLegacy storesLegacy share
Free243,96087,31935.8%
Paid166,67276,66046.0%
Custom95,68943,35545.3%

Legacy accounts are much less common on free-theme stores and much more common on stores running paid or custom themes. That lines up with what theme developers already see in practice: the trickiest migrations are not usually on a basic Dawn setup. They are on brands running themes like Prestige, Impulse, Broadcast, Warehouse, or Enterprise, often with extra account links, custom navigation logic, and adjacent app dependencies.

If your work is theme-focused, that is a strong signal to prioritize stores with premium theme footprints or redesign signals. Our find Shopify stores that need a redesign guide pairs well with this account migration angle.

Shopify Plus stores are more likely to remain on legacy

PlanClassified storesLegacy storesLegacy share
Shopify Plus211,94296,23545.4%
Standard Shopify294,379111,09937.7%

Almost half of classified Shopify Plus stores still use legacy customer accounts. That does not mean they ignored Shopify's roadmap. It means many high-value stores had reasons to stay put: existing Multipass flows, custom account page logic, B2B edge cases, or app dependencies that were easier to defer than rewrite.

That is why this topic sits next to, but does not overlap with, Shopify Plus upgrade signals and Shopify B2B features by plan. Plus adoption and customer account modernization are related, but they are not the same project.

Why Legacy Customer Accounts Persist in More Complex Stores

The simplest way to see the pattern is to compare the average complexity of new-account and legacy-account stores.

Account typeStoresAvg appsAvg pixelsAvg lead scorePlus ratePaid/custom theme rate
Customer accounts289,0234.46.070.339.0%46.8%
Legacy customer accounts207,3344.86.976.546.4%57.9%
Disabled accounts9,9643.05.265.030.3%70.3%

Legacy-account stores run more apps, more pixels, and score materially higher on our lead-fit model than stores already on customer accounts. They also skew harder toward paid/custom themes.

At 50K+ traffic, the gap stays real:

Account typeStores at 50K+ trafficAvg appsAvg pixelsAvg lead scorePlus rate
Customer accounts90,2758.210.296.793.0%
Legacy customer accounts80,1678.110.497.293.4%
Disabled accounts2,6986.710.093.986.8%

At that point, new-account and legacy-account stores look similarly sophisticated. The difference is not maturity. The difference is migration status.

The highest-concentration categories are mainstream DTC categories

CategoryClassified storesLegacy storesLegacy share
Beauty26,37412,63047.9%
Baby & Kids5,4942,55446.5%
Food & Beverage31,06014,34146.2%
Jewelry17,3387,58043.7%
Health & Wellness13,5135,88343.5%
Fashion74,06130,73441.5%

These are not obscure edge categories. They are core Shopify verticals where stores often combine email marketing, reviews, loyalty, support, upsell, and increasingly analytics.

If you want category examples to inspect manually, our top Shopify stores directory is a useful starting point, especially in fashion and beauty.

What Actually Changes When You Leave Legacy Customer Accounts

This is where the Shopify docs matter more than generic migration blog posts.

According to Shopify's help documentation, customer account theme docs, and customer account extension docs:

  • Legacy customer accounts were deprecated on February 26, 2026.
  • Shopify automatically redirects legacy account URLs like /account/login after upgrade.
  • Apps or Liquid customizations added to legacy customer account pages do not carry over automatically.
  • Customer accounts support one-time-code sign-in, optional social sign-in, store credit, self-serve returns, and stronger native support for B2B.
  • Customer accounts are not compatible with pixels, which catches a lot of teams off guard.
  • Multipass is not supported in customer accounts, though Shopify Plus stores can connect their own identity provider.

Old model versus new model

AreaLegacy customer accountsCustomer accounts
Sign-inEmail + passwordEmail one-time code, Shop recognition, social sign-in
Theme behaviorHeader link usually goes to a login pageshopify-account component can open an account sheet in the storefront
Customization modelTheme templates, Liquid edits, older app hooksApp blocks in the checkout and accounts editor, customer account UI extensions
Built-in featuresMore limitedStore credit, self-serve returns, B2B-oriented features
Tracking compatibilityLegacy patterns often relied on storefront scriptsCustomer accounts are not compatible with pixels
Identity caveatMultipass supportedMultipass not supported

For theme developers, the important shift is the account component. Shopify's theme docs note that stores using customer accounts can use the account component to open an account sheet directly from the storefront, while legacy stores still link to the sign-in page. That changes header behavior, account discovery, and the migration checklist for themes that previously treated the account link as a basic URL.

For app teams, the key replacement layer is customer account UI extensions plus app blocks inside the checkout and accounts editor. Shopify's customer accounts app guide explicitly supports customer-account app blocks on order, profile, and related account pages, and even supports full-page customer account extensions for use cases like loyalty, wishlists, returns, and subscriptions.

For merchants, the main trap is assuming the upgrade is "just a toggle." It is only a toggle if you were barely customizing accounts in the first place.

Which Legacy Stores Should Treat This as an Urgent 2026 Migration

Not every legacy store deserves the same priority. The migration risk clusters in a few clear cohorts.

CohortStoresShare of legacy stores
All legacy customer account stores207,334100.0%
Legacy stores at 50K+ traffic80,16738.7%
Legacy Shopify Plus stores96,23546.4%
Legacy stores on paid or custom themes120,01557.9%
Legacy stores with 5+ apps83,97140.5%
Legacy stores with 5+ pixels139,38467.2%
High-complexity legacy stores: 50K+ traffic + paid/custom theme + 5+ apps45,87322.1%
Legacy Plus stores with 10+ apps30,37514.7%

That 45,873-store high-complexity cohort is the real migration market. These are the stores most likely to have:

The practical prospecting angle

If you already use StoreInspect, a practical filter for agency outreach is:

legacy customer accounts + 50K+ traffic + paid/custom theme + 5+ apps

That gets you close to the highest-risk migration segment without needing perfect backend visibility.

From there, segment the list:

  • Theme agencies: prioritize legacy stores on paid themes or custom builds, then inspect headers, account navigation, and profile/order page UX.
  • App teams: prioritize merchants whose old account experience depended on apps, then verify whether your app already exposes customer-account blocks or a customer account extension.
  • Retention/CX consultants: prioritize stores with bigger review, loyalty, and support stacks because they have more customer-facing account surface area to recreate.

If you want fast examples to inspect, the StoreInspect themes, apps, and pixels directories are a quick way to sanity-check what a merchant's broader stack looks like before you pitch the migration.

This is also one of the few migration topics where the data directly supports consultative selling. "Shopify deprecated legacy customer accounts" is weak outreach. "You are in the 22.1% of legacy stores that also have high traffic, a paid/custom theme, and 5+ apps" is much stronger.

Legacy Customer Accounts FAQ

What are legacy customer accounts in Shopify?

Legacy customer accounts are Shopify's older account system, the one centered around email-and-password login pages and theme-managed account templates. Shopify now calls the newer version simply "customer accounts."

Has Shopify already deprecated legacy customer accounts?

Yes. Shopify announced the deprecation on February 26, 2026. Legacy customer accounts are no longer available to new stores and no longer receive feature updates or technical support.

Are legacy customer accounts still working right now?

Yes. Deprecation did not mean immediate shutdown. Our dataset shows 207,334 classified stores still using legacy customer accounts, which is 40.9% of classified stores.

What is the difference between legacy customer accounts and customer accounts?

The biggest differences are the sign-in model, the customization layer, and the built-in features. Customer accounts use one-time-code authentication and app-based extensibility, while legacy accounts depend more on theme templates, passwords, and older customization patterns.

Do legacy customer account URLs keep working after migration?

Shopify says legacy account URLs such as /account/login are automatically redirected after you upgrade. That helps preserve entry points, but it does not recreate any custom account-page behavior you previously built.

Do apps and theme customizations carry over automatically?

No. Shopify's help docs are explicit here: apps or Liquid customizations added to legacy customer account pages do not carry over automatically. Merchants need to rebuild the desired experience using app blocks, customer account extensions, or new app-compatible patterns.

Do pixels work inside customer accounts?

No. Shopify states that customer accounts are not compatible with pixels. That does not mean all storefront tracking disappears, but it does mean teams should not assume their old account-page tracking setup maps cleanly into the new environment.

Does Shopify Plus make this migration easier?

Not automatically. Plus stores have more flexibility, and they can connect their own identity provider, but our data shows 45.4% of Plus stores still use legacy customer accounts. In practice, Plus migrations are often more complex because the stores themselves are more customized.

Is Multipass supported in customer accounts?

No. Multipass is a legacy-account capability and is not supported in customer accounts. That is one reason some higher-complexity stores deferred migration.

Which stores should migrate first?

The highest-priority group is the set of legacy stores with 50K+ traffic, paid or custom themes, and 5+ apps. We found 45,873 stores in that segment. Those stores have the most customization risk and the most business impact if the migration is handled poorly.

Key Findings Summary

FindingWhy it matters
40.9% of classified stores still use legacy customer accountsThis is still a major installed base, not a fringe holdout segment
Legacy share rises to 46.2% at 50K-200K trafficThe migration issue gets more important as stores get more mature
45.4% of Shopify Plus stores still use legacy accountsHigh-value stores have not moved en masse
57.9% of legacy stores run paid or custom themesTheme-level migration work is a major part of the opportunity
45,873 stores match the high-complexity legacy profileThis is the clearest agency and app-team target list

If you want the short version, it is this: Shopify deprecated legacy customer accounts, but the stores still using them are often the ones with the most customization work to unwind. That is why this is a real migration market, not just a documentation update.

Share this post

Find Shopify Clients Worth Your Time

Search by niche, traffic, and tech stack. Export with verified founder contacts.

Related posts