Getting started

SubPorter does one job: migrate active subscriptions from one Stripe account to another while you stay on Stripe Billing. Use this page to check the fit and to prepare.

When SubPorter fits

• The source and the destination are both Stripe accounts.
• Most subscriptions are active and charge a saved payment method automatically.
• The destination owner is ready to bill from the destination account.
• You want a decision gate before any source subscription changes.
• Your team updates the application, database, and webhooks separately.

Subscriptions that need a decision

SubPorter flags these before anything is scheduled. The source owner decides each one: move now, or leave for now.

• Renews within 48 hours
• No saved payment method, or no default payment method
• Two customer records with the same email, each with an active subscription
• Trial, past due, or already set to cancel
• Coupon or discount
• Manual tax rates, or billed by invoice
• Already on a subscription schedule, or an unusual item shape

A flag does not stop the migration. It puts the decision in front of a person.

Subscriptions billed by invoice (send_invoice) are flagged and cannot move in the current version. Leave them for now.

Your first session

1. Create a migration project. Name it, and choose your role: source owner or destination owner.
2. Invite the other owner, or run both sides yourself.
3. Connect the source account with a read-only restricted key from the one-click link.
4. Run the scan. It reads every product, price, meter, customer, and active subscription. Nothing is written.
5. Decide each flagged subscription.

The result is a plan, not a change. It shows what moves, what waits and why, and what must be true before SubPorter writes to the destination account. Everything in the first session is free.

The source read-only key and the source cancellation key both include Invoices read. Invoices read is read only. After each renewal, SubPorter uses it to confirm that the customer was charged once.

Prepare

• A source owner who can create a restricted key in the source account.
• A destination owner who can create a restricted key in the destination account, or one person for both.
• A migration window that ends more than 48 hours before most renewals.
• A plan for who updates the application-side Stripe references.
• A customer message, if you plan to tell subscribers.