Do You Have to Migrate Off Legacy Accounts to Go Headless?
Migrating off legacy customer accounts is a prerequisite on any headless roadmap, not an optional follow-on. Shopify closed legacy accounts to new stores and to existing stores not using them on February 26, 2026 (verified Sep 2026). Shopify's own guidance is to switch to the Customer Account API as soon as possible. The final sunset date arrives later in 2026, still unannounced. Budget an estimated $12,000 to $45,000 (Deploi estimate, illustrative).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's changelog of February 26, 2026 on 2026-09-05: legacy customer accounts are no longer available to new stores and existing stores not using them, merchants should switch to the Customer Account API as soon as possible, and a final sunset date will be announced later in 2026. No sunset date is set as of this check, which is the single most important fact for anyone sequencing a 2026 or 2027 headless roadmap. Browsed the App Store's Store management, Security, Accounts and login category: 24 apps, several of which are genuinely about customer accounts, including Custlo, Hubble, Accofy and Customer Accounts Deluxe. Every one of them customizes or extends account UX and features; none packages the classic-to-new migration itself. Read shopify.dev's Multipass reference the same day: Multipass is available only with legacy customer accounts, so a Plus store using it inherits the deprecation directly. The migration is a one-time technical project owned by the merchant's dev team or launch agency, and there is nothing to install.
- Reference scenario
- $20M–$100M GMV · Shopify Plus on legacy customer accounts · 80,000–500,000 customer accounts with saved addresses and order history · a headless or replatform project planned inside 12 months · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Already on new customer accounts | WAIT | Nothing to migrate. Confirm the setting in the admin before anyone scopes a migration line item, because the assumption that a store is still on classic accounts costs an estimated $12,000 in avoidable work (Deploi estimate, illustrative). |
| On legacy accounts, headless launch inside 12 months | BUILD | Migrate first, then build the storefront. Doing it in the other order means writing an account area twice, and the sunset date lands somewhere later in 2026 without warning. |
| On legacy accounts with Multipass or a Storefront API login flow | BUILD | The hardest case, because Multipass works only with legacy accounts (verified Sep 2026). Federation gets rebuilt on new customer accounts at the same time, which adds an estimated $15,000–$50,000 to the project (Deploi estimate, illustrative). |
| On legacy accounts, no headless plan, 250,000+ accounts | CUSTOMIZE | Migrate anyway, at your own pace, and spend the budget on buyer communication rather than engineering. A large account base is what turns an unannounced sunset date into a support incident instead of a maintenance window. |
What Legacy Customer Accounts Migration Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | Every returning buyer meets the new login on the same day, so a migration run without notice converts into abandoned sessions and support tickets in a single week. |
| Operational efficiency | High | Sequencing the migration before the storefront rebuild means the account area gets written once; running them together means writing it twice and testing it three times. |
| Revenue — indirect | Medium | Logged-in buyers reorder, and a login surface that breaks mid-project suppresses that traffic until it is fixed, which is why the sunset date belongs on the roadmap now. |
| Data & insight | Low | Customer records, addresses and order history stay in Shopify across the migration, so the profile data itself is never at risk; only the login surface changes. |
| Retention & LTV | Medium | Passwordless sign-in with a one-time email code and Sign in with Shop passkeys removes the forgotten-password drop-off that classic accounts produced on every return visit. |
Spend ceiling: Cap this at the migration itself, an estimated $12,000–$45,000 one-time (Deploi estimate, illustrative), plus a separate line for a Multipass replacement. Anything else on the classic account pages is money spent on a surface with a sunset date.
What buying enables (top apps)
- + Account-area features that no migration provides on its own: reorder buttons, wishlists, custom profile fields and B2B locks on a themed store
- + A vendor maintaining that account UX through theme changes, which is real value once the store is on new customer accounts
- + Same-day installation, which is genuinely faster than any project — it just does not address the deprecation
What building additionally unlocks
- + A single account implementation that serves both the themed store today and the headless storefront later, on the Customer Account API
- + Passwordless login with a one-time email code and Sign in with Shop passkeys, which removes stored passwords from the risk register
- + Freedom from an unannounced sunset date, which is the only outcome that actually de-risks the headless timeline
- + A clean identity handoff on the Plus custom identity provider connection, replacing a Multipass dependency that has no future
Find Your Verdict in 3 Questions
Is your store already on new customer accounts rather than legacy ones — checked in the admin, not assumed?
Yes: Your verdict: WAIT — there is no migration to run; scope the headless account area straight onto the Customer Account API.
No: Go to question 2.
Is a headless build, replatform or major theme rebuild scheduled inside the next 12 months?
Yes: Your verdict: BUILD — run the migration first, at an estimated $12,000–$45,000 (Deploi estimate, illustrative), so the account area gets written once instead of twice.
No: Go to question 3.
Does a Multipass handoff, a membership portal login or a Storefront API login flow depend on legacy accounts today?
Yes: Your verdict: BUILD — start now; the replacement path runs through the Plus custom identity provider connection and adds an estimated $15,000–$50,000 (Deploi estimate, illustrative).
No: Your verdict: CUSTOMIZE — migrate on your own schedule this year, spend the effort on buyer communication, and stop adding dependencies to the classic account pages.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | No app performs this migration, so the buy lane buys account-UX polish and none of the work; the migration itself is an estimated 3–8 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | An accounts app adds a monthly subscription that survives the migration you still have to do; new customer accounts and the Customer Account API are included with the plan (verified Sep 2026). | ||
| Maintenance & upgrades | Account-UX apps track theme and API churn on their own schedule; after migration your side is one annual API version bump and the account routes you own. | ||
| Switching & exit | Deferring is not a neutral position: the longer legacy accounts stay live, the more theme, app and notification dependencies accumulate against a surface with a sunset date coming later in 2026. | ||
| Risk | |||
| Vendor risk | An accounts app is a second vendor sitting on a deprecated account surface; the migration removes the dependency rather than adding one. | ||
| Security & compliance surface | New customer accounts are passwordless by default with a one-time email code and support Sign in with Shop passkeys (verified Sep 2026), which removes stored passwords from the risk register entirely. | ||
| Platform-deprecation exposure | This is the whole page: legacy accounts closed to new stores on February 26, 2026 with a final sunset date to be announced later in 2026 (verified Sep 2026), and no app insulates you from that date. | ||
| Value | |||
| Fit to requirement | The requirement is a migration, and account-UX apps are not migration tools; only the project delivers what the headless timeline needs. | ||
| Time to market | An app installs in a day and moves the launch date not at all; the migration takes 3–8 weeks and is the thing standing between you and a headless account area (Deploi estimate, illustrative). | ||
| Performance & scale | The Customer Account API allows 7,500 cost points per store and customer, replenishing at 200 points per second on Plus and 100 below (verified Sep 2026), which is a budget you can design an account area against. | ||
| Data ownership & AI-readiness | Customer records, addresses and order history stay in Shopify through the migration; what changes is the login surface, so no profile data is stranded in a vendor's database. | ||
| Focus & opportunity cost | The migration consumes 3–8 weeks of a dev bench that could ship merchandising work, which is exactly why it belongs on the roadmap before a deadline sets itself. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| New customer accounts + Customer Account API | Native — First-party Shopify, and the destination Shopify names in its own deprecation notice. Passwordless by default with a one-time 6-digit email code, with Sign in with Shop passkeys and native Google and Facebook sign-in. The Customer Account API serves login, order history, addresses and B2B company context to a headless storefront, at 7,500 cost points per store and customer (verified Sep 2026). | Included with the plan; no per-account or per-login charge (verified Sep 2026) | Every store on legacy accounts, and every headless storefront regardless of timeline |
| Legacy customer accounts | Legacy — First-party Shopify, deprecated on February 26, 2026: no longer available to new stores or existing stores not using them, with a direction to switch to the Customer Account API as soon as possible and a final sunset date to be announced later in 2026. No date is set as of September 2026. Multipass works only with this account type, so a Plus store using Multipass inherits the deprecation (verified Sep 2026). | Included with the plan while it lasts; the sunset date is the cost (verified Sep 2026) | Nothing new. Keeping an existing login alive only until its replacement ships |
| Customer accounts apps | Category — The App Store's Store management, Security, Accounts and login category holds 24 apps, among them Custlo, Hubble, Accofy and Customer Accounts Deluxe (verified Sep 2026). Every one of them customizes or extends the account area: reorder buttons, wishlists, profile fields, B2B locks. None performs the classic-to-new migration, and none renders inside a headless storefront. | Monthly tiers on each listing; the migration is not among the things any tier buys (verified Sep 2026) | Enriching an account area after the migration, on a themed Online Store |
| The migration project | Build lane — The honest path: switch the account setting, rebuild or re-point the account area, replace any Multipass handoff, update notification and email links, re-test every app that reads the account pages, and tell customers the login is changing. Owned by the dev team or launch agency, done once, and sequenced before the headless storefront work. | $12,000–$45,000 one-time depending on account-area depth and app dependencies (Deploi estimate, illustrative) | Any store still on legacy accounts, whether or not headless is on the roadmap |
The Build Path
- Audit what depends on the classic account pages: Start with the inventory: theme templates, apps that inject into account pages, email and notification links, any Multipass or Storefront API login handoff, and support macros that tell customers to reset a password. The audit is a week and it sets the real number for the rest.
- Switch the account setting and rebuild the account area: New customer accounts are passwordless by default with a one-time 6-digit email code and Sign in with Shop passkeys (verified Sep 2026). On a themed store the account area moves to Shopify's hosted surface with extensions; on a headless storefront it becomes Customer Account API routes you write once and keep.
- Replace Multipass before it becomes the blocker: Multipass is available only with legacy customer accounts (verified Sep 2026), so a portal or membership handoff has to move to the Plus custom identity provider connection on new customer accounts. Budget this separately at an estimated $15,000–$50,000 (Deploi estimate, illustrative); it is the part that surprises people.
- Tell customers before they discover it at login: The login experience changes for every returning buyer, so the support load lands in one week rather than spread out. Send the notice ahead of the switch, update macros, and watch sign-in rates daily for two weeks. A 250,000-account base makes this the largest line item in the project.
- Effort band
- $12,000–$45,000 one-time for the migration on a mid-market store with a customized account area and app dependencies — Deploi estimate (illustrative); lands in the $10–25K to $25–75K contact-form bands. A Multipass replacement adds $15,000–$50,000 (Deploi estimate, illustrative).
- Typical timeline
- 3–8 weeks including the dependency audit, the account-area rebuild and the customer communication; add 4–8 weeks where Multipass has to be replaced (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15% of build cost per year (Deploi estimate): roughly $1,800–$6,800/yr (Deploi estimate, illustrative) once migrated, covering an annual Customer Account API version bump and account-route regression tests. Legacy accounts carry no maintenance line and an unannounced sunset date instead.
- What you own — and what you take on
- You own: the account-area routes, the notification links, the identity handoff and the customer communication. You take on: one API version bump a year. Shopify keeps: credential handling, the one-time email code, passkeys and the login surface itself.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$600 (app install and configuration) | $12,000–$45,000 |
| Years 1–3 (recurring) | $14,900–$52,200 (subscription plus the deferred migration, done under a deadline) | $5,400–$20,400 (maintenance) |
| 3-year total | ≈$14,900–$52,800 | ≈$17,400–$65,400 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column = deferring the migration and installing a customer-accounts app to improve the existing account area; the migration cost still arrives later, which the three-year total reflects.
- † Build column = running the migration now: dependency audit, account-area rebuild, notification and link updates, customer communication; Multipass replacement excluded and priced separately.
What the Sticker Price Hides
On the buy path
- — No app performs this migration (verified Sep 2026), so every month of subscription buys account-area polish on a surface with a sunset date
- — Deferring transfers the schedule to Shopify: a sunset announced later in 2026 turns a planned project into a rush one
- — Each new app that injects into classic account pages adds another dependency the migration has to unwind
- — Multipass works only with legacy accounts (verified Sep 2026), so a Plus store that keeps deferring keeps a deprecated handoff in production
On the build path
- — $12,000–$45,000 one-time (Deploi estimate, illustrative), and the dependency audit usually finds more than the theme
- — Returning buyers meet an unfamiliar passwordless login, so support volume spikes in the first week unless the notice goes out early
- — Notification and email links pointing at classic account URLs break quietly, and nobody notices until a customer replies to one
- — A Multipass replacement is a separate project at an estimated $15,000–$50,000 (Deploi estimate, illustrative), not a task inside this one
What Merchants Say
Teams planning a 2027 replatform describe finding the accounts deprecation late, after the storefront scope was already signed, and having to re-sequence the whole project around it.
The recurring pain on account migrations is support volume, not engineering: returning buyers hit an unfamiliar passwordless login and the tickets arrive in a single week.
If You Change Your Mind Later
If you bought and outgrow it
Deferring keeps every option open except the calendar. Customer records stay in Shopify, so nothing is stranded, but the migration cost is unchanged and moves from your roadmap to Shopify's announcement schedule. Buying an accounts app in the meantime adds a subscription and one more dependency to unwind later.
If you built and want out
Migrating is a one-way door and a welcome one: new customer accounts are the surface Shopify is building on, and the Customer Account API is the same lane a headless storefront needs anyway. The only thing you cannot walk back is Multipass, so replace that handoff deliberately rather than switching the setting and finding out.
When This Answer Changes
We're watching for:
- ▸ Shopify announcing the final sunset date for legacy customer accounts, which the February 26, 2026 changelog says arrives later in 2026
- ▸ A Shopify migration tool or guided flow for classic-to-new accounts, which would cut the project's dependency-audit half
- ▸ Multipass gaining a replacement path on new customer accounts below Shopify Plus
Verdict change log:
- 2026-02-26Shopify deprecated legacy customer accounts: no longer available to new stores or existing stores not using them, with a direction to switch to the Customer Account API as soon as possible and a final sunset date to be announced later in 2026. Before that date this migration was a nice-to-have on a headless roadmap; since then it is a dated dependency with an unknown deadline, which is why the verdict is BUILD and why the sequencing matters more than the cost.
Common Questions
Are legacy customer accounts being shut off?
Yes, legacy customer accounts are being shut off. Shopify's changelog of February 26, 2026 states they are no longer available to new stores or existing stores not using them. Shopify's own direction is to switch to the Customer Account API as soon as possible. A final sunset date will be announced later in 2026; no date is set as of September 2026.
Does going headless require migrating off legacy customer accounts?
Yes, a headless build should treat migrating off legacy customer accounts as a prerequisite. A storefront can still read legacy sessions through Storefront API customer tokens today, but Shopify closed that lane to new and unused stores on February 26, 2026 (verified Sep 2026). Sequence the migration first: an estimated $12,000 to $45,000 and 3 to 8 weeks (Deploi estimate, illustrative).
Is there an app that migrates classic customer accounts?
No app migrates classic customer accounts to the new ones. The App Store's accounts-and-login category holds 24 apps, including Custlo, Hubble, Accofy and Customer Accounts Deluxe (verified Sep 2026). Every one of them customizes account UX; none performs the migration. The switch is an admin setting plus storefront, notification and app-dependency work your team owns.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Check the admin today for whether the store is on classic or new customer accounts, and write the answer down
- Inventory every dependency: theme templates, apps on account pages, notification links, Multipass or Storefront API login handoffs
- Price the Multipass replacement separately if one exists, before the migration budget is signed
- Schedule the switch ahead of the headless storefront work, not alongside it
- Send the login-is-changing notice before the switch and watch sign-in rates daily for two weeks after
If you're going with WAIT
- Confirm in the admin that new customer accounts are already active, so nobody scopes a migration that does not exist
- Point the headless account area straight at the Customer Account API and budget its query cost
- Remove any leftover links to classic account URLs from emails, notifications and support macros
- Diary a re-check when Shopify announces the final sunset date later in 2026
Official Docs & Sources
- Legacy customer accounts are deprecated — shopify.dev
- New customer accounts — Shopify Help Center
- Customer Account API — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Observability for Checkout Functions on Shopify?
Shopify documents 12 function error types and stores each run in the Dev Dashboard, but no default alert tells you a checkout function has started failing.
Do Customer Accounts Follow Shoppers Across Plus Stores?
Each Plus store keeps its own customer records, so accounts don't follow shoppers between stores. Multipass rides legacy accounts Shopify deprecated.
Should You Build or Buy Cross-Store Staff Access on Plus?
Custom organization-level roles give one staff login reach across a Plus organization. No app grants staff access across stores; below Plus, every store is separate.
Customer Account API vs. a Custom Login System on Headless?
Shopify's Customer Account API authenticates buyers on headless. A custom login build costs six figures, and legacy accounts are deprecated since February 2026.
Build or Buy Performance Monitoring & App Audits on Shopify?
Measurement is free on Shopify; storefront speed comes from an audit-and-remediation program, not a speed app.
Ready to sequence the accounts migration before the rebuild?
We audit what depends on your classic account pages, price the migration honestly, and run it before the headless storefront work starts rather than during it.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.