A Magento 1 B2B store has four realistic paths: Adobe Commerce, BigCommerce B2B Edition, Shopify Plus B2B, or a composable build. Product, customer and order data can move to any of them. Themes, custom code, extensions and the Dynamics NAV connector cannot, so those are what you plan around, not the catalog.
Support for Magento 1 ended in 2020, so the store no longer receives security patches. The right target depends less on feature lists and more on where your customer-group pricing logic lives today, how many extensions you rely on, and how much platform upkeep you want to own. Our Magento migration services start with an audit of exactly those three things.
The four realistic options and what breaks in each
Each path keeps your data and changes who owns the pricing logic, the integration and the upkeep.
Best when: pricing logic lives in custom code, or the catalog needs heavy configuration.
What breaks: in a Magento 1 to Magento 2 migration, the theme, custom modules and the NAV connector are rebuilt, and some extensions have no Magento 2 version.
Watch for: company accounts, shared catalogs and quotes need the Adobe Commerce license, not Open Source, and you keep patching and hosting.
Best when: pricing is mostly group based and you want less platform upkeep.
What breaks: in a Magento to BigCommerce migration, code-based pricing rules move to price lists or middleware, and configurable products are remapped to variants and options.
Watch for: there is no server-side code access, so the NAV integration runs through middleware.
Best when: the catalog and pricing are simpler and speed to launch matters most.
What breaks: in a Magento to Shopify migration, customer groups become company catalogs and price lists, and custom attributes become metafields.
Watch for: checkout customization is bounded, and the NAV integration runs through middleware.
Best when: several brands or channels share one commerce backend and your team can own the frontend.
What breaks: everything is rebuilt, from storefront to checkout to the integration layer.
Watch for: the highest cost and longest timeline, and you own orchestration.
| Area | Adobe Commerce | BigCommerce B2B Edition | Shopify Plus B2B |
| Theme and frontend | Rebuilt as a Magento 2 theme | Rebuilt on a new theme or headless | Rebuilt on a new theme or headless |
| Extensions and custom code | Re-coded, some extensions unavailable | Replaced by apps or middleware | Replaced by apps, Functions or middleware |
| Customer-group pricing | Customer groups, shared catalogs, tier prices | Customer groups plus price lists | Company catalogs and price lists |
| Large catalog | Closest data model, easiest mapping | Variant and option limits need review | Variant and option limits need review |
| Dynamics NAV integration | Connector rebuilt for Magento 2 | Middleware or custom connector | Middleware or custom connector |
| Ongoing upkeep | You own patches and hosting | Platform managed | Platform managed |
What carries over and what does not
This split is the same whichever platform you choose, which is why the audit comes before the platform decision.
Products, categories, attributes, customers, order history, and group and tier price data. Each needs a mapping check before import.
The theme, custom modules, extensions, pricing rules written in code, the NAV connector, and your redirect map. Each is rebuilt, replaced or created new.
Five questions that decide the platform
If it sits in group prices and tiers, a SaaS platform covers it. If it sits in custom code, Adobe Commerce is the lower-risk move. For a closer look, see how customer-specific pricing for industrial distributors is handled.
Each critical extension needs a Magento 2 version, a replacement app, or a rebuild. Count them before you price anything.
Build the new connector so it survives an ERP upgrade, instead of tying it to one version’s web services. A well-built connector also keeps inventory accurate, which is the root of why your store shows stock your ERP says you do not have.
Heavy option sets, bundles and custom attributes are the first things to strain variant and option limits on SaaS platforms.
Adobe Commerce hands patching and hosting back to you. BigCommerce and Shopify Plus keep that with the platform.
For a B2B store with a large catalog, customer-group pricing and NAV, the default is BigCommerce B2B Edition when pricing is mostly price lists, and Adobe Commerce when pricing depends on custom code. Shopify Plus fits when the catalog and pricing are simpler than your current setup.
A recent Magento build
A merchant running dozens of storefronts from one Magento installation needed different tax treatment per website without splitting the shared catalog. We built a custom module that swaps in a website-specific tax class during calculation, so products stay unchanged in the shared catalog and native tax calculation is preserved.
Read more: how we solved multi-store Magento tax requirements
Send us your extension list, pricing rules and Dynamics NAV version, and we will map what carries over, what gets rebuilt, and which platform fits your catalog and buyers.
Frequently Asked Questions
Group and tier price data can usually be migrated, but pricing rules written in custom code have to be rebuilt on the new platform.
No. The connector was built for the old platform, so it must be rebuilt or replaced even though the ERP stays the same. Plan it as middleware that can survive a later ERP upgrade.
No. Support ended in 2020, so there are no security patches, which puts stored customer data and card payments at risk.
No. Adobe Commerce is the closest path, but BigCommerce B2B Edition and Shopify Plus also cover company accounts and customer-specific pricing without a self-managed stack.
Rankings hold when every old URL gets a one-to-one 301 redirect, metadata and structured data carry over, and the new site is crawled and checked before launch.
