Shopify Customer Accounts Migration: Legacy Is Deprecated

You opened a notice that legacy customer accounts are going away, and you're not sure what to do. Or you spun up a new store this year and the old account option simply wasn't there. Or your loyalty widget and custom login live on the old /account pages, and you don't know what survives a switch. Or you haven't moved yet because you're afraid customers will complain about login codes once you do. Legacy customer accounts are Shopify's original, password-and-Liquid version of the account pages, and they were deprecated in February 2026. This guide is the triage: what changed, what still works, what breaks when you switch, and exactly how to move — in merchant language, not developer docs.

What Actually Changed — and What Still Works Today

Deprecation is not the same as removal. Legacy customer accounts still function today, but three things changed at once. New stores can no longer enable legacy accounts at all — the option is simply no longer available to them. Existing stores that weren't already using legacy lost access to it too. And across the board, Shopify stopped shipping feature updates and technical support for the old version. In Shopify's own words, legacy accounts are “no longer available to new stores and existing stores not using it,” and Shopify “will stop providing feature updates and technical support for this older version.”

What's not set is the ending. Shopify says a final sunset date “will be announced later in 2026,” and as of July 2026 that date still doesn't exist — there's no tier-specific deadline and no announced extension. That gap is exactly what this guide is built around: the migration path itself is evergreen and holds whenever the date lands, while the countdown to sunset is the part that expires. Here is the sequence so far.

One more source of confusion is worth clearing before you plan anything, because it sends merchants chasing the wrong deadline.

Legacy vs New Customer Accounts: What Actually Changes

Shopify publishes a side-by-side comparison of the two versions. The differences fall into two groups: how the experience works day to day, and which features exist at all. This table is the full official comparison — scan it for the rows that describe your store.

Source: official feature comparison on Shopify Help Center — compare customer account features.

The bottom half of that table matters for revenue, not just experience: saved payment methods, self-serve returns, store credit, Buy-again reordering, B2B, and Markets are all things legacy accounts simply can't do. B2B is the sharpest case — you can't use legacy accounts for B2B customers and orders at all, and B2B is included at no extra cost on the Basic, Grow, Advanced, and Shopify Plus plans, not just Plus. If wholesale is your model, our guide to B2B on Shopify Plus covers where company-level logins and org SSO live in the native B2B stack.

The Login Change Your Customers Will Notice

The single most visible change is sign-in. New customer accounts are passwordless: a customer enters their email and receives a one-time six-digit verification code, and no password is required. They can also use Sign in with Shop — automatic for stores on Shop Pay or on the Shopify, Advanced, or Retail plans — or a saved passkey. This is genuinely divisive. Merchants worry aloud about deliverability and friction: what if the code lands in spam, or the email is slow? It's a fair concern, and the honest counter comes from Shopify's own team.

Who’s in the Blast Radius: What Breaks When You Switch

For most stores, the upgrade is uneventful. But four situations carry real work, and it's worth naming which one is yours before you touch the toggle.

Start with what survives, because it's more than merchants expect. Existing customers keep their records — order history and saved addresses are supported on both versions, so nobody re-registers and there's nothing to re-invite. Customers sign in with the same email they always used; only the method changes. And your /account links keep working: Shopify automatically redirects all legacy customer-account URLs, such as /account/login, to the new pages, including hard-coded links in your theme. Because that redirect is at the URL level, account links inside notification emails resolve too — you don't have to rewrite them.

What doesn't survive is customization. If you built a custom sign-in or registration experience — in a modal, or on a page separate from the legacy templates — you have to remove it from your theme before upgrading. And the Liquid account templates themselves are on the clock: a Shopify product manager confirmed exactly which files, and what happens to them.

That scope matters: it's those three named files, not every template in your theme, and the detail lives on the developer community, not the main changelog. Anything those files rendered has to move into a customer account UI extension, which gives a developer fixed slots on the Order and Profile pages rather than a blank Liquid canvas. On Multipass, Shopify is explicit: “Multipass isn't supported on customer accounts. If you need to use your own identity provider, then you can connect it to customer accounts” — a connection that requires Shopify Plus. One wording clash is worth untangling: Multipass has always signed customers in from another site, but, as the comparison table above notes, it never delivered true single sign-on across every surface — and that is exactly what connecting an OAuth/OIDC identity provider on new accounts adds. If you don't need single sign-on, customers simply sign in directly with a one-time code instead.

If your account area also gates members-only content or a customer portal behind login, that build is its own project rather than part of this switch — our guide to a Shopify members-only store covers it. And a fully headless storefront is a deeper rebuild: authenticated actions move to the Customer Account API, which sits in custom Shopify development territory.

How Big Is Your Migration? Find Your Route

You've seen what changes and what breaks. Now match it to your store. These five questions ask what lives on your account pages, how customers log in, and how exactly the old experience has to be preserved — and route you to the effort that fits, from “flip it this afternoon” to “this one needs a developer.”

Your Step-by-Step Migration Path

Whichever route fits, the workflow is the same shape: find what you have, rebuild it the right way, test on a copy, then flip. The one step that splits by route is step 3 — switch-ready readers have little to replace, app-swap readers install and confirm extensions, and rebuild readers hand their audit to a developer. You have a 30-day window to revert if something is wrong, but testing first is what keeps you from needing it. Tick each step off as you go; your progress saves on this device.

What a Rebuild Costs and How Long It Takes

There's no license fee for new customer accounts — the system is free, and the cost is entirely the development time to rebuild any custom functionality. Honest price data is thin, so treat the figures below as orientation from individual agencies, not a market rate; the more custom your account pages, the more the fix costs. The four rows map onto your quiz route — the toggle is switch-ready, the app swap is the app route, and the last two are both the developer rebuild (one custom page versus a Multipass, headless, or full migration).

Dollar and hour ranges are individual agencies' published estimates (ShopExperts substantial-feature bracket; PowerCommerce developer-hours and small-store timeline), not a market benchmark. App prices vary by vendor and tier.

DIY or Developer: Where the Line Falls

Cost tells you how much; this tells you who. The boundary between a job you finish in your admin and one that needs a developer is sharp, and getting it right saves you either an unnecessary invoice or a stalled migration. Pick the lowest route that faithfully reproduces what you had.

The Plus question is where merchants trip. To be precise: Shopify has not published a Plus-plan restriction specific to custom-built customer account UI extensions. What is Plus-gated are three nearby things people conflate with it: connecting your own identity provider, the checkout Branding API, and checkout UI extensions for the information, shipping, and payment steps. None of those is the customer-account UI extension itself. In plain terms: on any plan you get the upgrade toggle, your branding from admin settings, and vendor apps; you only need Plus to connect your own identity provider (or for checkout-API-level branding). Since building one of these extensions means a real app — scaffolded with the Shopify CLI, compiled under a strict bundle limit — it's squarely developer work regardless of plan. Watch two minutes of the walkthrough below to see why this is a developer's job and not a toggle, even if you don't write a line of it yourself.

How to Scope a Developer Brief

If your route is a rebuild, a tight brief keeps the quotes comparable and the cost honest. You already have the raw material in your migration audit. A workable brief lists:

1. Every custom account feature to rebuild, straight from your audit in step 1.
2. The exact behavior each one needs — what it showed, where, and under which conditions.
3. Whether you need Multipass replaced with a connected identity provider (this requires Plus).
4. Whether your storefront is standard or headless, since headless auth is a deeper rebuild.
5. The sign-in and account scenarios a developer should test before you sign off.

Hand that list over and ask for a fixed scope against it, not an open-ended hourly estimate. For the full process of finding, vetting, and briefing someone, see our guide to hiring a Shopify developer.

Why “Wait for the Date” Is the Losing Move

The temptation is to wait for a hard date. It's the wrong read. Legacy accounts already receive no feature updates and no technical support — that's not a future risk, it's the state today. Stores that upgrade now do it on their own schedule, with a real test window; stores that wait will do it in a rush when the date drops. And the destination is where the ecosystem already is: over 70% of Shopify merchants already use customer accounts, and 800+ apps have already built extensions for them.

None of that makes the new accounts perfect, and it's fair to say so. The most common criticism from Plus merchants is that the deep customization they get in checkout doesn't carry over to customer accounts.

That's a real limitation, not a dealbreaker — branding still carries your logo and colors from checkout settings, and the gap narrows as the platform matures. The point stands: the move is inevitable, the tools are ready, and going early is the only version of this you get to control.

The Bottom Line

The trap is waiting for a date. Legacy is already frozen — no fixes, no support — and the sunset will land “later in 2026” with no runway once it does. Starting today buys you the one thing a forced deadline takes away: time to test. And the first move costs almost nothing — the step-one audit is about half an hour that replaces “what will break?” with a concrete list you can act on.

Frequently Asked Questions