Every Magento-to-Shopify checklist on the internet walks the same route: export your products, import your customers, pick a theme, set up redirects, launch. Fine advice, and Shopify's own migration documentation covers that route well. But if you run a B2B operation, a manufacturer selling through dealer accounts, a distributor with contract pricing and an ERP, those checklists describe maybe a third of your project. The steps they skip are the ones that decide whether your wholesale buyers log in on launch day and find their world intact.
This is the B2B version: the full sequence, with the steps generic checklists never mention, ERP field mapping, customer group and price-list migration, purchase order workflow parity, private catalog access, marked where they belong in the order of work. Use it to build the internal business case, scope conversations with partners, or audit a plan someone else handed you.
Quick answer: A B2B Magento-to-Shopify migration runs in six phases: inventory what you actually run, map the B2B commercial structure onto Shopify's account model, map ERP integration field by field, migrate the data everyone remembers to migrate, build and validate against pilot accounts, and cut over with the old environment held in reserve. The generic checklists cover phases four and six. B2B projects live or die in one through three.
Phase 1: Inventory What You Actually Run
Before anything is scoped, get honest about what exists. Most Magento environments past year three contain more than anyone currently employed can list from memory.
List every custom module and extension, with what each one does, or flag the ones nobody can explain.
Document your ERP integration: which system, what data moves, in which directions, on what schedule.
Count your customer groups, pricing rules, and contract price records, including the retired ones still technically active.
Pull catalog, customer, and order volumes, and note which parts of checkout, quoting, or account behavior are custom.
Identify who internally knows each of the above, because that person is now on the project.
This inventory is the raw material for every estimate you will receive. Arriving without it means every quote you get is a guess, a point the cost breakdown linked below makes in more depth.
Phase 2: Map the B2B Commercial Structure
Here is the first block of work generic checklists skip entirely: translating Magento's B2B configuration into Shopify's company account model, deliberately, before any data moves.
Map customer groups to Shopify company accounts, deciding which groups become account tiers, which become price lists, and which get retired.
Map every contract price, tier price, and volume discount to a Shopify price list, and record which account gets which list.
Define catalog visibility: which accounts see which products, including the private catalogs and gated products your dealers or restricted lines depend on.
Confirm purchase order workflow parity: PO numbers captured at checkout, PO-based payment where your buyers use it, and net terms with credit handling that matches what accounts have today.
Map quote and requisition workflows to their Shopify equivalents, native, app, or custom, before assuming they exist.
Decide the buyer roles per account: who orders, who approves, who sees invoices.
The test for this phase is simple to state: a buyer who logs into the new store should see their price, their catalog, their terms, and their ordering workflow, without anyone having explained anything to them.
Phase 3: ERP Field Mapping
The second skipped block, and the one that separates B2B migrations from everything else. Your Magento-ERP integration does not transfer; it gets rebuilt against Shopify's APIs, and the rebuild is only as good as the mapping that precedes it.
List every entity the ERP exchanges with commerce today: items and variants, price records, customers and companies, orders, inventory by location, invoices, credit status.
For each entity, map field by field: what it is called in the ERP, what it becomes in Shopify, which direction it flows, and which system owns the truth.
Set sync cadence per entity: real-time for orders and inventory, scheduled for catalog attributes, event-triggered for price changes.
Flag the fields with no Shopify-native home, they become metafields or custom app territory, and catch them now, not in testing.
Decide what the old integration did that the new one deliberately will not, because every legacy sync carries workarounds not worth preserving.
This phase is where the ERP integration practice earns its place in the project plan, and the pattern that keeps the rebuilt sync maintainable, both directions, real time, ERP as system of record, is what Uncap Connect exists to run.
Phase 4: Migrate the Data Everyone Remembers
The familiar checklist, present and accounted for, with the B2B footnotes attached.
Migrate products and variants, validating that variant structures and B2B-relevant attributes survived intact.
Migrate customer records mapped to their company accounts, and plan the password reset: hashes do not transfer between platforms, so a reset flow and a timed communication to your account base are part of go-live, not a surprise.
Migrate order history so buyers and service teams keep their reference points.
Migrate content worth keeping, and let the rest retire.
Crawl the old site and build the 301 redirect map before cutover, pattern-level with explicit handling for the URLs that carry rankings.
Phase 5: Build and Validate Against Real Accounts
Rebuild the storefront, treating the buyer-facing refresh as the upgrade it is rather than a copy of the old theme.
Replace each audited module with its planned equivalent: native feature, maintained app, or custom build.
Stand up the rebuilt ERP sync and run it against staging until order, inventory, and price flows reconcile.
Recruit pilot accounts, real, friendly ones, and have them log in: their pricing, their catalog, their terms, a test PO order, a test quote.
Run both environments in parallel, with Magento still taking orders, until validation says otherwise.
Pilot accounts are the phase's whole point. Internal testing confirms the system works; a pilot buyer confirms the business survived the move.
Phase 6: Cut Over With a Net
Sequence go-live: DNS, redirect activation, and the account communication with password-reset instructions, timed together.
Verify redirects against the crawl map, then watch 404 reports and search-console coverage through the transition window.
Reconcile the first days of orders against the ERP line by line.
Hold the Magento environment in read-only reserve for a quarter, because the question you cannot answer from the new stack will arrive in week three.
Schedule the post-launch review where the punch list becomes a plan instead of a pile.
Using This Checklist
If you are building the internal case, phases one through three are your scoping document, and the cost logic that turns them into a budget is in the B2B cost breakdown. If you want the platform-agnostic version of this discipline for a broader replatforming evaluation, the enterprise replatforming checklist is the general-purpose sibling, and the revenue-preservation guide covers what protecting traffic and accounts through the move actually requires.
Uncap has been a Shopify Platinum Partner since 2013, with more than 380 B2B commerce projects delivered, and Magento migrations with full ERP continuity are a core capability. Talk to Our Experts if you want this checklist walked against your actual environment, phase one is a conversation we can have on the first call.
Frequently asked questions
What does a B2B Magento-to-Shopify migration checklist include that generic ones do not?
Three blocks of work: mapping the B2B commercial structure (customer groups to company accounts, contract pricing to price lists, private catalog visibility, purchase order and net-terms parity), field-by-field ERP integration mapping with sync direction and cadence per entity, and validation by real pilot accounts rather than internal testing alone.
What is ERP field mapping in a migration?
The entity-by-entity, field-by-field inventory of what your ERP exchanges with commerce: what each field is called on both sides, which direction it flows, which system owns the truth, and how fast it syncs. It is done before the integration rebuild so gaps surface on paper instead of in production.
How do customer groups and contract pricing migrate to Shopify?
They are mapped, not exported: Magento customer groups translate to Shopify company accounts and catalogs, and each contract or tier price becomes a price list assigned to the right accounts. The launch-day test is that a buyer logs in and sees their negotiated pricing without explanation.
Should the old Magento store be shut down at launch?
No. Run both environments in parallel through validation, keep Magento taking orders until cutover, and hold it in read-only form for around a quarter afterward, because early post-launch questions are often answerable only from the old system's data.
