Moving bots between projects

If a Telegram bot belongs to the wrong project, you can move it. You do not need to disconnect it, add its token again or create a new project.

For example, a Ceramics project has four bots. Move just its support bot into Studio and leave the other three in Ceramics. The same action can move several bots or all of them.

How to move

You must own both projects. An administrator or viewer cannot move bots. Both projects must be active; sandbox and regular projects cannot be mixed.

1. Open the source project and go to Settings → Overview.
2. Click Move bots.
3. Select the bots you want, or choose “All bots”.
4. Choose the destination project.
5. Click Review transfer and read its contents and any conflicts.
6. If there are no conflicts, click Move with the selected count.
7. Wait for “Bots moved” and open the destination project.

Nothing changes before confirmation. The review shows counts for contacts, messages, resources, flows, posts, tickets and pending jobs.

What moves

Selected bots retain their IDs, settings and conversations. Their contacts, connected resources and related flows move when remaining channels do not share those connections. History is never sent to users again.

If the same verified person already exists in the destination, their chats appear under one person. Matching names or email addresses alone do not merge people. A ticket keeps its ID; its number in the destination may change.

The destination team gains access to the moved bots and conversations. A person with access only to the source loses access to the moved channel.

The selected bot keeps its notification overrides, rules and private routes. A route shared with remaining bots or project settings must be resolved first; an active delivery must finish.

What stays

The team, knowledge base, shared agent, plan, balance, catalog, purchases and shared data belong to their project. Moving a bot does not move them automatically or merge two projects. Existing destination preferences are preserved.

The source remains available even when all its bots move. Archiving is a separate action. Source files stay there; a file available only through the selected bot's Telegram cache produces a conflict.

When a connection blocks the move

A transfer is never applied partially. Review identifies the blocking connection: for example, a shared flow, active work, site, payment or a purchaser's last recovery channel in the source.

Wait for active work to finish and review again. For shared flows, resolve their use by remaining channels first. Do not delete purchases or financial records to enable a transfer: those connections need a separate business-data transfer decision.

If data changes after review, review the selection again before confirming.

If the connection drops

A lost response does not mean that the transfer failed. Open “Move bots” again in the same browser tab. The workspace checks the saved operation; if needed, click Check and continue this operation. Retrying never moves data twice.

The operation is preserved across a page reload in that tab. Wait for a definite result before choosing another selection.