How do we communicate a subscription-platform migration to active subscribers so they don't think their subscription was cancelled or their payment failed?

Why do subscribers read a migration as a cancellation or a failed payment?

Subscribers read a migration as a cancellation or a failed payment because three things change at once: where they log in, who sends the emails, and sometimes the charge descriptor. On Skio, the subscriber portal sits at the store's home address plus /a/account/login (Skio Help Center, October 2026). Skio's notification emails come from no-reply@reminders.skio.com unless Skio Support sets up your own domain (Skio Help Center, October 2026). Any one of those changes, arriving without warning, reads as "they cancelled me" or "my card failed". Both misreadings end the same way, in a support ticket and then a cancellation. So the message plan is part of managing the subscriber-loss risk of moving onto Skio, not an afterthought to it.

Which four messages should subscribers get, and when?

Subscribers should get four messages: two keyed to the cutover and two to each subscriber's own charge date (Deploi practice, not a Shopify or Skio requirement).

1. Day minus 14: the heads-up. Name the change and the date, and say that the subscription, the price and the next charge date stay the same. Put that subscriber's own next charge date in the email.
2. Cutover day: the new portal. Link the new portal and say what it does. Skio lets you edit each notification's content, timing and sender (Skio Help Center, October 2026). Shopify Subscriptions merchants can also "receive, send, and modify subscription email notifications" (Shopify Help Center, October 2026). So match the transactional emails to this message.
3. Only where a card failed or did not transfer: the card prompt. Shopify's customerPaymentMethodSendUpdateEmail emails a secure link to update one existing vaulted payment method, such as a declined card; only its from and bcc fields can be set (Shopify developer docs, October 2026). No card in the new store means an add-card ask instead. Send the prompt 7 days before that subscriber's charge date, then at 2 days. Skio's billing reminder, once enabled, goes out 3 days before each renewal by default (Skio Help Center, October 2026), so make the three read as one sequence.
4. First charge day: the confirmation. A short "your order is on its way" that names the migration closes the loop.

Which subscribers should get which message?

Subscribers split into three cohorts, and the one who has to act should never get the same email as the one who does not. Telling an untouched subscriber to "update your payment details" creates the very failed-payment worry the plan exists to prevent, so keep the lists apart.

• Cards that transferred: the heads-up, the portal note and the confirmation, with nothing to do.
• Cards that need re-authorization: all four messages, including the card prompt.
• Shop Pay subscribers moving between stores: a genuine re-signup ask, not an update prompt. Skio cannot migrate Shop Pay payment methods from one store to another, and says it is not currently clear whether the Shopify Payments team can (Skio Help Center, October 2026).

Marketing-consent rules still apply to every cohort. A transactional notice about an existing subscription is not a license to email subscribers who opted out of marketing, so keep anything promotional out of these four messages.

Long-tenured, high-value subscribers get a personal note from a named sender in place of the day-minus-14 heads-up; the other three messages still reach them. Give the support team the migration date, the new portal address, the re-authorization list and one canned reply confirming that the subscription is active and the price unchanged.

When should you hold the migration announcement?

Hold the day-minus-14 email whenever the cutover date is still moving. A notice with a date you miss trains subscribers to distrust your emails, so it backfires in the week you most need them read.