StagingPro is designed to create staging environments and not (at least at this stage) a way of pushing data to production. One of the challenges faced is that item indexes are changed for each BigCommerce store and this includes the order id.
This will not impact the work you can do on your environment. StagingPro has still kept the relationships between records intact and the same amount of data has been moved, so none of your testing will be affected.
StagingPro will soon be rolling out a new feature which will resolve this issueNo, during StagingPro migrations from the source store to the destination store, we have no control of the increment ID’s assigned by BigCommerce’s systems when the data hits the target store. Which is why, as an example, products must use SKU as the point of reference, not product ‘increment’ ID. Such ID’s are internal reference numbers auto-generated by BigCommerce maintains and which StagingPro cannot control. Product SKUs will get moved. Similarly when you move Orders new Order IDs will get assigned by BigCommerce and the orders will be moved to Pending State so that a user does not fulfil the orders from the destination store, inadvertently.