Online store development that replaces an existing site includes migrating the catalogue, agreed order history and customer accounts, with checks on payments and stock. Before the move, decide what will be transferred, when updates to the old system will stop and how orders received during the change will be retained. A trial migration should show that staff can continue processing orders and customers can find and buy the right product.
Start by listing what you use today. The platform, extensions and connected business software determine the migration options. If you are preparing a quote from scratch, our guide to preparing for online store development helps you organise the catalogue. This article focuses on replacing a store that already receives orders.

Which data should move to the new online store?
Transfer the data included in the agreed scope, then check that the new system reads it correctly. Treat products, orders and customer accounts as separate parts of the migration. A successful catalogue import does not confirm that earlier customers or their purchases have also been transferred.
For each group, decide whether it must be available in the new administration, can remain in a protected archive or is no longer required. Check custom fields stored by extensions, such as the selected branch, a delivery instruction or a reference to a document in the business software.
Scroll the table sideways to see all columns.
| Data | What to transfer or connect | How to check it |
|---|---|---|
| Catalogue | Product codes, variants, prices and photographs | The customer selects the correct variant and staff see its corresponding code. |
| Orders | Items, amounts, statuses and the link to the original record | The totals and contents of sample orders match the old records. |
| Customers | Agreed accounts and their links to purchase history | The customer can access their account and only their own orders. |
| Stock | Current availability and existing reservations | Open orders do not return already reserved goods to sale. |
| Public URLs | Existing addresses or their new destinations | An old link leads to the corresponding product or category. |
How do you check products and variants before launch?
Start with a small sample in a separate test environment. Include products the store actually sells: a simple item, a product with variants, an unavailable item and one with a special delivery rule. Record the expected result before importing them.
Before the trial and final transfer, make a backup and check that it can be restored. Limit access to the copies and test environment to the people working on the migration.
A SKU is the code used to connect an item across systems. Check each variant's own code and its relationship to the parent product. A name and photograph cannot distinguish two sizes with different stock levels. The new system may assign different internal identifiers, so retain a mapping between the old and new records.
The WooCommerce CSV tool supports product imports and updates. Its documentation explains the spreadsheet format, variant relationships and matching during updates. Plan customer and order migration separately from this catalogue tool. After the trial, review skipped rows, photographs and whether each imported variant can be purchased.
Keep the test environment separate from live payment processing, courier bookings and customer notifications. Importing an old order should not send another email or trigger a second delivery.
Do customers keep their accounts, passwords and purchase history?
Account and history migration depends on what both platforms support. Confirm that before promising that existing passwords will work in the new store. If compatible password data cannot be transferred safely, prepare a password setup process and a clear customer notification.
A test account should see only its own history. Check guest purchases, duplicate accounts and changed email addresses too. Account merging needs an agreed verification rule; similar names are insufficient grounds for combining purchase histories.
Retain the original amounts and item names for historical orders. Today's product price should not change the display of an earlier purchase. Check open orders, returns and cases that staff are still handling separately.
What happens to orders received during the move?
Every new or changed order needs a known place for processing. Agree on the cutover point, a final transfer of changes and the person who confirms that the records match. If concurrent operation cannot be handled reliably, plan a controlled pause in ordering with a clear customer message.
Imagine a store whose data is copied to a trial version on Monday, with the new site launching later. This is a fictional planning example. In the meantime, purchases arrive, some earlier orders are cancelled and availability changes. The final transfer needs to include changes to existing records as well as newly created orders.
Keep a reference to the source system and its original order ID for every transferred order. Processing the same record again should update the corresponding order or report a problem without creating a duplicate. After the final transfer, compare open orders and their amounts, and resolve differences before normal processing resumes.
Check later payment confirmations and delivery updates that may still arrive through the old connection. For each integration, define when the new system takes over and how transactions started before the switch are handled.
How do you preserve stock availability and access to old pages?
Reconcile stock with the agreed source of availability immediately before the new store starts operating. Goods already reserved must remain linked to the relevant order. Our guide to connecting an online store to inventory covers regular data exchange.
Keep existing public URLs where there is no reason to change them. When addresses change, map old URLs to the corresponding new destinations. Google recommends URL mapping, permanent server redirects and monitoring the move; rankings may fluctuate during significant changes. Use our website redesign SEO checklist for the wider review of titles, indexing and internal links.
What if the new store needs to return temporarily to the old version?
A rollback plan must account for data created after launch. Restoring an earlier copy of the site can leave out new orders. Before doing so, retain the new records and decide where staff will continue processing them.
Agree in advance which problem stops sales, who makes the decision and who checks payments. For an order already paid, keep the payment confirmation and prevent another charge. Include a procedure for a customer who receives confirmation while the team is still switching between systems.
What should you send for a store development and migration estimate?
Send the existing store address, platform name, approximate catalogue size and a list of connected services. Explain which history you need in the new administration and when staff can check a trial transfer. For an initial review, provide a sample export with personal data removed.
As part of online store development, we can assess migration against that scope. In your project estimate request, explain that the store already receives orders and describe how they are processed today. The quote can then distinguish development, data migration and cutover checks.
