HAPPIFY REFERENCE ROOMCHK-011REPLATFORMING
Migration readiness checklist
Work through this before any replatforming project starts. Every unanswered line is a launch-day risk; every answered one shortens the migration blueprint.
01
Data inventory
Know exactly what has to arrive on the other side.
- Export counts for products, variants, collections, customers, orders, and gift cards — and decide how much order history actually needs to move.
- List every metafield or custom attribute your theme, feeds, or apps read.
- Identify data that lives only in apps (reviews, subscriptions, loyalty points) and confirm each has an export or migration path.
- Decide the system of record for inventory during the cutover window.
02
URLs and SEO
Rankings transfer through redirects, not hope.
- Crawl the current site and export every indexed URL, sorted by organic traffic.
- Map old URL patterns to Shopify equivalents (collections, products, pages, blog) and plan 301 redirects for everything that changes.
- List the pages earning backlinks so their redirects are checked by hand.
- Plan how sitemaps, canonicals, and structured data will be verified after launch.
03
Customers and accounts
- Decide how customer accounts move — passwords never transfer between platforms, so plan the activation or invite flow.
- Check which customer tags, segments, and marketing consents must survive the move.
- If subscriptions exist: confirm how active contracts, payment tokens, and renewal dates migrate with the new subscription app.
04
Integrations and operations
- List every system that reads or writes store data: ERP, 3PL, email, ads, accounting, support.
- For each, name the replacement app or integration on Shopify and who owns reconnecting it.
- Confirm tax, shipping, and payment configurations are rebuilt — not assumed.
05
Launch QA
The cutover succeeds in rehearsal before it succeeds in production.
- Test orders end-to-end on the new store: full price, discounted, taxed, international.
- Verify redirects with a sample of the top-traffic URL list, on mobile and desktop.
- Confirm analytics and conversion tracking fire once — and only once — per event.
- Write the launch-day sequence with a named owner and a rollback plan.
NEXT USEFUL ACTION
Want this checklist filled in against your actual store?
Plan a migrationFILED UNDER /RESOURCES · BACK TO THE CATALOG