BigCommerce to BigCommerce Migration

The standard migration scope includes Products and Product Categories, Customers, Orders, Manufacturers, Coupons, Reviews, and Blogs. The transferable fields are limited to the overlap between BigCommerce source export and target import capabilities.

Taxes, CMS Pages, and Multiple Languages are not included as standard transferable entities in the current scope.

BigCommerce-to-BigCommerce migration can be useful when you are rebuilding a store, replacing an existing storefront, changing store structure, separating a business unit, or starting with a clean target store while retaining supported business data.

No. Customer passwords are not included in the standard transferable fields for this route, and sensitive payment card credentials are not treated as standard migration data. Customers may need to set or reset login credentials on the target store.

Yes. The standard overlap includes Attributes, Variants, Thumbnail Image, and Additional Images, along with product names, SKUs, descriptions, prices, stock fields, metadata, dimensions, and product tags.

Source-only fields such as Product Tax Class and Created Date are not included when the target has no corresponding standard field.

CMS Pages are not included as a standard BigCommerce source export entity in the current migration capability for this route.

If you need to move page content separately, our Migration Customization Service can assess the available source data and mapping approach.

Yes. The migration copies supported data to the target store without requiring the source BigCommerce store to be shut down.

If new supported records are created after the main transfer, Recent Data Migration can be used when applicable.

BigCommerce does not allow a source Order ID to become the target store’s internal BigCommerce Order ID. When the original identifier needs to be retained, it can be stored in the BigCommerce External ID field instead.

Because importing orders linked to products can affect product quantity on BigCommerce, inventory should be checked during post-migration validation.

Supported Product and Product Category Meta Title and Meta Description fields can be transferred. Blog URLs are also included in the standard overlap.

When URLs change between stores, create 301 redirects where reliable mappings are available and review redirects, metadata, canonical behavior, sitemaps, internal links, and crawl errors before launch.

Yes. A Free Demo Migration lets you review representative records before the Full Migration. Check products, variants, categories, customers, orders, coupons, reviews, blogs, images, and field mapping carefully before proceeding.

The migration time depends on product volume, variants, customers, order history, images, blogs, selected migration options, API conditions, and any custom requirements.

Use the Cost Estimator on this page for an initial price estimate.