B2B Ecommerce Replatforming: A Step-by-Step Guide to Moving to Shopify Plus
Most B2B ecommerce replatforming projects take longer than planned. The ones that fail or run months over schedule almost always share the same root cause: the team treated the project as a data migration when it was actually a business logic migration.
Moving product records, customer data, and order history from one platform to another is tractable. Moving the pricing conditions your sales team negotiated account by account, the company account hierarchies that mirror how your buyers are organized, the ERP integration that makes inventory and orders accurate in real time, and the net terms workflows your finance team depends on, that is the work that takes time, and that is what most replatforming plans underestimate.
For B2B manufacturers and distributors considering a move to Shopify Plus, this guide covers the full replatforming process: what to audit before you start, how to sequence the build, what to protect at cutover, and where the common failure points are. As a Shopify Platinum Partner since 2013, with over 380 B2B commerce projects delivered, Uncap has run enough B2B ecommerce replatforming projects to know exactly where they go well and where they go wrong.
B2B ecommerce replatforming is the process of moving your ecommerce operations from one platform to another. That definition covers the mechanics. It does not capture the full scope.
For a B2C store, replatforming involves migrating products, customers, orders, and content, then rebuilding the storefront on the new platform. The complexity is real but bounded.
For a B2B operator, the same data categories are present, but each carries B2B-specific logic that has to be rebuilt, not just moved.
Products may be straightforward, or they may carry complex attribute sets, unit-of-measure configurations, and variant structures that need to map correctly to the new catalog architecture.
Customers on a B2B platform are not individual shoppers. They are company accounts with multiple contacts, multiple ship-to locations, negotiated pricing, credit limits, and payment terms. Migrating them as flat customer records loses all of that structure.
Pricing in most B2B operations is not a single price per product. It is a matrix of customer-specific conditions maintained in the ERP. Those conditions have to be mapped to the new platform's pricing architecture, whether that is Shopify Plus B2B price lists or a custom pricing layer.
Integrations with ERPs, CRMs, and warehouse management systems have to be rebuilt for the new platform's API architecture. The integration that worked on Magento or a legacy system does not transfer to Shopify Plus.
Order workflows, including draft orders, quote-to-order, rep-assisted ordering, and purchase order submission, have to be configured in the new environment.
The data migration is the straightforward part. The business logic migration is the work.
Most B2B operators do not replatform because they want to. They replatform because they have to. Here are the signals that indicate the current platform has become a constraint rather than a capability.
The platform cannot handle your B2B requirements natively. If every B2B-specific workflow requires a custom workaround, a third-party app patch, or developer intervention for routine tasks, the platform was not built for your use case. Account-specific pricing, net terms at checkout, and company account hierarchies should be native features, not workarounds.
Integration maintenance is consuming development capacity. A brittle ERP integration that requires regular intervention, or an integration architecture that breaks every time either system updates, is a sign that the underlying connection needs to be rebuilt rather than patched again.
The platform is limiting commercial growth. If launching a new B2B channel, adding a new customer tier, or expanding to a new market requires months of custom development, the platform is slowing the business down rather than enabling it.
Performance and reliability are affecting buyers. Slow load times, intermittent availability, and checkout failures during peak ordering periods are platform problems that erode buyer trust and drive orders to the phone and email instead of the portal.
Total cost of ownership has become difficult to justify. Licensing fees, ongoing custom development, and the developer time consumed by platform maintenance have to be weighed against what the platform actually enables. When maintenance cost outpaces capability, the case for replatforming becomes clear.
Data Migration: SKUs, descriptions, images, variants
Business Logic Migration: UOM, attribute sets, catalog visibility rules
Data Migration: Name, address, email
Business Logic Migration: Company hierarchy, contacts, ship-to locations, credit limits
Data Migration: Stored price records
Business Logic Migration: Customer-specific conditions, tiered pricing, contract pricing
Data Migration: Transaction history
Business Logic Migration: Net 30/60/90 configuration, PO workflows, credit approval
Data Migration: Historical order records
Business Logic Migration: In-flight orders, open quotes, reorder lists
Data Migration: API credentials
Business Logic Migration: Data mapping, sync logic, error handling, retry architecture
Data Migration: None, cannot be migrated
Business Logic Migration: Draft orders, rep-assisted ordering, approval chains
Most replatforming timelines are built around the left column. The right column is where the actual project time goes.
Before any technical work begins, the requirements have to be documented. This means mapping every B2B-specific workflow that exists on the current platform: how accounts are structured, how pricing conditions are managed, how orders move from inquiry to invoice, how the ERP connects to the store, and what the current integration architecture looks like.
Discovery is not overhead. It is how you avoid discovering, six weeks into the build, that your pricing data is stored in a custom ERP table that no one documented or that your current platform has a custom order approval workflow that three of your largest accounts depend on.
Uncap's Blueprint process is the structured discovery engagement we run before every B2B build: a full architecture review, integration mapping, and a project plan before development starts.
For most B2B operators, the ERP integration is the longest workstream in the replatforming project. It should be designed and scoped before any Shopify development begins, because almost every other build decision depends on it.
The integration architecture has to answer: Which system is the source of record for pricing? How will inventory availability be reflected on Shopify in real time? How will orders placed on Shopify reach the ERP with the correct data attached, including payment terms, PO numbers, and company account identifiers?
The Uncap Connector is the ERP integration suite Uncap uses for Shopify Plus B2B builds. It handles the sync between ERP customer master records, pricing conditions, inventory levels, and order data and the corresponding Shopify B2B data structures. The integration is built before the storefront, not after.
A data audit maps what you have on the current platform, what needs to migrate, what can be left behind, and what needs to be transformed during the migration. For most B2B operators, this means:
Auditing the customer master to identify which accounts are active, which have pricing conditions that need to migrate, and how each account's contact structure should map to Shopify company/location/contact hierarchy.
Auditing the product catalog for completeness, attribute quality, and any custom fields that need to map to Shopify metafields or product properties.
Auditing order history to determine what is needed for buyer-facing order history display and what is only needed for internal records.
Identifying data that should not migrate: inactive accounts, discontinued products, incomplete records that would create noise in the new environment.
With the ERP integration architecture defined and the data audit complete, the Shopify Plus B2B configuration follows a specific sequence.
Company accounts are created first, reflecting the customer master from the ERP. Each company gets its locations, its contacts, and its assigned permission roles.
Price lists are built next, reflecting the pricing conditions from the ERP. For operators with customer-specific contract pricing, this means building price lists at the account level. For operators with tiered pricing by customer segment, it means building catalogs and catalog-level price lists.
Net terms are configured at the location level for accounts that purchase on credit. PO number collection at checkout is enabled where required.
Catalogs are configured to reflect product visibility rules by account segment.
The new Shopify Plus environment should be built and tested in parallel with the live platform, never as a replacement. This means running the new store in a staging environment with real account data, real pricing, and real order scenarios tested by actual buyers before any cutover.
Testing should cover the full order cycle: a buyer logging in, seeing their account-specific pricing, adding items to cart, selecting net terms, submitting a purchase order number, and completing the order. It should also cover the ERP integration: the order reaching the ERP with the correct data, the inventory update reflecting in Shopify, and pricing changes in the ERP propagating to Shopify price lists.
For a detailed checklist of what to validate before go-live, the enterprise ecommerce replatforming checklist covers the full pre-launch verification sequence.
URL structure changes during a replatforming project can cost significant organic traffic if not handled correctly. The SEO preservation workstream runs alongside the build and covers: mapping every current URL to its new equivalent on Shopify Plus, configuring 301 redirects for changed URLs, preserving meta titles and descriptions for high-value product and category pages, and monitoring for crawl errors and ranking changes in the weeks following launch.
For B2B operators with significant organic visibility on product-specific or category terms, SEO preservation is not optional.
Cutover is the highest-risk phase of any replatforming project. For B2B operators, the additional complexity comes from in-flight orders, open quotes, and active accounts that need to transition cleanly.
A B2B replatforming cutover plan should address: how in-flight orders on the legacy platform are fulfilled, how open quotes are communicated to buyers during the transition, how active accounts are migrated to Shopify company accounts and notified of the new portal, and what the rollback plan is if a critical issue surfaces at go-live.
Zero-downtime cutover is achievable on Shopify Plus. It requires DNS planning, pre-migrated account data, and a communication plan for buyers that is sent before, not during, the cutover window.
The first 30 days after launch are the most operationally sensitive. Monitor order volume through the new portal against historical baselines. Track ERP integration error rates. Check that price lists are serving correctly to the accounts that were migrated. Review buyer login and checkout completion rates.
Issues that surface in the first 30 days are almost always configuration gaps that were not caught in testing, not fundamental platform problems. Catching them early minimizes operational impact.
Shopify Plus has become the primary replatforming destination for mid-market B2B operators for a specific set of reasons.
Native B2B features, including company accounts, price lists, catalog gating, and net terms at checkout, are built into the platform rather than requiring third-party apps or custom development. For operators coming off a legacy system where every B2B capability was a custom build, this matters.
The ERP integration ecosystem is mature. NetSuite, SAP Business One, SAP S/4HANA, Microsoft Dynamics 365, and QuickBooks all have documented integration paths to Shopify Plus, whether through native connectors, iPaaS platforms, or purpose-built connector suites.
Shopify Plus maintains a consistent release cadence for B2B-specific features. The platform roadmap for B2B native functionality has been active since 2022, and new capabilities continue to ship on a regular basis.
The total cost of ownership for a well-architected Shopify Plus B2B build is lower than maintaining a legacy platform with accumulated custom development. The ongoing platform cost is predictable, the development environment is well-documented, and the partner ecosystem is large.
Uncap's Migrate Accelerator is the structured engagement for B2B operators moving to Shopify Plus: a defined discovery phase, a built and tested integration architecture, a clean data migration, and a go-live cutover that preserves order continuity.
Talk to our team about your current platform, your ERP, and your B2B requirements.
B2B ecommerce replatforming is the process of migrating your online store and its underlying business logic from one ecommerce platform to another. It goes beyond moving product and customer data to include rebuilding pricing conditions, account hierarchies, ERP integrations, and order workflows on the new platform.
Most B2B replatforming projects run 14 to 24 weeks from discovery through go-live. The timeline depends on ERP integration complexity, the number of customer accounts and pricing conditions that need to migrate, and whether Shopify Plus B2B features need to be built from scratch. A structured discovery phase produces an accurate timeline before development begins.
Product catalog, customer accounts (including company hierarchy, contacts, and ship-to locations), historical orders, and pricing records need to migrate. Equally important is the business logic: customer-specific pricing conditions, net terms configurations, ERP integration data mapping, and order approval workflows. The data migration is manageable; the business logic migration is where most projects find unexpected complexity.
The most common risks are ERP integration scope creep (integration complexity that was not surfaced in scoping), pricing misconfiguration (customer-specific pricing conditions that do not map correctly to the new platform), SEO traffic loss from URL structure changes without proper redirects, and cutover disruption to in-flight orders. A proper discovery phase and a parallel-environment build reduce all four risks significantly.
The ERP integration has to be rebuilt for Shopify Plus's API architecture. The integration on your legacy platform will not transfer directly. However, for the major ERPs used by B2B operators, including NetSuite, SAP, Microsoft Dynamics, and QuickBooks, documented integration paths to Shopify Plus exist. The rebuild is an opportunity to design a cleaner integration architecture than the one being replaced.
