Transfer Stripe Account Ownership: What Stripe Allows, and How to Move the Subscriptions

If you are selling a SaaS or buying one, the question comes up fast: how do you transfer Stripe account ownership to the new owner? The answer depends on whether the Stripe account stays with the same legal entity.

If it does, Stripe lets you change the owner. If it does not, you need a new Stripe account, and the subscriptions have to move there. That second path is where things get complicated, and where most of the risk lives.

When you can transfer the account

Stripe allows an ownership transfer when the legal entity on the account stays the same. The current owner goes to Team settings in the Dashboard, gives the incoming person the Super Administrator role, and transfers ownership. The subscriptions stay in the same account because the account itself stays. Nothing moves.

Stripe's help page Change the owner of a Stripe account walks through the steps.

This works for officer changes, internal restructures, or handing the account to a co-founder in the same company. It does not work when a different company is buying the business.

When you need a new account

A sale to another company, a move to another country, or a new legal entity means the buyer opens a new Stripe account. The subscriptions cannot stay in the old one, because that account belongs to the seller's entity. They have to be recreated in the buyer's account and retired from the seller's, in the right order, at the right time.

Stripe has no button for this. Its Customer Data Copy moves customers and saved payment methods between accounts. It does not move products, prices, billing meters, subscriptions, or subscription schedules. It also does not copy charges, invoices, coupons, events, or logs.

After the copy, the destination account has customers and their cards. It has zero subscriptions. The source subscriptions keep billing until someone cancels them. Customer IDs stay the same after the copy. Payment method IDs change.

Three failures that happen when the order is wrong

The gap between "customers copied" and "subscriptions billing from the new account" is where things break.

Double charge. Create active subscriptions in the destination account while the source subscriptions still run, and both accounts charge the same customer for the same period. This is the most common mistake, and the hardest to unwind once the invoices are out.

Cancelled too early. Cancel the source subscriptions before the destination schedules are verified, and a customer loses paid access if the destination fails to collect.

Renewal date lost. Start a destination subscription on the wrong date and the customer pays early, or gets free days they were not supposed to have.

Every step below exists to prevent one of these.

The safe order for moving subscriptions

Step 1: Connect the source account with a read-only key. Create a restricted key on the source Stripe account that can only read. Never use a secret key. The source account stays read-only until the destination is verified, so nothing in the source can be changed by accident during the migration.

Step 2: Scan and decide. The scan reads every subscription in the source account and writes nothing. Some subscriptions need a decision before they can move.

Subscriptions renewing within 48 hours are flagged, because there is not enough time to copy the customer, verify the destination, and switch the application before Stripe charges. Subscriptions with coupons, trials, past-due status, existing schedules, manual tax rates, invoice billing, missing default payment methods, or unusual item shapes are also flagged.

Each flagged subscription gets a decision: Move now or Leave for now. A subscription left for now keeps billing in the source account. Coupons do not carry over: a customer with a coupon renews at full price in the destination account unless you apply the coupon there.

Step 3: Recreate the catalog and copy the customers. Recreate the products, prices, and billing meters the moving subscriptions use in the destination account.

Then run Stripe's Customer Data Copy. The source owner opens Customers in the Dashboard, chooses "Copy to account," uploads the customer list, and enters the destination account ID. The destination owner accepts the request.

After the copy, verify every customer in the destination account. The copy can lose the invoice default payment method. Set it from the copied payment method before you create any schedule, or the first renewal in the destination account will fail.

Step 4: Create one subscription schedule per subscription, on its renewal date. This is the step that prevents the double charge. Never create an immediate subscription in the destination account. Create a subscription schedule that starts on the source subscription's current_period_end, its real renewal date.

The customer is charged once, in the destination account, on the date the charge was already due. No double billing, no free days. Read every schedule back and compare it with the plan before you continue.

Step 5: Cancel the source subscriptions at period end. This step cannot be undone. Use a separate, narrow cancellation key on the source account that can only set subscriptions to cancel at period end. Set each source subscription to cancel at period end, only after every destination schedule is verified.

Each subscription ends in the source account at the same moment it starts in the destination account.

What stays your job

These steps cover Stripe Billing only. Your team still needs to update the application database with the new Stripe IDs, switch the API keys, point the webhooks at the destination account, and check entitlements for every user. Customer messages and the tax configuration also stay with you.

For the full step-by-step with Stripe field names, read the runbook to migrate Stripe subscriptions to another account. For the double charge in detail, read how to prevent double billing during a Stripe account transfer. Buying the business? Read the checklist for acquirers.

Run the migration as a project

SubPorter runs these steps as a migration project in six stages: Connect, Scan, Decide, Pay, Move, Schedule and cancel. It recreates the catalog, verifies the copied customers, builds the subscription schedules on the right renewal dates, and produces migration records both owners can review. One person can run both the source and the destination side, for example when moving to a new legal entity.

Creating the project, the scan, the plan, and the decisions are free. The fee is one-time, not based on MRR, and is charged before the first write to the destination account.

Start a migration project and scan the source account for free, or see the pricing.