Move to another team

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.

WhereCopy Anchor Link

Pick the destination team, read what the move costs, type the name to confirm.

Who can do itCopy Anchor Link

You need the capability in both teams:

The list only offers teams where you hold it. Owners have both by default.

What the move costsCopy Anchor Link

The dialog names every cost before you confirm. In short:

• It lands at the top level of the new team. A folder or an Environment stays behind.
• Backup schedules and cron jobs are removed. They belong to the old team. Backups already taken stay in the old team.
• It restarts once, for a second or two, on the new team's network. Nothing is rebuilt. A stopped app or database stays stopped.
• Apps and databases only reach each other inside one team. If web uses the orders database and only web moves, web stops reaching orders. The dialog names them, for example: It stops reaching orders, which stays in this team.

For an app, also:

• Shared variables of the old team are unlinked. The change applies on the next deploy.
• Per-app access is removed: people granted just this app, and API tokens limited to it.
• The git connection stays only if the new team has its own GitHub App on that account. Otherwise auto-deploy turns off until you reconnect the repository.

When it is refusedCopy Anchor Link

• The new team cannot use the server. An instance admin shares the server with that team in Settings -> Servers.
• 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 knowCopy Anchor Link

• Only the new team can hand it back. After the move, it is theirs.
• Both teams' Activity record the move, with who did it.
• The same through the API: transferAppToTeam and transferDatabaseToTeam, or the MCP tools transfer_app and transfer_database.