Migrating from Legacy to New Customer Accounts: FAQ
Q1: If I migrate and don’t like it, can I go back to legacy customer accounts?
A: Yes, but only within 30 days of switching. After that window closes, support cannot revert you — plan a test period before committing.
Q2: Will my custom login setup (password login, social logins, Multipass) still work after migrating?
A: Some legacy login customizations aren’t carried over 1:1. Merchants have reported losing password-based login and needing to reconfigure social sign-in (e.g., LINE/Yahoo) after migrating — review your login setup and any Multipass integration before switching.
Q3: Will apps that touch customer accounts keep working?
A: Not always automatically. Some merchants found apps tied to legacy account behavior (approval workflows, wholesale account menus) broke after migrating — check with app developers or your partner before migrating a live store.
Q4: Will I lose account-page customizations or B2B approval workflows?
A: Possibly — custom account portals and B2B-specific flows (email-change restrictions, order visibility, approval gating) built on legacy accounts may need to be rebuilt for new customer accounts.
The one that caught us out was that new customer accounts are passwordless by design. Customers get a six digit code by email and there is no password field left to keep, so anything built around a custom login form or a stored password has nowhere to land. Multipass is classic only as well, so if you are running sign in from another system, that is the actual blocker rather than a setting somewhere that you have missed.
Second thing, the account pages stop being Liquid templates. Whatever lives in customers/account.liquid does not carry across. The replacement is customer account UI extensions, which is a different build rather than a port, so budget for it as new work.
Third, search your theme and your apps for anything pointing at /account or /account/orders before you flip the switch. Some of those still resolve, some drop the customer somewhere they do not expect, and the new account sits on a shopify.com URL rather than your own domain. That search takes ten minutes and it is the step people skip.
Worth adding on the 30 day revert, it gives you the setting back, not the customizations you already tore out to make the new one work. So do the test run on a dev store with a copy of the theme rather than on the live one.
Has anyone here migrated a store with a wholesale or approval flow sitting on top of accounts? That is the part I would still be nervous about.