Upgrade from Shopify legacy customer accounts after you inventory password-based login customizations and replace the ones customers still rely on—not the moment you hear “deprecated,” and not by flipping the admin switch without a cutover plan. Shopify deprecated legacy customer accounts on February 26, 2026, stopped offering them to new stores, and said a final sunset date would be announced later in 2026. This article helps you decide whether to upgrade now, what to rebuild first, and how to use Shopify’s 30-day revert window safely.
Key takeaways
Legacy accounts use email-and-password sign-in; the current customer accounts product uses passwordless one-time email codes (plus Shop and social options when enabled).
Shopify recommends upgrading for more secure sign-in, app-block customizations, and native features such as store credit and self-serve returns—while noting you can revert within 30 days.
Do not treat upgrade day as a branding project. Treat it as a dependency cutover: custom login UI, Flow automations, segments, Multipass/identity, and market domains can all change behavior.
Use the Account Upgrade Timing Ladder and Dependency Scorecard below to decide whether you are ready to publish—or still in replacement mode.
What changed—and what did not
Shopify’s help documentation still describes two account versions: customer accounts versus legacy customer accounts. Current customer accounts are passwordless by default: shoppers enter an email and receive a six-digit verification code. Legacy accounts keep the familiar register-and-password path.
What changed for merchants is the support posture. In the February 26, 2026 changelog, Shopify stated legacy accounts are deprecated, unavailable to new stores and to existing stores not already using them, and no longer receive feature updates or technical support. A final sunset date was not fixed in that announcement—only promised for later in 2026—so calendar pressure is real, but the immediate work is readiness, not improvisation.
What did not change is the commercial job of an account system: order history, profile data, addresses, and—when enabled—post-purchase self-serve actions. Shopify’s comparison table shows the newer product adding native capabilities that legacy accounts lack, including saved payment methods, self-serve returns, store credit, Buy again reordering, B2B compatibility, and Markets compatibility. Those features matter only if your customers and channels will actually use them.
The Account Upgrade Timing Ladder
Use this ladder to decide what to do this week. Move one level only when the previous level’s outputs exist. Skipping levels is how stores “upgrade” into broken loyalty links, dead Flow triggers, and support tickets about missing passwords.
L0 — Confirm which account system is live
In Shopify admin, confirm whether the storefront and checkout still point to legacy accounts. Do not start redesigning the portal until you know which authentication model customers currently complete.
L1 — Inventory legacy dependencies
List every place login or registration was customized: theme templates, modal sign-in, hard-coded /account/login experiences outside default templates, loyalty widgets, subscription portals, Multipass or external identity, customer segments using customer_account_status, and Flow or other automations tied to legacy account events. Shopify’s upgrade guide treats this inventory as step one for a reason—redirects alone will not preserve custom UI.
L2 — Replace must-keep experiences with supported building blocks
Recreate only the customizations customers still need, preferably with customer-account app blocks or native features, then preview in the checkout and accounts editor. Shopify positions customer accounts as managed separately from the theme so theme updates do not quietly break the portal—an architectural win if you stop editing Liquid account pages as the primary customization path.
L3 — Run a controlled publish-and-test cutover
Follow Shopify’s sequence: duplicate configuration, replace customizations, update branding, connect the customer-accounts subdomain, verify sender email, publish the configuration, preview and test, then upgrade so the online store and checkout actually link to the new system. Treat the 30-day revert window as a rollback plan with success criteria—not as permission to skip testing.
L4 — Stabilize measurement and support
After upgrade, verify web pixels for post-purchase account events, re-train support scripts (password reset tickets should fall; one-time-code delivery issues may rise), and confirm B2B or Markets journeys if those channels matter. Only then expand optional portal features such as loyalty blocks or wishlist apps.
Dependency Scorecard: are you ready to upgrade this sprint?
Score each row from 0 to 3. Total ranges from 0 to 18. Higher scores mean more unfinished dependency work—upgrade later in the sprint, not sooner.
Dependency | 0 | 1–2 | 3 |
Custom login / registration UI | Default legacy templates only | Minor theme tweaks | Custom modal, alternate page, or heavily branded Liquid login |
Automations & segments | None tied to legacy accounts | A few Flows or one customer_account_status segment | Core lifecycle emails, VIP segments, or ops workflows depend on legacy account events |
Identity / Multipass / IdP | Shopify-native login only | Shop sign-in or light SSO exploration | Production Multipass or required enterprise IdP path |
App / loyalty / subscription portals | None, or already app-block ready | One secondary integration | Multiple account-dependent apps with Liquid embeds |
Markets / domains / branding | Single domain, checkout branding ready | Some brand settings unfinished | Per-market domain expectations for accounts pages (Shopify notes one domain for customer accounts across markets) |
Support & measurement readiness | Scripts and pixels prepared | Partial FAQ updates | No staff briefing; analytics still assume password registration |
Interpretation: 0–5 usually means you can schedule an L3 cutover after a short L1/L2 pass. 6–11 means stay in replacement mode this sprint—upgrade date is a milestone, not today’s button. 12–18 means the account system is entangled with retention and ops; commission a structured rebuild before you publish the new configuration.
What Shopify’s upgrade limitations change in practice
Shopify documents several limitations you should treat as decision inputs, not footnotes.
Custom sign-in experiences: Legacy URLs such as /account/login redirect after upgrade, including hard-coded theme links—but custom modals or non-template login pages may still need theme cleanup before go-live.
Workflows: Automations based on legacy customer accounts are not supported in the new product and do not migrate.
Segments: Filters that use customer_account_status are legacy-only; Shopify states there are no equivalent filters for the newer customer accounts version.
Markets domains: Even with multiple international storefront domains, customer accounts use one domain across markets.
Multipass: Shopify’s comparison and upgrade docs state that existing Multipass integrations on Shopify Plus continue to work after upgrade; for signing customers in from your own system more broadly, connecting an OAuth2.0 + OIDC identity provider is the documented path.
Sign-in page blocks: You can brand the sign-in page in the checkout and accounts editor, but you cannot add customization blocks to the sign-in page itself.
These constraints explain why “we’ll upgrade Friday and rebuild Monday” is a weak plan. The portal may look modern on day one while VIP segments, Flow triggers, or a custom login modal still fail quietly.
Worked example: a hypothetical DTC brand
Consider a hypothetical apparel brand on Shopify Advanced with legacy accounts, a theme modal for “Members login,” a Flow that tags customers after account creation, a loyalty app injected via Liquid, and a VIP segment filtered on customer_account_status. Marketing wants native store credit and self-serve returns. Ops wants fewer password-reset tickets.
Dependency Scorecard lands around 13–15: custom login (3), automations/segments (3), identity (0–1), apps (3), markets/branding (1–2), support/measurement (2). On the Timing Ladder, the team is at L1, not L3. The right move is a two-week replacement track: remove the modal in favor of Shopify’s account links, recreate loyalty with a customer-accounts app block, rewrite the Flow around events that still exist, rebuild the VIP audience without the legacy filter, then publish, preview, and upgrade with a monitored 30-day rollback window.
If the same brand had only default legacy templates and no Flow or loyalty embeds, the scorecard might sit under 5. In that case, Shopify’s recommended upgrade path can typically move from inventory to cutover inside one sprint—after branding, subdomain, sender email, and a checkout-plus-account smoke test.
When waiting is still reasonable—and when it is not
Waiting can be justified when your scorecard is high and a major campaign, seasonal peak, or B2B onboarding wave would amplify a broken login. Waiting is weaker when the only reason is preference for passwords, or when you are still investing in Liquid account customizations Shopify is steering merchants away from.
Because Shopify already stopped feature updates and technical support for legacy accounts, new account-adjacent work—returns UX, store credit programs, B2B account experiences—should usually be designed on the current customer accounts product. Building deeper legacy Liquid portals now increases stranded work when the eventual sunset arrives.
If your storefront path question is larger than accounts—for example whether checkout logic belongs in Functions apps—pair this decision with related platform guidance such as what to rebuild after Shopify Scripts stopped. If Plus is on the table for identity-provider requirements, use Shopify Advanced or Shopify Plus: how to decide when to upgrade as the commercial companion—not as a substitute for the account dependency inventory.
Common failure patterns
Upgrade-first, inventory-later. The admin switch is easy; recovering VIP segments and custom login is not.
Assuming passwords will remain available. The current product’s default shopper path is one-time email codes, with Shop and social options when configured.
Leaving ghost Liquid login UI in the theme. Redirects help, but orphaned modals create duplicate paths and confused shoppers.
Ignoring the single accounts domain across Markets. International brands that expected per-market account hostnames need an explicit UX and support plan.
Treating revert as a strategy. The 30-day revert window is a safety net for a tested cutover, not a substitute for L2 replacement work.
Recommended next steps
Confirm whether legacy accounts are still live on storefront and checkout.
Complete the L1 inventory and score the Dependency Scorecard with marketing, ops, and whoever owns Flow or CRM.
Replace must-keep customizations with native features or customer-account app blocks; remove obsolete Liquid login UI.
Run Shopify’s publish → preview → upgrade sequence on a low-traffic window, with support coverage and a written rollback trigger.
After go-live, verify one-time-code delivery, order history, returns or store credit if enabled, B2B/Markets paths if relevant, and pixel or analytics continuity.
When implementation help is worth it
If your score sits in the 12–18 range—or if Multipass, a custom identity provider, Hydrogen account experiences via the Customer Account API, or multiple account-dependent apps are in play—treat the upgrade as a scoped development project, not a settings toggle. Oasbit’s website and SaaS development services include Shopify storefront and account-path implementation work when teams need a controlled cutover rather than an unverified admin flip.
If you want a practical readiness review of your login customizations, automations, and upgrade sequence before you publish, book a growth strategy session and bring your Dependency Scorecard draft.
