Action
How to Transfer Discord Bot Ownership to a Team
Move a bot to a developer team without losing control of it.
Is this your situation?
Your bot lives on your personal account, and you want it shared with or moved to a developer team. You cannot find a transfer button on the application page.
The short answer
To transfer an app to a team, you must own the receiving developer team. The app must be individually owned by your account.
Before you start
- Confirm individual ownership The app must be individually owned by your account in the Applications section.Verify: Check the Applications section of the Developer Portal.
- Confirm you own the receiving team You must be the team owner of the receiving developer team.Verify: Check the Teams section of the Developer Portal.
- Check account standing The account must be in good standing according to Discord's Warning System.Verify: Review any warnings on the account.
- Enable multi-factor authentication MFA must be enabled on the account before beginning the transfer.Verify: Check security settings for MFA status.
How Discord handles this
- Being an administrator, developer, or read-only member of the receiving team is not sufficient to transfer the app.
- Monetized apps, or apps Discord identifies as requiring additional review, must use Developer Support instead of this flow.
- If the receiving team already has a verified identity, the app stays verified after transfer.
- An individual app can complete no more than 3 transfers in a rolling 365-day period.
Step by step
- Confirm individual ownership Select the individually owned bot you want to transfer in the Developer Portal.Confirm: Check the Applications section for the app under your account.
- Open General Information Go to the application's General Information section.Confirm: Check for the Transfer App to Team button.
- Start the transfer Click the Transfer App to Team button to begin the transfer.Confirm: Check that the transfer modal opens.
- Select the receiving team Within the transfer modal, select the developer team that should receive the app.Confirm: Check the modal shows your chosen team.
- Review before confirming Review the destination team, verification outcome, and transfer limits.Confirm: Check the review details shown in the modal.
- Confirm the transfer Select the team as the new owner and confirm the transfer.Confirm: Check that the Transfer to Team button disappears.
- Check the receiving team Once complete, the app appears under the receiving team on the Applications page.Confirm: Check the Applications page for the app under the team.
Before you change who is in control
- Treating team membership as ownership Being an administrator, developer, or read-only member of the receiving team is not enough to transfer the app.Why it happens: Owner-only decisions, including transferring ownership, remain restricted to the team owner.Already happened: If control has already changed hands — Recover Admin Access to a Discord Server After the Owner Disappears
- Expecting verification to carry over If the receiving team lacks a verified identity, the app becomes unverified and must complete verification again.Why it happens: If the receiving team already has a verified identity, the transferred app remains verified.Already happened: If this happened, see personal account or team ownership.
- Trying to reverse a transfer right after A completed transfer cannot be reversed through the self-service flow right away.Why it happens: A completed transfer begins a 30-day cooldown and counts toward the limit of 3 transfers in a rolling 365-day period.
Roles at a glance
| Role | Can transfer app | Can change settings | Access level |
|---|---|---|---|
| Team owner | Owner-only decisions, including transferring ownership, remain restricted to the team owner. | Retains owner-only permissions after a transfer. | Can make broader changes than developers and read-only members. |
| Administrator | Not sufficient to transfer the app to the receiving team. | Can make broader changes than developers and read-only members. | Controlled by the receiving team's member roles. |
| Developer | Not sufficient to transfer the app to the receiving team. | Not stated by Discord | Controlled by the receiving team's member roles. |
| Read-only member | Not sufficient to transfer the app to the receiving team. | Not stated by Discord | Controlled by the receiving team's member roles. |
Keeping track of who has access
After you move a bot to a team, Delvia is where you track who holds ownership and team roles. Keep a record of the transfer so access stays clear as the team changes.
Was this helpful?