Migration

Magento to BigCommerce migration
without the server work.

We move Magento 2 or Adobe Commerce catalogues, customer groups, orders and CMS content to BigCommerce, map attribute sets and store views, and redirect every .html address.

A warehouse worker in a high-visibility vest beside a trolley of boxes
Field map

See how Magento data maps to BigCommerce

Data type: Products
MagentoBigCommerceHow it moves
Products
Configurable productsProducts with variantsMaps directlyChild products become variants with their own SKUs, prices and stock.
Attribute setsOptions, custom fields or metafieldsChanges shapeEach set’s attributes are sorted into variant options, shown fields or API data.
Bundle productsModifiers or a bundle appNeeds a workaroundRebuilt with modifiers, a bundle app or custom code.
Read the detail: See how Magento data maps to BigCommerce
Data type: Customers, Orders, Content, URLs
MagentoBigCommerceHow it moves
Customers
CustomersCustomersMaps directlyNames, emails, addresses and consent.
PasswordsReset inviteNeeds a workaroundHashes cannot move between platforms; customers set a new password from an invite.
Customer groupsCustomer groupsMaps directlyGroup pricing moves to price lists, plan permitting.
Orders
Order historyOrdersMaps directlyImported with dates, totals and line items.
Order statusesBigCommerce statusesChanges shapeCustom states are mapped to the nearest status.
Inventory sourcesInventory locationsChanges shapeEach source becomes a BigCommerce inventory location.
Content
CMS pagesWeb pagesMaps directlyCopy, titles and meta.
CMS blocks and widgetsPage Builder widgetsNeeds a workaroundRebuilt as widgets or theme sections.
Store viewsStorefronts or channelsChanges shapeEach store view becomes a storefront or a localised channel.
URLs
/blue-mug.html/blue-mug/Changes shape301 added in BigCommerce’s redirect manager.
/kitchen/mugs.html/kitchen/mugs/Changes shapeThe category tree is kept without the .html suffix.
/customer/account//account.phpChanges shapeAccount pages redirected so bookmarks still work.
Why migrate

Why migrate from Magento to BigCommerce?

A Magento to BigCommerce migration fits stores that like what Magento does but are tired of what it takes. That means server patching, extension conflicts and a developer on call for small changes.

  • No servers to patch

    BigCommerce hosts and updates the platform, so server patching and upgrade projects come off your list.

  • Catalogue depth mostly kept

    Configurable products become products with variant options. Attributes become options, modifiers or custom fields, depending on their job.

  • B2B pricing carried over

    Customer groups and tier prices map to customer groups, price lists and bulk pricing rules. This depends on the plan, so we confirm it against yours.

  • Several storefronts, one back office

    Websites, stores and store views become storefronts and channels, with languages and currencies set per storefront.

  • An alternative to an upgrade bill

    If your Magento version is due a costly upgrade, get a migration quote too and compare the two side by side before you sign either.

  • When to stay on Magento

    A store that is mostly custom code will need it rebuilt as apps or services. Staying on Adobe Commerce with better hosting can be right, and a simple catalogue may be cheaper on Shopify.

Migration process

Magento to BigCommerce migration process

Six steps from the first audit to the night the domain moves. We rehearse the whole move before cutover night.

  1. Step 01

    Plan around trading

    We agree the timeline around your sales calendar and pick a quiet night for cutover. Your Magento store keeps trading throughout; a typical Magento to BigCommerce migration takes 8–12 weeks, rehearsal included.

  2. Step 02

    Prepare BigCommerce

    We set up a BigCommerce sandbox store, confirm the plan against your B2B needs, and agree a storefront plan for your store views before any data moves.

  3. Step 03

    Theme and design

    We build the storefront as a Stencil theme or a Catalyst storefront. Each module becomes a native feature, an app or a small service using webhooks and the API.

  4. Step 04

    Move the data

    We move catalogues, customer groups, orders and CMS content through the API in batches, timed on the rehearsal store. We rebuild promotions rule by rule.

  5. Step 05

    Test

    We run a full rehearsal migration on a BigCommerce sandbox store about a week before launch. You place test orders and check accounts, emails and payments, and we test every redirect row before sign-off.

  6. Step 06

    Go live

    We pause the Magento checkout for one to two hours at your quietest hour and move the orders placed since the rehearsal. We then point the domain at BigCommerce, switch on the redirects, place test orders and compare the crawl.

Magento → BigCommerce

Magento to BigCommerce migration: what moves, what changes, what we rebuild

We sort every item into one of these three columns before we quote.

Moves across

scripted

Exported, mapped and imported by script.

Catalogueconfigurables, images, stock
Customerswith groups and consent
Order historyimported through the API
CMS pageswith titles and meta

Changes shape

mapped

Same data, a different home on BigCommerce.

Attribute setsoptions and fields
Store viewsstorefronts or channels
Inventory sourcesinventory locations
CheckoutBigCommerce’s checkout

We rebuild

new build

Built fresh, because it cannot be copied.

ThemeStencil or Catalyst
Modulesnative, app or custom
Cron jobswebhooks or scheduled jobs
Hostingretired with the old site
Pricing

Magento to BigCommerce, priced up front

Typical ranges. Your fixed quote follows the free audit, and nothing is billed before you agree it.

Core

Store move

from $22k8–10 weeks

  • Up to 20,000 products
  • Customers, groups and order history
  • Every 301 redirect mapped
Scope this
Most chosen

Store + new theme

from $38k10–12 weeks

  • Stencil theme or Catalyst storefront
  • Modules replaced or retired
  • Two weeks of post-launch fixes
Scope this
Larger

Multi-storefront or B2B

Custom quoteScoped after the audit

  • Several storefronts
  • Price lists and B2B
  • Phased cutover
Scope this
Other routes

Going the other way, or somewhere else?

Questions

Magento to BigCommerce, answered

Anything else, ask on the audit call.

Not answered here? Ask on the free 30-minute audit call.

Book a free audit
Do we have to give up B2B features?

No. Customer groups and price lists cover many B2B needs; full buyer portals use BigCommerce B2B Edition or a quoting app.

What happens to our Magento modules?

Each module is listed in the audit and matched to a native feature, a marketplace app or custom code.

Can we keep several store views?

Yes. Store views become separate storefronts or localised channels, planned before the data moves.

Will customers need new passwords?

Yes. Password hashes cannot move between platforms, so customers get a reset invite.

How long is the order freeze?

Usually a few hours at your quietest time, with a top-up import of the orders placed during the freeze straight after.

Can BigCommerce handle as many SKUs as Magento?

For most Magento catalogues, yes. Very large or very wide catalogues are checked against BigCommerce’s current limits in the audit, and imports run through the API in batches.

What happens to Magento tier prices?

They become BigCommerce bulk pricing rules or price list entries, depending on whether they apply to everyone or to a customer group.

Do we need BigCommerce B2B Edition?

Only if you need company accounts with several buyers, quotes or buyer portals. Customer groups and price lists cover simpler trade pricing.

Certifications

Certifications and partner programmes

Intelligize Digital is a registered partner of these platforms and hosts.

  • BigCommerce BigDev CertifiedBigCommerce Certified
  • BigCommerce Certified PartnerBigCommerce Certified
  • Liquid Storefronts for Theme Developers (Shopify Certified)Liquid Storefronts for Theme DevelopersShopify Certified
  • Headless at Shopify for Developers (Shopify Certified)Headless at Shopify for DevelopersShopify Certified
  • Shopify Foundations (Shopify Certified)Shopify FoundationsShopify Certified

Which Magento module
costs you most sleep?

Tell us about your Magento store. An engineer replies within one business day with the risks and a rough plan.

We save what you type here so we can follow up if you get interrupted.
One file, up to 10 MB: PDF, Word, Excel, CSV, text, PNG or JPG.

An engineer replies within one business day.

What happens next

  1. An engineer replies Within one business day, by email.
  2. A free 30-minute audit On a call with an engineer.
  3. A fixed quote It follows the audit. Nothing is billed before you agree it.
All routes

Book a free audit. One form, one reply from an engineer.

Tell us what you are building or fixing. An engineer reads every request and replies within one business day, with a fixed scope, price and dates once we have talked.

Direct
[email protected]
Response time
Within one business day
Cost of asking
Nothing. The first 30-minute audit is free.

An engineer reads every request.