B2B Ecommerce Replatforming: A 9-Step Migration Checklist
B2B ecommerce replatforming is the process of moving your wholesale storefront, buyer accounts and pricing logic from one ecommerce platform to another. It is harder than a B2C migration because the value sits in data that platforms model differently: customer groups, contract price lists, minimum order quantities, pack sizes, net terms and tax exemption certificates. A safe migration runs in three stages. First, audit what you have and write down which buyer sees which price before you touch anything. Second, move products, accounts and price lists into a staging store and test with real buyer logins. Third, launch behind a complete 301 redirect map and monitor orders and rankings for 90 days. Before committing, check whether you need a new platform at all: many Shopify brands close their B2B gaps with a wholesale layer instead, which avoids the migration entirely.
Key takeaways
- Replatform only when the platform blocks revenue you can name. A missing discount rule is a configuration problem, not a migration.
- The B2B data that breaks is always the same: customer groups, price lists, MOQs and pack sizing, net terms, and tax exemption certificates.
- Rebuild pricing from the rules, never from an export of calculated prices, or your new store goes stale the first time a cost changes.
- A complete URL-for-URL 301 redirect map, kept live for at least a year, is what separates a few weeks of dip from a permanent traffic loss.
- If you are on Shopify and the gap is B2B capability, adding a wholesale layer keeps your URLs, theme and integrations intact.
What does B2B ecommerce replatforming actually mean?
B2B ecommerce replatforming is moving your wholesale storefront off one platform and onto another: the catalog, the buyer accounts, the negotiated pricing, the order history and every integration hanging off them.
It covers three quite different projects, and confusing them is where budgets go wrong:
- A full platform move. New platform, theme, URLs and checkout. Months of work.
- A front-end replatform. The commerce engine stays, the storefront is rebuilt. Faster, but you keep the limits that made you look.
- An extension, not a move. You keep the platform and add the B2B capability it lacks. No migration, no redirect map, no re-integration.
Most teams that say "we need to replatform" have diagnosed a missing capability, not a broken platform. Work out which one you have before you scope anything.
How do you know it is time to replatform?
Replatform when the platform blocks revenue you can name, not when it annoys you. Four signals justify the cost.
- Pricing you cannot express. Your reps have agreed contract prices the platform cannot store, so someone edits orders by hand after checkout.
- Buyers who will not use it. Reorders keep arriving by email or PDF because the portal is slower than emailing a rep.
- Integration debt. Every ERP or accounting sync needs custom middleware, and each platform update breaks it.
- Cost that scales with orders, not value. Per-order fees, developer retainers, and a plan tier you were pushed onto for one feature.
If none of those apply and the complaint is checkout design or a missing discount rule, you have a configuration problem. Fix that first. An industry roundup of replatforming data puts the share of data migration projects that fail or run over budget at around 83%, which is a poor trade for a feature you could add in a week.
Why do B2B migrations break more often than B2C ones?
A B2C migration moves products, customers and orders, and those map cleanly between platforms. A B2B migration moves relationships, which platforms model differently. Five things break most often:
- Customer groups. Platform A has one tag per account. Platform B has nested company hierarchies with multiple buyers per company. There is no automatic mapping.
- Price lists. Percentage-off rules, fixed contract prices and volume breaks are three different mechanisms. Exporting a price does not export the rule that produced it.
- MOQs and pack sizing. Often stored as theme logic or app metafields rather than product data, so a standard CSV export loses them silently.
- Net terms and credit limits. Frequently held in the payment gateway or the ERP, not the store.
- Tax exemption certificates. Usually attached to the account, and usually the last thing anyone tests.
Test each of these with a real buyer login before launch, not with an admin account. Admins see list price. Buyers see the number that matters.
Steps 1 to 3: what should you finish before migration week?
1. Inventory every rule, not every record
Records export. Rules do not. Write down every pricing rule, access rule (who sees which products) and order rule (MOQs, pack sizes, dollar minimums) as plain sentences. That document becomes the acceptance test for the new platform, and it also tells you whether you need to move at all.
2. Pick the platform against your rules, not a feature grid
Take that list into every demo and make the vendor build three of your real rules live. Our guide to choosing a B2B ecommerce platform covers the seven criteria worth scoring, and the complete B2B ecommerce platform guide compares the main categories in depth.
3. Map the integrations before the catalog
List every system touching the store: ERP, accounting, 3PL, CRM, tax engine, EDI. For each, note sync direction, trigger and owner. Integrations are the longest pole in the project, so start them first. Our breakdown of B2B ecommerce integrations covers which systems to connect first and what usually breaks.
Steps 4 to 6: how do you move the data without breaking pricing?
4. Migrate in dependency order
Products, then customers, then customer groups, then price lists, then order history. Loading price lists before the groups they attach to is the most common cause of a rebuild.
5. Rebuild pricing from rules, never from a price export
Exporting the price each buyer currently pays gives you a frozen snapshot that goes stale the moment a cost changes. Rebuild the rule ("Tier 2 accounts pay 40% off list, with a further 5% at 100 units") so the new platform recalculates correctly forever.
6. Test with real buyer accounts on staging
Pick five accounts covering your hardest cases: your largest contract price, a tax-exempt account, one on net-60 terms, one that only sees a restricted catalog, and one that orders in cases. Place a real order as each. Every failure you find here costs a fix. Every one you find after launch costs an order.
Steps 7 to 9: how do you launch without losing search traffic?
7. Build a URL-for-URL redirect map
Crawl the old site, export every indexed URL, and map each one to its closest match on the new site. Google's guidance on site moves with URL changes is explicit: use server-side 301 or 308 redirects, avoid chains longer than three hops, do not dump everything on the homepage, and keep the redirects live for at least a year. Submit the new sitemap in Search Console once the redirects are active.
8. Launch quietly, then tell buyers
Go live in a low-order window and keep the old store read-only for a fortnight so support can check historical orders. Then email every buyer with the new URL, a password reset link and two lines on what changed for them. Wholesale buyers reorder on a rhythm, so a buyer who first hears about it at their next cycle is a buyer who calls support.
9. Watch orders and rankings for 90 days
Track order volume by account, not in aggregate: a flat total can hide your five largest buyers reverting to email. Expect ranking fluctuation for a few weeks on a small or mid-sized site. Check crawl errors and index coverage weekly, and fix broken redirects the same day you find them.
Do you need to replatform at all?
If you are on Shopify and the gap is B2B capability rather than the platform itself, adding a wholesale layer beats migrating on every criterion that matters: time to live, risk to rankings, and whether you have to re-integrate your ERP. A full replatform only wins when the platform genuinely cannot host your business.
The first three rows decide it. A full replatform changes your URLs, so every ranking you hold rests on a redirect map being complete and correct, and every ERP, 3PL and accounting sync has to be rebuilt. A wholesale layer on Shopify touches none of that: storefront, URLs and integrations stay as they are, and the B2B behaviour is added on top. PortalSphere handles tiered pricing by customer group, MOQs and pack sizing, net terms and a gated catalog natively, and runs wholesale and retail from one store rather than two. On a full replatform those same capabilities are a "depends on the platform", which is exactly what step 1 exists to find out.
Still weighing native Shopify features against a dedicated app? Our comparison of Shopify B2B versus a wholesale app works through where each one runs out of road.
Frequently asked questions
How long does B2B ecommerce replatforming take?
Plan for three to six months for a mid-sized wholesale business with ERP integration, and longer with custom pricing logic or EDI. The catalog migration is rarely the bottleneck. Integrations and pricing rules are, which is why both should start in week one. A front-end-only rebuild can land in six to ten weeks, and adding a B2B layer to an existing store takes days.
Will replatforming hurt my SEO?
A migration with a complete URL-for-URL 301 redirect map usually sees a dip of a few weeks before recovering. A migration without one can lose a large share of organic traffic and may never fully recover. Google advises keeping redirects in place for at least a year so ranking signals transfer, and submitting an updated sitemap as soon as the redirects go live.
Should I migrate order history?
Migrate enough for buyers to reorder and for support to answer questions, typically 12 to 24 months. Older records can stay in an archive or your ERP. Full history migration is a common source of schedule overrun, because old orders reference products, prices and accounts that may no longer exist.
Can I run the old and new platforms at the same time?
Briefly, and in one direction only. Keep the old store read-only for one to two weeks after launch so support can look up historical orders, but never take orders on both. Dual order intake splits your inventory truth and creates oversells within days.
What is the alternative to replatforming?
Extending the platform you have. If your storefront, checkout and integrations work and the only gap is B2B capability, a wholesale layer adds customer-specific pricing, MOQs, gated access and net terms without touching URLs, themes or existing syncs. It removes the migration risk, and it is reversible in a way a replatform is not.
Get the B2B features without the migration
PortalSphere adds tiered pricing, MOQs, gated catalogs and net terms to the Shopify store you already run. No redirect map, no re-integration, free onboarding on a draft of your store.
