Legacy Customer Accounts on Shopify [2026 Study]

What the September sample shows

StoreInspect recorded legacy customer account signals on 4,236 store domains in a recent seven-day observation window. Among domains with an identified legacy or newer account mode, the legacy share was 10.0% for paid themes and 2.1% for free themes.

That makes paid-theme stores a useful starting point for agencies researching account migration work. A paid theme does not prove that a merchant has customized their account pages, needs an agency, or intends to buy services. Those questions need a separate review.

The sample contains 107,048 domains with retained account observations dated August 29 through September 4, 2026. We could identify a legacy or newer account mode for 86,501 of them. The remaining 20,547 had inconclusive checks, failed requests, or an unavailable account entry point.

These are results from StoreInspect's recently observed domains, not an estimate of adoption across every Shopify merchant.

Why account migration still matters

Shopify deprecated legacy customer accounts on February 26, 2026. Its announcement says the old version is unavailable to new stores and existing stores not already using it. Feature updates and technical support are ending, with a final sunset date to be announced later in 2026. The announcement does not supply a shutdown date.

Theme work can trigger the change. Shopify says that a legacy-account store upgrading to a theme without legacy account templates will automatically move to the newer customer accounts.

On July 30, Shopify also made its account component a Theme Store requirement for new themes and updates submitted to the store. The component must appear in the header on desktop and mobile. Legacy account templates are no longer required.

For an agency planning a theme update, that is a reason to review the account experience before publishing the theme. For an app developer, it is a reason to check whether an integration depends on legacy Liquid account pages.

How we built the sample

We used dated account observations from StoreInspect's public storefront checks, rather than treating every saved account label as current.

This is an operational sample determined by which domains our collection process checked. It is not a random draw from Shopify's merchant population. Freshness filtering improves the age of the evidence; it does not make the sample representative.

The observation system retains a previous successful classification when a later attempt fails. The timestamp belongs to that retained evidence. This dataset is therefore a set of retained observations within the window, not a log of every request or every store's most recent attempt.

Of the 107,048 domains, 105,889 had a recorded myshopify.com identity, with no repeated identities in that group. The other 1,159 had no recorded identity. Different stores can still belong to the same merchant, so we report domain counts throughout.

Account results and unresolved checks

Legacy detections account for 4.9% of the 86,501 identified modes. We do not assign the 20,547 other domains to either account version. A failed request says nothing about which version a merchant uses, and a missing login page does not establish that the merchant disabled accounts in Shopify admin.

Browser spot checks

On September 5, we rechecked 64 domains selected by a fixed hash within each result group: 20 legacy, 20 newer, and eight from each of the three excluded groups. We visited public login URLs without signing in, submitting forms, or accessing customer data.

All 20 legacy examples displayed a customer login form with Shopify's customer_login form marker and customer email and password fields. All 20 newer examples reached a Shopify-hosted account endpoint or a branded account subdomain with the newer sign-in flow.

The excluded groups showed why missing evidence should stay separate. All eight previously inconclusive examples and seven of eight previously failed requests reached newer account flows on recheck; the remaining failed example did not resolve in DNS. One domain stored as disabled displayed a legacy login form. Others returned missing pages or redirected away from login.

These checks support the interpretation of the sampled signals, but they are a small quality check, not a measured error rate for the full dataset. We did not use them to reweight or silently change the frozen counts.

Legacy signals were more common on paid themes

The paid-theme group had roughly 4.8 times the legacy share of the free-theme group among domains with identified account modes.

The third group needs care. StoreInspect's custom classification also includes modified and unidentified themes. It is not a count of verified bespoke builds. Likewise, the paid classification identifies a theme category, not a verified purchase or the amount a merchant spent.

Theme labels are the stored classifications at extraction. We did not independently re-audit every theme or require its evidence to have the same timestamp as the account check.

The difference also appears when all observed domains are used as the denominator: detected legacy signals occurred on 1.7% of the 70,864 free-theme domains and 8.0% of the 20,113 paid-theme domains. Those figures describe detections only; they do not classify unresolved domains as newer accounts.

For agencies, the practical use is to combine a legacy account signal with theme research, then inspect the actual account journey. Our Shopify redesign prospecting guide covers related checks. Theme category alone cannot establish migration difficulty.

What this study cannot tell you

Public account pages show how a visitor enters the account experience. They do not show a merchant's migration plan, sales, account usage, private configuration, or the cost of rebuilding customizations.

We cannot establish why any store retained legacy accounts. A paid theme might coexist with a basic login page, while a free theme might have extensive custom account work. We also did not measure whether the theme itself caused a merchant to keep legacy accounts.

Domains excluded by the liveness filter were already marked confirmed dead. That does not independently certify every remaining domain as an active Shopify business. Redirects, ownership changes, bot protection, and collection errors remain possible.

This update does not report a migration rate. The April study used a different, broader collection of stored account labels without this observation-date filter. Comparing its percentage with the September sample would mix changes in coverage, classification, and sample composition with any actual merchant migrations.

What to review before upgrading accounts

Start with the account experience customers use today. Check the header link, login screen, account navigation, and any routes into subscriptions, loyalty, returns, or order management. Ask the merchant which features customers rely on before deciding what to rebuild.

Shopify's upgrade guide explains the preparation workflow. Legacy Liquid customizations do not transfer automatically. Teams can replace account features with compatible app blocks and test a prepared configuration before switching the storefront and checkout to it.

Check app dependencies individually

An app detected on a storefront is not proof that it modifies account pages. Use StoreInspect's app directory to research the stack, then confirm the merchant's actual configuration and the app's support for newer customer accounts.

Shopify's customer accounts developer guide describes the extension model for building account features. Do not assume a legacy Liquid integration works unchanged in the newer experience.

Review identity, links, and automations

Shopify redirects standard legacy account URLs after an upgrade, but custom sign-in modals and separate registration pages may need edits. For Shopify Plus stores with an existing Multipass integration, Shopify says the integration continues after upgrading. Contact Shopify Support if the setting disappears; connecting a new identity provider is a separate configuration decision. The upgrade guide also lists limitations affecting legacy account workflows and customer segments.

Test account analytics rather than assuming it disappears

Shopify's July 21, 2025 pixel announcement says web pixels load on customer account and order status pages when accounts use a custom domain. It lists page-view events, the Advanced DOM API, and custom events published through app blocks.

That is different from carrying arbitrary legacy theme scripts into the new account experience. Check the account domain and the events your implementation needs. Shopify also documents publishing analytics events from customer account UI extensions.

Our Shopify server-side tracking guide covers the broader tracking context. This account study does not measure whether a store's analytics setup works.

Using the findings for store research

In StoreInspect's searchable Shopify store database, account and theme signals can help narrow the domains worth checking. The next step is to verify the login experience and ask about the merchant's account customizations.

For outreach, refer to something you confirmed on the store and explain what you would review. Do not tell a merchant that their account setup is broken, that a paid theme makes migration expensive, or that Shopify will shut it down on a date the platform has not announced.

Legacy customer accounts FAQ

What are legacy customer accounts on Shopify?

They are Shopify's older customer account system, built around password-based customer login and theme-managed account templates. The newer system uses a different account experience and extension model.

Has Shopify deprecated legacy customer accounts?

Yes. Shopify announced deprecation on February 26, 2026. The announcement says a final sunset date will be announced later in 2026; it does not give a shutdown date.

How many stores still use legacy accounts?

StoreInspect detected legacy account signals on 4,236 domains with retained observations dated August 29 through September 4, 2026. That is 4.9% of the 86,501 domains with an identified legacy or newer mode in this sample, not an estimate for all Shopify merchants.

Are legacy accounts more common on paid themes?

In this sample, yes: 10.0% of identified account modes in the paid-theme group were legacy, compared with 2.1% in the free-theme group. The comparison uses stored theme classifications and does not explain why merchants chose either account version.

Does a newer account mode mean migration is complete?

A public newer-account sign-in flow does not prove that every customization, integration, or customer journey has been tested. This study did not inspect private configurations or sign in as a customer.

Do account customizations transfer automatically?

Legacy Liquid customizations do not. Review the features that need to survive, find compatible replacements, and test the account experience using Shopify's upgrade guide.

Do web pixels work in newer customer accounts?

Yes, subject to Shopify's documented setup requirements. Shopify's pixel announcement specifies a custom account domain. Do not confuse support for Shopify web pixels with support for arbitrary scripts previously placed in legacy templates.

Update and correction note

Identity and upgrade guidance was rechecked against Shopify's primary documentation on October 10, 2026. This editorial correction does not change the September observation window or counts.

This page was originally published on April 16, 2026 and revised on September 5, 2026. The earlier 40.9% figure described a different dataset of stored account labels and must not be read as a September measurement. The dated cohort above replaces it as this page's main finding. We have removed the earlier Plus and migration-complexity claims because this update does not validate them.

The earlier statement that newer customer accounts are incompatible with pixels was incorrect. Shopify announced account-page web pixel support in July 2025. The analytics section above describes that support and its stated requirements.