Yes, in one sense: no platform can move customer passwords to Shopify, so no customer keeps their old one. In practice, most customers never have to reset anything. Stores that launch on Shopify’s new customer accounts let people sign in with their email address and a one-time code, so imported customers can log in from the first day.
Why passwords can’t be moved
Every store platform saves passwords in a form that can’t be turned back into the original. Customer passwords never move to Shopify from any platform, because they are stored as one-way hashes.1 Magento stores passwords as one-way hashes that Shopify cannot read, so in our Magento migration no customer passwords transferred.2 The same applies to WooCommerce and WordPress, since WordPress uses phpass hashing and Shopify uses bcrypt,3 and to Shift4Shop, BigCommerce and the rest. This is how passwords are stored securely, not a weakness of any one migration method.
What your customers actually do after launch
This depends on which kind of customer account your Shopify store uses. Losing old passwords is rarely a problem now: Shopify’s customer accounts sign in with an emailed one-time code, so imported customers can log in straight away without an invitation.1 For that reason, we launch on Shopify’s new customer accounts and recommend explaining the email-and-code sign-in in the launch email.1
If a store uses password-based accounts, returning customers set a new password the first time they sign in. On the Magento project, a clear message about that at launch prevented most of the support emails.2 Whichever setup you use, the launch email matters. On projects like this we have found that one sentence explaining how to sign in heads off most “I can’t log in” messages in the first week.
What moves with each account
The account itself moves, including addresses and order history; only the password stays behind.2 On that Magento store we brought across 7,019 customers with their addresses and 4,504 orders with their original dates, line items and totals. Each order is linked to its customer, so a buyer who logs in sees what they bought in the years before the move.2
Signing in with a code only works if the email on each account is right, so the customer import needs the most care. On one BigCommerce migration, an export of 5,728 rows became 5,720 live accounts after we removed a demo account, merged duplicates and set aside two invalid emails. We also repaired and imported 3 accounts: two with typos in the email address and one with spam text injected into the name.4 Marketing consent needs similar care. When a historical order’s email differs from the customer account it belongs to, Shopify can rewrite the customer’s email and reset their marketing consent, so we keep the account email during import and compare subscriber counts with the source afterward.1
What decides it for your store
For most stores the question comes down to three things. First, whether you launch on Shopify’s new customer accounts, which removes the need for resets. Second, how clean your customer emails are, because the email address is now the login. Third, whether anything outside the store depends on that login. If you run a separate customer portal or web app, Shopify’s passwordless customer accounts can serve as its login too, so one account covers both the store and the service.1 Those links are worth mapping before launch, along with the wording of the email that tells customers how to sign in.
Sources
- Customer accounts From our project notes
- Magento to Shopify Case Study: Urban Remains Chicago Case study
- WordPress to Shopify Migration Guide (2026): Cost & Timeline Migration guide
- Shopify Data Migration Report: Sample Final Report Sample report
“From our project notes” are short, anonymised lessons from migrations we have run. They describe what we typically see, not a guarantee for every store.