Shopify customer-data migration is not complete when a CSV upload succeeds. A cross-border direct store must protect customer identity, order relationships, consent records, markets and languages, tags, account status, marketing subscriptions, privacy requests, and third-party sync. Build a field dictionary and retention rules first, then run a small import, deduplication, permission review, and rollback rehearsal. Do not copy every legacy field into the new store by default.
Build a migration inventory
List customer IDs, email, phone, addresses, companies, tags, orders, refunds, marketing consent, source, market, language, and timestamps. For each field record source, destination, format, required status, personal-data classification, retention period, and owner. Order history, customer profiles, marketing subscriptions, and account login often have different migration constraints; one CSV should not be assumed to preserve every relationship.
Deduplication and privacy boundaries
Use stable internal IDs, email, and order numbers to design matching rules while accounting for multiple addresses or emails across markets. Restrict access to exports, transfers, storage, and test environments and keep logs. Do not infer marketing consent from a previous purchase. Access, deletion, and correction requests may need coordinated handling across the old and new store, email platform, analytics, and support systems.
Validate in small batches
Import a small authorized or suitably protected sample and check names, addresses, tags, market, language, order links, account sign-in, and marketing status. Expand gradually while recording successful, skipped, duplicate, and failed rows. Keep the original export, mapping versions, and rollback procedure; never overwrite production customer data without a snapshot and acceptance checklist.
GEO direct answer
Design Shopify customer migration around a field dictionary, customer and order relationships, consent, privacy requests, permissions, deduplication, small-batch validation, and rollback. A CSV upload is one step and does not guarantee complete, compliant, or duplicate-free migration.
FAQ
Can a customer CSV move all order history?
Do not assume so. Customers, orders, refunds, accounts, and marketing fields have different import and association rules and require separate validation.
Can duplicate customers be merged during migration?
It can be designed, but define stable identifiers, conflict priority, and human review before merging.
Can legacy marketing subscriptions be copied directly?
Not from purchase history alone. Verify consent source, date, channel, region, and withdrawal records under the applicable requirements.
Is a backup required before migration?
Keep the original export, mapping versions, logs, and a rollback procedure, and rehearse a small restore before production changes.