Move to Shopify's new customer accounts without losing what you built
Shopify has deprecated legacy customer accounts and will announce the final shutdown date. Custom sign-up fields, account pages and login rules built in Liquid don't carry over when your store switches. We move them to the new accounts properly — with metafields, account extensions and Shopify Flow — for a fixed price.
The clock is already running
Dates and quotes are from Shopify's own changelog, help center and announcement.
Legacy customer accounts deprecated
No new features or technical support, and no longer available to new stores. Shopify strongly recommends upgrading ahead of the deadline.
Shopify developer changelogFinal shutdown date to be announced
The legacy templates — customers/account, login and register — will first be locked from editing, then removed. Storefront API customer mutations used by headless stores will be deprecated too.
Shopify's availability updateA theme update can switch you over
Theme Store themes no longer have to include the legacy templates. A store on legacy accounts that moves to a theme without them is upgraded automatically.
Shopify developer changelog30 days to change your mind
Shopify lets you revert to legacy accounts within 30 days of upgrading — a safety net, not a plan.
Shopify Help CenterWhat doesn't carry over
The new accounts are faster and passwordless, but anything you customized in Liquid has to be rebuilt.
Custom sign-up fields
Birthday, company, VAT ID, trade licence: fields added to the register form have no place in the new sign-in. Accounts are created on first sign-in with a one-time code, and Shopify points to apps for collecting custom fields after sign-in.
Content on account pages
Loyalty balances, downloads, price lists, custom order info added to account.liquid don't carry over. New account pages are extended with UI extensions instead.
Wholesale-only access and approvals
Approving customers before they can sign in isn't possible on new accounts. The supported pattern is a check after sign-in — or Shopify's native B2B, now on every plan.
Headless stores and mobile apps
Logins built on Storefront API customer mutations need to move to the Customer Account API.
Apps that inject into legacy pages
Apps that render inside the old Liquid account pages won't appear in the new accounts unless they ship account extensions.
Data hidden in notes and tags
Legacy forms often wrote extra answers into the customer note. Moving them into typed customer metafields keeps them usable in Flow, segments and emails.
Four steps, fixed price
The audit fixes the scope and the price before any work starts.
Audit
We inventory every customization in your theme, apps and customer data, map each one to its new-accounts replacement and send you a fixed quote.
€390 · about 3 business daysMove the data
Answers stored in notes or tags move into customer metafields with proper definitions, so nothing gets lost.
Part of the migrationRebuild what matters
Profile fields, account blocks and pages as customer account extensions; first-sign-in tags and Shopify Flow triggers where you need them.
Usually 1–2 weeksTest and switch
We test on a development store or a duplicate theme, switch you over at a quiet hour and watch the first days.
Fixes for 30 daysStart with the audit, know the price
Audit
Fixed · credited if you go ahead
- Inventory of every legacy customization
- A replacement for each: native, app or custom
- Risks for headless, B2B and apps
- A fixed quote for the migration
Standard migration
Fixed price after the audit
- Custom sign-up fields → customer metafields
- Profile block to view and edit them
- Up to 3 account blocks or pages
- Data moved from notes and tags
- First-sign-in tags or a Flow trigger
- Testing, switch-over and 30 days of fixes
Complex migration
Fixed price after the audit
- Headless storefronts and mobile apps
- Customer Account API login
- Wholesale and B2B portals
- Plus: identity providers and Multipass
- Multi-market account setups
Prices exclude VAT. Every project starts with the audit, so the price is fixed before work begins.
Shopify engineering, not guesswork
We build on these APIs
Our own App Store app, SplitFlow, runs in production on the Admin GraphQL API, webhooks, Shopify Flow and app extensions.
Read the SplitFlow case studyNative first
If a Shopify setting, Shopify Forms or a $10 app covers it, we'll tell you. Custom code only where it pays off.
Fixed price, one engineer
No hourly surprises and no account managers — you talk to the person who does the work, by email or WhatsApp.
Questions merchants ask
When do legacy customer accounts stop working?
Shopify hasn't published the final date yet. It deprecated legacy accounts on 26 February 2026 and said the sunset date would be announced later in 2026. Migrating before the date lands avoids a rushed switch.
Will my customers lose their accounts or order history?
No. Customer records and order history stay in Shopify. Customers sign in with a one-time code sent to their email — or with Shop, Google or Facebook — instead of a password.
Can I keep my custom registration fields?
Not on the sign-in page itself: Shopify doesn't allow custom fields there. We collect them right after the first sign-in — in the profile or on a “complete your profile” page — and store them in customer metafields.
Do I need custom code at all?
Often only partly. Shopify settings, Shopify Forms or an existing app may cover some of what you have. The audit tells you exactly which parts need code and which don't.
We run a headless storefront or a mobile app. Can you help?
Yes — that's the complex package: moving your login from the Storefront API customer mutations to the Customer Account API.
What access do you need?
A collaborator request that you approve in your Shopify admin. You choose the permissions and can remove access at any time.
What does “credited” mean for the audit?
If you book the migration within 30 days of the audit, the €390 is deducted from its price.
Don't wait for the date
Book the audit now and you'll know exactly what changes, what it costs and how long it takes — before Shopify sets the deadline.