The direct answer
A legal-entity change does not automatically require subscription migration. If the operating business and country remain compatible, Stripe may support an ownership or entity update. If contracts, country, merchant of record, settlement, or account ownership must move to a new account, plan a controlled migration instead. Stripe Support should confirm the account path first.
Reviewed July 24, 2026 by the MoveMRR product team.
Start with the legal and operational facts
Document who owns the customer contracts before and after the change, which entity issues invoices, which country and bank receive settlement, and whether the buyer needs isolation from the seller’s other products. These facts determine whether an account update or a new account is appropriate.
Use migration when the destination must be a separate account
A separate destination creates new Stripe object IDs and operational ownership. The migration plan must therefore cover data-copy eligibility, catalog mapping, subscription creation timing, source deactivation, application changes, accounting, and customer support.
Do not use a migration tool as legal advice
MoveMRR implements the technical workflow selected by the business. It does not decide contract assignment, tax registrations, privacy roles, customer notices, or regulatory obligations.
Entity update or new-account migration
| Question | Account update may fit | Migration may fit |
|---|---|---|
| Operating country | Unchanged | Different country or unsupported change |
| Contracting entity | Continuity accepted by Stripe and advisers | New merchant or asset buyer |
| Billing isolation | Whole account transfers together | Only one product or customer set moves |
| Application impact | Existing object IDs remain | New customer, price and subscription IDs |
A controlled workflow
- 1
Confirm transaction structure
Record entity, country, contracts, settlement, and scope.
- 2
Ask Stripe for the supported account path
Do not assume that an ownership edit or data copy is available.
- 3
Create a dependency inventory
Map Stripe objects, application IDs, webhooks, reports, tax, and support flows.
- 4
Rehearse if migration is required
Resolve mappings and exceptions before live cutover.
- 5
Retain the acceptance record
Keep sign-offs, mappings, audit logs, and reconciliation evidence.
Limits to verify before migration
- Stripe has final authority over account ownership and entity-change procedures.
- This page is technical guidance, not legal, tax, accounting, or regulatory advice.
- Data-copy and payment-method coverage varies.
- A new account means new object identifiers and application work.
Frequently asked questions
Does changing a company name require a subscription migration?
Not necessarily. A name or representative update may be handled within the existing account, but Stripe must confirm what is permitted for the exact legal change.
When is a new Stripe account usually needed?
Common triggers include a new account country, an asset buyer becoming merchant of record, a carve-out, or a requirement to separate billing ownership.
What changes in the application after migration?
Customer, price, product, subscription and possibly invoice identifiers change. Webhook secrets, portals, reporting, entitlement mappings, and support tooling may also need updates.