August 31, 2026

Migrating to Shopify's New Customer Accounts: What Breaks, and How to Rebuild Your Account Pages

Shopify deprecated legacy customer accounts on February 26, 2026. New stores can’t enable them anymore, feature updates and technical support have ended, and Shopify has said the final sunset date “will be announced later in 2026.” In July 2026, Shopify also made the new shopify-account header component a requirement for every theme in the Theme Store — so even theme updates now push stores toward the new system.

If your store still runs legacy accounts, migration is a when, not an if. This guide covers what actually breaks when you switch, and how to rebuild what matters.

Legacy vs. new customer accounts in one minute

Legacy customer accounts live inside your theme. They use Liquid templates (customers/account.liquid, customers/login.liquid, customers/register.liquid), password login, and can be customized with theme code or apps that inject into those templates.

New customer accounts are hosted by Shopify, outside your theme. Customers sign in with a one-time email code (no passwords), the pages match your branding settings, and they get their own subdomain like account.your-store.com. There is no Liquid and no theme code — customization happens through the branding editor and through apps built on customer account UI extensions.

What breaks when you migrate

Here is the full compatibility list, from Shopify’s own migration documentation and from merchants who have been through it:

1. Everything on your old account Liquid templates

Any customization living in customers/account.liquid or the other legacy templates — custom dashboards, extra links, injected widgets, loyalty panels — is simply gone. The new pages are hosted by Shopify and your theme code never runs on them.

2. Apps built for legacy accounts

Apps that render into the legacy account Liquid become incompatible the moment you switch. Check every app that touches your account pages: does it have a version built on customer account UI extensions? If its listing doesn’t mention new customer accounts support, assume it stops working.

3. Passwords — and Multipass

New customer accounts are passwordless: customers sign in with a six-digit code sent to their email. That also means:

4. Shopify Flow automations

Workflow triggers and automations based on legacy customer accounts can’t be migrated. If you have Flow workflows keyed to legacy account events, rebuild them after the switch.

5. Customer segments using customer_account_status

That segment attribute is exclusively for legacy accounts. Segments built on it won’t work as expected after you upgrade — review and rebuild them.

6. Custom sign-in and registration experiences

Custom login/registration forms in your theme must be removed before upgrading. The new sign-in page is Shopify-hosted and — worth knowing — it’s the one page that can’t take customization blocks at all.

What migrates fine

Order history and B2B generally carry over without issues — merchants who have migrated consistently report both working. Your customer data, tags, and metafields are untouched: the account pages change, the customers don’t.

The migration checklist

  1. Inventory your legacy customizations. Open your theme’s customers/ templates and list everything custom. This is your “rebuild list.”
  2. Audit your apps. For each app touching account pages, confirm new-customer-accounts support.
  3. Check Flow and segments for legacy-account dependencies.
  4. Verify your sender email (customers now receive sign-in codes by email — deliverability matters).
  5. Set up branding in the checkout and accounts editor: colors, logo, fonts.
  6. Rebuild your account-page content (next section).
  7. Preview and test the new pages before completing the upgrade.
  8. Optionally connect the account.your-store.com subdomain.

The part nobody warns you about: your new account pages will be empty

After migration, customers get exactly four pages: sign-in, orders, order status, and profile. Clean — and bare. The loyalty info, FAQ, support links, promotions, and custom content your old account page carried are gone, and there’s no theme editor to put them back.

Shopify’s official answer is that extra functionality comes from apps, via customer account UI extensions. That’s the mechanism for putting content back:

You can build extensions yourself if you have a developer. If you don’t, this is exactly what account-page apps are for — Account Blocks (our app — free plan available) lets you rebuild all of the above from the Shopify admin with no code.

When should you migrate?

Now, honestly. The sunset date isn’t announced yet, but every signal points one way: legacy is closed to new stores, unsupported, and themes no longer even ship its templates. Migrating on your own schedule — with time to audit apps and rebuild content — beats migrating during a forced cutover alongside every other remaining legacy store.

The stores that will have the worst time are the ones with the most legacy customization. Which means the best time to inventory and rebuild is before the deadline exists.

FAQ

Do my customers need to create new accounts? No. Customer records, order history, tags and metafields are unchanged. Customers simply sign in with an email code instead of a password.

Can I customize the new sign-in page? No — it accepts no customization blocks. Branding (colors, logo) applies, but no custom content.

Can I still use Liquid on the new account pages? No. There is no theme code on new customer accounts. Customization = branding editor + apps (UI extensions).

Does B2B work? Yes — new customer accounts are actually where Shopify’s B2B features live going forward, and B2B data is available to extensions for conditional content.

What happens if I do nothing? Legacy templates will eventually be locked from editing, then removed, per Shopify’s announcement. At sunset, your store will be moved to new customer accounts — with empty pages — whether you’ve prepared or not.