E-Commerce Nov 19, 2026

Migrating Customer Accounts: Logins, Order History and B2B Companies

Migrating Customer Accounts: Logins, Order History and B2B Companies

Time to read: 11 minutes

Content

  1. The account migration decision matrix
  2. Passwords: legacy hash support, passwordless sign-in or a reset campaign
  3. Order history: migrate as records, keep an archive, or leave it behind?
  4. B2B accounts: companies, buyers, roles, price lists and payment terms
  5. Consents, loyalty balances and store credit: data that must keep its evidence
  6. Cutover and delta migration: accounts created during the freeze
  7. First-login acceptance tests and the customer-service script
  8. What our migration projects show
  9. Exceptions
  10. Test the result
  11. FAQ
  12. Your next step
Bookmark

Customer records usually migrate; working logins often do not. Before cutover, decide for each account type how customers sign in on day one, which order history and balances move, how B2B companies and buyers are rebuilt, and how marketing consents keep their evidence. Then prove it: a seeded account of every type signs in, sees its last order, reorders and, for B2B, orders within its limits.

Whether old password hashes can be reused depends on the target platform and the migration route. Shopify says "you can't migrate customer passwords from another online store using a CSV", because "passwords are encrypted outside of Shopify". Shopware's guide for Magento migrations, by contrast, advises keeping its migration extension installed, "as the password algorithms used by Magento would otherwise no longer be available and migrated customers would no longer be able to log in." So choose early, per account type, between legacy-hash support, a passwordless or one-time-code login, and an invitation or reset campaign. Accounts are the part of a migration customers notice first: a failed sign-in, a missing order or a wrong balance shows up on their first visit, and then in your support queue.

Below: an account migration decision matrix, a first-login acceptance test and a customer-service script. The example is fictional; vendor rules are as documented in November 2026. Where accounts sit in the whole project is covered in our replatforming guide.

The account migration decision matrix

Fill one row per account type, with these columns:

Illustrative example (fictional). A home-textiles retailer with 120,000 customers moves from Magento 2 to Shopify Plus. Passwords cannot be imported, so the team relies on one-time-code customer accounts and a staged email to the 38,000 customers active in the last 24 months. Its 9,000 B2B buyers from 1,400 companies are rebuilt as B2B companies with locations and catalogs; three years of orders migrate for display; marketing consents keep their original timestamps; store-credit balances are reconciled on a 500-account sample; and a delta run imports accounts created during the 48-hour freeze. The filled matrix, condensed:

Account typeDay-1 loginWhat migratesFirst visitCommunicationTest and owner
GuestOne-time code, once the order email is matched to a profileProfile built from guest orders; three years of orders; consent only where the order record holds an opt-inPast orders appear if the email matchedNone; orders appear at first sign-inSeeded guest with two orders sees both; CRM owner
RetailOne-time codeProfile, addresses, three years of orders, consents with original timestampsCode instead of passwordStaged email if active in 24 monthsSigns in, opens last order, reorders; ecommerce lead
LoyaltyOne-time codeAs retail, plus store creditBalance equals the reconciled ledgerAs retail, plus balance confirmationBalance matches on the 500-account sample; loyalty owner
SubscriberOne-time codeAs retail; subscription and payment method follow their own planNext delivery and charge date unchangedAs retail, plus next charge dateSubscription test passes; subscriptions owner
B2B adminOne-time codeCompany, locations, contacts, catalogs, payment terms; three years of orders and consentsCompany location, catalog prices, net termsNotice to company admins before launchSigns in, orders on net terms; B2B lead
B2B buyerOne-time codeContact with "ordering only" permission at its location; three years of orders and consentsCatalog prices; old spending limit not yet mappedSign-in guide through the company adminOrder within and above the old limit behaves as agreed; B2B lead
Account migration matrix and cutover lane Matrix of six account types (Guest, Retail, Loyalty, Subscriber, B2B admin, B2B buyer) against four day-1 outcomes (Login, History, B2B, Consent). Login is Action for every type. History is Action for Guest and Ready for the other five. B2B is n/a for the four consumer types, Action for B2B admin and Gap for B2B buyer. Consent is Action for Guest and Ready for the other five. Below, the cutover lane runs freeze and final export, delta import of freeze changes, first-login tests on every type, then go-live. Day-1 outcome by account type Login History B2B Consent Guest Action Action n/a Action Retail Action Ready n/a Ready Loyalty Action Ready n/a Ready Subscriber Action Ready n/a Ready B2B admin Action Ready Action Ready B2B buyer Action Ready Gap Ready Ready: migrates as is Action: decision, rebuild or message Gap: no confirmed target route n/a: not applicable Cutover lane 1 Freeze and final export 2 Delta import of freeze changes 3 First-login tests, every type 4 Go-live
Day-1 outcomes in the fictional example. Login is Action for every type because passwords do not move and every customer switches to code sign-in; the B2B buyer gap is the unmapped spending limit. The lane shows the cutover order.

Passwords: legacy hash support, passwordless sign-in or a reset campaign

RoutePossible whenCustomer experiencePlan for
Legacy hash supportThe target verifies the old hash format on this exact migration pathSame password as beforeKeep the component that holds the old algorithms; test with real migrated hashes
Passwordless or one-time codeThe target offers code sign-in for migrated profilesEmail address plus a codeCustomers who expect a password; a different email creates a new, empty profile
Invitation or resetHashes cannot move and codes are not availableSets a new password from an emailCustomers who never act; ticket load after launch

What the vendors document:

Code-based sign-in makes the message simpler, not optional: the Communication column records who hears what, and when. Our Shopify migration services cover this decision as part of the move.

Order history: migrate as records, keep an archive, or leave it behind?

Order history serves three jobs: the customer's order list, reorders and customer service. Decide per job:

Reorder depends on product mapping. An imported order line becomes a new cart only if its old SKU maps to a live product, so test the reorder, not just the display.

Order history: decide per jobOrder history choices: migrate as records for the period customers reorder from, keep a searchable read-only archive, or leave it behind when nobody needs it, and test that reorders map to live products.Order history:decide per jobOrder list, reorders, customer serviceMigrate as recordsFor the period customers reorderfrom or ask aboutKeep an archiveA read-only export customer serviceand finance search by customer IDLeave it behindWhen nobody needs it: GDPR dataminimizationTest the reorder, not justthe displayAn order line becomes a cart only ifits old SKU maps to a live product

B2B accounts: companies, buyers, roles, price lists and payment terms

A B2B account is a structure, not a profile. Shopify B2B, for example, has three levels: "A company is the parent organization for one or more company locations"; a location "can have its own tax ID, tax exemptions, ship-to address, billing address, pricing, payment terms, checkout settings, and contacts"; and a customer "represents the individual that purchases on behalf of a business". To sign in as B2B, a customer must be "associated with one or more company locations". Shopify lists "Location-level permissions (location admin and ordering only)" on every B2B plan, while catalogs assigned directly to a company or location need Plus. The Admin API's companyCreate can create a company with an initial contact and location in one operation.

Source structureTarget (Shopify B2B)Acceptance check
Company accountCompanyName, external ID, main contact
Branch or ship-to addressCompany locationAddresses, tax ID, exemptions
Buyer and roleCustomer as location contact with a permissionEach buyer sees only their locations
Customer-specific price listCatalogPrices for sampled SKUs per company
Payment termsLocation payment termsNet terms offered at checkout
Spending limit or approval ruleNative feature, app or custom rule, confirmed before cutoverOver-limit order blocked or routed as agreed

In the example, the old store's per-buyer spending limits have no confirmed target route yet, so the B2B buyer row stays marked as a gap until one is chosen and tested.

Consents, loyalty balances and store credit: data that must keep its evidence

GDPR Article 7(1): "Where processing is based on consent, the controller shall be able to demonstrate that the data subject has consented to processing of his or her personal data." A yes/no flag is not that evidence. Shopify's customer CSV takes only yes or no in its marketing columns, while the Admin API's email consent input takes the marketing state, an opt-in level and consentUpdatedAt, "The latest date and time when the customer consented or objected". Carry the original timestamp where the target accepts it, keep the source evidence (form, wording, date) in an archive, and import any contact without proof as not subscribed. Never turn an unknown into an opt-in. This is a practical checklist, not legal advice; your DPO decides.

Loyalty points, store credit and gift card balances behave like money. Reconcile them account by account against the source ledger, not only in total: in the example, all 500 sampled accounts must match before go-live. How points behave across pickup and returns is covered in loyalty, pickup and returns during replatforming.

Data that must keep its evidenceConsents keep their original timestamp and archived source evidence, contacts without proof import as not subscribed, and loyalty, store credit and gift card balances are reconciled account by account.Data that must keepits evidenceConsents, loyalty and store creditCarry the originaltimestampWhere the target accepts it; ayes/no flag is not evidenceArchive the source evidenceForm, wording and dateNo proof means notsubscribedNever turn an unknown into an opt-inReconcile balances peraccountPoints, store credit and gift cardsagainst the source ledger, not onlyin total

Cutover and delta migration: accounts created during the freeze

The final export is a snapshot; customers keep registering, ordering and editing addresses until the old store stops. Plan a freeze window and a delta run. For Magento 1 to 2, Adobe's Data Migration Tool has a delta mode that carries "Data that customers added via storefront (created orders, reviews, and changes in customer profiles)". Between different platforms, build the delta from created and updated timestamps.

Test three delta cases: new accounts (in the example, those created during the 48-hour freeze), changed email addresses and duplicates. Shopify's CSV import skips duplicate emails or phone numbers and imports "Only the last profile", and signing in with an unknown email creates a new profile automatically, so a customer who changed email during the freeze can end up with two profiles. Staff can merge them in the Shopify admin.

First-login acceptance tests and the customer-service script

Seed one account per type on staging with known orders, balances and consents. Every type also opens its last migrated order and reorders it; the rows below add the type-specific check.

Account typeTestPass
GuestSign in with the order emailMatched orders visible
RetailSign in with a code; reorder the last orderCart holds the mapped products
LoyaltySign in, open the balanceEquals the ledger
SubscriberSign in, open the subscriptionNext charge date unchanged
B2B adminSign in, switch location, order on net termsCatalog prices and terms correct
B2B buyerOrder within and above the old limitAgreed behavior both times

Go-live needs no "cannot access" result for any type.

Give customer service a one-page script before launch: what changed in sign-in, where orders older than the migrated window live, how to merge duplicate profiles, how to correct a balance, and whom to escalate to. Subscribers' payment methods and next charge need their own test; see migrating subscription customers.

What our migration projects show

Our case pages show data scope, not login outcomes. The Zebrapack migration (Magento 1.9 to 2.4.1) says all essential data, including customers, products and order history, was transferred "without disruption". The Mon Tresor Bebe wholesale store moved from Shopify to Magento 2 with users, products, articles, gallery and orders migrated. Goddess, a Magento 1 to 2 migration, listed "Implementing the delta-migration" among its tasks. For Prostor, a Magento 2 migration for an omnichannel drugstore chain, the case page lists a unified loyalty balance across online and in-store, and guest checkout. None of these pages says how passwords were handled.

The honest limit: no route makes every customer's first sign-in uneventful. The tests remove the surprises you can find before launch; the customer-service script handles the rest.

Exceptions

Test the result

Seed one account per type on staging, run the first-login, order-history and reorder tests with no "cannot access" result, and reconcile consents and balances on a sample. If any type fails, its matrix row is not ready, whatever the import log says.

FAQ

Can we migrate customer passwords to Shopify?

Not with the customer CSV, and the Admin API's customer input has no password field. Shopify's current customer accounts sign in with a one-time code instead, so a migrated profile can sign in without a password.

Do customers have to register again?

On Shopify's current customer accounts, no: a customer with a profile "already" has an account. With password-based accounts, they need a reset or invitation unless the target can verify the old hashes.

Can B2B buyers keep their logins?

They keep their email address. On Shopify B2B they sign in with a one-time code once they are contacts of a company location.

Can marketing consent be imported?

Yes, as a state. Carry the timestamp where the target accepts it, and keep the evidence in an archive.

Your next step

Fill the matrix for your account types and seed one test account for each before you approve the migration plan. For a second review, our ecommerce replatforming consultancy team can check the matrix and the test results against your source and target platforms.

Let professionals meet your challenge

Our certified specialists will find the most optimal solution for your business.

Please enter valid name
Please enter valid company
Please enter a valid phone
Please enter valid E-mail
Message is too short

    Your message has been successfully sent. We will be in touch shortly! Success icon