Scope: Official Shopify Help facts are cited inline. The failure hypotheses, test matrix, repair sequence and customer macros are our ops recommendations, not documented Shopify migration behavior. An ownership transfer of the same store is different from rebuilding in a different store. We do not promise that historical orders, tokens or app links move between stores.
The pain: a working shipment, a dead link, a WISMO spike
A broken tracking button is not proof a parcel is lost. Separate the customer-facing URL from the carrier shipment: establish whether the carrier has tracking information before offering a replacement. Conversely, do not tell a buyer “it is just a website issue” until you have checked their shipment. No carrier scan? Say what you know and investigate.
For searches such as shopify migration tracking links broken, store transfer lost tracking and shopify domain change order tracking, the useful first question is the same: which exact link fails, from which message, for which order? Record the original hostname, destination, error and affected customer cohort. Treat order-status URLs as private: keep full links and tokens out of public tickets, analytics exports and screenshots.
What actually breaks? Facts versus hypotheses
| Layer | What Shopify documents | What to test (ops hypothesis, not a platform claim) |
|---|---|---|
| Ownership transfer | Shopify calls for checking that store operations work, transferring custom-domain ownership and updating store notification information. It also calls out billing information for third-party apps outside Shopify (Shopify Help: Change or transfer ownership). | Confirm the new owner controls the domain, support inbox and relevant vendor accounts. Do not assume an ownership change erased tracking data; it might instead coincide with another change. |
| Primary domain | When the primary domain changes, the previously primary domain becomes a redirect domain and stays connected. Other domains listed in the store redirect to the new primary domain (Shopify Help: Change your primary domain). | If an old hostname no longer reaches the store, check whether it is still connected and controlled. Shopify's domain-level redirect description does not guarantee every custom path or old order-status token works. Test the complete URL. |
| Notification templates | Templates can be edited individually, previewed, sent as test emails and reverted to Previous or Default (Shopify Help: Customizing email notification templates). | Look for a hard-coded old hostname or a link to a removed custom tracking page. An old email in a customer's inbox is a historical artifact; changing the next template is not a repair to that already-delivered message. |
| Theme / tracking app | The checkout and accounts editor is separate from the theme editor (Shopify Help: Customizing and editing your checkout and accounts pages). | A missing storefront navigation link or custom page after a theme publish is a possibility to investigate, not something we claim every theme does. For an app switch, ask each vendor about its specific old URLs and historical orders; we verified no app migration behavior. |
| Checkout extension / customer accounts | Shopify's checkout and accounts editor manages checkout, thank you, order status and customer account pages; apps can add functionality, with eligibility depending on page and plan (Shopify Help: Customizing and editing your checkout and accounts pages). | Inspect the actual affected surface after a configuration change. Do not assume publishing a storefront theme proves the order status page or an app block still works. |
Different-store migration: if you moved into a newly created Shopify store, do not transplant old order-status URLs or guess their structure. Confirm the historical-order and link handling with Shopify and the migration provider. This guide intentionally supplies no invented token-conversion recipe.
Pre-migration checklist: prove the customer journey first
- Name the change. Same-store owner transfer, primary-domain change, theme publication, app replacement or a new-store rebuild? Assign one person to own the tracking journey and keep a rollback plan for the specific change.
- Inventory real entry points. Privately retain examples of an old order-confirmation email, shipping email, support macro, storefront tracking link and order-status page. Include in-transit, delivered and split-shipment examples where your store uses them. Save template/configuration copies before editing.
- Preserve domain control. Follow Shopify's domain connection checks before changing the primary domain (Shopify Help: Change your primary domain). On an ownership transfer, include the custom domain in the handover (Shopify Help: Change or transfer ownership). Our recommendation: do not cancel the old domain while customers still rely on its links; we prescribe no universal retention period.
- Audit outgoing messages. On the documented Settings → Notifications page, open the relevant template, review its links, use Preview and Send test email (Shopify Help: Customizing email notification templates). Then separately test actual order-specific links; a rendering preview is not proof every historical order works.
- Ask tracking vendors before switching. Will existing emailed URLs continue to resolve? Which historical orders are supported? Who owns the tracking hostname? Can notifications duplicate during overlap? Get answers for your configuration; do not assume Track123 or any other app automatically repairs old links.
- Test checkout surfaces separately. Use Shopify's checkout/accounts documentation (Shopify Help: Customizing and editing your checkout and accounts pages), rather than an invented menu path. Test the published storefront, thank you/order status experience and customer-account route that your customers actually use.
- Run a go/no-go test. Check old and new messages on mobile and desktop, including a logged-out view where appropriate. A protected page requesting legitimate authentication is not automatically broken. Confirm no cross-customer order details appear.
- Set a peak-season change freeze. Our ops advice: postpone optional migrations until after your peak shipping/support workload. If it is unavoidable, arrange staffed testing and a rollback decision before changing anything.
After the fact: repair the broken layer, then reply
- Contain. Pause only the misdirecting notification flow if it is sending bad links, not fulfillment itself. Keep a known-good contact route. Preserve examples privately before editing.
- Validate the parcel. Match order, carrier and tracking number in your authoritative fulfillment records. Obtain a verified carrier URL; do not fabricate a link by replacing a domain or guessing an order token.
- Classify failures. Old-host failure: investigate domain ownership/connection. New-host 404: investigate that specific path. Wrong app destination: ask its vendor. Missing checkout block: inspect that configuration. Authentication: test the legitimate customer flow. These are diagnostic branches, not Shopify-documented causes.
- Fix future messages. Back up the customized template. Correct only verified stale links and test. If reverting is appropriate, Shopify documents Revert to → Previous or Default, then Save (Shopify Help: Customizing email notification templates); review custom content before replacing it.
- Handle historical links deliberately. A public tracking landing page may need a carefully scoped routing fix. Private order-status links need platform/vendor guidance. Do not blanket-redirect every failed order link to a generic page and call it repaired, and never bypass order authentication.
- Notify affected buyers selectively. Use the authorized customer communication workflow, suppress duplicates and include only the recipient's verified link. Test one example from each affected cohort before sending a larger correction.
- Verify recovery. Log failed-link reports and migration-related WISMO tickets against order volume. Recheck historical and newly generated links. Set your own review cadence and success threshold; we have no sourced repair SLA or promised ticket reduction.
Customer macro: link broken, carrier tracking verified
Hi [name], sorry—the tracking link in our earlier message isn't opening correctly after our store update. I checked your shipment with [carrier]. Its current status is [verified status, checked at date/time with timezone]. Your working tracking link is [verified URL]. This link issue does not itself tell us whether the parcel is delayed. If it still won't open, reply here and we'll help.
Customer macro: still investigating, no verified shipment update
Hi [name], I'm sorry the tracking link isn't working. We're checking both the link and the shipment record for order [reference]. We haven't confirmed an updated delivery date, so I don't want to guess. We'll update you by [a date/time with timezone your team can actually meet]. You can reply here in the meantime.
Internal handover macro
Change: [type and time with timezone]. Affected cohort: [orders/messages]. Failing destination: [hostname and path without private tokens]. Shipment status checked: [yes/no]. Owner: [name]. Proposed fix: [layer]. Old/new order tests: [results]. Customer correction needed: [scope]. Rollback decision: [owner and trigger].
Only use the first macro after the carrier check. Never paste a guessed ETA into either macro. If a parcel really is lost, use the reship vs refund worksheet instead of treating a new URL as the entire remedy.
Tools: tracking notifications first, WISMO macros second
Track123 is the primary tracking-notification option to evaluate here. Before adopting it, confirm support for your historical orders, domain and notification setup with the vendor. This is an affiliate recommendation, not a claim that installation preserves previous app URLs, imports all old orders or fixes Shopify's private order-status links. Use your existing working setup if it already covers the need.
Check Track123 for your tracking-notification setup
Gorgias is the secondary helpdesk option for organizing WISMO replies around the macros above. Validate any required integration and macro fields in your own setup; we provide no migration guarantee, price or promised deflection rate. A simple shared-inbox template is enough when volume is low.
Evaluate Gorgias for WISMO macros
Who should skip—and why not to migrate in peak week
- Stable links and no planned change? Keep your working setup. Do not buy an app just because the guide describes a failure scenario.
- Carrier delay, not a dead URL? Focus on shipment investigation and clear expectations. A tracking redesign does not make a parcel arrive sooner.
- No verified old-order path or rollback owner? Delay optional changes rather than gambling with customer access.
- BFCM / peak dispatch week? Our recommendation is don't migrate in peak week. This is risk-management advice, not a Shopify prohibition or a sourced deadline. Security incidents or urgent outages may require changes; keep those narrow, tested and staffed.
Plan support coverage with the BFCM WISMO guide and keep your Christmas cutoff messaging consistent. A tracking outage should not turn into a second promise you cannot meet.
Related guides
- Reduce WISMO tickets before Black Friday
- Reship vs refund break-even
- Christmas shipping cutoff dates 2026
- Wrong-item support playbook
Sources and disclosure
Official Shopify Help pages opened 6 Nov 2026 (Asia/Kuala_Lumpur / MYT):
- Shopify Help: Change or transfer ownership — store/domain handover and notification information.
- Shopify Help: Change your primary domain — connected domains and primary-domain redirects.
- Shopify Help: Customizing email notification templates — editing, preview, test emails and reverting templates.
- Shopify Help: Customizing and editing your checkout and accounts pages — checkout/accounts editor versus theme editor; eligible app surfaces.
Left out: the dedicated order-status and individual-fulfillment pages did not load usable content. The old Tracking orders URL redirected to a general fulfillment overview, so it is not used as proof of tracking behavior. We include no unsupported admin paths, app-specific migration/import promises, order-token rewrites, propagation/repair timelines, prices, conversion claims or guaranteed WISMO reduction. Checkout configuration documentation supports the editor's scope, not a claim that a particular extension breaks in a migration.
Verdict
Start with the exact failed customer link and a separate shipment check. Preserve domain control, test old and new notifications, and inspect checkout surfaces separately from the theme. Fix one verified layer at a time. If the change is optional and peak week is here, postpone it.
Review Track123 for your tracking workflow
Shopify Help sources opened 6 Nov 2026 (MYT). No app-specific migration behavior or repair timeline verified. Track123 and Gorgias links are affiliate links.