May 19, 2026

Customer Account Migration: Why Passwords Don't Carry Over

Plan customer account migration to Shopify Plus: profiles, sign-in, payment methods, B2B access and clear launch communications.
7 min read
Flux Insights Static Hero
Adam Tregear
Founder @ Flux

Customer profiles and customer sign-in are different parts of a migration. Shopify's customer CSV does not import passwords, but that does not mean everyone needs a reset email. Choose the account experience first, then plan how customers will find their profiles, orders and subscriptions after launch.

Why a customer import does not move passwords

Passwords are normally stored as one-way hashes rather than readable text. A customer-data export is not a portable sign-in system.

Authentication formats and migration options vary by platform and account version. Do not promise that old credentials will work without checking the supported route.

For Shopify, the practical limit is clear: customer CSV imports do not import passwords. Order history and calculated customer totals also need separate handling; they are not imported with the customer CSV.

Current Shopify customer accounts support passwordless sign-in. Shopify Plus can also connect an external identity provider. Plan and test the chosen experience rather than treating a reset as inevitable.

Keep the scope specific to the source, target and identity setup. The right question is whether customers can reach the correct profile and order history after the move.

What needs separate planning

Three areas need their own checks before cutover.

Sign-in. Choose current passwordless accounts, an approved identity-provider setup, or a legacy account flow where applicable. Test it with migrated profiles before sending instructions.

Stored payment methods. Migration depends on the payment provider, target gateway and supported route. Shopify documents saved-payment-method migration options; changing processors does not automatically mean every customer must re-enter a card.

Confirm eligibility and responsibilities with the providers before cutover. Test supported imports and prepare a clear payment-update route for customers whose method cannot move.

Subscription payment authorisation. The contract and payment method need a supported migration plan, with provider confirmation before billing starts. Recharge, Skio, and most subscription apps have re-vaulting tooling that handles 80 to 95% of subscriptions automatically. The remainder need a customer-initiated payment update. Confirm actual coverage for your store rather than using that range as a guarantee.

Explain the chosen sign-in experience

For current customer accounts, explain the email verification code. The reset and activation patterns below apply only where a legacy password-based setup is retained.

Pattern 1: Pre-launch email campaign. Two to seven days before cutover, explain the move and the sign-in method customers will use. For a legacy setup, confirm that activation is ready before sending links.

Pattern 2: At-cutover email. On launch day, send the correct account link and simple sign-in instructions. Use password or activation instructions only for the account version that needs them.

Pattern 3: First-login guidance. Make the account page and support content explain the same steps as the email. Test the fallback for customers who cannot access the expected profile.

Use a launch announcement plus clear on-site guidance. The email, account page and support team should all describe the same sign-in experience.

Specific guidance for high-value segments

For three customer segments, the standard email isn't enough.

Active subscribers. These customers have recurring billing authorisations that need attention. The email needs to explain that subscriptions continue but they may need to update payment details. Most subscription apps handle re-vaulting silently, but the 5 to 15% that fail need explicit communication. Best to stage subscriber communications separately from the broader customer base.

B2B and wholesale. Account managers should reach out individually to top accounts before the broader email. The B2B login flow is different (company-aware) and the workflow changes are bigger. A single email isn't enough for this segment.

VIPs and top spenders. A personal email from someone known to them (account manager, founder, head of CX) outperforms the generic broadcast significantly. For brands with a top 5% segment that drives a disproportionate share of revenue, the extra effort pays back.

The standard customer email handles 90+% of the base. The other 10% deserves named attention.

B2B customer migration specifically

B2B customer migration is more involved than B2C. It's not just data; it's structure.

Source platforms model B2B differently. WooCommerce plugins, Magento companies, Salesforce customer groups and ATG organisations need an explicit mapping. The migration usually involves these steps:

Step 1: Audit source B2B structure. What does a company look like on the source platform? What are the buyer roles? What pricing rules apply per account?

Step 2: Reconstruct companies. Create company records with all locations.

Step 3: Re-assign customers. Map customers to the correct locations with ordering-only or location-admin permissions. Check who can order and which history they can see.

Step 4: Build catalogues. Translate pricing rules into Shopify B2B catalogues. Each pricing tier or per-account pricing rule becomes a catalogue.

Step 5: Configure payment terms. Map net-30, net-60 or prepaid arrangements to the right locations. Specify order-review rules separately from buyer permissions.

Step 6: Test before broadcast. Sample companies log in and complete a test transaction before broader cutover.

For B2B-heavy brands, customer migration can be the longest workstream of the entire migration. A 4 to 8 week project parallel to the rest of the build is normal.

Edge cases worth flagging

Three edge cases come up often enough to plan for.

Duplicate customers. Source platforms often accumulate duplicates: same person registered twice with different emails, account merges that didn't fully complete, guest checkouts that created shadow records. Migration is the moment to deduplicate. The script logic merges by primary email, secondary email, and phone where confidence is high, and flags ambiguous matches for manual review.

Inactive customer pruning. Some brands use the migration to retire customers who haven't ordered in 24+ months. Reduces the customer database, improves email metrics, and clarifies the active base. The decision is brand-specific. Some brands keep inactive customers because reactivation campaigns work. Others prune.

International customer data. Customers across multiple regions may have different consent states or privacy obligations. GDPR, CCPA, and Australian privacy law all apply differently. The migration needs to preserve consent state per customer per region, and the password reset email needs to comply with local consent requirements.

Where to start

If you're planning a migration and want to handle the customer side cleanly, the audit phase should include a customer data audit covering total count, duplicate count, B2B structure, subscription population, and segmentation. The output is a migration plan, a communications timeline, and a re-vaulting strategy for any payment authorisations.

For the related glossary entry that covers this in summary form, see customer account migration. For broader context on Shopify Plus migrations, see the complete migration guide.

For the SEO and infrastructure work that runs alongside customer migration, how to preserve SEO when migrating to Shopify Plus covers the URL and ranking work. For platform-specific guidance on customer data structures, the Magento, WooCommerce, and Salesforce Commerce Cloud playbooks cover what's specific to each source.

Or browse the rest of our Platform Migration insights for more on the operational decisions that come with a re-platform.

Our Shopify Plus migration process covers customer data alongside catalogue, integration and SEO work.

Frequently asked questions

Why can't customer passwords transfer between platforms?

Shopify does not accept passwords in a customer CSV import. That is separate from account access: current accounts support passwordless sign-in, and a Plus store can use a connected identity provider. Test the chosen setup with migrated profiles before launch.

What customer data actually transfers during migration?

Profiles, addresses, consent records and supported custom data need explicit mapping and validation. Customer CSV imports do not import passwords, order history or calculated spend/order totals. Plan the appropriate migration route for each, with separate checks for payment methods, subscriptions and B2B membership.

How do customers regain access after migration?

Current Shopify customer accounts use passwordless sign-in, so explain the email verification code rather than sending everyone a reset. If a legacy password-based setup is retained, plan activation and support separately. For a legacy reset flow, the completion ranges are 30 to 50% within 30 days, 50 to 70% within 90 days, and 70 to 85% within 12 months. The remaining 15 to 30% are inactive customers who never come back regardless. These are not targets for the passwordless flow.

Will my saved payment methods transfer to Shopify Plus?

Sometimes. Supported saved-payment-method migration depends on the providers, target gateway and migration route. Ask the providers to confirm eligibility, test the import, and prepare a payment-update route for unsupported methods rather than assuming either full portability or universal re-entry.

What about active subscriptions during migration?

Subscription apps like Recharge and Skio have re-vaulting tools that handle 80 to 95% of subscriptions automatically by working with the payment processor. The remaining 5 to 20% need a customer-initiated payment update. Subscriber communications should be staged separately from the broader customer base because the message and stakes are different.

How should I communicate the migration to customers?

A single launch-day email handles 80 to 90% of the customer base. Subject line should be brand-led and direct ("We've moved [Brand] to a new home" rather than "Your password has expired"). Body should be a one-paragraph note from a real human at the brand explaining the move and previewing what's better. For VIPs, B2B accounts, and active subscribers, send personalised communication separately.

How does B2B customer migration differ from B2C?

B2B is more involved because it's not just data, it's structure. Source platforms model B2B differently (Magento companies, SFCC customer groups, ATG organisations). The translation involves reconstructing companies, locations, customer permissions, catalogues, payment terms, and approval workflows. For B2B-heavy brands, customer migration is usually 4 to 8 weeks of parallel work.

What happens to inactive customers during migration?

Inactive customers (no orders in 24+ months) migrate by default but are candidates for retirement. Some brands prune them during migration to clean up the database, improve email metrics, and clarify the active base. Other brands keep them because reactivation campaigns work. The decision is brand-specific. The migration audit should flag inactive customer counts so the decision is deliberate.

/score

Does AI recommend your brand?

We ask ChatGPT and Perplexity 10 real buying questions for your category and score you against your biggest competitor. Live, in about 2 minutes.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Free. Enter your store's website, e.g. yourstore.com

Flux is a Shopify Plus Agency for Advanced Engineering & AEO

TLDR Summary
  • Shopify customer CSV imports do not import passwords. Confirm the source, target and identity setup before promising that old credentials will work.
  • Map customer profiles separately from order history, calculated totals, payment methods and B2B structures. Validate what each migration route actually carries.
  • Current customer accounts support passwordless sign-in. Reserve legacy activation or reset instructions for a setup that actually needs them.
  • For high-value segments (subscribers, B2B, VIPs), the email needs to be staged differently. Generic "your password expired" emails get ignored or marked as phishing.
  • B2B customer migration is more involved: company hierarchies, locations, payment terms, and approved buyers usually need to be reconstructed rather than imported as flat customer records.