Shopify legacy customer accounts are deprecated: a practical migration checklist

Shopify deprecated legacy customer accounts on 26 February 2026. New stores can no longer choose them, and Shopify says a final sunset date will be announced later in 2026. Existing merchants still using the old version therefore have time to prepare, but waiting for a fixed deadline turns a manageable project into a rushed one.

The upgrade is not just a new login page. Legacy accounts live in theme templates and often carry years of small additions: a loyalty balance, subscription link, invoice download, returns entry point, wholesale note, tracking code, or an automation triggered when an account is enabled. The latest customer accounts are managed outside the theme and use app blocks, UI extensions, and Shopify's Customer Account API instead.

That architectural change is useful, but it means old Liquid customizations do not transfer automatically. A safe migration starts with an inventory of what customers and staff actually use, followed by a replacement decision and a staged test.

Why this migration needs an audit now

Shopify has stopped feature updates and technical support for legacy customer accounts. Its deprecation notice also says apps that depend on legacy customer-account Liquid pages will not work on the latest account version. This is the main operational risk: the standard order list may look fine after the switch while a less visible but important function has disappeared.

The latest accounts also change authentication. Customers sign in with a one-time code sent by email instead of a password. Optional Google, Facebook, Apple, and Shop sign-in can sit alongside this passwordless flow. For Plus merchants, an OpenID Connect identity provider can replace the default sign-in experience. These are better options for many stores, but support teams, email delivery, custom SSO, and customer instructions must match the new flow.

Treat the project as a post-purchase journey migration, not a settings toggle. Give it an owner, a test store or draft configuration, a list of customer scenarios, and an agreed rollback window.

Map the current account experience before changing it

Start in the theme editor and inspect every legacy customer-account template: account overview, activation, addresses, login, order, registration, and password reset. Then inspect templates/customers and related snippets in the theme code. Shopify's upgrade guide explicitly recommends reviewing these areas because their customizations do not carry over.

Do not stop at code. Follow the journey like a customer and record each task the account supports:

• Sign in, register, activate an account, and reset a password.
• View orders, fulfillment status, tracking, invoices, or digital downloads.
• Edit addresses, profile data, consent, or company information.
• Start a return, cancel or edit an order, or buy an item again.
• View loyalty points, store credit, memberships, wishlists, or subscriptions.
• Reach support, warranty, repair, or product-care workflows.

For each task, note where it comes from: Shopify, theme Liquid, an app embed, a hard-coded link, an app proxy, or a custom backend. Add the business owner and approximate usage if you can. A rarely used warranty form may still prevent many support tickets during peak season.

Also search notification templates, navigation menus, help pages, QR codes, and external campaigns for /account links. Shopify redirects legacy account URLs after the upgrade, but a custom login modal or registration page outside the normal templates might need to be removed or rebuilt.

Decide what to keep, replace, or retire

Classify every item in the inventory before choosing technology. Keep functions that customers rely on or that save staff time. Replace them with a native Shopify feature where it meets the requirement. Use a compatible app when the workflow is standard and the app owns the operational complexity. Build a customer account UI extension or full-page extension when the workflow is specific to the business.

The latest accounts already support order history, order status, profile management, buy again, store credit, and optional self-serve returns. Apps can add functions such as subscriptions, loyalty, wishlists, downloads, reviews, or order editing. Shopify's customization guide provides a useful capability-by-capability comparison between native features, App Store options, custom solutions, and unsupported behavior.

Retire features deliberately. An old link that nobody owns should not be recreated automatically, but record the decision. This prevents a missing feature from being mistaken for a migration defect after launch.

When evaluating an app replacement, test more than its feature list. Confirm that it supports customer account blocks or extensions, works in every required market and language, exposes the necessary data, and has a workable uninstall path. If a custom extension calls an external system, define authentication, error handling, monitoring, and what customers see when that system is unavailable.

Rework sign-in, links, branding, and email delivery

The default sign-in uses a six-digit code sent to the customer's email address. There is no customer password to migrate. Check that the store's sender email is current, authenticated, and monitored, then test delivery with the main mailbox providers used by your customers. Update support instructions that still tell people to reset a password.

Choose a customer-account subdomain such as account.example.com if it fits the brand and analytics setup. Only one customer-account domain can be used across markets, so stores with separate international domains need to plan navigation and language behavior carefully. Review desktop and mobile account entry points; current Theme Store submissions must use Shopify's account component in the header, but an older or custom theme may need manual work.

Duplicate the checkout and accounts configuration before editing. Apply the logo, colors, fonts, and brand image, add the required app blocks, and check visibility rules by market. The sign-in page allows branding changes, but Shopify does not support arbitrary app blocks there. Keep this boundary in mind when comparing the new experience with a heavily customized legacy login page.

Check automations, segments, data, and analytics

Some dependencies are visible only to staff. Shopify warns that automations based on legacy account triggers cannot be migrated. Customer segments using customer_account_status also stop behaving as expected because that filter belongs to legacy accounts. Inventory these rules in Shopify Flow, email platforms, CRM integrations, support tools, and custom jobs. Replace the business outcome rather than copying an obsolete trigger.

Review any integration that reads customer-scoped data or assumes a legacy login session. Headless storefronts and custom experiences should use the Customer Account API for authenticated customer data and actions. Custom account extensions should use the supported extension targets and session-token model rather than trusting a customer ID supplied in a URL.

Analytics needs a separate check. Shopify says pixel tracking across customer account pages requires a custom customer-account subdomain. Decide which post-purchase events matter, verify consent behavior in every target region, and document expected gaps before comparing data across the launch date.

Build a staged test around real customer scenarios

Shopify lets merchants duplicate an existing checkout and accounts configuration, publish that configuration, preview the new account URL, and only then perform the account upgrade. Use that separation. Publishing the configuration does not by itself switch online-store and checkout links away from legacy accounts.

Create test customers that represent the store's actual edge cases:

• A guest with one order and no prior account.
• A returning customer with several fulfilled and unfulfilled orders.
• A customer with a pending return, store credit, or active subscription.
• A customer using a secondary market, language, or currency.
• A B2B buyer, if the store uses Shopify B2B.
• A customer whose email delivery is delayed or filtered as spam.

Test from storefront entry to completion on mobile and desktop. Verify one-time-code delivery, social sign-in if enabled, order history, address changes, tracking links, invoices, returns, subscription management, loyalty data, support links, and logout. Test app failures as well as success. Check that a customer cannot see another customer's data and that staff can still support the workflow from the admin.

Record screenshots and expected results. Ask someone outside the implementation work to run the critical scenarios without guidance. A technically correct extension can still fail if customers cannot find it.

Shopify currently states that merchants can revert within 30 days after upgrading. Treat that as a safety net, not the test plan. Before launch, define who can make the rollback decision, what data or events might not replay, and how support will communicate if the old account version is temporarily restored.

Use a launch checklist and monitor the first weeks

Before switching, confirm that:

• Every legacy customization has a keep, replace, or retire decision.
• Required app blocks and extensions are deployed and configured.
• Sign-in emails arrive reliably and customer-facing instructions no longer mention passwords.
• Account links, menus, notifications, and custom login components have been checked.
• Automations, segments, integrations, consent, and analytics have an explicit replacement or accepted limitation.
• Critical scenarios pass on mobile and desktop in every important market and language.
• Support has a short troubleshooting guide and the rollback owner is available.

After the upgrade, monitor login-related tickets, code-email delivery, return and subscription completion, account-page errors, and post-purchase conversion. Compare these signals daily for the first week and again after a normal order cycle. Keep the migration inventory as operational documentation for future app and theme changes.

If your store has years of account-template code or custom integrations, a focused technical audit can identify the real dependencies before the deadline. Stormdev can help map the current journey, build missing customer-account extensions, and test the migration with your team.