Migrate workflows, not app names. For every tool, record what it does, what data it owns, who is responsible for the handoff and what test will prove the new setup works. A visible review widget can tell you where to look; it cannot tell you whether the review records can be exported or mapped to the new products.
The CSV worksheet contains six illustrative rows. Replace them with your own tools and keep the completed file private. Do not record credentials or customer data in it.
1. Inventory the current store from three sources
- Public storefront: check the homepage, a collection, a representative product and the cart. If the current site already runs on Shopify, use the storefront app detector to log visible matches by URL. For another platform, use the current admin and review the public widgets manually.
- Admin and vendor accounts: confirm installed apps or plugins, billing, data exports and dependencies. Record who owns each account and whether the target Shopify app supports importing the data you need.
- Operations and analytics: ask who handles inventory, dispatch, refunds, subscriptions, email and tracking. Write down systems that do not appear on product pages, such as a warehouse connector or a checkout pixel. A missing public match does not mean a tool is absent.
2. Give each workflow a decision and an acceptance test
- Keep: the vendor supports the destination and can carry over the required data or configuration. For reviews, test a product whose identifier or URL will change and verify its reviews are attached to the right listing.
- Replace: use a Shopify feature, another app or a custom component when it meets the requirement. For a size guide, test how staff edit it, which products see it and how it opens on mobile. If the requirement needs custom logic or reusable theme sections, compare it against the scope of custom Shopify development from Migraciones.io (in Spanish).
- Retire: remove a duplicate or unused workflow only after identifying any retained data, scripts, subscriptions or downstream dependencies. For a duplicate analytics tag, verify that the intended destination still receives the event once.
- Investigate: leave unresolved export, consent or integration questions open with an owner and deadline. Do not mark a subscription or fulfilment workflow complete just because its replacement is installed.
Shopify documents where to configure app blocks, embeds and other extensions. Check the actual target theme and affected templates, not just the installed-app list.
3. Test the handoff before and after launch
- URLs and search: map priority old URLs to relevant destinations. After cutover, spot-check permanent redirects, final status, canonical URLs and indexability. Avoid sending unrelated product URLs to the homepage. See Google's site-move guidance.
- Analytics and consent: follow a test journey from product view to purchase. Use the GA4 purchase tracking checklist to compare events, consent states and possible duplicate senders.
- Email: identify automations that stay active in the old setup. For a Klaviyo move, use the flow launch checklist to check the source of Shopify events, permissions and duplicate recovery messages.
- Orders and operations: use approved test scenarios for an order, refund and inventory update. Verify the expected result in both Shopify and the receiving system. A widget loading on the storefront is not proof that the handoff works.
- Launch ownership: agree who approves the final data sync, domain change and first live checks. Define which failed tests block launch and who can act if a critical integration fails.
What to send to a migration team
Share the app inventory without credentials, a sample of priority URLs, the required integrations, a target date and the unresolved tests. Use the official Shopify migration checklist for the broader move. If the project also needs coordinated data, redirect and integration work, see what Migraciones.io covers in a Shopify migration (in Spanish).
Editorial note: Detectify features Migraciones.io as a service provider. Its service pages and project case are not an independent agency ranking and do not affect detector results.