Governance
How to Transfer Ownership of a Discord Bot Application
Moving a Discord bot application to new ownership changes who controls it, not how it runs.
Is this your situation?
You are stepping away from a Discord bot project and want ownership to pass on cleanly. You want the bot to keep working while control moves to someone else via a developer team.
Where teams go wrong
- Transferring to an individual instead of a team An app already owned by a team cannot use the self-service transfer flow.Why it happens: The owner assumes any account can receive the app.
- Skipping recipient consent Discord requires consent from the recipient before any ownership transfer.Why it happens: The owner submits the request without confirming the recipient agrees.
- Ignoring verification loss If the receiving team lacks a verified identity, the app becomes unverified.Why it happens: The owner does not check the receiving team's verification status first.
- Retrying too soon An app can complete no more than 3 ownership transfers in a rolling 365-day period.Why it happens: The owner does not track prior transfers before trying again.
What good practice looks like
| Approach | What happens | Result |
|---|---|---|
| Transfer via Developer Portal | Owner selects 'Transfer App to Team' and confirms. | Ownership moves to the selected team. |
| Transfer with verified app | Receiving team already has a verified identity. | The app stays verified after transfer. |
| Transfer to unverified team | Receiving team lacks verified identity. | App becomes unverified, must reverify under new team. |
| Bot token and OAuth2 | Existing OAuth2 authorizations are not affected. | Bot token stays unchanged across the transfer. |
How Discord handles this
- The self-service ownership transfer flow does not apply to apps already owned by a team.
- An app's bot token does not change after an ownership transfer.
- Discord may clear the verification tied to the previous owner unless another app still depends on it.
- If the self-service option is unavailable, a user should submit a ticket to Developer Support.
Before you start
- Confirm team ownership Before starting a transfer, confirm the app is individually owned by your account.Verify: Check the Applications section of the Developer Portal.
- Confirm receiving team ownership Confirm you are the team owner of the receiving developer team.Verify: Check the Developer Portal's Teams section.
- Check account standing The account must be in good standing according to Discord's Warning System.Verify: Review the account's warning status before proceeding.
- Enable multi-factor authentication MFA must be enabled on the Discord account before beginning the transfer.Verify: Check that MFA is active in account settings.
- Check the 30-day cooldown At least 30 days must pass since the app's last completed transfer.Verify: Check the date of the last completed transfer.
Which scenario is yours?
- Is the app monetized or flagged for additional review? Monetized apps and apps requiring additional review must use Developer Support instead of self-service.
- Does the app already belong to a team? The self-service flow does not apply, and a ticket to Developer Support is needed.
- Is the receiving team's identity already verified? The app remains verified after the transfer.
- Has the app already completed 3 transfers this year? The app owner must reach out to Developer Support for further issues.
Keeping this working over time
- After transfer, the receiving team's existing roles determine what each member can view or change.
- The team owner retains owner-only permissions, including ownership-transfer decisions.
- Review who holds admin and developer roles on the team; see why not to share owner login or admin access.
If control is already lost — Reclaim a Discord Server Owned by a Former Team Member
Keeping track of who has access
You are leaving the project and want the next owner to pick it up without confusion. Keeping a clear record of ownership and roles across people and time reduces confusion after a transfer. Delvia helps teams see who holds access to their applications at a given moment. That visibility matters most when a project changes hands and the next owner needs to know what they received.
Was this helpful?