Customer Data Mapping

Why Customer Data Mapping needs Custom Migration

Customer groups, custom attributes, address formats, and password hashes differ by platform. A generic import can drop group memberships, flatten addresses, or force password resets. Cart2Cart Custom Migration maps customer data to the target cart’s model so accounts stay useful for marketing, B2B pricing, and support.

Who this customization is for

• B2B stores using customer groups or wholesale roles
• Merchants with loyalty, CRM, or custom customer attributes
• Teams that need a clear password migrate-vs-reset decision
• Stores with messy duplicates or mixed guest/registered history

Common use cases

• Converting Magento customer groups to Shopify tags, Woo roles, or discount segments
• Mapping custom attributes used by CRM or loyalty programs
• Normalizing billing/shipping address formats across countries
• Password migration strategies where hashing is compatible
• Merging duplicate emails or deciding guest-vs-registered rules

What Cart2Cart customizes

We document field-level mapping, group/tag conversions, and password handling options. Test customers are verified before Full Migration so login and account pages behave as expected.

Platform considerations

Shopify lean on tags and metafields; WooCommerce uses roles and user meta; Magento uses customer groups and EAV attributes. Custom Migration translates those models rather than dropping non-default fields.

Note: The Target platform may require installing additional apps, plugins, or add-ons when a capability is not available by default. Custom Migration can map and import the data, but those Target-side apps/plugins often need to be installed and configured so the feature works in admin and on the storefront.

The best way to make sure everything is mapped correctly is to run a Demo Migration with your real Source platform data, then carefully check how entities look on the Target store before Full Migration.

Checklist for evaluating this customized migration

• Inventory customer groups/roles/tags and how they should map on the target.
• List custom attributes needed by CRM, loyalty, or B2B pricing.
• Decide password strategy (compatible hash migrate vs forced reset).
• Define duplicate-email and guest-vs-registered merge rules.
• Test login and account pages for sample customers after Demo Migration.

How to apply for this customization

1. Go to Custom Migration or schedule a call.
2. Share platforms and whether you use groups, B2B roles, or loyalty fields.
3. Clarify password expectations and any privacy constraints.
4. We scope mapping rules, validate on Demo customers, then run Full Migration.

Self-service Additional Options vs Custom Migration

Customers migrate as a core entity. Passwords and group→tag conversion are common Wizard Additional Options. Custom Migration handles broader field maps, address rules, and B2B role strategies.

• Migrate customers’ passwords — Self-service: Where hash compatibility allows, customers can sign in on Target with source credentials (Wizard option). Choose Custom Migration when: Custom Migration when hashes are incompatible and you need a defined reset/notification plan plus attribute mapping.
• Migrate Source customer groups into customer tags — Self-service: Map groups to Shopify (or similar) customer tags in the Wizard for supported pairs. Choose Custom Migration when: Custom Migration for roles, metafields, loyalty attributes, or non-tag group models.
• Preserve customer IDs on Target Store — Self-service: Keep customer IDs when supported (usually with Clear Target data). Choose Custom Migration when: Custom Migration for CRM external IDs stored as metafields/references when native IDs cannot be preserved.

Availability depends on your Source → Target pair—confirm checkboxes in the Migration Wizard Entities / Additional Options step. See the Additional Options guide and Additional Options FAQ for pair-specific details. If Wizard options are not enough, schedule a Custom Migration call.

Already ran a self-service migration?

Yes—you can still apply this Custom Migration after a Wizard (self-service) run. Cart2Cart can restart migration with the customized rules; the Target store typically needs Clear current data on Target Store before Migration (or an equivalent cleanup of the entities from the previous self-service migration) so customized results are not mixed with the old import. Share your Source/Target carts and what already moved—Migration Experts will confirm the safest clear-and-rerun plan before Full Migration. Schedule a call if you already completed a Demo or Full Wizard migration and need customization next.

Case studies from real Custom Migrations

Cart2Cart Migration Experts have delivered custom work related to Customer Data Mapping across 243 recorded customization projects spanning 58 Source→Target platform pairs. Below are pairs we see most often, the entities typically involved, and sample data volumes when available.

Platform pairs already in focus

• WooCommerce → Shopify — 42 customization projects
• Magento → Shopify — 36 customization projects
• Wix → Shopify — 17 customization projects
• PrestaShop → Shopify — 16 customization projects
• BigCommerce → Shopify — 13 customization projects
• Magento → WooCommerce — 10 customization projects

Entities commonly customized

• Customers — seen in 172 related projects
• Orders — seen in 158 related projects
• Products — seen in 130 related projects
• Categories — seen in 68 related projects
• Coupons — seen in 32 related projects

How much data was migrated

Among projects with recorded store size, median migration volume is about 15.4K records, with larger builds reaching roughly 130.9K at the 90th percentile and peaks near 2.6M. Exact counts depend on products, customers, orders, and related entities in scope.

Sample projects

• BigCommerce → Shopify — entities: Coupons 2.2M, Orders 302.3K, Customers 141.3K, Products 8.5K — total volume ~2.6M
• BigCommerce → WooCommerce — entities: Orders 524K, Customers 381.1K, Reviews 7.1K, Coupons 6.4K — total volume ~912.2K
• WooCommerce → Shopify — entities: Orders 529.8K, Customers 82K, Coupons 15.1K — total volume ~655.7K
• Magento → Shopify — entities: Orders 320.5K, Customers 8.2K — total volume ~328.8K

Every store is different—share your Source/Target carts and entity scope on a Migration Expert call and we will estimate a similar Custom Migration path.

What we need to scope customer data mapping

Customer groups, custom attributes, address formats, and password hashes vary by platform version and how B2B or loyalty data was added over time. Your Source schema—not a generic field list—drives the mapping plan.

The cleanest approach is temporary staging or production access so we can inspect groups, attributes, and login behavior on sample accounts. Without access, a customer-related database dump can be analyzed offline; that path commonly needs a refundable deposit for secure restore and schema review before we finalize Custom Migration scope.

Tip: Initial data-structure analysis is much more efficient when you prepare exact examples of the important attributes and fields on the Source, plus how each should be mapped on the Target store (sample products/customers/orders with field names, values, and desired Target destinations). Clear examples reduce discovery time and help Migration Experts quote and implement the customization accurately.

FAQs

Can customer passwords always migrate?

Only when hash algorithms are compatible with the target. Otherwise we plan a reset/notification flow.

What happens to customer groups?

We map them to the closest target construct—tags, roles, or metafields—based on how you price and segment.

Will addresses import cleanly internationally?

Usually with normalization. Unusual country/state formats are part of the mapping review.

Keep customer relationships intact when you change platforms—talk to Cart2Cart.