Shopify Store Migration Services

Product options are the part most exports flatten. A garment listed as size and colour on the current platform can arrive as a single line with a text field, which means no stock per size, no filter, and a buy button that cannot tell a medium from a large. We rebuild options as structured values, map each combination to a variant, and confirm the stock number attached to every one.

Bundles, kits and made-to-order items need a decision rather than a conversion. Some become a product with components held in metafields; others stay as a single code because the warehouse never separates the parts. That decision goes into a short mapping sheet so the storefront, the warehouse and the accounts team work from the same list.

Every indexed product address, collection address and campaign landing page gets a row in a redirect map before launch. The map names the old path, the new path and the status code, and it is tested by opening a sample from each traffic source rather than by trusting the export. A redirect aimed at a category instead of the exact product loses the sale and the ranking together.

Where a page has no like-for-like replacement, we send it somewhere useful rather than to the home page. A discontinued range can point at its successor collection, and an article can keep its address even when the shop moves, because content links outlive product lines.

Passwords almost never travel in a usable form, and pretending otherwise creates a locked door on day one. We plan a reset invitation that explains the move, keeps the old order history attached to the same email address, and gives support a lookup that does not require the customer to remember an account number from three years ago.

Order history matters for returns, warranties and repeat purchase. The new store receives the orders it needs for service, with the original reference preserved so an agent can match a conversation to the right purchase. Guest orders are matched by email or phone using a written rule, not a guess.

Recurring billing is the part of a migration that cannot be recreated by importing rows. A saved card exists as a token held by the payment provider, and that token has to keep working, or every subscriber needs to re-enter payment details at the worst possible moment. We confirm the token arrangement with the provider before the move and run a live test charge on a low-value plan.

Subscription records carry a plan, a billing date and a status. Those three fields have to line up after the move, or a customer is charged twice in one month or skipped entirely. A rehearsal that includes a renewal, a pause and a cancellation is worth more than a clean spreadsheet.

Every store accumulates tools that did a small job: a quote form, a delivery-date picker, a loyalty ledger, a product configurator. Some have a direct equivalent on the new platform; others do not. We list each one, state whether it is replaced, rebuilt or retired, and price the gap before the cutover rather than after it.

An app with no equivalent usually signals a process the business depends on. Retiring it quietly is how a store loses a workflow nobody documented. The list is reviewed with the people who use each tool, not only with the person who pays the invoices.