You can use change sets to move bots between sandbox and production. Testing your bot in a sandbox and then moving it to production ensures your bot works as designed and reduces downtime.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To build and manage Einstein Bots: |
Customize Application OR Modify Metadata OR Manage Bots |
Before creating a change set, make sure your source and destination orgs have a deployment connection.
- In your source org, create an outbound change set.
- In the Change Set Components section, click Add.
- Select the Bot component type, and then select your bot name. Click Add to Change Set.
- Click View/Add Dependencies. Select the bot version you want to include, and then select Add to Change Set.
- If your bot references custom flow definitions or Apex classes, include those components.
- Upload your outbound change set.
- When the change set is available in your target org, deploy your change set. Your bot is available on the Einstein Bots setup page.
Troubleshooting:
- If you’re moving a new flow into an org where it doesn’t yet exist, you must activate the flow in the destination org before opening the bot.
- Make sure to include the bot version in the change set.
- If you’ve deleted a dialog that was attached to an intent set, you may have an isolated intent set. Learn more at Delete a Dialog with Intent Enabled.
Change Sets with Multiple Languages:
To migrate a bot with changes in multiple languages (for example, adding a secondary language to a preexisting bot)"
- Select the Language Translation component type and include the secondary language.
- Add a translation for the dialog name of each dialog.