An app or a database can change team. It keeps its data, its address and its connection string. The team it leaves loses access to it.
Where
| What | Where |
|---|---|
| An app | Settings -> Advanced -> Danger zone -> Transfer, or Transfer to another team in the app's menu |
| A database | Settings -> Advanced -> Danger Zone -> Transfer, or Transfer to another team in its card menu on Storage |
Pick the destination team, read what the move costs, type the name to confirm.
Who can do it
You need the capability in both teams. The list only offers teams where you hold it.
| What | Here | There |
|---|---|---|
| An app | move_apps and manage_env | move_apps |
| A database | move_databases | move_databases |
What the move costs
The dialog names every cost before you confirm:
- It lands at the top level of the new team. A folder or an Environment stays behind.
- Backup schedules and cron jobs are removed. Backups already taken stay in the old team.
- It restarts once, briefly, on the new team's network. Nothing is rebuilt, and a stopped app or database stays stopped.
- Apps and databases only reach each other inside one team. If
webuses theordersdatabase and onlywebmoves, the dialog saysIt stops reaching orders, which stays in this team.
For an app, also:
- Shared variables of the old team are unlinked, from the next deploy.
- Per-app access is removed: people granted just this app, and API tokens limited to it.
- A GitHub repository stays connected only if the new team has its own GitHub App on that account. Any other git connection belongs to the old team and is dropped. A dropped repository turns auto-deploy off until you reconnect it from the new team.
Move them together
To keep an app and its database working, move both to the same team. The order does not matter: they reach each other again as soon as both have arrived.
When it is refused
- The new team cannot use the server, or the server the app's previews run on. An instance admin shares a server with a team in Settings -> Servers.
- An app outside the new team routes one of its hostnames. A hostname belongs to one team.
- The new team already has a database with that name. Rename one of the two first.
- A database is still being created. Wait for it to finish.
Good to know
- Only the new team can hand it back. After the move, it is theirs.
- Both teams' Activity record the move, with who did it.
- Over the API:
transferAppToTeamandtransferDatabaseToTeam, or the MCP toolstransfer_appandtransfer_database.
Did this page help you?