You migrate WooCommerce without losing order history by exporting all your orders from the source before you leave, then deciding how much of that history to import into the new platform, while always keeping the full export for your records. Order history is private data in the database, so a front-end capture cannot reach it; it has to be exported while you still have admin access. What you do with it then splits in two: importing the orders into the new store recreates the customer-facing history, so returning customers see their past purchases, and this depends on the new platform supporting historical order import, which not all do fully. Separately, and non-negotiably, you retain the complete export for accounting, tax, warranty, and customer-service needs, since you must be able to answer questions about past orders regardless of what the storefront shows. WPBuildAI exports your full order history before cutover, imports what the new platform supports so customer records stay intact, and hands you the complete export to keep.
Orders are private data, so export before you leave
The first principle is that orders live behind the login. Each order, with its line items, totals, customer, and status, sits in the store’s database, not on the public storefront, so a front-end capture cannot read it, the same boundary that applies to customer accounts. That makes exporting the orders from the source a hard deadline tied to your admin access: once you leave the old platform, the history may be unreachable. So the very first order-history task is a complete export while you still control the store, capturing every order as data. Everything else, importing, retaining, reconciling, depends on having that export in hand, which is why it comes before the migration itself, not after.
Two separate goals: customer-facing history and your records
The reason order history needs a clear plan is that it serves two different purposes that are easy to conflate. One is the customer experience: a returning shopper logging in and seeing their past orders. The other is your own business record: the ability to look up any order for accounting, tax, warranty, returns, disputes, or a support question, long after the sale. These are distinct, and they migrate differently. Customer-facing history depends on importing orders into the new storefront; your business record depends only on retaining the export. Recognizing that they are two goals, not one, is what prevents the mistake of importing orders into the shop and assuming that also satisfies your record-keeping, or vice versa.
Import what the new platform supports
For the customer-facing side, you import the exported orders into the new store, mapping each order to the right customer so their account shows their history. The honest caveat is that platforms differ: some import historical orders fully into customer accounts, some only partially, and some not into the customer-facing view at all. So confirm what your new platform actually supports before promising customers their full history, import what you can, and set expectations for the rest. Where the platform’s import is limited, you can often still surface key history through the account or handle lookups internally from the export. This is ordinary migration mapping, much like moving products and categories, applied to orders, and it is bounded by the destination’s capabilities.
Always retain the full export
The record-keeping side is non-negotiable regardless of what the storefront can show. You will need to answer questions about past orders for years, for tax and accounting, for warranty and returns, for chargebacks and disputes, and for customers asking about an old purchase, and that data is personal and financial, so it falls under privacy rules like the GDPR and must be kept securely. So retain the complete order export as a permanent, protected business record, independent of the new store’s display. Treat the storefront import as the customer experience and the retained export as your books. Even if you imported nothing, you would still keep the export, because the obligation to account for past orders outlives any platform, and a careful site move protects your data as well as your URLs.
Reconcile and verify what came across
Whatever you import, verify it rather than assuming. Reconcile the order counts and totals between the old store and the new import, so you know the history is complete and accurate, not silently truncated. Spot-check individual orders, especially recent ones and any tied to open warranties or subscriptions, to confirm the line items, totals, and customer mapping are right. Because a loyal minority of customers often accounts for much of the revenue, echoing the concentration the Ahrefs study finds in traffic, pay particular attention that your repeat buyers’ histories came across intact. The platform change itself carries no ranking penalty, as the Backlinko analysis shows, so this is purely a data-integrity check: confirming the numbers match is how you know the history truly survived.
Steps to migrate order history
- Export all orders as data from the source while you have admin access.
- Keep the export secure as personal and financial information.
- Confirm what your new platform supports for historical order import.
- Import the orders, mapping each to the correct customer, up to what is supported.
- Retain the full export permanently for accounting, tax, warranty, and support.
- Reconcile counts and totals and spot-check key orders after import.
Worked example: history for customers and for the books
Consider an established store with years of orders, many tied to warranties and repeat customers. Before migrating, the team exported the complete order history as data and stored it securely as a permanent record. They confirmed the new platform could import historical orders into customer accounts, then imported them, mapping each to its customer, so returning shoppers saw their past purchases. They reconciled the total order count and revenue between old and new, and spot-checked recent and warranty-linked orders. Where the platform’s customer-facing import had limits, they relied on the retained export for internal lookups. The result was that customers kept their visible history and the business kept its complete records, because the two goals were planned and handled separately.
Limitation: full customer-facing history is platform-dependent
It is honest to bound this. You can always preserve your business record through the export, but how much customer-facing history the new store can display is genuinely limited by the destination platform, so on some platforms returning customers will see less than they did, no matter how complete your export is. That is a constraint to discover and communicate early, not a failure of the migration. Very large order histories also take care to export and import without errors, and privacy rules govern how long and how you retain the data. So separate what you can guarantee, your retained records, from what depends on the platform, the customer-facing view, and set expectations for the latter honestly rather than promising history the new store cannot show.
Key points
You migrate WooCommerce without losing order history by exporting every order from the source before you leave, since orders are private database data a capture cannot reach, then handling two separate goals. Importing the orders into the new store recreates customer-facing history where the platform supports it, so confirm what yours can do, map orders to customers, and set expectations for any limits. Separately and non-negotiably, retain the full export as your permanent business record for accounting, tax, warranty, and support, kept securely as personal and financial data. Reconcile counts and totals and spot-check key orders to prove the history came across, paying special attention to repeat customers. Remember the customer-facing view is platform-dependent while your retained records are always in your control. WPBuildAI exports your full order history before cutover, imports what the new platform supports so customer records stay intact, and hands you the complete export to keep. Send your web address for a free analysis.
Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.