Migration overview
This guide provides a structured approach for migrating conversational AI solutions from watsonx Assistant to watsonx Orchestrate. It is designed for technical teams, solution owners, developers, and administrators who need to ensure a smooth transition with minimal downtime and no data loss for critical components.
The migration process covers the following components:
Actions
Dialog (Classic and New UI)
Extensions
Web chat integrations
Custom application connections
It also highlights what cannot be migrated automatically, such as environments and historical analytics, and provides strategies to address these gaps.
Why migrate?
watsonx Orchestrate offers enhanced orchestration capabilities, improved integration options, and a unified experience for managing assistants and workflows. Migrating ensures your solution remains aligned with IBM’s latest platform capabilities and roadmap.
Who should use this guide?
Customers running watsonx Assistant on IBM Cloud who want to move to watsonx Orchestrate.
Teams responsible for assistant configuration, integration management, and application connectivity.
Developers maintaining custom applications that consume watsonx Assistant APIs (v1 or v2).
What migrates and what does not
Migrates | Does NOT migrate automatically |
|---|---|
Actions (via JSON export/import) | Environments (must be recreated) |
Dialog skills (Classic and New UI) | Historical usage data |
Extensions (manual recreation) | Analytics logs |
Web chat settings and embed code (manual) | Service Desk, Phone, Webhooks (future support) |
Custom application connectivity (manual reconfiguration) |
Migration at a glance
Export and import Actions.
Migrate Dialog (Classic or New UI).
Recreate Extensions and attach credentials.
Migrate Web chat settings and embed code.
Update custom applications to point to the new Assistant (IDs, API keys).
Validate, cut over, and monitor.
Next steps
Proceed to Planning your migration to continue the process.