Blog / Shopify & e-commerce /

Preparing a Shopify migration when the catalogue keeps changing

Say a Shopify migration is booked, but the catalogue won’t sit still. New variants appear, items go out of stock and descriptions get rewritten while the new store is still being built. Freeze the catalogue too early and the launch data is stale. Let it change without control and the migration map drifts.

A moving catalogue needs a way to record changes and a rule for when to sync them. You’re not trying to stop merchandising. You’re making sure every change has a known destination and gets checked before launch.

Establish a source of truth

Decide which system owns each type of information during the migration: product identity, titles, descriptions, variants, inventory, media, pricing, URLs and collections. Different systems may own different fields. Write the ownership down so two teams do not overwrite each other’s work.

Give each product a stable identifier that exists in both environments, such as a verified SKU or another internal key. I don’t trust titles alone, because they change and get duplicated. Find missing or reused identifiers before transfer and give someone the job of fixing them.

Keep a change log for edits made after the first export: product identifier, field changed, date, source and destination status. A shared log is far easier to audit than a chain of messages or a late spreadsheet merge.

Decide what can keep changing

Classify changes by risk. A corrected description may be safe to sync through an established process; a new variant, changed URL or price may need additional review. Define which edits can continue freely and which require notifying the migration owner.

Set a content freeze only where it’s necessary and practical. If merchandising can’t pause, agree a final data cut-off and a catch-up process. Make the date visible to everyone and say how later changes will be handled.

Inventory moves fastest. Decide how the launch environment gets the latest stock state and how orders and stock changes are protected during the transition. The exact process depends on your integrations, so check it with the technical and commerce owners.

Map URLs and product relationships

Build a mapping from old product and collection URLs to their destinations. Check how handles are generated and what happens when a title changes. Don’t assume the platform keeps every path. When I plan a migration, I test redirects for renamed, merged and retired products early, not on launch day.

Review variants and their identifiers. Ensure options, images, availability and product data remain associated with the right variant. A catalogue import can appear successful while variants have been reordered or product relationships lost.

Check collections and internal links after data changes. A newly added product may need to appear in a relevant collection, while a retired item may still have incoming links. Record these decisions as the catalogue evolves.

Run repeatable comparison checks

Compare source and destination data by stable identifiers. Check for missing products, duplicates, variant counts, required attributes, images, prices and URL changes. Use automated comparisons where available, then review exceptions manually.

Keep a representative sample for deeper review: products with many variants, products with unusual content, items with subscriptions or bundles if applicable, and products with important search traffic. Confirm the live page, not only the import report.

When an exception appears, record the decision and owner. It may be an intentional consolidation or a data error. Do not silently ignore unmatched records.

Coordinate launch and rollback

Name who approves the final catalogue, who applies the last sync and who verifies the public site. Agree how to handle changes made during the launch window. Plan a rollback or correction path that covers URLs, orders and inventory, not just page files.

After launch, check key products and collections, monitor error reports and update the migration log. Keep old systems available until the agreed conditions for retirement are met.

Protect order and operational data

A migration process must account for more than product descriptions. Inventory, orders, customer records and fulfilment systems may update while the new storefront is being prepared. Decide which system remains authoritative for each data type and how changes are synchronised during the cutover. Involve the people responsible for operations and privacy; search planning cannot define that process alone.

Test representative product records after import, including bundles or subscriptions if the store uses them. Check that variant IDs, images, tax treatment and shipping settings remain connected. A product page can look correct while the underlying option or fulfilment rule is wrong.

Set a point where the team compares a final export with the live destination. Any changes that occur after that point should have an owner and a reconciliation process. Keep the change log with the migration records so decisions can be traced.

If an item can’t be moved cleanly, don’t silently omit it. Record the reason, business owner and customer-facing impact, then decide whether to publish, redirect or hold it.

Keep the SEO decision separate from the data cutover

URL continuity, product data accuracy and inventory sync are related but distinct workstreams. Give each its own check and owner. A successful import doesn’t prove redirects work, and a redirect test doesn’t confirm the right variants or stock. I’d connect them in the launch review without letting one stand in as evidence for another.

Do not use a temporary staging URL as a final canonical destination. Confirm that production domain settings replace preview references and that internal links point to public routes. Search engines need a coherent published environment, while the operations team needs the correct live catalogue.

When a product changes after launch, decide whether the migration log continues as the source for that adjustment or whether the normal merchandising workflow takes over. Make the handoff explicit. Who will maintain the record once the migration project closes?