Legacy Shopify Customer Accounts Are Deprecated: A Migration Playbook for Subscription, SSO and B2B Stores

Shopify legacy customer accounts are deprecated. If your store runs subscriptions, a loyalty programme, a B2B portal or single sign-on, that one line in the February 2026 changelog is a bigger deal than it looks. The login flow your customers use every day is now on borrowed time, and the migration touches far more than the login page.

Most of the coverage so far explains the mechanics of the upgrade button. Very little of it tells a subscription or loyalty brand what will actually break, in what order, and how to sequence the work. This is that playbook.

What deprecated means for Shopify legacy customer accounts right now

On 26 February 2026 Shopify published the legacy customer accounts deprecation notice. Three things changed. Legacy accounts are no longer available to new stores, or to existing stores that were not already using them. Shopify will not ship feature updates or provide technical support for them. And a final sunset date will be announced later in 2026. As of October 2026 that date has still not been published.

So nothing has been switched off yet. But you are running an unsupported login system, and the clock is set by Shopify, not by you. There is one safety net worth knowing about: after you upgrade to the new customer accounts, you have a 30-day window to revert. After that the switch is permanent.

The scale of exposure is not trivial either. A StoreInspect sample of roughly 107,000 Shopify domains taken in early September 2026 found legacy account signals on about 10 percent of stores running paid themes, against roughly 2 percent of stores on free themes. Paid themes correlate with customisation, and customisation is exactly what makes this migration hard.

What breaks in a Shopify new customer accounts migration

The new customer accounts run on a Shopify-hosted domain, use passwordless one-time codes by default, and do not render your theme's Liquid. Every customisation that depended on the old account pages being part of your theme needs rethinking. The common casualties:

Custom Liquid account templates. Order history tweaks, bespoke address forms, reorder buttons, custom dashboards. None of it carries over. The new accounts are extended through customer account UI extensions built by apps or by a developer, not through theme files.Multipass and SSO. Multipass is closed to new stores. Stores that were already using it keep access after they upgrade, but it is a dead end for new integrations. Shopify Plus stores can connect their own OpenID Connect identity provider instead, which is now the supported route for enterprise SSO.Headless storefronts. Shopify explicitly recommends that custom storefronts using Storefront API customer-scoped mutations move to the Customer Account API. The old storefrontCustomerAccessTokenCreate mutation was already deprecated in API version 2025-01. If your Hydrogen or custom front end still logs customers in the old way, this is a rebuild, not a toggle.Subscription and loyalty app sessions. Customer portals that relied on the legacy account session need re-linking. Skio, for example, documents adding its login link to the new accounts navigation so subscribers do not face a second sign-in. Loyalty apps that injected points balances into the old account page need their account extension enabled instead.Flow automations and hard-coded links. Shopify redirects the old /account URLs automatically, which is helpful. But Flow triggers and app logic that assumed legacy account events may need checking.

B2B is the exception that forces the issue. Shopify's own documentation is clear that you cannot use legacy customer accounts for B2B customers and orders. If you have been putting off native B2B because of the account change, the two decisions are now the same decision. We covered the wider trade-off in our piece on native Shopify B2B versus wholesale apps.

Why a theme update can silently switch your accounts

This is the part that catches established stores out. On 30 July 2026 Shopify made the shopify-account header component a Theme Store requirement and dropped the requirement for themes to include legacy account template files. The consequence: a store on legacy accounts that updates to, or installs, a theme without those legacy templates is upgraded to the new customer accounts automatically.

In practice that means a routine theme version bump, done by a junior marketer on a Friday afternoon, can flip your login system without anyone deciding to migrate. If your subscription portal or SSO is wired to the old accounts, customers find out before you do. Before any theme update on a legacy-accounts store, check whether the new version still ships the legacy templates. If it does not, treat the update as the migration itself and plan accordingly. This is one of the reasons we insist on staging and a checklist for every Shopify theme change we ship.

If a theme update can trigger the switch, your migration date is whenever someone next clicks Update. Pick the date yourself instead.

Work out your risk tier before you touch anything

Not every store faces the same job. We sort clients into three tiers, and the tier decides the plan.

Tier 1: low complexity

Standard theme, no custom account Liquid, no SSO, apps that already support the new accounts. The upgrade is a settings change plus a test pass. Budget a day, including checking app portals and updating any hard-coded account links in emails and footers.

Tier 2: subscriptions and loyalty

You run Recharge, Skio, Bold, Smile, LoyaltyLion or similar, and the account page is where customers manage renewals and points. Confirm each app's new-accounts support, enable its customer account extension, map the navigation links, and test the full subscriber journey on a development store first. If you are weighing a subscription platform change at the same time, our comparison of Recharge, Skio and Bold is a useful starting point. Allow one to two weeks with proper testing.

Tier 3: SSO, headless or B2B

Multipass integrations, a Hydrogen or custom storefront using Storefront API customer mutations, or a B2B portal. This is development work: an OpenID Connect provider for Plus stores, a Customer Account API implementation for headless, and a company and location model for B2B. Expect several weeks, and treat it as a project with a proper discovery phase. Our Shopify migration services team scopes this kind of work regularly, and the honest answer is that the effort varies a lot depending on how much custom code is involved.

The migration checklist

Confirm which account version you are on under Settings, then Customer accounts. Record the date.Inventory every account dependency: theme templates in the customers folder, apps that render on account pages, Flow automations, SSO, headless code and hard-coded account URLs in emails and content.Check each app's documentation for new customer accounts support and its account extension. Note anything that lacks one.Freeze theme updates on the live store until the migration is scheduled, so an update cannot trigger the switch early.Rebuild custom account functionality as customer account UI extensions, or decide what you can live without.Replace Multipass with an OpenID Connect provider if you are on Plus, or confirm your existing Multipass access carries over.Test on a development store: login codes, order history, address changes, subscription management, loyalty balances, B2B company switching, and every redirect from an old account URL.Upgrade in a quiet trading window, monitor support tickets and login success for the first fortnight, and use the 30-day revert only if something is genuinely broken, not as a plan.

The upside most merchants miss

It is tempting to treat this as pure maintenance cost. It is not. Passwordless login removes one of the most common friction points in the post-purchase journey, and customers who can actually get into their account reorder more often. Shop Pay and the new accounts share identity, so returning customers are recognised across checkout and account. For a brand with repeat purchase at the heart of the model, that is a conversion lever, not just a compliance task.

We have argued before that most stores get customer accounts and loyalty wrong by treating the account area as an afterthought. The forced move is a chance to fix that. The same principle applies here as everywhere else on a mature store: most Shopify brands do not have a traffic problem, they have a conversion problem, and the logged-in experience is part of it.

What to do this week

Find out which account version you are on and whether your next theme update would force the switch. If you are Tier 1, book the upgrade and test it. If you run subscriptions, loyalty, SSO or B2B, write down every dependency before anyone touches the settings, and get the sequencing right.

If you would rather have a senior team run it, we have handled this kind of platform change for UK and international brands from our base in Glasgow for over twelve years, with no juniors and nothing outsourced. Clients on our Conversion Growth Retainer get this type of work planned into their roadmap rather than as an emergency. Either way, get in touch and we will tell you honestly which tier you are in and what it will take.