Shopify Thank you page migration: the full checklist

To migrate before Shopify's 26 August 2026 Thank you and Order status page deadline: list every script still running on those pages, map each one to a replacement Shopify supports — a checkout block, a web pixel, an app pixel, a built-in feature or an app — rebuild and test the upgraded pages, publish, then verify the data is actually arriving in each destination. That last step is the one that turns a hopeful migration into a checked one.

This checklist is for merchants on any non-Plus Shopify plan who have tracking, surveys or custom content on their post-purchase pages — the background and dates are in our news piece on the 26 August upgrade.

How do I find what is still running on those pages?

Audit before you touch anything. Three places hold the answer:

1. The additional scripts box. In your Shopify admin, the Order status page scripts sit in the checkout settings. Copy everything out into a document — this is your inventory.
2. Apps that write script tags. Any app that "just worked" on the order confirmation — surveys, referrals, affiliates, review requests — may have installed a script tag you never saw. List every app that touches post-purchase.
3. Institutional memory. Tags pasted by a previous agency or freelancer are the classic blind spot. If nobody can say what a script does, that is an inventory line too, marked unknown.

For each line, record what it is, which platform it reports to, and who owns it. An unknown script is a risk to resolve, not a line to delete quietly.

What replaces each script?

Map every inventory line to one of the replacement paths Shopify documents — a checkout block, a web pixel, an app pixel, a built-in feature, an App Store app or a custom app — per its upgrade guidance (Shopify documentation).

Two rules keep this honest. First, prefer an app's own integration over hand-rolling a pixel — the developer maintains it and keeps events from firing twice. Second, never assume an app has migrated itself: check its listing, and if the answer is unclear, ask the developer directly.

How do I test before publishing?

The upgrade flow lets you build and preview the upgraded pages before making them live, so use the window rather than publishing blind. Preview the Thank you and Order status pages, confirm every block you mapped is present and rendering, then place a test order end to end. Check the confirmation page a customer sees and the Order status page they return to later — both surfaces, not just the first one.

If a block is missing here, you can fix it before the pages go live. After 26 August, the same gap is a live tracking hole.

How do I verify the data is actually arriving?

Publishing is not the finish line — arrival of data is. For each destination in your mapping table, positively confirm receipt:

• GA4: watch your test order appear in the real-time and debug views with the right value and currency, then compare a full day of purchases against orders in Shopify.
• Google Ads and Meta: use each platform's event-testing screen to see the purchase event land once — not zero times, not twice. A doubled event from an old tag plus a new pixel corrupts your return figures as surely as a missing one.
• Surveys, referrals, reviews: confirm a response, referral link or request actually fires for the test order in the app's own dashboard.

Then reconcile daily for the first week: orders in Shopify against conversions in each platform. Matching counts are the proof; a zero on any line means a gap, not a quiet day. If your measurement has never been set up rigorously enough to reconcile like this, that is the underlying job — it is exactly the analytics and tracking setup discipline that makes every later ad decision trustworthy, and the same data hygiene that pays off in how stores get found in AI-led shopping.

The checklist in one place

Get the migration done and proven

How long the migration takes depends on how much is in the box and which apps are involved. The value is in the last step — knowing, rather than hoping, that your conversion data survived the move.