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.
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.
Widgets
For bulk migration, StagingPro migrates Page widgets but cannot determine their location/position on the page. As per current BigCommerce implementation, widgets created in Page Builder will continue to have an empty region as they are wrapped in a Layout. To allow for ‘store-to-store’ widget transfers, BigCommerce engineers are working on changes, possibly the Layouts API. Use Selective Content migration as the alternative.
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.
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.
Please refer to the following url → https://developer.bigcommerce.com/docs/rest-content/pages
‘Shared Modifier Options’ and ‘Shared Variant Options’ for Products
Currently migration for ‘Shared Modifier Options’ and ‘Shared Variant Options’ for products isnt 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.
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
On rare occasions, selected orders are not able to be created. We are working with BigCommerce in the hope of finding a solution soon.
Complex Rules
Migration of complex rules (product rules attached to multiple SKUs allowing merchants to set up conditions & actions based on shopper option selections on the storefront) is currently not supported in StagingPro and will be considered as roadmap item for future release.
Migrating Apps
Channel data is migrated successfully between stores only if the information is stored within BigCommerce however, the apps or extensions to which this data belongs do not get migrated. Any data stored within an installed app itself can also not be migrated.
Migrating Custom Scripts
Currently, StagingPro does not migrate custom scripts that are in Script Manager.
Migrating Meta fields
This feature request is implemented. Customers can now choose Metafields at the Brand, Category and Product levels and migrate the same to the destination environment.
Related Products
Related Products migration is implemented in Staging Pro.
Migrating Custom Fields
Generally speaking, BigCommerce stores have custom fields only for Products and is implemented in StagingPro. To clarify, Custom Fields don't exist for Customers or Customer Groups.
For Companies, (only in relation to B2B) and the attribute name is ‘Extra Fields’.
Migrating ‘Custom Form’ Fields for Customers
This option is also implemented in StagingPro. Please be clear that Please note the custom fields should also be present in the destination store (not just in the source store alone) for this migration to work. There is no BigCommerce API available to create the customer custom fields, it only provides the API to migrate the customer ‘custom form field values’
Payment Methods
The payment methods in a store are not publicly available and, therefore cannot be migrated at this time.
Gift Certificates
Gift certificates can be migrated but only if the “Enable Gift Certificate” option is enabled within BigCommerce. For instructions on how to use the content migration settings to migrate gift certificates, please go here.
Images
There is currently no BigCommerce API to move banners and home page carousel images. We are looking at alternative migration methods and hope to have a solution shortly. It is worth noting that images outside of the THEME/ Template folder cannot be migrated as of now.
BigCommerce has no API to move images from WEBDAV and Image Manager. Any images such as Carousel images used in the Cornerstone theme, will not automatically move using StagingPro. Those images can be moved manually from your side.
Social Media Links
The BigCommerce API does not currently support the migration of Social Media links.
Category Landing Pages & Brand Landing Pages
The BigCommerce API does not currently support the migration of Category Landing pages and Brand Landing pages. The workaround is to perform a Bulk Content Migration of Categories, Brands, Widgets, Widget Templates and Pages.
Data Dependencies
There are many cases where data migration may cause a conflict unless related data is migrated simultaneously. An example of this is the relationship between a product and its variations or a product and its categories. A summary list of dependencies can be found below.
Tax Classes
Please note that tax classes are not yet available. We will endeavour to add this as soon as APIs are available.
URL Redirects
This will be added soon and is currently not being migrated.
Themes
Currently themes are applied to the default store. Manual selection is needed for association with a different storefront.
BigCommerce Product API issues when recreating products with high variant count
In some instances when recreating products with high variant count (e.g. a product with more than 600 variants), BigCommerce returns an Internal Server 500 error. Adjusting the product variant count and listing it shows success. Another related error type is with product URL's redirecting to 404 Webpage not found.
In such cases a ticket needs to be raised with the BigCommerce developer team for further investigation.
Customer Segmentation
Customer segmentation for targeted promotions is a planned roadmap release item.
Other Issues
If you encounter any issues that we may have missed in this document, please feel free to share them with us by raising a support ticket. The StagingPro team will investigate all new problems and will do so if we can provide a solution.
To view our onboarding steps, please access the following article → StagingPro Onboarding