There is a banner in your customer accounts settings telling you to upgrade. It does not tell you what you lose.

On February 26, 2026, Shopify's changelog declared legacy customer accounts deprecated. New stores cannot select them. Existing stores not already using them cannot enable them. Feature updates and technical support have stopped. A final sunset date will be announced later in 2026.

So the question is no longer whether to migrate — it is when, and in what order. Below: the features that only exist on the new version, and the six things the Help Center states cannot be carried across. Plus what has to be rebuilt as app blocks when your Liquid customizations do not come with you. Researched September 1, 2026.

The short version

Deprecated February 26, 2026. Sunset date: not yet set. Shopify says it will be announced later in 2026. There is runway, but stores with heavy customization will not be able to rebuild it inside a short notice period.

You can revert within 30 days. The Help Center states this explicitly. Treat those 30 days as your real test window.

Seven features exist only on the new version. Saved payment methods, self-serve returns, store credit, Buy again reordering, B2B, Markets, and post-sign-in homepage redirect. None of them work on legacy.

Six things do not carry over. The two with the widest blast radius are Shopify Flow workflows built on legacy customer accounts, and any customer segment using customer_account_status. Neither migrates, and there is no equivalent filter on the new version.

Customization moves from Liquid to app blocks. Code in your theme's customer templates is not transferred. Equivalent functionality comes from apps that work with customer accounts — 1,396 of which were listed as of September 1, 2026.

What actually changes

From the Help Center's comparison table:

Feature	Customer accounts	Legacy customer accounts
Sign-in	Six-digit one-time code by email, Sign in with Shop, social sign-in with Google or Facebook	Email and password, Sign in with Shop (manually enabled)
External identity provider	Any OAuth 2.0 + OIDC-compliant provider, with SSO across all surfaces	Multipass (no SSO)
Account creation	No separate step. A new email signing in creates a customer in your admin	Customer must register on a separate page or accept an invite
Branding	From checkout settings	From online store theme settings
Customization	App blocks, edited in the visual editor	Liquid code edits, breaks on theme updates
Updating customer info	Customers self-serve their name and email	Customers must contact your support staff
Saved payment methods	Yes	No
Self-serve returns	Yes	No
Store credit	Yes	No
Buy again reordering	Yes	No
Works with B2B	Yes	No
Works with Markets	Yes	No

Two observations.

Several new-version-only features are already prerequisites for other things you may be trying to build. Self-serve returns do not work on legacy customer accounts. Neither does store credit. If you have been trying to set up either and hitting walls, your customer accounts version may be the reason.

Multipass is not supported on the new version. If you have connected your own authentication system to Shopify, you are re-architecting from Multipass to an OAuth 2.0 + OIDC-compliant identity provider connection. This is the least predictable piece of work in the whole migration.

Worth noting on the upside: sign-in sessions persist for up to 365 days, so returning customers are not asked to sign in repeatedly.

The six things that don't carry over

The upgrade guide has a Limitations section. In rough order of operational impact:

1. Flow workflows built on legacy customer accounts

Workflow triggers and automations based on legacy customer accounts are not supported on the new customer accounts. Existing workflows cannot be migrated.

If you have automations like "send a welcome email when an account is created" or "tag customers on registration," inventory them before you upgrade and design replacements first.

2. Segments using customer_account_status

That filter is exclusive to legacy customer accounts and will not behave as expected after upgrading.

More importantly, there are no filters available for the new version of customer accounts. If you segment on "has an account" to target email campaigns, that logic has to be rebuilt on different criteria entirely.

3. Custom sign-in and registration experiences

After upgrading, Shopify automatically redirects all legacy customer account URLs — /account/login and the rest — to the new customer accounts, including hard-coded links in your theme.

But if you built a custom sign-in or registration experience somewhere else — in a modal, or on a page separate from the legacy account templates — you may need to edit your theme to remove those customizations before upgrading.

4. Custom domains per market

You cannot set a custom domain per market for customer accounts pages. Even with multiple international domains configured, customer accounts use one domain across all markets.

If you run example.jp and example.com for different markets, customer accounts will live on one of them for everyone. Check this early if brand consistency across markets matters to you.

5. Multipass

As above: not supported. Use a connected OIDC-compliant identity provider instead.

6. Customization blocks on the sign-in page

You cannot add customization blocks to the sign-in page. What you can change, via the checkout and accounts editor, is the logo, colors, fonts, and a brand image.

Stores that put notices or promotional messaging on the sign-in screen need somewhere else to put it.

Rebuilding Liquid customizations as app blocks

Legacy customer account customizations live in these theme templates. Audit all of them before migrating:

• Customer account
• Customer activate account
• Customer addresses
• Customer login
• Customer order
• Customer register
• Customer reset password

You can review them from the theme editor under Legacy customer accounts, or in code under templates > customers. None of this transfers.

On the new customer accounts, equivalent functionality comes from app blocks, added in the checkout and accounts editor. App blocks inherit the same brand settings — colors, fonts, styling — as checkout, and unlike Liquid customizations they are unaffected by theme updates.

Finding compatible apps

In the App Store, search for the feature you need, click Refine, and under Works with select Customer accounts. As of September 1, 2026, 1,396 apps were listed in the customer account extensions group.

Apps you already run may support the new version. Open the checkout and accounts editor, click Apps in the left sidebar, and find the app — if its blocks offer to be added to Orders, Order status, Profile, or Accounts, that app works with customer accounts.

Widely-used apps that support it

Some of the most-reviewed apps in the customer account extensions group as of September 1, 2026, by use case. All carry the Built for Shopify badge and offer a free plan.

Use case	App	Rating (reviews)
Product reviews	Judge.me Product Reviews App	5.0 (44,419)
Subscriptions	Appstle℠ Subscriptions App	5.0 (8,397)
Subscriptions	Seal Subscriptions App	4.9 (3,003)
Loyalty and points	Smile: Loyalty & Rewards	4.9 (4,231)
Loyalty and points	BON Loyalty	5.0 (1,830)
Order tracking	17TRACK Order Tracking	4.9 (3,968)

Ratings and review counts verified on the Shopify App Store. Check each listing for current pricing and feature details.

If you have been linking out to an external portal, check first whether a Shopify feature or app can provide the same thing. On the new customer accounts, one sign-in unlocks everything — whereas linking to an external portal usually forces additional verification steps.

Where an external link is genuinely necessary, you can add it to the customer account main menu, or use an app to place it in a page body. The Help Center names Shopify Checkout Blocks as an app that can add content blocks, including links, to the order status page.

How the migration runs

The Help Center lays out nine steps. The parts that matter operationally:

Work on a duplicate configuration. Under Settings > Checkout, duplicate your existing configuration and build app blocks and brand settings on the copy. Nothing is customer-facing until you publish.

Publishing does not switch anything over. Even after publishing the configuration, your online store and checkout still link to legacy customer accounts. Only the final upgrade step flips it.

You can test before upgrading. Copy the URL from Settings > Customer accounts and open it in a new tab. The default format is https://shopify.com/{your-store-ID}/account; with a subdomain configured it looks like account.example.com.

Test every sign-in method you offer. Verification code email, social sign-in, and your own identity provider if connected. Note that connecting your own identity provider replaces the default experience entirely — verification code emails and social sign-in are no longer used.

Verify your sender email address. Sign-in codes are sent from it. Get this wrong and customers cannot sign in at all.

Connect a subdomain. The default URL is a shopify.com address containing your store ID. Connecting something like account.example.com puts customer accounts and the order status page on your own domain.

Pre-migration checklist

• Inventory every Flow workflow triggered by legacy customer accounts
• Inventory every customer segment using customer_account_status
• Audit customizations in theme customer templates and Liquid code
• Check for custom sign-in experiences in modals or standalone pages
• If you use Multipass, decide your path to an OIDC-compliant provider
• If you run multiple international domains, choose the single one customer accounts will use
• Decide where sign-in page messaging will move to
• Check in the editor whether your installed apps support customer accounts
• Confirm your sender email address is valid and monitored
• Preview and run sign-in tests on the duplicated configuration
• Plan to complete validation inside the 30-day revert window

Bottom line

Three decisions:

1. Audit Flow and segments first. This is the only area of the migration with no replacement provided. Workflows do not migrate, customer_account_status segments do not work, and no equivalent filter exists on the new version. Migrate without mapping this and your email targeting and tagging quietly stop working.

2. Assume Liquid customizations become app blocks. Code in your customer templates is not carried over. Find the apps that cover each function, build them into the duplicated configuration, then upgrade.

3. Use the 30-day revert window as a real test period. Watch sign-in rates, cart abandonment, and the shape of your customer support inbox. It is enough time to catch behavior you did not anticipate.

The sunset date is due to be announced later in 2026. Stores with more customization need more preparation, so start the audit now rather than when the date lands.

Specifications may change. Verify current details on the Shopify Help Center and the Shopify Changelog.