ERP Migration: A Commerce-First Guide

For many commerce teams evaluating enterprise resource planning (ERP) migration in 2026, the pressure is coming from two sides: operational complexity and customer expectations.

ERP systems are designed to maintain stable financial and operational records. Customer-facing commerce often moves faster than ERP update cycles. Teams can end up managing inventory mismatches at checkout and fragmented customer data across systems.

These problems can affect whether customers come back: 29% of consumers say they stop buying from a brand after a poor customer experience, online or in-person. At the same time, US ecommerce sales reached $1.23 trillion in 2025 and accounted for 16.4% of total retail sales, as ecommerce continued to outpace overall retail growth.

ERP migration is one route to address these issues. This guide is for commerce-led businesses considering an ERP migration in 2026. It covers how to decide whether to replace the ERP or replatform commerce, then outlines a commerce-first architecture for moving customer-facing work off the ERP while keeping finance and operations connected.

What is ERP migration?

ERP migration is the process of moving business-critical data, configuration, and workflows from one enterprise resource planning system to another. That can mean replacing an existing ERP entirely. It can also mean unbundling commerce from an ERP-centric stack while keeping the ERP for finance and business operations.

For commerce-led businesses, the second path targets constraints in customer-facing commerce. ERP systems govern back-office operations: finance, inventory, procurement, manufacturing, and reporting. They’re less effective at running customer-facing work like storefront experience, checkout, merchandising, or B2B buying workflows.

Here are two paths to consider for better ERP and commerce performance:

Path A: Replace the ERP while replatforming commerce

This can make sense when the ERP itself is end-of-life or misaligned with current operations. Expect higher cost, a longer timeline, and more operational risk.

Path B: Move commerce to a modern platform, and keep the ERP for back-office operations

This retains the ERP as the system of record while relieving pressure on the storefront, B2B portal, and point of sale (POS). 

With Path B, the ERP remains the record-keeper. Commerce moves to a platform built for faster merchandising, checkout performance, B2B workflows, and omnichannel visibility. 

A commerce platform like Shopify sits in front of the ERP as the customer-facing layer. Bidirectional integration keeps inventory and orders aligned between systems, along with customer and catalog data.

The distinction between migrate, integrate, and sync matters throughout the project. Migration is a one-time transfer of records from one source system to another. Integration then connects two live systems so data flows between them on an ongoing basis. Sync keeps both sides aligned on the specific data fields that need to match continuously.

Why commerce brands migrate off ERP-centric commerce

Path B starts to make sense when ERP-centric commerce begins producing visible problems like updates shipping slowly, data accuracy degrading, and customer experience becoming harder to control. When product data, inventory, and the customer record live in separate source systems, customers feel the disconnect as they shop.

Customer experience (CX) teams still struggle to turn customer insights into coordinated action. Medallia’s 2026 “State of Customer Experience” report found that 66% of CX practitioners believe experiences improved over the past year, but only 17% of consumers agree. The same research found that 30% to 40% of departments take no action after receiving customer insights.

WIth ERP-centric commerce, some problems can show up frequently across operations. Use this checklist to identify them in your own architecture:

• Inventory discrepancies between the storefront and the back office are frequent enough that support teams work around them daily.
• Product updates or promotions need developer or ERP team involvement to reach the storefront.
• B2B buyers struggle with account self-service for quotes, reorders, negotiated pricing, or role-based permissions.
• Customer data is fragmented across POS, storefront, and ERP, so segmentation and loyalty programs underperform.
• Integration maintenance consumes more engineering time than new feature delivery.
• Launching a new site, market, or brand takes longer than the commercial window allows.
• Order exception rates are rising, and manual reconciliation absorbs operations capacity.
• Technology cost per order is growing faster than revenue per order.

When several of these patterns appear together, the fix may be acommerce layerbuilt for fast storefront updates, integrated with an ERP that still handles finance and inventory reporting. 

Sea Bags shows what that looks like in practice. The brand is a Maine-based maker of recycled sailcloth bags with 36 retail locations, and they were splitting their operations across a Clover POS, a Salesforce Commerce Cloud storefront, and a NetSuite ERP. 

Customer records, inventory, order history, and pricing rules were fragmented. After Sea Bags consolidated their operations on Shopify with a NetSuite Connector integration, the brand began capturing 1,200 customer emails weekly at POS checkout. Platform fees dropped by 20% (a $70,000 first-year savings), and POS email opt-in reached 47%.

ERP migration vs. ERP integration: Choosing the right architecture

The next decision is architectural. The choice usually comes down to three options:

• Replace the ERP entirely, alongside the commerce layer.
• Replatform commerce only, keeping the existing ERP and integrating with it.
• Phase the work: Move commerce first, then migrate the ERP on a separate timeline.

Each fits a different set of conditions.

1. Replacing the ERP fits when the ERP itself is the constraint. Triggers include vendor end-of-life dates, regulatory gaps, multi-entity limitations, or maintenance costs outpacing replacement costs. From the commerce side, these constraints show up as blocked product launches, an inability to support multi-market pricing, or storefront workarounds that engineering can no longer sustain. Replacement is high-cost and has a long timeline (mid-six figures for a medium-complexity move taking five to eight months). It's worth the disruption when the ERP can't be fixed by integration alone.
2. Replatforming commerce only suits brands where the back office is stable, but the customer-facing side needs to evolve. The ERP continues to handle finance, inventory, procurement, and reporting. Commerce moves to a platform built for fast storefront updates, B2B workflows, and omnichannel visibility. ERP integration handles the data flow between the two.
3. Phasing the work applies when the ERP needs replacing eventually, but commerce can't wait. Move commerce first, integrate with the existing ERP, then migrate the ERP on a separate timeline. Spreading the work limits operational risk and preserves customer experience through the ERP cutover. 

Options 2 and 3 both start by replatforming commerce, whether or not the business migrates to another ERP later. If you're choosing Option 1, ERP Research is a useful source for finding a new ERP system. The architecture and framework below pick up where options 2 and 3 leave off.

The next step is mapping ownership across three categories: what stays in the ERP, what moves to commerce, and what syncs between them. This is where apparent ERP problems often turn out to be integration or commerce-layer problems instead.

A starting architecture for commerce replatforming

The table below lays out a starting architecture for commerce businesses running an ERP plus Shopify. 

Shopify is designed for unified commerce at enterprise scale. Storefront, POS, B2B, and customer data live on one commerce platform. Finance, supply planning, and operations stay on the ERP of record. The integration layer handles the handoff.

For brands running this architecture, the Shopify Global ERP Program includes certified connectors for NetSuite, Microsoft Dynamics 365 Business Central, Brightpearl by Sage, Acumatica, and Infor. SAP-led environments follow a different route. SAP doesn't offer a first-party Shopify connector. Integration happens through integration-platform-as-a-service (iPaaS) platforms or custom API connections built with specialist partners.

A commerce-first ERP migration framework

The framework below sequences a commerce-first ERP migration to minimize disruptions. Order flow, inventory accuracy, and customer experience stay intact. It assumes the starting point is existing ERP-centric or fragmented commerce. The target is a Shopify commerce layer integrated with an ERP, new or existing, for back-office work.

1. Audit your current architecture and business processes

A thorough audit starts with system inventory, but it can't stop there. Map the failure points that affect customers and revenue, not just the systems that hold them.

Document the following before writing a migration plan:

• Every source system that holds customer, order, product, inventory, pricing, or financial data
• How data moves between systems, how often, and via which integration method
• Manual workarounds that operations or support teams have built to compensate for integration gaps
• Broken customer journeys: inventory mismatches, checkout errors, and B2B quote bottlenecks
• Order-exception rates and the categories of exception behind them
• Lead times for product updates, market launches, and promotional changes

Teams may discover during the audit that the root problem is business process design, not system capability. Porting legacy processes into a new system can recreate the original constraints. The audit requires collaboration across commerce leaders, IT, finance, and operations leads to prevent this.

2. Decide what data to migrate, archive, and sync

Not every legacy record belongs in the new environment. Split data into three categories before extraction begins:

• Operationally necessary data: Active customer accounts, current product catalog and variants, open orders, live pricing and price lists, inventory positions, and any records required for ongoing fulfillment or compliance.
• Historical reference data: Closed order history, superseded product data, and archived customer records. This may move to the new commerce platform, stay in the ERP, or go to a data warehouse for reporting and advanced analytics.
• Live synchronized data: The fields that flow continuously between Shopify and the ERP after go-live: product and variant updates, inventory by location, order status, customer accounts, tax-relevant transactions, and returns.

Work through this checklist for typical data fields requiring a decision:

• Customer accounts, contact records, and segmentation data
• Product catalog, variant structure, and media assets
• Contract pricing and B2B price lists
• Inventory by location, including committed and available quantities
• Open orders and fulfillment status
• Historical order and returns data
• Tax records and jurisdictional settings
• SEO assets, URL structure, and redirects (if storefront URLs change)
• Promotional and loyalty records

Data quality matters more than data quantity. Duplicate customer records, incomplete product data, and legacy SKU taxonomies produce worse outcomes after migration, not better. Investing in data profiling and cleaning before extraction helps support reliable ecommerce data integration after cutover.

If storefront URLs will change, plan redirects before launch. A poorly handled SEO migration can erase months of organic traffic and take quarters to recover.

3. Choose your integration model and implementation partners

Three integration patterns cover most commerce ERP platform migration projects.

• Prebuilt or certified connector: This is the fastest deployment and has the lowest ongoing maintenance. It works best for standard pairings: Shopify and NetSuite, Shopify and Microsoft Dynamics 365 Business Central, Shopify and Acumatica, and similar certified connections.
• Middleware or iPaaS: Useful when multiple systems need orchestration. For example, Shopify, an ERP, a warehouse management system (WMS), and customer relationship management (CRM) platform may all need to share data. Platforms like Celigo, Boomi, Jitterbit, and Patchworks provide prebuilt templates that handle a large part of the integration work, with configuration completing the rest.
• Custom API integration: This is usually reserved for niche legacy systems where no connector fits. Requires a higher upfront cost and ongoing engineering investment. In return, it offers more flexibility.

Partner selection matters as much as the method you choose. A migration partner needs more than integration engineering experience. They also need commerce operations experience, including data mapping, cutover planning, order flow testing, and post-launch support. 

When selecting partners, make sure they have references from ERP data migrations of comparable size. For B2B-heavy operations, ERP integration shifts the partner criteria further toward wholesale workflow expertise and negotiated-pricing complexity.

Gesswein shows what this kind of partner selection can deliver. The 110-year-old precision tools distributor had 12,000 SKUs running through a fragile BigCommerce-ERP connector. The system was producing frequent product and inventory mismatches. 

Essential B2B functions, including quote generation and reordering, relied on unreliable plugins. Gesswein migrated to Shopify with implementation partner Zaelab, which built a custom Acumatica integration. From there, transactions rose 101% year over year. Site traffic grew 225%, site visitors rose 343%, and the brand reported double-digit revenue growth.

4. Rebuild commerce workflows before cutover

Workflows that matter most should be redesigned before go-live to avoid reproducing their original constraints.

Workflows worth redesigning include:

• B2B ordering: Company accounts, role-based permissions, approval chains, negotiated pricing, and reorder patterns
• Returns and exchanges: Cross-channel policy, restocking flows, and financial reconciliation
• Inventory exposure: Which channels see which stock, safety stock rules, and low-stock behavior
• Omnichannel fulfillment: Ship-from-store, buy online, pick up in-store (BOPIS), and cross-location transfers
• Promotions and discounts: Tier-based, time-boxed, and buyer-specific offers

Shopify's native B2B features support several of these directly. Company accounts, buyer permissions, price lists, and Shopify Flow keep workflow logic in the commerce layer. That's cleaner than layering the same logic across ERP customizations and third-party plugins.

Simon Pearce is a brand that shows the gains available from workflow redesign. The Vermont glassware and pottery maker ran separate ecommerce, POS, and B2B systems, all integrating into an outdated ERP. Inventory updated once daily. POS outages disrupted peak-season operations.

After glassware brand Simon Pearce moved to Shopify, they gained real-time inventory visibility across stores and eliminated POS reliability issues. The platform now supports over 400 wholesale partners on the same system. Custom engraving approval moved from a multi-day email workflow to same-day, with in-store and online preview.

5. Test in phases, validate aggressively, and plan cutover

Migration testing involves a sequence of validation gates:

• Data migration dry runs: Extract, transform, and load into a test environment. Reconcile record counts and spot-check data integrity. Document mapping errors.
• Integration testing: Verify bidirectional syncs. Inventory updates should flow from ERP to Shopify, and orders from Shopify to ERP. Customer changes should move in both directions.
• Order flow testing: Walk test orders through the full lifecycle. Cover B2B purchase orders, POS transactions, returns, exchanges, partial shipments, and split payments.
• Permissions and role testing: Verify that staff, store managers, and admins see and can do only what they should.
• Performance testing: Load-test the storefront, checkout, and POS under expected peak conditions, including promotional and Black Friday and Cyber Monday (BFCM) traffic.

Validate data after load. Reconcile key figures against the source systems before and after cutover, including financial totals, inventory counts, customer counts, and tax liabilities. Discrepancies that appear after launch are more expensive to fix than those caught in staging.

A phased rollout can reduce your risk in larger environments. Going live by brand, region, or channel allows each phase to inform the next. A successful phased rollout includes a rollback plan for each phase, with documented triggers for when to use it. A realistic timeline with named milestones also gives finance and ops leaders the reference points they need to keep the migration project on track.

6. Train teams and measure post-launch success

Training starts before go-live, not when it happens. Give operations, merchandising, customer service, and finance teams hands-on access to the new environment during user acceptance testing. Document the workflows that changed most. B2B account management, returns, and inventory adjustments often see the biggest structural shifts.

Post-launch success is measured in operational and commercial terms, not in whether the migration was completed on schedule. Track these metrics from the first reporting period after launch:

• Inventory accuracy, by location and by channel
• Order exception rate and categories of exception
• Storefront performance: site speed, uptime, and checkout conversion
• Time to publish product updates or launch promotions
• B2B self-service adoption, including quotes, reorders, and buyer portal usage
• Total cost of ownership (TCO) for the combined commerce and ERP stack
• Support tickets categorized as data-sync or reconciliation issues

If improvements don’t show in the first reporting period after launch, the integration pattern, data mapping, or workflow redesign needs revisiting.

Brand Collective shows the maintenance dividend available at scale. The Australian retail group runs 19 brands on Shopify with Apparel21 ERP integrated via DotApparel middleware. After Brand Collective consolidated their portfolio on Shopify, new site migrations take only about three months. Teams report up to 60% less time spent on maintenance and upgrade work, alongside 10% sales growth.

ERP migration planning checklist

Work through the items below before drafting a project plan:

• Every source system that holds customer, order, inventory, or pricing data is documented.
• The top customer-affecting failure points are identified and quantified.
• All data is classified as operationally necessary, historical reference, or live-synced.
• Integration partners are shortlisted by pattern (certified connector, iPaaS, custom).
• Workflows requiring redesign before cutover are named and owned.
• Success metrics are agreed between finance, operations, IT, and commerce leads.
• A phased rollout plan exists by brand, region, or channel.
• A rollback plan with documented triggers exists for each phase.