first migration notice reply for legacy download links

A practical copy pattern for first migration notice reply. Adapt it to the current Shopify product page, delivery instructions, and policy pages visible to customers.

View product preview Back to hub Delivery & Support

Use case

Customers click old links, bookmarks, or previous receipt URLs and need to find the current Shopify support path.

Writing rule

Make the new path clear before explaining the old path. Do not promise old link restoration, redirect coverage, or permanent link recovery. Give a safe current route.

Compliance note

This is a self-serve copy resource, not a checkout, waitlist, migration service, account repair offer, or third-party support desk.

Draft reply

Subject: About the current download path Hi [name], Thanks for checking. The customer-facing path for this digital product has changed, so an older download link, receipt page, course area, or account route may not match the current Shopify instructions. The current place to start is: [current product page or support page]. If you need help locating an order, please send only your order number or purchase email. Please do not send passwords, one-time codes, card details, private account links, mailbox access, API keys, or remote access. This reply explains the current support route and does not promise old-link restoration, third-party account changes, redirect coverage, or a custom migration service. Thanks, [store name]

Customize safely

Replace [current product page or support page] with the public page that customers can use now.

Support boundary

Keep the answer focused on the current Shopify delivery path and published policy, not private platform access.

Useful CTA

Link to product preview, product status, Delivery & Support, Terms, or a current resource page.

Checklist

Does the reply explain the current route first?
Does it avoid promising old link recovery?
Does it avoid asking for sensitive access credentials?
Does it avoid official support or partnership claims?
Does it route to public policies and support pages?