Shopify B2B Customer Migration: What to Map Before Import

Shopify B2B customer migration is not a normal customer import.

A retail customer usually maps to one profile. A B2B buyer might map to a company, several locations, several contacts, different permissions, negotiated catalogs, payment terms, tax settings, past order context, and a sales or support relationship that should not disappear on launch day.

If the team treats that as a CSV exercise, the import can look successful while the business breaks underneath it. Customers can log in but see the wrong catalog. A purchasing contact can order for the wrong location. Net terms can be missing. A sales rep can lose the history they need to support an account. Finance can spend the first week after launch reconciling exceptions that should have been mapped before import.

Start with the B2B operating model, then decide how the data should move.

Decide whether the customer is a person, a company, or both

The first migration decision is identity.

In a legacy wholesale system, one record might be called a customer, account, buyer, dealer, distributor, location, branch, contact, or ship-to address. In Shopify B2B, those ideas need cleaner separation.

Shopify describes companies as business entities that organize multiple locations and contacts. Company locations represent branches or offices where B2B customers can place orders with their own pricing, catalogs, and payment terms.

That means the migration map needs more than name, email, and phone number.

Before import, decide:

• Which legacy records become companies.
• Which branches, stores, warehouses, departments, or buying groups become company locations.
• Which people become contacts attached to those locations.
• Which contacts can only place their own orders.
• Which contacts can manage the location, view broader order history, or update address details.
• Which DTC customer profiles should remain normal customers instead of becoming B2B contacts.

This matters most when a brand has a blended Shopify store, where B2B and DTC customers share the same storefront and admin. A customer profile can exist, but the B2B buying rights come from the company and company-location relationship. If that relationship is wrong, the customer account can look clean while the buying experience is wrong.

Map company locations before contacts

Many teams start with contact lists because contacts are familiar. That is understandable, but it is usually the wrong order.

The company location is where the operating rules live. Shopify's B2B setup and company-management documentation connects company locations to shipping and billing addresses, catalogs, payment terms, customer permissions, tax settings, and checkout settings. Contacts only make sense after those location rules are clear.

Build the location map first:

• Legal company name.
• Parent account or buying group.
• Location name and legacy location ID.
• Billing address and shipping address.
• Tax exemption or tax settings.
• Assigned catalog or pricing group.
• Payment terms.
• Checkout settings.
• Main contact.
• Sales rep or account owner, if that is needed in reporting or support.
• Any locations that should be inactive at launch.

Then map contacts against those locations. A buyer who orders for one warehouse is not the same as an admin who manages five branches. A finance contact might need invoices but should not place orders. A regional manager might need broader order visibility than a store-level buyer.

If the team does not decide these rules before import, it will usually rebuild them manually after launch.

Treat catalogs and pricing as migration data

B2B customer migration is not only customer data. It is also catalog and pricing access.

Shopify B2B features include companies, catalogs, payment terms, checkout settings, and customer permissions. Shopify's catalog documentation explains how B2B catalogs control product access and pricing, with plan-specific differences in how catalogs can be assigned.

That turns the catalog into part of the migration plan.

Ask:

• Which customers see the full product catalog?
• Which customers see a restricted assortment?
• Which customers have location-specific pricing?
• Which customers use volume pricing or quantity rules?
• Which SKUs are blocked for certain accounts?
• Which old price lists are still valid, and which are legacy clutter?
• Which customer-specific discounts should become catalog logic, price lists, discounts, or manual account review?

Do not import old wholesale tags and hope the team remembers what they mean. If a tag controls catalog access, rename it into a rule that a future operator can understand. If a price list is no longer used, leave it behind. If a customer has a negotiated exception, assign an owner before launch instead of burying the exception in a note.

Decide how payment terms and checkout should behave

B2B migration can expose payment rules that were never written down.

Some accounts pay upfront. Some use net terms. Some need purchase order numbers. Some need deposits or partial payment. Some should submit orders for review before fulfillment. Some have a credit process that still lives outside ecommerce.

Shopify's B2B payment documentation explains that B2B orders can be paid upfront or collected later with payment terms. That flexibility is useful only when the team decides which accounts get which rule.

Create a payment map:

• Which companies can check out without immediate payment.
• Which companies have payment due on fulfillment, on a date, or by standard terms.
• Which accounts need deposits, purchase order numbers, or manual review.
• Which accounts should be blocked until finance approves them.
• Which payment rule is temporary for migration and which is the future operating model.
• Who owns exception approval after launch.

This is not only finance work. It affects customer experience, sales, support, fulfillment, and reporting. If payment terms are wrong, the migration can create both customer friction and revenue risk.

Preserve order history for the work it needs to do

Order history can mean several things in a B2B migration.

The buyer may need to reorder from past purchases. Support may need proof of previous shipments. Sales may need account context. Finance may need aging or credit context. Marketing may need to avoid treating a wholesale buyer like a retail first-time customer.

Those are different needs.

Do not move order history just because it exists. Decide what it has to support:

• Reordering common products.
• Customer-service lookup.
• Sales account planning.
• Finance reconciliation.
• Contract or negotiated-price validation.
• Segmentation and suppression logic.
• Post-launch reporting continuity.

Some history may belong in Shopify. Some may belong in ERP, CRM, BI, or support tools. Some may only need a reference ID and a reliable lookup path. The important part is that teams agree on what history migrated means before the migration is called complete.

Clean legacy wholesale tags before they become Shopify logic

Old B2B systems tend to accumulate labels.

Wholesale. Dealer. VIP. Net30. Do not email. Tax exempt. Distributor. Region West. Old portal. Sales rep initials. Special price. Manual account. These labels may have been useful once, but they are dangerous when imported without ownership.

Tags can still be useful in Shopify, Klaviyo, reporting, or support. They should not be treated as a substitute for company structure, catalog rules, payment terms, or permissions.

Before import, split tags into four groups:

• Keep because the tag still drives a clear operating rule.
• Rename because the meaning is real but the label is unclear.
• Convert into a structured field, catalog, payment term, company note, metafield, or segment.
• Drop because the tag is legacy noise.

This is where B2B migration connects to lifecycle and support work. A wholesale customer should not receive a retail discount flow because an old account label was missed. A tax-exempt account should not rely on a tag if the actual tax setup belongs in the company or location configuration.

Validate with real B2B scenarios, not only row counts

A clean import report is not enough.

The team needs scenario QA. Shopify's own blended B2B store checklist puts companies, locations, catalogs, accounts, payment and shipping methods, sales staff ordering, and final testing into the setup sequence. That is a useful reminder: B2B migration is only done when the buying workflow works.

Test accounts should include:

• A company with one location and one buyer.
• A company with several locations and different buyers.
• A location admin who needs broader order visibility.
• A buyer with restricted catalog access.
• A buyer with special payment terms.
• A tax-exempt account.
• An inactive or blocked account.
• A customer who is both a retail customer and a B2B contact, if the store is blended.
• A customer-service lookup scenario.
• A finance review scenario.

Run the test from login to checkout, order confirmation, fulfillment, support lookup, reporting, and any downstream Klaviyo or CRM behavior. The customer does not care that the import succeeded. They care whether the account works the way their business buys.

Keep B2B migration tied to the larger Shopify replatforming plan

B2B customer migration should not sit in a separate spreadsheet until the end of the project.

It touches catalog structure, pricing, customer accounts, checkout, tax, sales workflows, support, finance, fulfillment, Klaviyo, reporting, and team ownership. If those workstreams make decisions without the B2B map, the import will inherit contradictions.

The right order is practical:

1. Map companies and locations.
2. Map contacts and permissions.
3. Map catalogs, pricing, payment terms, and tax rules.
4. Decide what order history and account context need to do.
5. Clean tags and legacy fields.
6. Import a controlled test set.
7. Run scenario QA.
8. Launch in a way support, sales, finance, and operations can monitor.

Lake House Group treats Shopify migration as operating-system work, not just data movement. If your B2B customer data, catalogs, pricing, and team workflows need to survive a move to Shopify, talk to Lake House Group about Shopify migration.