Yes. On a managed migration, your BigCommerce orders move to Shopify as real orders, not as a spreadsheet. On our inlinePRO project, every historical order kept its original order number, payment state and tracking, and the import sent no email to any customer1. That was 1,419 orders worth $824,684, all with their original order numbers and going back to the store’s first order in 20181.

How much history can move

The size of your history isn’t a limit. On the Andersen Restorations project, we moved a BigCommerce store to Shopify with 2,242 parts, 40,736 customers and 41,268 orders2. A history that size simply takes longer. On BigCommerce stores with tens of thousands of orders, we have found that the order history is the longest part of the import: Shopify limits how fast past orders can be created, so the import runs in the background for about a week3. We start it early. Smaller stores go much faster. On inlinePRO, the data itself (every product, customer and order) was imported and verified in the first two days of a 26-day project1.

Abandoned carts are the one part of order history that shouldn’t become orders. BigCommerce keeps them alongside real orders, so we preserve them as draft orders or import them into your email marketing platform for targeted recovery campaigns4.

Where BigCommerce order data goes wrong

BigCommerce exports don’t always show what really happened. On inlinePRO, one full orders export later arrived empty, and some records marked Incomplete were not orders at all, so we rebuilt the missing data from the API and excluded abandoned checkouts1. We have run into two other quirks on projects like this:

  • BigCommerce can record a refund amount on an order whose status still says Shipped or Completed. Keying refunds off the status leaves those orders fully paid in Shopify and overstates net sales3, so we refund based on the amount recorded.
  • Discounts are missing from the export, so we derive them to make the totals reconcile3.

Errors like these are why we check order history one order at a time rather than by count. When we audit stores that automated tools have moved, the order history is where most problems hide: abandoned checkouts imported as real orders, tracking numbers dropped, declined orders left open and a few orders skipped entirely3. We compare every source order number against Shopify instead of trusting the import’s own range.

Keeping your order numbers

Your original numbers only survive if the import sets them correctly the first time. Shopify keeps the original order number when it is set as the order is created; orders cannot be renamed later3. There is also a launch-day detail to handle: unless the next order number is set above the imported range before launch, new orders can look like duplicates of historical ones3. Handled properly, this means your support team and customers can look up an old order by the number on the confirmation email.

What decides the scope for your store

Whether you can keep your history isn’t really in question; how much you bring over is a choice. Three things decide the scope and how long it takes: how many orders you have, how far back you want to go, and how much of that history includes refunds, partial shipments and tracking. Our pre-migration audit checks those details against your live BigCommerce data before anything is imported.

Sources

  1. BigCommerce to Shopify Migration Case Study: inlinePRO Case study
  2. Ecommerce Migration Case Studies Page
  3. Order history From our project notes
  4. BigCommerce to Shopify Migration Guide (2026): Cost & Timeline Migration guide

“From our project notes” are short, anonymised lessons from migrations we have run. They describe what we typically see, not a guarantee for every store.

Want it answered for your store?

Tell us about your store in ten minutes. We come back within one business day with an honest assessment, a recommended track and a fixed price.