Safety model

The risk in a Stripe account handoff is specific: the customers on your active subscriptions are the ones you just sold, and a mistimed cutover charges them twice or skips a renewal. SubPorter is built around that risk. Each safeguard below is a gate, not a promise.

The source stays read-only until the destination verifies

SubPorter does not treat a migration as a single switch. Destination catalog setup, customer-copy checks, schedule creation, schedule verification, and owner approval all happen while the source account keeps billing untouched. The only write SubPorter ever makes to the source is cancel_at_period_end, and only after the destination passes verification.

Renewals keep their real dates

A subscription that renews inside the migration window leaves no room to copy customers, confirm payment defaults, and schedule the destination cleanly. SubPorter flags near-renewal rows against a buffer so the team can defer the row, handle it by hand, or move the window, instead of racing a charge date.

Destination writes are verified, not assumed

A billing API accepting a request says nothing about whether the result is correct. After SubPorter creates destination schedules, it reads each one back and checks the customer, start date, item prices and quantities, collection method, proration, and automatic tax against the plan. Source cancellation stays blocked until those checks are clean.

Manual review is explicit

When a subscription carries a condition that deserves human judgment, SubPorter sets it aside and says so. Missing payment details, trials, past-due status, stacked discounts, unusual tax setup, existing schedules, and tight renewal timing all route to review rather than into an automatic batch. You decide; the tool does not guess.

The scope stays narrow

SubPorter migrates Stripe Billing account state. It does not touch your application database, rewrite webhook handlers, change entitlement logic, deploy product code, or make tax and legal calls for your business. Keeping that boundary visible is what makes the Stripe side easy to verify and easy for your app team to coordinate around.

Evidence is part of the run

Every completed migration leaves a packet a buyer, seller, finance lead, or operator can open later. It documents the plan, the review decisions, the destination verification, and the source cancellation outcome, so the handoff holds up without anyone trusting it from memory.