New vs Classic Shopify Customer Accounts: What Breaks

What Changed With Shopify Customer Accounts in 2026?

Shopify deprecated legacy (classic) customer accounts on February 26, 2026. New stores cannot enable classic accounts. Existing classic stores receive no new features or support on the legacy path. Shopify has stated a final sunset date will be announced later in 2026—plan as deprecation in effect now, with full removal timing still TBD.

Customer records—order history, addresses, marketing consent—persist through upgrade. What changes is authentication and customization: password login gives way to passwordless email OTP, and theme Liquid account templates give way to a hosted account experience plus Customer Account UI extensions.

What Do Shoppers and Merchants Notice After Upgrade?

Shoppers sign in with a one-time passcode emailed to them—not a stored password. The account experience is hosted by Shopify at your configured account subdomain rather than fully theme-rendered pages at /account routes you customized in Liquid.

Merchant-safe setup: configure your account subdomain under Settings → Domains so login links match your brand. Developer step: audit hard-coded /account/login links in theme files, email templates, and marketing automations.

What Breaks When You Upgrade Customer Accounts?

Native B2B buyer features work on new customer accounts. For catalog architecture and wholesale pricing, see the Shopify B2B catalog vs wholesale apps guide—this article stays on account migration mechanics.

What Should Your Pre-Upgrade Inventory Include?

Merchant-safe checklist before you toggle upgrade in admin:

1. List every file under templates/customers/ and snippets that render account UI.
2. Search theme and checkout for hard-coded account URLs and login modals.
3. Confirm subscription, loyalty, and returns apps support new customer accounts.
4. Review Flow workflows and customer segments that reference customer_account_status or legacy account triggers.
5. Document must-keep account UX (order actions, loyalty balance, subscription management) for extension or app mapping.

Developer additions: inventory Customer Account UI extension opportunities, verify shopify-account web component usage on storefront login entry points, and test OTP deliverability (SPF/DKIM) before cutover.

How Do You Rebuild Custom Account UX?

Must-keep custom account UX rebuilds on Customer Account UI extensions—sandboxed React components on the hosted account surface—or certified apps that publish compatible extensions. This mirrors checkout extensibility: Liquid customization sunsets in favor of governed extension APIs.

Which Surfaces Need Extensions vs Apps?

Order actions, loyalty balances, and subscription management each map to an extension target or a certified app. Inventory what classic Liquid pages did, then match each behavior to an extension API or app—not a theme snippet.

For the parallel checkout migration pattern, see the Shopify checkout extensibility guide. For Flow trigger breakage, see the Shopify Flow automations guide. For theme template inventory, see the Shopify theme development guide.

Can a Theme Publish Force the Migration?

Shopify documents that publishing a theme without legacy customer account Liquid files can upgrade stores still on classic accounts. Theme projects are migration triggers—not only the Settings → Customer accounts toggle. Coordinate theme releases with account extension readiness.

What Are Common Customer Account Migration Mistakes?

• Upgrading before rebuilding subscription or loyalty app account links.
• Assuming passwords carry over to the new OTP flow.
• Custom sign-in modals that conflict with automatic URL redirects after upgrade.
• Ignoring Flow segment filters that reference customer_account_status.
• Treating deprecation as distant when theme publish can force migration sooner.

When Should You Bring in a Developer?

Merchants with default account pages and compatible apps may upgrade after a checklist review without custom development. Bring in a Shopify developer when custom customers/*.liquid pages, subscription portals, loyalty widgets, or Customer Account UI extensions are required to preserve revenue-critical account UX.

Zqdo's Perspective

Customer account migrations sit at the intersection of theme inventory, app compatibility, and CX troubleshooting—core Zqdo lanes. We start with the same audit as checkout extensibility: what custom surfaces exist, which apps own them, and whether Flow segments will silently break. Passwordless login also makes email deliverability part of login reliability—an ops detail merchants rarely test until OTP volume spikes.