Move a Bot to Another Workspace
A bot can move from one workspace to another, taking its conversations, leads, uploaded files and analytics with it. The widget on the customer's website keeps working throughout, and the installed snippet does not change.
You must own both workspaces. To hand a bot to an organisation you are not part of, put it in a workspace of its own and transfer that workspace to them.
Move It#
- Open your bot, then the Admin tab.
- Select Choose a destination.
- Pick the workspace it is going to. You see only workspaces you own.
- Read the report. It lists everything blocking the move and everything that changes because of it.
- Start the move. It runs by itself and reports when it is done.
What Travels#
| Travels | Stays behind |
|---|---|
| The bot, its settings and its workflows | Conversation usage and what it cost |
| Every conversation and lead | Ledger entries and invoices |
| Uploaded files, re-encrypted for the new workspace | The ClickUp token and the WordPress secret key |
| Analytics and daily rollups | |
| The tags its leads carry | |
| Anyone who asked not to be contacted |
Switch the Integrations Back On#
If the bot sends leads to ClickUp or to an email address and the destination workspace has no connection of its own for that service, the configuration arrives switched off with its settings intact, so nobody's leads are sent somewhere the new owner did not agree to.
Check the destination, then turn them back on under Automated Lead Tracking on the bot's Lead capture tab.
Reconnect ClickUp and WordPress#
The ClickUp token saved on the bot and the bot's WordPress secret key do not move with it, because somebody in the old workspace entered or copied them. The report lists both when the bot has them. To reconnect each one:
- ClickUp. Open the gear on the ClickUp Task Creation row, paste a token from the new owner's ClickUp account, and choose a list.
- WordPress. The old key stops working when the move finishes. On the Channels tab, open the WordPress card, click Create secret key, and paste the key into the plugin. The chat on the site keeps answering visitors in the meantime; only the plugin's own screens stop until the new key is in.
Opt-Outs#
Anyone who asked the previous owner not to be contacted through this bot is copied into the destination workspace, where the request covers every bot in it. The source workspace keeps its own copy, so a move cannot undo an erasure.
What Can Block a Move#
The report names every blocker at once.
- The destination plan has no room for another bot.
- The destination plan has no connections left for the channels this bot brings.
- The destination plan does not include a channel this bot has connected, such as WhatsApp or Instagram.
- Another bot in the destination is part way through connecting the same channel.
- The bot has more workflows or knowledge documents than the destination plan allows per bot.
- The bot holds files from before stored encryption keys, which cannot be re-keyed automatically.
Fix them in any order and run the report again.
If a Move Stops Part Way#
Start it again. It finishes the job rather than repeating it, and a run that stopped leaves the bot and its files where they were.