Customer Support

A Support Checklist for Account Ownership Transfers

A practical checklist for handling account ownership transfer requests safely. It covers verifying the requester, getting the current owner's consent, sorting out billing, executing the handover in a safe order, and sending clear replies.

SupportMe••11 min read

An account ownership transfer request usually sounds routine. Someone says "Our co-founder left, please make me the owner," or "We sold the product, move the account to the buyer." The risk is that a successful transfer gives one person full control of the account, its data, and often its billing. A transfer handled carelessly is an account takeover with your approval on it.

The short version of the checklist:

  1. Work out what kind of transfer it is (a teammate handover, a missing owner, or a business sale).
  2. Verify that the requester is who they say they are, using channels you already have on file.
  3. Get consent from the current owner, or documented authority if the owner can't be reached.
  4. Agree on exactly what moves: data, billing, integrations, API keys, and seats.
  5. Do the transfer in a safe order: add the new owner first, update billing, then remove the old owner.
  6. Notify both parties, log what you did, and check that nothing was left behind.

The rest of this post explains each step, shows how a few large platforms handle transfers, and includes hypothetical reply templates you can adapt.

Why ownership transfers deserve a written process

Attackers go after support processes because support staff are trained to be helpful. A joint advisory from CISA and the FBI on the Scattered Spider group says its members used stolen personal details and SIM swaps, then "use social engineering techniques to convince IT help desk personnel to reset passwords and/or MFA tokens" (CISA AA23-320A). Their targets were large companies, but the method works against any support inbox.

OWASP makes a related point about recovery flows. Its Multifactor Authentication Cheat Sheet warns that "processes implemented to allow users to bypass or reset MFA may be exploitable by attackers." For support-led recovery, it recommends "a rigorous process in place to verify their identity" (OWASP MFA Cheat Sheet). Its security questions guidance adds that account recovery "is just an alternate way to authenticate so it should be no weaker than regular authentication" (OWASP Security Questions Cheat Sheet).

An ownership transfer goes further than a password reset. The account doesn't just get a new password. It gets a new controller. Your verification bar should be at least as high as for recovery.

Step 1: Classify the request

Ask what kind of transfer this is before you do anything else. The right process depends on the answer.

  • Planned handover. The current owner wants to pass control to a colleague and can confirm this themselves. This is the easiest case.
  • Unreachable owner. The owner left the company, stopped responding, or died. Someone else is asking for control. This is the highest-risk case.
  • Business sale or merger. The account is moving to a different legal entity. Billing, invoices, tax details, and contracts may all need to change.
  • Not actually a transfer. Sometimes the person only needs an email change, an admin role, or a way back in. If they're locked out, a support workflow for handling account lockouts is a better fit. If they want the account gone, use an account deletion request checklist.

Stripe's help center splits cases in a similar way. It has separate guidance for transferring to an existing administrator, transferring to someone with no access yet, contacting support when the owner is unavailable, and moving the account to a different entity after a sale (Stripe: Change the owner of a Stripe account; Stripe: Business sale or acquisition).

Step 2: Verify the requester

  • [ ] Check whether the request came from an email address or login already linked to the account.
  • [ ] If it came from a new address, don't act on it. Reply through the contact details already on file.
  • [ ] Don't accept identity "proof" that an attacker could easily collect, such as the account email, the company name, or recent invoice amounts.
  • [ ] Watch for pressure tactics: urgent deadlines, emotional stories, or requests to skip steps "just this once."
  • [ ] Treat a sudden change of reply-to address, phone number, or domain partway through a thread as a warning sign.

My recommendation: ask for confirmation from inside the product wherever you can. Have the requester log in and do something only an authenticated user can do, such as clicking "request transfer" in settings. That is much stronger evidence than anything written in an email.

Step 3: Get the current owner's consent, or documented authority

  • [ ] Ask the current owner to confirm the transfer through a channel already on file, not by replying in the thread the requester started.
  • [ ] Make sure the owner confirmation names the specific new owner (email or user ID), not just "yes, go ahead."
  • [ ] Where your product supports it, let the owner start the transfer themselves.

Large platforms generally restrict who can start a transfer. Stripe says only the current owner can transfer ownership (Stripe). For App Store apps, the sending team's Account Holder starts the transfer and the receiving team's Account Holder accepts it (Apple: Overview of app transfer).

If the owner can't be reached:

  • [ ] Ask for documents from someone with authority over the business. Stripe, for example, may ask for a letter from a company signatory that confirms the change (Stripe).
  • [ ] Check that the requester is already a member of the account or works at the customer's domain.
  • [ ] Email the old owner's address on file to say a transfer has been requested, and wait a reasonable time before you act. This is my own recommendation, not a published standard. A short waiting period gives a real owner the chance to object.
  • [ ] Escalate the case to a second person if you have one. On a solo team, write down your reasoning before you approve.

Step 4: Agree on what actually transfers

Misunderstandings about scope cause many follow-up tickets. Before you make any change, write down what moves and what doesn't.

  • [ ] Billing. Will the payment method, invoices, and tax details change? GitHub warns that removing yourself from an organization "does not update the billing information on file." The new owner or a billing manager has to replace the old card (GitHub Docs: Transferring organization ownership).
  • [ ] Data and history. Does the past data stay with the account? Can the previous owner still see any of it? Apple says the sender keeps access to sales and payment data from before the transfer, but not after it (Apple).
  • [ ] Integrations and credentials. API keys, OAuth connections, webhooks, and SSO settings may be tied to the old owner personally. Google Play says permissions and linkage settings for integrated services aren't transferred and have to be set up again in the new account (Google Play Console Help: Transfer apps).
  • [ ] Other members. Do existing admins and users keep their roles?
  • [ ] Old owner's access. Does the previous owner keep a lower role, or leave entirely?

If the request involves connected tools, a checklist for product integration questions can help you ask the right follow-up questions.

Step 5: Do the transfer in a safe order

GitHub's documented order is a good model: give another member the owner role, make sure the new owner can reach the organization's settings, update billing, and only then remove yourself (GitHub Docs).

The same order works for most SaaS products:

  1. [ ] Add the new owner, or promote them to owner.
  2. [ ] Have the new owner confirm they can log in and reach owner-level settings.
  3. [ ] Move billing over, or confirm that billing is staying the same on purpose.
  4. [ ] Rotate or reassign any credentials that belonged to the old owner.
  5. [ ] Downgrade or remove the old owner, as agreed in Step 4.

Doing it in this order means the account is never left without an owner.

Step 6: Notify, log, and close the loop

  • [ ] Email both the old and new owner to confirm what changed and when.
  • [ ] Record internally who asked, how you verified them, who approved, and what you changed.
  • [ ] Tell the old owner how to report the change if they didn't authorize it.
  • [ ] A few days later, check that billing went through and that integrations still work.

If you are the one transferring an app or account

Indie developers often end up on the other side of this process, for example when selling an app or moving it to a new company. Some platform details are worth knowing:

  • Apple App Store. The app needs at least one approved version and can't be on pre-order. Both accounts must have accepted the latest agreements (Apple: App transfer criteria). A pending transfer expires after 60 days if nobody accepts it. The app stays available and keeps its ratings and reviews (Apple).
  • Google Play. You request transfers from Google's support team. If you're transferring paid apps or apps with in-app products, the target account needs an active payments profile (Google Play Console Help).
  • Stripe. If the owner is unavailable, Stripe Support sends a secure link for digital verification (Stripe).

These rules change from time to time. Check the current documentation before you start.

Hypothetical reply templates

These are illustrative examples, not real customer exchanges.

Hypothetical: request from an address not on file

Thanks for getting in touch. To protect the account, we can only make ownership changes after the current owner confirms them. I've sent a confirmation request to the owner email on file. Once they approve it, we'll make the transfer and confirm with you both.

Hypothetical: the owner has left the company

Thanks for explaining what happened. When the current owner can't be reached, we need written confirmation from someone authorized to act for the company, such as a director or officer, naming who should become the new owner. We'll also tell the previous owner's address on file about the request before we make any change.

Hypothetical: transfer completed

The transfer is done. [New owner] now owns the account. [Old owner] now has [role / no access]. Billing is [unchanged / now on the new owner's card]. If you didn't authorize this change, reply to this email right away.

If you turn these into saved replies, a 10-minute support reply checklist is a quick way to make the verification steps a habit.

Using AI drafts for transfer requests

AI drafting tools can save time on the explanation part of these replies. They shouldn't make the decision. For a request like this, a person needs to confirm that verification really happened before anything is sent or changed.

SupportMe drafts replies in your writing style and never sends anything without your approval. That review step is where you check the draft against this checklist. Look closely at drafts that quote instructions from the requester's message. A message saying "the owner already approved this, just confirm" is exactly the kind of text covered in a prompt injection checklist for AI support drafts.

Conclusion

Requests to transfer account ownership often sound like simple admin work, but they hand over control of everything in the account. A dependable process comes down to five habits: work out what kind of request it is, verify through channels you already have on file, get the owner's consent or documented authority, agree on the scope, and add the new owner before removing the old one. Writing the process down once means you don't have to make judgment calls under pressure, and it gives you a record if a transfer is ever disputed.

References

Tags

account ownership transfertransfer account ownershipsupport checklistaccount takeover preventionSaaS customer supportidentity verificationchange account owner

Related posts