What BigCommerce is, and where it fits
BigCommerce is a hosted SaaS ecommerce platform: BigCommerce manages hosting, security patching and uptime, and you manage the store through its admin and APIs rather than a server you control. Plans range from standard tiers aimed at small and mid-size merchants up to Enterprise. Multi-Storefront is available across plan levels with different storefront limits, while Enterprise can provide higher API limits, service levels and additional B2B capabilities. BigCommerce also offers a headless approach, letting you use its backend and APIs with a custom-built frontend instead of its own theme layer.
Storefronts on the standard, non-headless path are built with BigCommerce's Stencil theme framework, with themes sourced from the BigCommerce Theme Marketplace or built custom. As with any closed, hosted platform, migrations to or from BigCommerce work within its data model and API surface rather than a direct database copy, so what the API exposes for products, orders and customers determines what can move automatically.
Products, categories and the data model
Unlike platforms that rely purely on tag-based collections, BigCommerce supports a native, nested category tree alongside products and their variants. This makes it a comparatively good fit for catalogs with multi-level category structures, since you don't have to flatten a category hierarchy into tags or smart collections the way you would on some other hosted platforms.
Customer and order data can be transferred through supported APIs and import paths, but available fields and the behavior of imported history depend on the source, target and chosen method. We test representative records and agree acceptance criteria instead of assuming historical orders will behave like newly placed orders. Custom product data usually maps to BigCommerce's custom fields, and price lists (BigCommerce's mechanism for customer-group or currency-specific pricing) are one of the first things we check when a source platform has its own tiered-pricing setup.
Apps, themes and what doesn't move automatically
A working BigCommerce store commonly relies on apps from the BigCommerce App Marketplace, for reviews, subscriptions, search, marketing automation or shipping rules. App-stored data doesn't transfer as part of a platform migration; moving off BigCommerce means exporting anything held inside an app separately, and moving onto BigCommerce means reinstalling and reconfiguring equivalents rather than carrying over app settings.
Stencil themes don't translate to another platform's templating system, so a move off BigCommerce typically means rebuilding the storefront design on the new platform, and a move onto BigCommerce means adapting a marketplace theme or commissioning custom theme development. If you go the headless route instead, the frontend is decoupled from BigCommerce's theme layer entirely, which changes the scope of what "design migration" even means.
SEO, URLs and how we handle a BigCommerce migration
BigCommerce is more flexible about URL structure than some hosted competitors, letting you set custom URLs for products, categories and pages rather than enforcing a single fixed pattern. That flexibility helps when you're migrating onto BigCommerce and want URLs to resemble your old ones, but it doesn't happen automatically, and moving off BigCommerce still means mapping its URL patterns to whatever the new platform requires.
As part of a managed migration we compare your existing URL structure against BigCommerce's, set up the redirects needed in either direction, and carry over metadata that's still accurate under the new URLs, using the same approach described in our SEO & Redirect Migration service, scoped to BigCommerce's specific API and routing constraints.
Frequently asked questions
Can I keep my nested category structure when moving to BigCommerce?
Yes. BigCommerce supports a native, multi-level category tree, so a deep category structure from another platform usually maps over more directly than it would to a platform that only supports flat tags or collections.
What happens to my BigCommerce apps if I migrate away?
App-specific data generally needs to be exported separately from each app before migration. We migrate the core store data an app relies on, but not the app's internal configuration or stored records.
Does BigCommerce's headless option change how a migration works?
It changes what theme migration means, since a headless setup decouples the frontend from BigCommerce's own theme layer, but the underlying product, order and customer data still moves the same way through the API.
Will my URLs stay the same if I move to BigCommerce?
Only if you deliberately configure matching custom URLs, which BigCommerce allows for products, categories and pages. We typically set up redirects rather than assuming a 1:1 URL match.