Playbook · July 9, 2026

Migrating a subscription programme without losing subscribers

A subscription migration account covering payment token portability, the communication sequence that kept churn contained, and the reconciliation checks we ran for six weeks afterwards.

By Verdehouse· Updated September 17, 2026
Rollout timeline with four overlapping delivery phases
Rollout timeline with four overlapping delivery phases

The technical migration took a fortnight. Deciding what to tell subscribers, and when, took longer and mattered more.

## Confirm token portability before anything else

If stored payment credentials cannot move, you are not migrating — you are asking every subscriber to re-enter a card, and you will lose a meaningful share of them. Establish this in writing with both providers before committing to a date.

## Tell subscribers what changes for them

Two notices before, one at cutover, one after, each naming exactly what changes: next charge date, delivery date, and how to skip. We stopped explaining the platform and started explaining consequences, and the support volume halved.

## Reconcile for six weeks

Compare expected charges, successful charges and shipments weekly against the pre-migration baseline. Silent failures in the first cycles are the real risk, and they only show up in reconciliation rather than in dashboards.

Where this applies

  • Shopify
  • Email Marketing

Work with Verdehouse

This playbook comes from the work Verdehouse does. See what they offer, the results they can evidence, and how to start a conversation.

More from Verdehouse