Migrating to watsonx Assistant

This feature is currently not available in the AI assistant builder of IBM watsonx Orchestrate.

If you are using an older product instance, you might still be using the classic experience. To take advantage of the latest features, consider switching to watsonx Assistant.

You can freely switch which experience you see without losing any of your work or affecting other users of the instance.

For more information about how to switch between the classic experience and watsonx Assistant, see Switching between watsonx Assistant and the classic experience.

Consider the following questions to decide which experience you want to use:

Do you want to use actions to build a new assistant?

IBM® watsonx™ Assistant provides a simplified user interface that was designed around actions, and has an improved deployment process. If you plan to use actions to build a new assistant, use watsonx Assistant for access to the latest features and improvements.

Are you working on an existing assistant built in the classic experience?

If you have a dialog-based assistant that was built by using the classic experience, and you are not currently planning to migrate to an actions-based assistant, you might consider migrating to watsonx Assistant to take advantage of the new process for publishing and deploying your assistant. Migrating to watsonx Assistant also makes it easy for you to use actions when you are ready.

For more information about how to migrate a dialog-based assistant to watsonx Assistant, see Activating dialog and migrating skills.

Do you want to convert an existing dialog-based assistant to use actions?

If you have a dialog-based assistant, but you want to reimplement it to use actions instead, start by migrating it to watsonx Assistant. You can then use actions alongside your dialog, and you can replace your dialog nodes with actions at your own pace.

For more information about using a dialog with actions, see Calling actions from a dialog.