Shopify deprecated legacy customer accounts on February 26, 2026. They are gone for new stores, no longer get updates or support, and a final sunset date is due later in 2026. Every store still on the legacy version should upgrade to the new passwordless customer accounts now, while the 30-day revert window and a calm timeline are still on your side. For a Canadian merchant, the risk is not the upgrade button itself. It is the handful of things that quietly stop working when you press it, and that most stores only discover after a customer cannot sign in. Here is what changed, what breaks, and how to migrate without a support fire.
Quick answer: new customer accounts sign customers in with a one-time code emailed to them instead of a password, and they live outside your theme in the checkout and accounts editor. The migration is mostly about rebuilding your old theme customizations as app blocks and checking that Multipass, Flow automations, and customer segments are not silently left behind.
01. The Quick Answer
- What changed: legacy customer accounts were deprecated on February 26, 2026, with a final sunset date to be announced later in 2026.
- What replaces them: new customer accounts with passwordless email sign-in, self-serve returns, store credit, and subscription management built in.
- What to watch: Multipass, Flow automations on legacy triggers, and segments using customer_account_status all stop working and cannot be migrated.
- Your safety net: a 30-day revert window after upgrading, best used to test real sign-in and rebuilt app blocks before you rely on it.
02. What Is Changing, and When
On February 26, 2026, Shopify marked legacy customer accounts as deprecated. In practice that means three things: the legacy version is no longer offered to new stores or stores that were not already using it, Shopify has stopped shipping feature updates and technical support for it, and a final sunset date will be announced later in 2026. Nothing broke overnight, which is exactly why it is easy to ignore.
Why it matters: a deprecated system that still works is a trap. It keeps running until the sunset date, then stops, and stores that waited end up migrating under pressure during whatever season the cutoff lands in. Migrating now, while you can revert and test calmly, is far cheaper than migrating in a hurry.
03. Legacy vs New Customer Accounts, Compared
| Factor | Legacy accounts | New accounts |
|---|---|---|
| Sign-in | Email and password, with resets and locked-out customers | Passwordless email and one-time passcode, plus optional Google or Facebook sign-in |
| Where it lives | Built from Liquid templates you edit and maintain in the theme | Managed separately from the theme in the checkout and accounts editor |
| Built-in features | Basic order history and address management | Self-serve returns, store credit, subscription management, reorder, and tracking |
| Customization | Custom Liquid code in customer account templates | No-code app blocks, or the Customer Account API for headless builds |
| Support status | Deprecated: no new features, updates, or technical support | Actively developed, with new features shipped to your store automatically |
Why it matters: the two versions are not just a reskin. Sign-in, where the pages live, and how you customize them all change, so treat this as a small project rather than a settings toggle.
04. What Quietly Breaks When You Upgrade
This is the part most stores get wrong, because the upgrade itself is smooth and the damage shows up later. Shopify lists specific limitations that carry real consequences for a working store. Read this table before you touch the upgrade button.
| Area | What changes |
|---|---|
| Theme customizations | Custom sign-in or registration built in a modal or on a separate page may need to be removed from the theme before you upgrade. Legacy account URLs auto-redirect, but bespoke pages do not carry over. |
| Flow automations | Workflow triggers and automations based on legacy customer accounts are not supported and cannot be migrated to the new version. |
| Customer segments | Segments that use the customer_account_status filter stop working after the upgrade, and there is no equivalent filter for new customer accounts. |
| Multipass SSO | Multipass is not supported on new customer accounts. If you single sign-on customers from an external system, connect your own identity provider instead. |
| Per-market domains | You can use only one customer accounts domain across all markets, even if your store runs multiple international domains. |
| Sign-in page | You can brand the sign-in page with a logo, colors, and fonts, but you cannot add app blocks to it the way you can to the account pages. |
Multipass is the one that catches Plus merchants off guard. If any external membership site, portal, or app signs your customers in automatically, that flow will break unless you connect an identity provider to customer accounts first.
Why it matters: none of these show an error before you upgrade. They only reveal themselves once the new accounts are live, which is why the audit in section six matters more than the upgrade click itself.
05. What Your Customers Actually Gain
The upgrade is not only risk. New customer accounts remove the single biggest source of account support tickets, the forgotten password, by replacing it with a one-time code sent to the customer email. On top of that, customers get self-serve returns, a visible store credit balance they can spend at checkout, and the ability to pause, skip, or cancel Shopify subscriptions on their own, all without a support email to you.
Why it matters: because the account pages are managed outside your theme now, these features keep improving without theme edits, and B2B buyers get a cleaner self-serve experience that pairs well with a proper Shopify B2B setup.
06. How the Migration Works, Step by Step
- Audit your legacy customizations first. Review every legacy customer account template and any .liquid code in templates/customers, plus external links to subscription, loyalty, or returns portals. Note what actually matters so you can rebuild it, and ignore what does not.
- Duplicate your checkout and accounts configuration. Work on a copy so you can stage changes and preview them before customers ever see them. Nothing goes live until you publish and then complete the upgrade.
- Rebuild customizations with customer account apps. Replace legacy Liquid customizations with app blocks that work with customer accounts, filtering the App Store by apps that work with customer accounts. Use the Customer Account API only if you are running a headless or Hydrogen storefront.
- Confirm brand settings, subdomain, and sender email. Checkout and customer accounts share brand settings, so check your logo and colors. Connect a branded subdomain such as account.your-store.com, and make sure your sender email is set up, since the passcode customers use to sign in is sent from it.
- Publish, test the real account URL, then upgrade. Publish the configuration, open the new account URL in a fresh browser tab, and test sign-in, order history, and every app block. Only then complete the upgrade, and keep the 30-day revert window in mind while you monitor.
Why it matters: the stores that migrate cleanly do the audit and the app-block rebuild before they publish. The stores that struggle press upgrade first and reverse-engineer what broke, which is the slower and more stressful path.
07. What Canadian Merchants Should Do Now
Run through this short checklist before you schedule the upgrade. It sorts a five-minute switch from a real project.
- You still sign customers in with email and password. That is the tell of a legacy account. If your store still shows a password field on the account login page rather than a code sent to email, you are on the version being sunset.
- You use Multipass, Flow automations, or custom segments. These are the pieces that silently stop working. A store with none of them can upgrade quickly. A store with all three needs a real project plan before flipping the switch.
- Your account pages have custom Liquid or app tie-ins. Loyalty widgets, wishlist links, and subscription portals wired into legacy templates need an app-block equivalent rebuilt and tested inside the revert window.
- You sell into Quebec or run multiple markets. New customer accounts allow only one accounts domain across markets, so confirm the branded subdomain and language experience work for every market you serve before you commit.
If you are already planning around the checkout extensibility deadline or the Scripts to Functions migration, it is efficient to handle the customer accounts move in the same window, since all three share the checkout and accounts editor.
08. How AtlanticWorks Helps
AtlanticWorks audits what your legacy customer accounts actually rely on, rebuilds the customizations that matter as customer account app blocks, and reconnects Multipass or an identity provider, Flow automations, and segments so nothing goes dark after the upgrade. For stores doing custom or headless work, we handle the Customer Account API side too. If you want the deeper build context, our custom Shopify development guide covers how we scope this kind of work, and the free assessment is where a migration plan starts.
09. Key Takeaways
- Shopify deprecated legacy customer accounts on February 26, 2026, stopped feature updates and support for them, and will announce a final sunset date later in 2026.
- New customer accounts are passwordless: customers sign in with an emailed one-time passcode, with optional Google or Facebook sign-in, and no password resets.
- The upgrade is not just a toggle. Multipass, Flow automations on legacy triggers, and segments using customer_account_status all stop working and cannot be migrated.
- Custom Liquid in legacy account templates does not carry over, so rebuild important customizations with customer account app blocks before you upgrade.
- Shopify gives a 30-day revert window after upgrading. Use it to test real sign-in, order history, and every rebuilt app block on a live store.
- Confirm every figure and behavior in your own admin before you migrate, since Shopify has not yet published the final legacy sunset date.
10. Frequently Asked Questions
Are Shopify legacy customer accounts being removed?
Yes. Shopify deprecated legacy customer accounts on February 26, 2026. They are no longer offered to new stores, and Shopify has stopped shipping feature updates and technical support for the legacy version. Shopify has said a final sunset date for legacy customer accounts will be announced later in 2026, so any store still on the legacy version should plan its upgrade now rather than wait for the cutoff.
What is the difference between legacy and new customer accounts on Shopify?
Legacy customer accounts are built from editable Liquid templates in your theme and sign customers in with an email and password. New customer accounts are managed separately from your theme in the checkout and accounts editor, sign customers in with a passwordless email and one-time passcode, and include self-serve returns, store credit, and subscription management natively. New accounts are customized with no-code app blocks or the Customer Account API instead of theme code.
How do customers sign in to new Shopify customer accounts?
New customer accounts use passwordless sign-in. A customer enters their email address and Shopify sends a one-time six-digit passcode to that address, which they enter to sign in. There is no stored password to reset. You can also enable social sign-in with Google or Facebook. Because the passcode is emailed from your store sender address, that sender email must be set up and accessible before you upgrade.
Does Multipass work with new Shopify customer accounts?
No. Shopify states that Multipass is not supported on the new customer accounts. If your store used Multipass to single sign-on customers from an external system, you need to connect your own identity provider to customer accounts instead. This mostly affects Shopify Plus merchants with a separate membership site or app, and it is the change most likely to be missed before an upgrade.
Can I revert after upgrading Shopify customer accounts?
Yes, for a limited window. Shopify provides a 30-day revert period after you upgrade, which lets you switch back to legacy customer accounts if something is wrong. Once a store passes that window, or once the final sunset date arrives, reverting is no longer an option. Use the revert window to test real customer sign-in, order history, and any app blocks you rebuilt before you rely on it.
Do I lose customizations when I upgrade Shopify customer accounts?
Custom Liquid code in your legacy customer account templates does not carry over, and neither do Flow automations triggered by legacy accounts or customer segments that use the customer_account_status filter. Shopify auto-redirects legacy account URLs such as /account/login to the new pages, but any custom sign-in or registration page you built separately may need to be removed from the theme first. Plan to rebuild important customizations with customer account apps before upgrading.
Is this the same as the Shopify checkout extensibility deadline?
No, they are separate changes that are easy to confuse. Checkout extensibility is about replacing checkout.liquid and Additional Scripts, with a non-Plus deadline in August 2026. The customer accounts deprecation is about moving off legacy account pages to the new passwordless accounts. They share the same checkout and accounts editor, so it often makes sense to plan both migrations together rather than as two separate projects.
Related resources
The other 2026 Shopify deadline non-Plus stores need to plan for
Another legacy Shopify feature being retired in 2026
A feature customers now self-manage inside new customer accounts
How AtlanticWorks scopes app blocks and Customer Account API work
Still on legacy customer accounts?
AtlanticWorks audits your legacy setup, rebuilds the customizations that matter, and migrates you to new customer accounts without breaking sign-in, Multipass, or your automations.
Start the Assessment