MJM Digital Start a conversation
Menu

Online Store Migration

Move the catalog and protect the order flow

Moving a store is not just copying product names. The project needs to account for variants, inventory, orders, customer accounts, payment connections, and product pages people already find.

Check the business records, not just the storefront

An attractive new storefront can still have missing products, mixed prices, or an incomplete order history. Use a sample export and compare fields like SKU, variant, stock, discount, and shipping class with their equivalents in the new platform. Confirm what is imported, what stays as an archive, and what cannot be moved under the current setup.

A store migration is three handoffs

Work through each set of records separately so that the final launch check reflects what the business actually needs.

  1. Catalog

    Check products, variants, prices, images, stock, and old product links. Compare samples on both systems.

  2. Customers

    Decide what happens with accounts, account access, order history, subscriptions, and customer communications where relevant.

  3. Active sales

    Test payments, fulfillment, order notifications, and how new orders are handled during the switch.

Keep a plan for live orders

Decide which site should accept changes during the move. Stock can change because of a refund, physical sale, or purchase while the new catalog is being tested. Agree on which system has the final say, how those changes will be moved, and which staff need access to verify the handoff before the new store accepts orders.

Preserve the product paths already in use

List important product and collection URLs from marketing, search, and emails. Match them to the new product or the closest meaningful replacement if they are changing. Check that any discount or campaign linked to a moved page still has a valid destination. This protects customer paths without pretending the old and new catalogs are identical.

Review customer access, payments, and orders separately

Depending on the platforms, customers may have to set a new password or take a separate step. A stored payment or subscription may have different limitations than a prior order. Explain those changes before launch if they affect buyers. Test order creation, refund handling, and the staff handoff in the new environment instead of assuming a successful product import proves every step works.

Scope the move without suspending day-to-day work

Share both platforms if you know them. Call out any sales, subscriptions, pickup, fulfillment, or customer records the new setup must preserve.

Discuss your project

Check what can transfer

Compare the source and destination using a small sample of products. Confirm how variants, images, attributes, discounts, and stock are represented. Customer passwords and some payment details may not be transferable.

Decide where orders live during the move

Establish how new orders, refunds, or inventory changes will be handled between the initial copy and launch. Confirm whether order history must be imported, retained in the old system, or exported for reference.

Compare the new store before switching

Check sample product counts and variant prices against the source. Test checkout, order messages, shipping calculations, and redirects for important product and category URLs.

What to bring

Bring the current store address, the destination if chosen, and a list of integrations and records that must survive the transition.

Common questions

Will every customer need a new account?

It depends on the platforms and what can be migrated securely. Account reactivation or password reset may be necessary.

Do all old products need redirects?

Pages that have moved should point to their closest relevant replacement when one exists. Review discontinued products separately rather than sending every old link to the home page.

Tell us what you want to do

Bring a goal, a website address, or the problem you are trying to solve.

Start a conversation