Getting started

SubPorter does one job: move active subscriptions from one Stripe account to another while you stay on Stripe Billing. Here is how to tell if that is your situation, and what to have ready before you start.

Best-fit migrations

You are likely a fit when:

• The source and destination are both Stripe accounts.
• The subscription set is mostly active recurring billing.
• The destination owner is ready to take over future charges.
• Customer and card data can move through Stripe's Customer Data Copy.
• You want a review gate before any source subscription changes.
• Your app team will separately handle product code, database references, and webhooks.

Rows that need a human

Some subscriptions should not run through an automatic path. SubPorter holds these for manual review before anything is scheduled:

• Renewals that fall inside the migration window
• Missing or ambiguous default payment methods
• Two or more customer records sharing one email, each with active subscriptions
• Trials, past-due subscriptions, or subscriptions already set to cancel
• Stacked discounts, coupons, or unusual tax settings
• Existing subscription schedules or unusual item shapes
• Any handoff where the buyer and seller disagree on timing

A review flag does not block the migration. It puts the decision in front of a person before billing changes, instead of burying it in a batch.

Invoice-billed subscriptions (send_invoice collection) are the one exception in the current version: they are flagged for review but cannot be migrated yet, so keep them outside the packet. Charge-automatically subscriptions are unaffected.

Your first session

In the first session you create a migration room, name the source and destination owners, connect the source Stripe account with a read-only key, and let the scan run. You then decide each flagged subscription — include it or keep it outside the packet.

What you get back is a plan, not a cutover. It shows which subscriptions look ready, which need review, and what has to be true before SubPorter will schedule the destination or cancel the source. The destination account connects later, in the Copy step, and the source stays read-only until the final cutover key.

Before you open a room

Have these ready:

• A source owner who can authorize the current Stripe account.
• A destination owner who can receive the subscriptions.
• A migration window with enough room before the next wave of renewals.
• A decision on who updates application-side Stripe references.
• Agreement on customer messaging, if you plan to notify subscribers.