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 which are migrated have their status changed to “Pending” as keeping the original status may trigger emails to be sent out to clients.
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 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.
Shared Options, Shared Variants and Shared Modifiers
There is no API available to move shared options and modifiers, but this does not affect product options or modifiers from being migrated with their related Products; instead, the list of options and modifiers available to use is missing. BigCommerce’s engineering team are reportedly working on sharing an API for this, so there isnt a confirmed ETA yet.
Product options and modifiers are currently being worked on and made available in the next release.
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) 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
While Products are successfully migrated, links to similar or related products cannot be migrated. This will require multiple API calls and may have an impact on the Production site hence has been de-prioritised at the moment.
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. 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.
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 136 variants), BigCommerce returns an Internal Server 500 error. Reducing the product variants to less than 30 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.
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