Moving Customers and Order History to Shopify: What Can Be Preserved?

Direct answer: a customer list, a login account and an order history are three different parts of a Shopify migration. Importing customer profiles does not move their previous passwords or recreate their orders. Each part needs a supported transfer method and its own acceptance tests.

The useful question is not whether the source system can export a CSV. It is whether staff and customers will still be able to find, trust and act on the information they need after launch.

Start with the purpose of the records

An ecommerce business may need old customer data for returns, warranty enquiries, customer service, accounting or legitimate marketing preferences. Those uses do not all require the same destination.

Inventory customer identities, billing and shipping addresses, order line items, payment and fulfilment states, refunds, discounts and existing marketing preferences. Record the source system, the original identifier and the reason each field is still required. An archive may be appropriate for information that must remain accessible but does not need to behave like a live Shopify order.

Shopify's migration documentation lists distinct methods for products, customers and historical orders. That separation is important: a single successful import file does not prove that a customer's purchasing history has survived.

Customer CSV files have a defined scope

Shopify's customer import guidance describes customer profiles and supported fields, not a universal transfer format. In particular, a customer CSV cannot import historical orders or passwords. Its Total Spent and Total Orders columns do not recreate transactions from the previous platform.

Before the import, normalize addresses, identify guests, establish the handling of missing email addresses and inspect duplicate email or phone records. Shopify documents specific duplicate-handling and overwrite behaviour; test the chosen options with a small file rather than assuming that two source profiles will be merged in a useful way.

Keep a secure source-to-target ID mapping for records that must later be associated with transactions. Where identifiers cannot be retained in native fields, decide how authorised staff will recover the corresponding source record. Never make identity decisions from display names alone.

An example where customer counts are misleading

Imagine a source export containing two customer profiles that share an email address and have different order histories. Importing one profile into Shopify may make the customer count look plausible while leaving the relationship to historical orders unresolved.

A meaningful acceptance test follows the original customer IDs, expected addresses, order identifiers and links between them. Matching a total count is a preliminary check, not a reconciliation result. This is an illustrative test case, not a client case study.

Design the first login instead of migrating passwords

Passwords from another ecommerce system cannot be copied through Shopify's customer CSV. The correct first-login experience depends on the account configuration used by the new store.

Shopify distinguishes its newer customer accounts and legacy customer accounts. Current customer accounts use an email-based sign-in flow, while legacy experiences follow different rules. Do not promise that everyone must reset a password, and do not promise that an old password will continue to work.

Test a returning customer on a real supported account configuration. Can they receive the sign-in email? Do they recognise which address to use? What does the account show when historical orders are retained elsewhere? Prepare support instructions that describe the actual configuration rather than a hypothetical one.

Treat historical orders as a separate migration

Orders contain more than a date and a total: customer references, product lines, quantities, tax treatment, discounts, fulfilment, payments and possible refunds all affect their meaning.

The Shopify migration guide identifies migration apps and supported APIs as routes for historical orders. The customer CSV is not one of those routes. Shopify also recommends importing products first, then customers, then historical orders, so that references can be connected where the chosen method supports them.

Decide in advance whether old transactions need to be visible in the customer's account, accessible only to support agents or available in an external archive. These are different deliverables, with different testing and maintenance implications.

There is also an operational side effect to check: Shopify warns that staff configured to receive new-order notifications may receive notifications for imported historical orders. Review the actual notification setup and the selected import process before running a large historical import.

Reconcile behaviour, not just records

A test dataset should include an ordinary fulfilled order, an order with a refund, an order with multiple tax treatments, a guest checkout and an order whose original product no longer exists. Include a customer with several addresses and an account with no transferable password.

For each test, compare the source and destination on the details that matter: original order number, customer relationship, transaction date, line items, subtotal, taxes, discounts, shipping, payment state and refund history. A discrepancy can be intentional if the chosen archive or import model cannot represent an old event exactly; document that decision instead of silently changing the meaning.

Record Destination to evaluate Acceptance evidence
Customer identity Shopify customer profile Correct identity and address mapping
Previous password Supported first-login process Legitimate returning customer can access the account
Fulfilled historical order Supported migration method or archive Original transaction retrievable without a duplicate sale
Refunded order Supported method or archive Refund state and amounts remain understandable
Marketing preference Verified consent mapping Provenance and permissions remain distinguishable

This matrix is a planning example. It should be expanded to reflect the actual platform and the business's retention obligations.

Possessing a customer's email address does not establish permission for promotional messages. Subscription preferences, the source of a consent and any supporting evidence need their own mapping and review.

Do not invent missing marketing permissions, convert a general contact into a subscriber by default or carry across unnecessary personal information simply because the old platform can export it. Check the applicable legal basis, retention rules and access controls for the actual business.

Also distinguish an imported marketing preference from engagement history. The Shopify customer CSV documentation describes limits on transferring historical email engagement data. A new profile is not proof that past campaign activity is available in the destination.

Choose import, archive or both before launch

A full historical import can create complexity without improving service if the importer cannot preserve the required statuses or relations. Conversely, an inaccessible archive can make returns and warranty enquiries needlessly difficult.

Use the following decision sequence: define which historical actions staff and customers must perform; select the lowest-complexity supported method; import a representative sample; test the full customer journey; and obtain explicit acceptance of documented gaps. Protect the original export and a recovery path according to the agreed retention policy.

After launch, sample real support workflows without exposing private customer details in public logs. Confirm that staff can identify an old order, distinguish it from a new Shopify order and respond correctly when a customer cannot access their purchase history.

For mapping products and variants before historical orders, see the Shopify catalogue migration guide. To evaluate a complete migration with its data, account and operational requirements, the Shopify migration service is delivered directly by Francesco Guiducci.

A defensible migration preserves the meaning and accessibility of necessary records. It does not treat every piece of historical data as a field that must be recreated in the new store.

Sources cited in this article

Official documentation and external references linked in the text. Shopify features change: always check against the current version.

Topic: Migrations and platform choice · customer migration, historical orders, customer account access

How to cite this article

Guiducci, F. (2026). Moving Customers and Order History to Shopify: What Can Be Preserved?. IFG Digital. Last updated 17 November 2026. https://ifgdigital.com/en/ifgwebdesign/ecommerce/blog/shopify-customer-order-migration-accounts-history/

With your consent, Google Analytics 4 measures visits and interactions. With both categories enabled, it also uses Google click identifiers to attribute requests to Google Ads. Marketing also enables Meta Pixel for page views and WhatsApp clicks. Google and Meta do not receive form entries, messages or contact details. Google remarketing and ad personalisation stay off. You can refuse or withdraw from the footer. With Marketing enabled, the OpenAI pixel measures visits and may detect contact details from forms and send them as hashes with advertising identifiers.