Data Migration Known Issues

StagingPro cannot migrate all parts of BigCommerce, and we know most of the issues. Some are currently in development, while others may only become available in later versions of BigCommerce.

Products
Orders
Widgets
Blog-type pages
‘The url is duplicate’ API notification (Pages, Categories and Products)
Multi-Shipment Orders
Incorrect Order Count
Complex Rules
Migrating Apps
Migrating Custom Scripts
Migrating Meta fields
Related Products
Migrating Custom Fields
Migrating ‘Custom Form’ Fields for Customers
Payment Methods
Gift Certificates
Images
Social Media Links
Category Landing Pages & Brand Landing Pages
Category Template Layout File selection that is present in Product Categories
Data Dependencies
Tax Classes
Page Redirects
Themes
BigCommerce Product API issues when recreating products with high variant count
API Rate limits by plan type
Customer Segmentation
Coupon Codes
Promotions
Other Issues

Products

Channel Assignment Required for Product Migration: Products that are not assigned to any channel currently impact both bulk content migration and selective content migration processes.
This limitation has been validated through internal testing. If a product is not assigned to a channel, it will not be included in migration tasks, potentially resulting in incomplete data transfer.

‘Shared Modifier Options’ and ‘Shared Variant Options’ for Products

Currently migration for ‘Shared Modifier Options’ and ‘Shared Variant Options’ for products is not supported in StagingPro (on the destination store Control Panel under Product > Product Options, under the 'Shared Options' and 'Shared modifiers' tabs will show as empty since the option datasets dont migrate). However, unlike Shared options, regular modifier options & regular variant options for products will migrate across as per current implementation.
BigCommerce’s engineering team are reportedly working on sharing an API for this, so there isn't a confirmed ETA yet.

Go to top

Orders

Order IDs in BigCommerce are incremental, so StagingPro cannot keep the original order number. It will still migrate the order, but it will have a different order number. Because of this incremental behaviour, records in the destination store cannot be deleted, thus having the effect of the destination store continually growing with each migration that occurs. It is therefore recommended not to migrate orders unless it is necessary.

The ability to store the original order number in the order notes field is on the roadmap for a future release.

All orders are now migrated with their order statuses ‘as-is’.

When migrating orders and customers to a destination store, BigCommerce recommend in general, you can disable the notifications directly in Marketing -> Transaction Emails. If you disable the emails there, the default notifications will not be sent to customers.

Go to top

Widgets
Widget migration is supported for BigCommerce stores whitelisted to use the new Page Widgets API through Selective Migration (Custom Pages and Page Templates). If needed, please raise a Helpdesk portal request, to ensure your stores are properly whitelisted for use with Selective Page Migrations.

If you are migrating widgets, also please select pages, widget templates and theme (if the theme hasn't been migrated already)

Multi-column layout widget migration is currently not supported through the BigCommerce API.

Although BigCommerce don’t have a specific ETA, we are actively working with BigCommerce on a solution for this for a release at a later date.

Go to top

Blog-type pages

A page that contains blog posts cannot be migrated as BigCommerce API’s currently does not support any ‘Page Type’ with the attribute value ‘blog’. At present, blog-type pages can only be created in the Store Control Panel. This holds true, even with the new Page Widgets API
Please refer to the following url → https://developer.bigcommerce.com/docs/rest-content/pages
Additional note (Feb-2025): BigCommerce recently made a change so that a web page with the type of "blog index page" cannot be changed to a different web page type. This operation was not supported in the BigCommerce Control Panel and consequently, is now also prevented it via API.

Go to top

‘The url is duplicate’ API notification (Pages, Categories and Products)

For Pages and Categories:
If you see this API error when migrating Pages, then it is likely because you have Category urls at the destination store with the same url value. And vice versa, check if when migrating Categories, if there are conflicting Page urls on the destination store. As long as you ensure there is no url conflict between Category and Page urls by using unique url values, the migration will work without issue.

For Products:
If you see this API error when migrating Products and if you dont see any Product with matching url value in the destination store, then BigCommerce support may need to run an orphan url cleanup tool, removing any unseen/remnant url links from your store data tables, to fix this issue. After the cleanup tool is used by BigCommerce support, the migration will work without any conflict on retry, after clearing the remnant url links.

Go to top

Multi-Shipment Orders

Even though permitted through the UI, the BigCommerce API does not allow an order to contain more than one shipment, thus causing some missing shipment information.

The payment type on the source reflects an unknown payment method.

There is currently no mechanism to move the payment type on orders. BigCommerce automatically inserts a "Manual" payment method when creating the order in the new store.

Incorrect Order Count