How to Migrate from Cassidy to Ceven
Cassidy builds AI teammates that run business workflows across your tools and deploy in Slack and Teams. It's a powerful tool for automating tasks and enhancing productivity. However, as your needs evolve, you might consider migrating to Ceven, an AI workflow automation platform that connects to 1,000+ tools, runs end-to-end workflows on a schedule with AI steps, and can build & host no-code pages/apps.
This guide walks you through the process of migrating from Cassidy to Ceven, ensuring that you can continue to automate your workflows efficiently and effectively.
Migrate from Cassidy to Ceven in 5 steps
Inventory Your Workflows
Start by listing all the workflows you have in Cassidy. Note the outcomes, not the steps. This will help you understand what you need to rebuild in Ceven. Focus on the results and the business value of each workflow.
Connect Your Apps in Ceven
Connect the same apps in Ceven that you used in Cassidy. Ceven supports a wide range of integrations, making it easy to replicate your existing connections.
Rebuild Your Workflows
Describe the outcomes of your workflows in Ceven. You don’t need to recreate them step-by-step. Instead, focus on the end results and leverage Ceven’s capabilities to achieve them more efficiently. Add AI steps and human-approval gates where Cassidy was brittle or lacked robustness.
Validate in Parallel
Run both Cassidy and Ceven in parallel on real data to ensure that Ceven is working as expected. This will help you catch any issues before fully switching over. Add human-approval gates on writes to systems of record during this phase.
Schedule the Cutover
Plan a cutover date and time. Communicate this to your team and stakeholders. Ensure that all workflows are validated and stable in Ceven before making the final switch.
Why teams switch from Cassidy to Ceven
Teams often switch from Cassidy to Ceven for enhanced flexibility and scalability. While Cassidy excels at deploying AI teammates in Slack and Teams, Ceven offers a broader range of integrations and more robust workflow management capabilities. Ceven’s ability to run end-to-end workflows on a schedule, with AI steps and human-approval gates, makes it a powerful tool for complex automation needs. Additionally, Ceven’s no-code page and app builder can further streamline your workflows and enhance your productivity.
What moves over and what doesn't
When migrating from Cassidy to Ceven, it's important to understand what will move over and what won’t. Your AI workflows, as outcomes, will move over, but you will need to rebuild them in Ceven. The actual workflow steps and settings in Cassidy do not transfer automatically. You will also need to reconnect the same apps and services in Ceven. However, the data and integrations themselves do not move over. This means you will need to set up your integrations and data connections again in Ceven.
Avoiding the common pitfalls
One of the most common pitfalls during migration is the assumption that the new platform will work exactly like the old one. Avoid this by focusing on the outcomes you want to achieve in Ceven, rather than trying to replicate Cassidy’s workflows step-by-step. Another pitfall is not validating the migration thoroughly. Running both Cassidy and Ceven in parallel on real data is crucial to ensure a smooth transition. Additionally, be mindful of the differences in how Cassidy and Ceven handle AI steps and human-approval gates. Utilize these features to enhance the robustness of your workflows in Ceven.
Frequently asked
Can Ceven auto-import my workflows from Cassidy?
No, Ceven does not support auto-importing workflows from Cassidy. You will need to rebuild your workflows in Ceven, which usually results in fewer, more capable workflows.
Will I lose any data during the migration?
No, you will not lose any data during the migration. However, you will need to reconnect your apps and services in Ceven, and your workflows will need to be rebuilt.
How long does the migration process typically take?
The duration of the migration process depends on the complexity and number of your workflows. It is recommended to allocate sufficient time for rebuilding, validating, and testing your workflows in Ceven before fully switching over.