Transfer to another account#

A transfer changes the bot's owner. The bot moves to another account as a whole — with its scenarios, contacts, conversations and connected messengers — and disappears from yours. It does not stop working in the process.

This is how, for example, a contractor hands a customer a bot they built and launched in their own account.

If you need to hand over only the scenario, without contacts, make a template with access via link from the bot.

How a transfer goes#

1. The sender creates a transfer and enters the recipient's email.
2. The recipient accepts it in their account within 7 days and chooses a project for the bot.
3. 24 hours after acceptance, the bot moves to the recipient. Until that moment the sender can cancel the transfer.

Conditions#

The conditions are checked three times: when the transfer is created, when it is accepted and before the bot changes owner. If something changed while waiting — the subscription ended, a mailing started — the transfer does not take place, and the bot stays with the sender.

Note

Two-factor authentication must be turned on not on the day of the transfer but in advance: the bot moves together with its contacts, and this way it cannot be taken even if the password is stolen. If it was turned on recently, the transfer window shows the date from which you can transfer.

What moves and what stays#

The same list is shown in the transfer window — to both the sender and the recipient.

What to pay attention to:

• Keys and payments. Payment systems, integrations and keys in blocks move as they are. Until the new owner replaces them with their own, payments through the bot go to the previous owner's accounts. Agree on the replacement in advance.
• Messenger tokens. The previous owner knows the bot tokens in the messengers. The new owner should change them after the transfer.
• Blocks that need to be reconfigured. Some blocks refer to sections of the previous owner's account — for the new owner such references are reset. How many such blocks there are is shown in the transfer window.
• Team members. The previous owner's team members lose access to the bot. Assignees in CRM deals are removed.
• Notifications about requests. The new owner sets up the notification recipients again.
• Scheduled mailings move together with the bot.
• The number of contacts. The bot's contacts are added to the new owner's contacts — the price of their plan depends on it. The recipient sees how many contacts the account will have after the transfer before accepting.

Transferring a bot#

1. In the list of bots, open the bot's "⋯" menu and choose "Transfer to another account".
2. In the "Recipient email" field, enter the email the recipient's account is registered with.
3. Check what will move to the new owner and what will stay with you.
4. Tick "I confirm that I have the right to transfer the personal data of the bot’s contacts to another owner".
5. In the "Two-factor authentication code" field, enter the code from the app or a recovery code.
6. Click "Transfer bot".

The recipient sees a notification in their account and gets an email. You get an email with the "Cancel transfer" link.

Important

Check the recipient's address. The window does not say whether an account with this email exists: if it does not, there is nobody to accept the transfer, and after 7 days it is cancelled by itself.

No more than three bots can be transferred at the same time.

If two-factor authentication is not enabled, the window shows the "Open security settings" button instead of the form.

Accepting a bot#

A transfer is announced by a notification in your account, an email and a line above the list of bots: "The chatbot … is being transferred to you by …" with the "View" link.

1. Open the "Bot transfer" page by the link from the notification or the email.
2. Check what moves to you and how many contacts the account will have.
3. In the "Project to add the bot to" field, choose one of your projects.
4. Click "Accept bot". To refuse, click "Decline".

The bot appears in the chosen project 24 hours after acceptance — the page shows the date. When the bot has moved, a notification and an email arrive.

After the transfer:

• set up notifications about requests;
• replace the previous owner's payment systems and integrations with your own;
• change the bot tokens in the messengers — for example, via BotFather in Telegram;
• invite your team members to the bot;
• check the blocks that need to be reconfigured.

Cancelling a transfer#

Until the bot has moved to the recipient, the sender can cancel the transfer:

• in your account — choose "Transfer to another account" in the bot's menu again and click "Cancel transfer";
• by the link from the email — the "Cancel transfer" button works without signing in to your account.

The email with the cancellation link comes twice: when the transfer is created and when the recipient accepts it.

Warning

If you did not start a transfer but the email arrived, cancel it by the link, change your password and check the active sessions in the security settings.

After the recipient has accepted the transfer, the bot's team members and its project cannot be changed until the transfer is completed or cancelled.

If something does not work#