Migration room

A migration room is the shared workspace for one Stripe account handoff. It gives the source owner, the destination owner, and the operator one place to review eligibility, approve the risky steps, and confirm the destination is ready before the source account changes.

Two accounts, two sides

Most account handoffs have more than one stakeholder. A seller controls the source account; a buyer or new legal entity controls the destination. The room keeps those roles separate so every approval is tied to the correct side of the handoff, and neither side can move billing on its own.

The payment gate

A migration room runs on a single flat project fee, charged only before the first live billing change. Planning, source review, and eligibility all happen for free. Destination scheduling and source cancellation require the project to be paid, so you see exactly what will move before any money changes hands.

The gates

The room is organized around the steps that affect billing:

• account access and role confirmation
• source subscription review
• manual-review decisions
• destination readiness checks
• destination schedule verification
• source cancellation approval
• final packet generation

Each gate exists to make the next billing-affecting step understandable before it happens.

Data handling

SubPorter treats Stripe credentials, subscription data, customer identifiers, and migration records as sensitive operational data. Access is limited to project participants and the support staff a run requires. Stripe keys are encrypted, scoped to the active migration, and removed after completion or inactivity, per the retention policy shown in the product.

What the room does not cover

The room is not your release plan. Your team still owns application-side Stripe references, database updates, entitlement behavior, customer communication, and any monitoring inside your own product after the handoff. SubPorter moves the Stripe Billing side and stops there, on purpose.