Payments migration checklist
A payments migration fails in the gaps between platforms, not inside either one: unverified accounts that hold the first payouts, subscribers who never re-consent, taxes that nobody is remitting for a month, affiliates whose links die. This ten-step sequence puts verification and tax first, models cost before committing, bridges subscribers with an explicit offer, and keeps the old processor alive for refunds.
The sequence
- Verify first. Open the Whop account, complete business KYC, connect the payout method and withdraw a test amount before announcing anything.
- Decide tax handling. Self-managed, Whop calculates/collects (you remit), or Whop collects and remits (US, EU, UK). If leaving an MoR, confirm your registrations.
- Get a rate. Above ~$50k a month, ask Whop's network team for volume pricing before you model the move.
- Rebuild the catalogue. Identical prices and names. Attach delivery (Discord, course, files, licence keys). Test every product with a real card.
- Ask about card import. If leaving Stripe, ask both Stripe and Whop about PAN migration. Assume no until confirmed.
- Plan the bridge. Announce a date; offer extended access or a discount for re-subscribing; write the emails for day −14, −7, 0 and +7.
- Dual-run one cycle. Close new sign-ups on the old platform; keep it live for renewals until each subscriber has moved or churned.
- Move affiliates. Recreate affiliate rates on Whop; tell affiliates their new links; honour pending commissions on the old platform.
- Keep the old account open. At least 120 days for refunds and disputes; export all data before closing.
- Measure. Re-subscription rate, dispute rate, effective fee rate after 60 days; compare with the model.
What to expect on re-subscription
There is no public benchmark for creator-platform migrations; operators we have spoken to plan for losing a fifth to a third of subscribers in the switch and recovering part of that over the following quarter. Bridging offers and a short, honest explanation of why the move benefits members raise the number. Model the move at 70% re-subscription, not 100%.
Timeline
| When | What |
|---|---|
| Week 0 | Verification, payout test, rate request, tax decision |
| Week 1–2 | Catalogue rebuild and testing; affiliate setup; email drafts |
| Week 3 | Announce; open Whop for new sign-ups; close old sign-ups |
| Week 3–7 | Dual-run through one billing cycle; chase non-movers |
| Week 8+ | Old platform in refund-only mode; measure; close after 120 days |
Start with verification
The account is free; verify, test a payout, then decide.
Talk to Whop about migratingWhop Network · 2.7% + $0.30 · custom rates at volumePartner link · free to start · no monthly fee
Frequently asked questions
How long does a payments migration take?
Roughly eight weeks from verification to old-platform-in-refund-mode, including one full billing cycle of dual running.
Will I lose subscribers moving processors?
Some. Subscriptions cannot transfer, so every subscriber re-consents; plan at 70% re-subscription and bridge with an offer.
Should I close my old processor account?
Not for at least 120 days; you need it for refunds and disputes on past sales.
Written by Karel Moreau, editor of Migrate Payments. Fees and policies re-checked against the providers' published pricing pages on 20 September 2026. Spotted a change? karel.moreau@migratepayments.com.