A standard Shopify migration guide will tell you to move products, customers, orders and redirects, then test checkout. That advice is necessary but not sufficient for a B2B or wholesale migration, there’s a whole layer of complexity around accounts, pricing and workflow that a B2C migration simply doesn’t have to deal with.
If you’re moving a wholesale business onto Shopify Plus from a legacy platform, a custom-built portal, or a general ecommerce system that’s been stretched to handle B2B, this is where the real migration risk lives. This post covers what’s genuinely different, so you can scope the project realistically rather than discovering the gaps mid-migration.
Why a B2B Migration Is a Different Project, Not Just a Bigger One
A typical B2C migration is fundamentally about moving product, customer and order data cleanly, then preserving SEO value through redirects. A B2B migration has all of that, plus:
- Business entities (companies) with hierarchical structures, not just individual customers
- Negotiated, tiered, or contract pricing that varies buyer to buyer
- Payment terms and credit arrangements instead of simple card-on-file
- Approval workflows for purchasing
- Often, integration with an ERP or accounting system that’s treated as the source of truth for pricing, inventory or invoicing
None of this is impossible on Shopify Plus, native B2B tools handle most of it well, but it changes what “done” looks like for the migration, and it changes where the risk sits.
Data Migration: What’s Actually Different
Company and contact structure
Unlike B2C, where a customer record is fairly flat, B2B data needs to map businesses, their locations, and the individual buyers within them, plus who’s authorised to place orders versus who just has view access. If your source system doesn’t cleanly separate “company” from “individual buyer,” this mapping work needs to happen before data lands in Shopify, not after.
Pricing and catalogue data
This is usually the most labour-intensive part. Wholesale pricing on a legacy platform is often scattered across spreadsheets, a separate pricing engine, or hardcoded into a custom portal. It all needs to be reshaped into Shopify’s catalogue and price list structure, and validated carefully, because a pricing error that goes live is a genuinely costly mistake with wholesale customers who order in volume.
Order history and terms
If buyers need visibility into past orders and outstanding invoices under net terms, historical order data needs to migrate in a way that preserves that context, not just as a generic order list, but tied correctly to the right company and location.
Payment terms and credit status
Which customers are on net 30 versus net 60, who’s on card-only, who has a credit limit, this data needs to transfer accurately, because getting it wrong either blocks a trusted customer’s order or extends credit to an account that shouldn’t have it.
Workflow Differences That Affect Scope
- Approval chains need to be recreated, not just the account structure. If your current system has purchase-order sign-off logic, someone needs to map that onto Shopify’s approval settings (or a custom extension of them).
- Minimum order quantities and case-pack rules often exist informally in a legacy system (a sales rep just knows not to sell single units of a certain product). These need to be made explicit and enforced in Shopify’s ordering rules, which is actually an improvement in most cases, but takes deliberate setup.
- ERP and accounting sync is frequently the backbone of a B2B operation in a way it usually isn’t for pure B2C. Invoicing, credit checks and stock allocation across a legacy platform and an ERP need to be re-established on Shopify, and this integration work is often the longest single piece of a B2B migration.
- Sales rep workflows. Many wholesale businesses still have reps who build orders on behalf of customers or manage key accounts personally. Shopify Plus can support this (draft orders, rep login on behalf of a company), but it needs to be planned as part of the migration rather than assumed to work identically to whatever tool the team is used to.
SEO and Continuity Considerations
If your B2B storefront has any organic visibility, product pages, resource content, category pages, the same core migration principles apply as any Shopify move: mapping old URLs to new ones with proper redirects, preserving metadata, and not losing indexed content. B2B search intent tends to be lower-volume but higher-value than B2C, so losing rankings on a handful of key product or category pages can have an outsized revenue impact relative to the traffic numbers. This is worth folding into your broader Shopify migration planning rather than treating as an afterthought once the B2B-specific data work is done.
A Practical Sequencing Checklist
- [ ] Map company/location/contact structure from source system to Shopify’s model
- [ ] Reshape and validate all wholesale pricing into catalogues and price lists
- [ ] Confirm payment terms and credit status for every account before cutover
- [ ] Rebuild approval workflows and test with real permission levels
- [ ] Define and enforce MOQs and order increments per product line
- [ ] Plan ERP/accounting integration and test invoicing end-to-end
- [ ] Migrate and verify order history against the correct company accounts
- [ ] Set up redirects and preserve SEO value for any indexed B2B content
- [ ] Run a full buyer-side UAT with real company accounts before go-live
- [ ] Communicate the transition clearly to existing wholesale customers, with support available for their first few orders
Testing: What “Done” Actually Looks Like for a B2B Migration
A B2C migration is generally considered tested once you’ve confirmed products display correctly, checkout works for a standard card payment, and key pages redirect properly. B2B testing needs to go further, because the failure modes are less visible until a real customer hits them:
- Test as multiple different buyer types, not just as an admin, a contact with order-placement permission, one with view-only access, and one requiring approval, each against a different pricing tier.
- Test net-terms checkout specifically, including what happens for a company account without approved terms yet (should default to upfront payment, not an error or, worse, no payment requirement at all).
- Test quantity rules and MOQs at the edges, ordering below a minimum, ordering a quantity that doesn’t match a case-pack increment, and confirming the cart behaves as expected rather than silently allowing an invalid order.
- Test multi-location scenarios, a company with several locations placing orders against different shipping and billing destinations.
- Reconcile a handful of test orders through to your ERP or accounting system before go-live, not just confirm the order appears correctly in Shopify, the accounting side is often where migration gaps actually surface.
Cutover Planning: Minimising Disruption to Active Wholesale Customers
Unlike a lot of B2C migrations, where a short amount of downtime is a minor inconvenience, a B2B cutover can directly disrupt a wholesale customer’s own operations, if they can’t place a routine reorder, it can affect their stock levels and their own customers. A few things that meaningfully reduce risk:
- Choose a cutover window around your customers’ ordering patterns, not just your own convenience, avoid peak ordering periods for your specific wholesale customer base if you can identify them from historical order data.
- Communicate the change directly to key accounts in advance, with a specific date and what to expect, rather than a generic announcement buried in a newsletter.
- Keep a fallback path (a phone number, an email address, a rep who can manually process an order) for the first week or two after cutover, in case a specific buyer runs into an issue with the new self-serve flow.
- Monitor order volume and support requests closely in the days immediately following go-live, since this is when structural gaps in the account or pricing setup tend to surface, not weeks later.
Data Cleanup: Often the Real Bottleneck
It’s common for legacy B2B systems, particularly older custom-built portals or heavily customised platforms, to carry years of pricing exceptions, one-off discounts, and inconsistent customer records that nobody has cleaned up because there was never a forcing function to do so. A migration is exactly that forcing function, and it’s worth budgeting real time for it rather than assuming source data can simply be exported and re-imported as-is. Expect to spend meaningful time reconciling which pricing exceptions are still genuinely active agreements versus historical artefacts that shouldn’t carry forward.
When to Get Specialist Help
A B2C migration is a well-trodden path with predictable steps. A B2B migration has more moving parts that are specific to your business, your pricing model, your ERP, your approval logic, which makes it harder to run purely from a generic checklist. Combining Shopify B2B development expertise with migration experience matters here, because the risk isn’t just “did the products move”, it’s “did every wholesale customer end up with the right price, the right terms, and the right access on day one.”
FAQs
Can I migrate B2B and D2C at the same time, or should they be separate projects?
They can be migrated together since they’ll live on the same Shopify store, but it’s usually smarter to sequence the work, get the core store and D2C catalogue solid first, then layer in company accounts and B2B pricing, so you’re not troubleshooting both systems simultaneously.
What’s the biggest risk in a B2B migration compared to B2C?
Pricing errors. A B2C migration mistake (a wrong product image, a missing collection) is usually visible and easy to fix. A wholesale pricing error can mean a customer gets billed incorrectly on a large order, which is a harder problem to unwind and a bigger trust issue.
Do we need Shopify Plus to migrate a B2B store, or can we start on standard Shopify?
Native company accounts, catalogues and B2B payment terms require Shopify Plus. If you’re currently on standard Shopify with a wholesale app and considering B2B growth, migrating to Plus is usually the more scalable long-term path.
How long does a typical B2B migration take?
It varies significantly with catalogue size and pricing complexity, but B2B migrations with meaningful pricing structures and ERP integration typically take longer than an equivalent B2C migration, plan for a longer discovery and data-mapping phase before development even starts.
Will our wholesale customers notice a disruption during migration?
There will typically be a defined cutover window, and it’s worth communicating this clearly in advance along with a simple guide to the new ordering process, since even a well-executed migration involves some change for customers used to the old system.
Ready to Scope Your B2B Migration?
If you’re weighing up moving a wholesale operation onto Shopify Plus, a strategy call is the most efficient way to get a realistic view of scope, timeline and the specific risks in your current data and pricing setup.
