Loading…
Your Full-Service Digital Agency & AI Strategy Partner
Real strategists. Real AI tools. Real growth. — 1Digital® since 2012
Workspace by 1Digital® — the agency platform we built. Coming to select agencies. Join the early-access list →
Magento → BigCommerce Replatform
Replatform from Magento / Adobe Commerce to BigCommerce — projecting the EAV catalog into BigCommerce's relational product model, re-mapping Customer Groups, tier prices, MSI sources, and B2B Suite workflows, and converting the .html + layered-navigation URL surface into a page-level 301 map. 200+ migrations completed on a documented no-data-loss cutover playbook with rollback paths.
Trusted by 400+ Brands · Certified Partners
Of results, scale, and quality at the enterprise level.
Specialists across SEO, AI SEO, PPC, design, dev, and strategy.
US core team for clear communication; vetted global specialists for international client work.
Rated 4.9/5 across 941+ verified client reviews.
Reviewed by the 1Digital® Migration TeamLast updated:
TL;DR
1Digital® migrates merchants off Magento 1, Magento 2, Adobe Commerce, and Adobe Commerce Cloud onto BigCommerce — Stencil themes, Catalyst headless, and B2B Edition. The EAV catalog is projected to BigCommerce's relational model, Customer Groups and tier prices become B2B Edition Price Lists, MSI sources become Multi-Location Inventory, and the .html + layered-navigation URL surface is converted into a page-level 301 map with a rebuilt schema graph.
Related: All platform migrations · Magento → Shopify Plus · BigCommerce Experts · BigCommerce Developer · Magento Developer · Data Migration
Why Replatform
Adobe Commerce stores product data in the Entity-Attribute-Value (EAV) model — catalog_product_entity plus a dozen catalog_product_entity_* value tables, attribute sets, and input types. BigCommerce flattens this into a relational product + variant + custom-field schema with Product Modifiers for option-driven price and SKU deltas. The hard work is the EAV-to-relational projection, not the row count.
Magento 1 has had no official security patches since June 2020. M1 stores carry PCI-DSS exposure, an aging extension marketplace, and SUPEE-patch debt. BigCommerce's PCI-DSS Level 1 SaaS surface removes the patch-cadence liability entirely — there is no server you can fail to patch.
Adobe Commerce on-prem means Varnish, Redis, OpenSearch/Elasticsearch, RabbitMQ message queues, cron consumers, and the bin/magento setup:upgrade deploy ritual. BigCommerce is multi-tenant SaaS — the indexer, cache, and search tiers you tune by hand on Magento are simply not your problem on BigCommerce.
Adobe Commerce B2B (Company accounts, Shared Catalogs, Requisition Lists, Negotiable Quotes) is a paid Adobe Commerce tier. BigCommerce B2B Edition (Companies, Buyer Roles, Quoting, Shopping Lists, Invoice Portal, Net Terms) delivers the same buyer workflows without the Adobe Commerce license uplift on top of hosting.
BigCommerce Catalyst (Next.js + GraphQL Storefront API + Makeswift visual editor) is a maintained, first-party headless framework. It is a clean exit from Magento PWA Studio / Venia or a self-built Hyvä-headless stack you would otherwise carry the maintenance tax on.
BigCommerce's REST + GraphQL Storefront/Admin APIs and Webhooks cover the integration surface Magento exposes via its REST/GraphQL endpoints — without you running the application servers, queue workers, and search cluster behind those Magento endpoints.
What We Migrate
Field-level mapping with referential integrity — the EAV catalog, Customer Groups, tier prices, MSI sources, and B2B workflows all carry across with audit trails intact.
Simple, configurable, grouped, bundle, virtual, and downloadable product types plus EAV custom attributes and attribute sets → BigCommerce products + variants + custom fields + Product Modifiers. Configurable products resolve to variant matrices; bundle/grouped logic re-expressed with Modifiers or product relationships.
Customer accounts, address books, Customer Groups, wishlists, and saved carts → BigCommerce Customer Groups, or B2B Edition Company Accounts where group pricing/visibility is involved. Passwords are reset-on-first-login (no hash port between platforms).
Full order history, line items, invoices, credit memos, RMAs, store credit, and gift cards preserved for revenue reporting, LTV continuity, and support look-back after cutover.
Catalog price rules, tier prices, and customer-group prices → BigCommerce Price Lists (B2B Edition). Magento negotiable quotes → BigCommerce Quoting; punchout via PunchOut2Go.
Multi-Source Inventory (MSI) sources and stock reservations → BigCommerce Multi-Location Inventory with source-priority and per-location stock preserved where the model maps cleanly.
CMS pages, static blocks, and Page Builder content → BigCommerce Pages + Page Builder. Slugs preserved or explicitly 301'd to BigCommerce equivalents.
Product, category, CMS, and layered-navigation canonical URLs exported in full, then projected onto a page-level 301 map. Title/meta/canonical/hreflang carried per URL; schema graph rebuilt with consistent @id references.
Yotpo, Bazaarvoice, Okendo, Trustpilot review corpora preserved with star ratings, verified-buyer flags, and AggregateRating schema continuity so AI engines keep citing the brand.
How We Migrate
Inventory every installed module (composer.json + app/code), custom plugin, observer, EAV attribute set, B2B Suite workflow, ERP/PIM integration, and tax/shipping rule. Each is mapped to a BigCommerce equivalent (native, app, Stencil, Catalyst, or Open Checkout customization) and any gap is flagged before quote.
Catalog count, EAV attribute density, configurable-product fan-out, customer/order volume, media library size, CMS pages, and the full layered-navigation canonical URL set parsed from the Magento sitemap and DB. Produces data-parity targets and a page-level URL-mapping spreadsheet.
Magento /<category>/<product>.html (and the layered-nav ?attr= canonical mess) → BigCommerce trailing-slash /<category>/<product>/ with 301 rules, canonical strategy, and a rebuilt schema graph (Product, BreadcrumbList, FAQPage, Organization) with consistent @id references.
Stencil theme or Catalyst storefront build. Iterative loads with field-level parity reports: EAV attributes → custom fields/Modifiers, Customer Groups → B2B companies, tier prices → Price Lists, orders, reviews. Apps configured against staging.
Freeze Magento writes, run the final delta sync (orders, customers, MSI stock), flip DNS at low TTL, and validate checkout, payments, shipping, tax, search, GA4, Consent Mode v2, and pixels live. The cutover window is typically under 60 minutes.
30+ days of crawl-error triage, Search Console change-of-address, ranking and AI-citation monitoring, Core Web Vitals tracking, B2B workflow validation, and an edge-case fix sprint for issues that only surface under live traffic.
Extension Mapping
The third-party stack you depend on rarely needs to change — only the connectors and the host platform. Custom Magento modules and observers are the line items that need a rebuild estimate.
| Magento / Adobe Commerce | BigCommerce Equivalent |
|---|---|
| Adobe Sensei Live Search / Product Recs | Searchspring, Algolia, Klevu, or Nosto for BigCommerce |
| Magento Klaviyo extension | Klaviyo for BigCommerce (native connector) |
| Yotpo / Bazaarvoice / Okendo for Magento | Same vendors with native BigCommerce connectors |
| Avalara AvaTax for Magento | Avalara AvaTax for BigCommerce (native) |
| ShipperHQ / ShipStation / Temando | ShipperHQ / ShipStation native BigCommerce integrations |
| Magento Subscriptions / Aheadworks recurring | Recharge or Rebillia for BigCommerce |
| Stripe / Braintree / PayPal Magento modules | BigCommerce native Stripe / Braintree / PayPal / Apple Pay / Affirm / Klarna |
| Adobe Commerce B2B Suite | BigCommerce B2B Edition (Companies, Quoting, Shopping Lists, Invoice Portal) |
| PWA Studio / Venia / Hyvä | BigCommerce Catalyst (Next.js + GraphQL) or Stencil theme |
| Custom Magento modules / observers | BigCommerce apps, Stencil customizations, or services on BigCommerce APIs + Webhooks |
| NetSuite / SAP / Dynamics connectors | Celigo, Boomi, MuleSoft, or custom BigCommerce Admin API middleware |
The Technical Reality
Adobe Commerce stores almost nothing in a single product row. catalog_product_entity holds the entity skeleton; the human-readable values live across catalog_product_entity_varchar, _text, _int, _decimal, and _datetime, joined by attribute_id through eav_attribute and grouped by attribute set. A configurable product is a parent entity with super-attribute links to its simple children; a bundle is a parent with selection options pointing at other simples. None of that shape exists on BigCommerce.
We project the EAV graph into BigCommerce's flat product model: a configurable's simple children collapse into a single product with a variant matrix, super-attributes become variant options, and price/SKU-affecting attributes that are not true variants become Product Modifiers. Attribute sets with descriptive (non-variant) attributes become custom fields. Bundles and grouped products are re-expressed with Modifiers or product relationships depending on how they were sold. The deliverable is an attribute-by-attribute projection table approved before any data moves — not a generic CSV importer run.
Magento's default product URL is /<url_key>.html, optionally prefixed by the category path when 'Use Categories Path for Product URLs' is on, plus the catalog URL-rewrite table accumulates historical rewrites every time a url_key changes. BigCommerce uses a trailing-slash /<category>/<product>/ structure with no .html suffix, so every product and category URL changes and needs an explicit 301.
The harder issue is layered navigation. Magento generates crawlable filtered-category URLs (?price=, ?color=, multi-select facets) that search engines have indexed for years — a notorious duplicate-content and crawl-budget sink. We export the full Magento URL set including the url_rewrite table and the indexed facet URLs, decide per pattern whether each filtered URL 301s to a BigCommerce faceted page, a category, or is canonicalized away, and verify the redirect chain post-launch with Screaming Frog plus Search Console coverage reports. Skipping the facet URLs is the single most common cause of post-migration traffic loss on this route.
Adobe Commerce B2B Suite workflows (Company accounts, Shared Catalogs, Requisition Lists, Negotiable Quotes, company credit) map onto BigCommerce B2B Edition Companies, Buyer Roles, Price Lists, Quoting, Shopping Lists, and Net Terms — but Negotiable Quotes with custom approval chains usually need a light rebuild on BigCommerce's quote engine, and that has to be scoped at discovery, not discovered at cutover. Multi-Source Inventory sources map to Multi-Location Inventory; source-selection-algorithm logic that drove order sourcing on Magento has to be re-expressed in BigCommerce's location priority or pushed to an OMS.
The integrations that break quietly are Magento-specific extensions with no behavioral equivalent: custom sales-rule cart-price logic, observer-driven side effects, and PIM/ERP connectors written against Magento's REST/GraphQL schema. These are rebuilt as BigCommerce apps or middleware on the Admin API. We catalog every module from composer.json and app/code at discovery so the rebuild list — and its cost — is on the quote, not a surprise mid-build.
SEO Equity Protection
Migrations that lose SEO equity lose months of revenue. On this route the layered-navigation facet URLs are the single biggest risk — they are treated as a release-blocker, not an afterthought.
Timeline & Engagement
Standard B2C
Catalog under 5K SKUs, moderate EAV attribute density, standard checkout, common app stack (Klaviyo, Yotpo, ShipStation), 2 payment gateways, single-storefront, Stencil theme.
B2B / Mid-complexity
B2B Edition (Companies, Quoting, Shopping Lists, Invoice Portal), tier prices → Price Lists, ERP / NetSuite, Avalara, dense attribute sets, configurable-product fan-out, custom shipping rules.
Catalyst / Headless / Enterprise
Catalyst (Next.js) storefront, multi-storefront, multi-currency, custom Magento modules/observers with no clean equivalent, large catalog (50K+ SKUs), heavy layered-nav URL inventory cleanup.
Engagements start at $185/hour. Fixed-fee proposal after discovery, sized to your catalog, EAV density, integrations, B2B requirements, and target architecture.
Request a Proposal
Share your Magento version (M1, M2, Adobe Commerce, Adobe Commerce Cloud), EAV attribute density, configurable-product complexity, B2B Suite usage, ERP/OMS, and non-negotiables. A senior strategist responds within one business day with a pricing band and a draft migration roadmap.
FAQ
Free migration audit. Fixed-fee proposal. EAV projection table approved before data moves. 200+ migrations run on a documented no-data-loss cutover playbook.
