【Mypage Blocks】Preparing for the End of Shopify's Legacy Customer Accounts: How Do You Migrate Your Store's My Page?

"So legacy customer accounts — the 'old accounts' — are going away. What exactly are we supposed to do about it?"

That's the question we hear most often right now. Most Shopify merchants have built up their account pages ("my page," as it's known in Japan) with a stack of apps: loyalty points, membership tiers, account deletion, receipts, and more. "Which of these carry over, and which need to be rebuilt?" — it's easy to feel lost at first. We completely understand.

In this article, we'll start by laying out the facts about Shopify account pages, and then walk through a way of thinking that lets you approach the migration calmly.

What's happening right now (the exact timeline)

• On February 26, 2026, legacy customer accounts were officially deprecated. New stores can no longer use them, and they will no longer receive feature improvements, bug fixes, or technical support.
• The final sunset date is scheduled to be announced within 2026. Only once it's announced will the concrete date be fixed. The longer you wait, the less time you'll have to prepare.
• Shopify recommends not waiting for the announcement — plan for a migration with two to three months of buffer, including a testing period.

In other words, "it still works, so we're fine" isn't the right read. The countdown has quietly begun.

According to Shopify, more than 70% of stores are already on the new customer accounts. Note that this is a global figure — the percentage for Japan hasn't been published.

At DotDev, Shopify's developer event held in July, it was mentioned that adoption has climbed even further since. New stores can't choose legacy accounts, so this ratio will only keep rising.

And the stores that haven't migrated yet have their reasons: custom login flows, heavily customized pages, mechanisms wired into daily operations. The heavier the migration, the more likely a store is to still be waiting — that's the reality.

Japanese stores in particular have a history of filling the gaps in Shopify's defaults with apps and Liquid — furigana name fields, receipts that comply with Japan's qualified invoice system, and so on. That same history makes their migrations heavier.

Which is exactly why looking inside early makes everything easier. Once you know what's there and which parts take real work, the rest is just tackling them in order.

What changes with the new customer accounts

The new customer accounts are not a mere swap-in replacement.

• Passwordless login: customers sign in with a one-time code sent by email. No more reused passwords or reset flows.
• App extensions (UI Extensions): apps can add features as blocks on the order status, order index, and profile pages — or as full pages.
• Stronger native features: store credit and self-serve returns (customers initiate a return and print the shipping label) are supported. Neither was available on legacy customer accounts.

The key point: features you used on legacy customer accounts do not carry over automatically. Anything an app was providing depends on that app shipping its own support.

That's why a pre-migration inventory pays off.

Everything splits into four groups, by "can it be migrated?"

The biggest stumbling block in this migration isn't the number of features — it's not knowing where you currently stand.

Sorting features by type doesn't help much, because what you actually want to know is "can this move, or not?" Sort along that axis and you get four groups.

* A "block" here is a component you can place in designated spots on the account pages. It's similar to a theme "section": you can add, remove, and reorder without writing code. The content itself is provided by an app.

② and ③ differ app by app

"Surely the app vendors will handle it" — tempting to assume, but support status varies completely from app to app.

Some apps already ship blocks. Others genuinely have plans but no committed timing or scope. Loyalty points, membership tiers, receipts, furigana fields, address autocomplete, subscription management — all classic "an app was doing that" territory, and whether each one can move is entirely up to that app.

So the core of your inventory isn't classifying features — it's checking your apps one by one. Unglamorous, but this is the step that pays off most.

If you land on ③, your options are to wait or to switch. If you wait, keep an eye on whether the app will make it in time once the sunset date is announced.

About ④

This is the easiest part to miss.

Legacy customer accounts were part of your theme. Write some Liquid and you could freely change the display by membership tier, show a banner under specific conditions, and so on.

The new customer accounts live outside the theme, so Liquid doesn't work there.

Checkout makes a good analogy. Checkout has long lived outside the theme, untouchable by Liquid. To customize it, you use extensions (apps) and branding settings (logo, colors, and fonts configured from the admin).

The new customer accounts work much the same way. The internals differ, but the principle is shared: they sit outside the theme, and you add to them with extensions. The account pages have moved from the theme side to the checkout side — that framing makes it click.

Just as we all gave up on "writing Liquid to change checkout freely," something similar is now happening to the account pages.

The replacement mechanism is called a Customer account UI extension, and it's part of an app. So if you want to reproduce what you had, you either:

• install an existing app that offers the same feature, or
• build a custom app just for your store.

There is no "paste the Liquid somewhere else and it works" path.

What makes this heavy is that it requires development, not configuration. Even if someone on your team can customize themes, that alone isn't enough — theme editing and app development are different kinds of work.

And none of this shows up in your app list, because it isn't an installed app — it's code written into your theme. Run your inventory from the app list alone and this whole category falls through the cracks. Then, after migrating, you notice it has quietly disappeared.

That's why for ④, finding it early is itself the countermeasure. Once you know development is needed, you can estimate timeline and cost. Discover it after the sunset date is announced, and your options shrink.

One more thing that's neither an app nor Liquid

Shopify Flow automations and customer segments.

Workflows conditioned on legacy accounts, and segments using customer_account_status, do not carry over to the new customer accounts — and no replacement filter is provided.

Because they have nothing to do with how the account pages look, they're the easiest thing of all to overlook. If you have any, they'll need to be rewritten around different conditions.

There's an upside, too

Everything written in Liquid was invisible — it appeared in neither the app list nor the admin. What was tucked away where tended to live only in the head of whoever wrote it. Once the person in charge changes, it becomes even harder to trace.

After migrating, everything on the account pages is a block. Open the editor and you can see at a glance exactly what's in there.

This, too, mirrors checkout: open the checkout editor and you can see every extension installed, in one list. The account pages become much the same.

You lose some freedom, but you gain visibility — and handovers become far easier to trace.

Five steps to a calm migration

Rather than diving straight into migration work, we recommend first taking stock and sorting out the traffic.

1. List every app and feature currently on or around your account pages
2. Check whether your theme's Liquid touches the account pages (this won't show in the app list). Shopify's upgrade guide describes the exact procedure.
   • In the theme editor, open "Legacy customer accounts" from the page selector and review each of the seven templates (account / account activation / addresses / login / order / register / password reset) one by one
   • Also check the .liquid files under templates → customers in the code editor
3. For each app, confirm its support status for the new customer accounts (supported, or undecided)
4. Check Flow automations and customer segments for any conditions based on legacy accounts
5. Sort everything into the four groups above and set priorities

That alone turns "I don't know where to start" into "here's what to do next." Start there.

And here's the reassuring part: even after migrating, you can revert to the previous version within 30 days. So you can prepare, flip the switch once, and roll back if anything unexpected happens.

Migration is also a chance to tidy up

Taking inventory often surfaces features you no longer use, or features that overlap. "We installed it but never really used it." "Two apps do the same thing." Run a Shopify store long enough and it happens to everyone.

Since you'll be reviewing everything once anyway, this is a good moment to consolidate.

Mypage Blocks bundles receipts, extra profile fields, notification categories, and more into a single app (currently free). If you've been running one app per feature, there may be room to consolidate.

Japanese e-commerce in particular has needs that overseas apps rarely reach: furigana fields, receipts compliant with the qualified invoice system, address autocompletion from postal codes. We built Mypage Blocks to fill in those gaps around Shopify's defaults — so the step you don't want to give up on is just one block away, no code required.

The three account-page features Japanese merchants ask for most

Once your inventory is done and you're assembling account pages suited to Japanese commerce on the new customer accounts, these three features are in especially high demand. With Mypage Blocks, each one is added simply by placing a block — no code.

1. Receipt / invoice PDFs (qualified invoice compliant)

"Where can I download a receipt?" — an inquiry that has only grown since Japan's invoice system took hold. Customers resolve it themselves, right from their account page. Receipts include your registration number and per-rate consumption tax breakdowns (taxable totals and included tax by rate).

2. Collecting extra profile fields

Birthdays, gender, referral codes — information Shopify's defaults can't collect — entered by customers themselves on their account page. It becomes the starting point for your next campaign: birthday offers, segmented sends, and more.

[Profile fields (customer view)]

[Profile fields (app settings)]

3. Notification category preferences

Before customers hit "unsubscribe from everything," let them choose the genres they actually want. Fewer unsubscribes, and only the information each customer needs.

[Notification preferences (customer view)]

[Notification categories (app settings)]

In closing

The earlier you take stock, the calmer the migration from legacy customer accounts becomes — and it doubles as a great opportunity to rethink your account pages.

Two points to remember:

• Don't assume "the apps will handle it." Check each app's support status for the new customer accounts (supported, or undecided), one by one
• Anything custom-built in your theme's Liquid won't appear in the app list — go looking for it deliberately

"We've installed so many apps we don't know where to start" — that's a perfectly fine place to begin. Start with the inventory, one step at a time.

Feature requests welcome!

Mypage Blocks is still a growing app. "It would really help if it could do this" — those voices directly set the priority of what we build next.

We're actively surveying the stores using it today. Nothing is too small — if something comes to mind, please send it our way.

Stories like "another app did it this way" or "here's a custom that matters in Japan" help enormously too. We'd love to grow this app together with you, so that running your shop keeps getting better.

Learn more

You can explore Mypage Blocks features and settings here:

• Help Center (Mypage Blocks) … how to set up and use each feature
• Feature list … everything the app includes, at a glance

Questions after trying it out? Feel free to reach our support desk anytime.

References

• Legacy customer accounts are deprecated (Shopify Changelog)
• Upgrading to customer accounts from legacy customer accounts (Shopify Help Center)
• Setting up and managing customer accounts (Shopify Help Center)
• Customer account UI extensions (Shopify.dev)
• Building apps for customer accounts (Shopify.dev)
• Legacy customer accounts are deprecated (Shopify Changelog, for merchants)