How do we communicate a subscription-platform migration to active subscribers so they don't think their subscription was cancelled or their payment failed?
A subscription migration needs four subscriber messages to avoid reading as a cancellation: a notice 14 days before cutover, a portal-change note on cutover day, a payment-update prompt wherever a card did not transfer, and a confirmation on the first charge day (Deploi practice, not a Shopify requirement). Shopify's customerPaymentMethodSendUpdateEmail mutation sends the secure update link (per shopify.dev, September 2026).
Why subscribers misread a migration
Three things change at once from the subscriber's side: the login destination, the sender and look of the transactional emails, and sometimes the charge descriptor. Any one of those, arriving without warning, reads as either "they canceled me" or "my card failed." Both misreadings produce the same behavior, which is a support ticket followed by a cancellation.
The four messages, timed against the first charge, not against go-live
- Day minus 14: the heads-up. Name the change, name the date, and state explicitly that the subscription continues, the price does not change, and the next charge date does not move. Put the next charge date in the email, personalized. That single line prevents most of the tickets.
- Cutover day: the new portal. Where to log in, what the new portal can do, and a direct link. Shopify Subscriptions merchants can receive, send and modify subscription email notifications, so the transactional set can be aligned to the same voice as this message (per Shopify's Help Center, September 2026).
- Only for the cohort whose card did not transfer: the update prompt. Do not send this to everyone. Send it to the segment your vault discovery identified, and use
customerPaymentMethodSendUpdateEmail, which sends a secure link to update a specific vaulted payment method and supports a customfromaddress (per shopify.dev, September 2026). Send it at least 7 days ahead of that subscriber's charge date, then once more at 2 days. - First charge day: the confirmation. A short "your order is on its way" that references the migration by name. This is the message that closes the loop for anyone who ignored the first three.
Segment before you write
The cohort that has to act and the cohort that does not should never receive the same email. Telling an untouched subscriber to "update your payment details" manufactures exactly the failed-payment anxiety you are trying to prevent. Build three lists: cards that transferred, cards that need re-authorization, and Shop Pay subscribers, who cannot be migrated store to store at all (per Skio, September 2026) and therefore need a genuine re-signup ask rather than an update prompt.
What to tell the support team, in one paragraph
The migration date, the new portal URL, the list of subscribers in the re-authorization cohort, and one canned reply that confirms the subscription is active and the price unchanged. Support answers this question more often than the emails do.
When NOT to announce
When the cutover date is still moving. A migration notice with a date you miss is worse than no notice, because it trains subscribers to read your emails as unreliable in the week you most need them read. Hold the day-minus-14 email until the parallel billing run has a confirmed end date.
Marketing-consent rules still apply to these sends. Transactional notices about an existing subscription are not a license to email subscribers who opted out of marketing.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Put the next charge date and the unchanged price in the first email, personalized. Most migration comms lead with the platform name, which the subscriber does not care about, and bury the two facts they do.
- What we’ve seen: Support ticket volume peaks on the first post-migration charge day, not on cutover day, which is why a comms plan anchored to go-live misses the spike entirely. The teams that keep churn near the bottom of the 2 to 5% band are the ones who segmented the re-authorization cohort and left everyone else alone.
- Where we disagree: The standard advice is to over-communicate. We would rather under-communicate to the cohort that needs to do nothing, and over-communicate to the small cohort that has to act. Volume is not reassurance.
- What this page adds: the four-message sequence, its timing relative to each subscriber's own charge date, and the Shopify mutation that sends the secure update link.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Our decision records