How to migrate a B2B catalog without breaking price lists
Migrations fail quietly when guest prices look fine and logged-in companies see the wrong net. Here is a checklist we use before cutover.
A B2B migration is not a theme swap. You are moving companies, price lists, order history expectations, and often SEO equity. The scary bug is not a broken homepage. It is a trade buyer who places a large order at the wrong price on Monday morning.
1. Inventory the commercial objects
- Companies / customer groups and login contacts
- Price lists, volume tiers, and contract exceptions
- MOQs, pack sizes, and units of measure
- Credit limits and payment terms
- Open quotes and recurring order templates, if you have them
2. Map before you move pixels
Decide the source of truth for each object after launch. If the ERP owns prices, the new storefront must consume them instead of storing a rival spreadsheet. Blueprint-style scoping exists for this reason: schemas and integration maps before theme code.
3. Run parallel checks on real accounts
Pick ten real companies across your hardest price lists. Compare line prices, cart totals, and tax behaviour in old vs new. Automate where you can; still have a human spot-check the weird accounts, the ones with handshakes and exceptions.
4. Cut over with a boring plan
- Freeze price-list edits for a short window
- Redirect SEO URLs and preserve purchase paths
- Monitor first-day orders for price mismatches
- Keep a rollback path for DNS and payment config
The migration wasn’t scary because of the theme. It was scary because one wrong price list on Monday morning would torch trust.
Need a migration plan?
We run fixed-price Blueprint engagements and full replatforms for wholesale operators. Tell us how orders move today. We will say what should move first.
Written by B2B Point, wholesale commerce agency in Riga, Latvia.