How to Migrate from Dust to Ceven
Dust is a powerful platform for building custom AI agents connected to your company data and tools. Ceven, on the other hand, offers a comprehensive AI workflow automation platform that connects to over 1,000 tools, runs end-to-end workflows with AI steps and human-approval gates, and can build and host no-code pages/apps.
This guide will walk you through the process of migrating from Dust to Ceven, ensuring that your workflows are rebuilt efficiently and effectively. We'll cover the steps you need to take, what moves over and what doesn't, and how to avoid common pitfalls.
Migrate from Dust to Ceven in 6 steps
Inventory Your Workflows
Start by documenting all your Dust workflows. Focus on the outcomes they achieve rather than the specific steps. This will help you identify which workflows are critical and which can be consolidated or streamlined in Ceven.
Connect Your Apps to Ceven
Re-authorize all the third-party tools and data sources you used in Dust. Ceven supports a wide range of integrations, making it easy to connect your existing tools and data.
Rebuild Your Workflows
Instead of recreating your Dust workflows one-for-one, focus on rebuilding them in Ceven to achieve the same outcomes. Take advantage of Ceven's AI steps and human-approval gates to make your workflows more robust and flexible.
Add AI Steps and Approval Gates
Identify areas where your Dust workflows were brittle or lacked flexibility. Add AI steps and human-approval gates in Ceven to handle exceptions and ensure data quality.
Validate in Parallel
Run your Dust and Ceven workflows in parallel for a period of time. Use real data to validate that your Ceven workflows are producing the expected outcomes before making the switch.
Schedule and Cut Over
Once you're confident in your Ceven workflows, schedule a cutover date. Ensure all stakeholders are aware of the transition and provide support during the switch to address any issues that may arise.
Why teams switch from Dust to Ceven
Teams often switch from Dust to Ceven because of Ceven's broader range of features and integrations. While Dust excels at building custom AI agents, Ceven offers a more comprehensive solution for AI workflow automation, including the ability to run end-to-end workflows with AI steps and human-approval gates. Ceven also provides the capability to build and host no-code pages/apps, which can be a significant advantage for teams looking to streamline their operations.
What moves over and what doesn't
When migrating from Dust to Ceven, the primary focus is on rebuilding your AI workflows. Your custom AI agents and the logic they contain will need to be recreated in Ceven. However, the data and integrations you used in Dust will need to be re-authorized and connected in Ceven. Ceven does not support automatic import of workflows from Dust, so you'll need to manually rebuild your workflows in Ceven.
Avoiding the common pitfalls
One common pitfall is trying to recreate your Dust workflows one-for-one in Ceven. Instead, focus on the outcomes you want to achieve and rebuild your workflows to be more robust and flexible. Another pitfall is not validating your Ceven workflows in parallel with your Dust workflows. Running both systems simultaneously ensures that your Ceven workflows are producing the expected outcomes before you make the switch. Finally, ensure that you have human-approval gates in place for any workflows that write to systems of record to prevent data loss or corruption.
Frequently asked
Can Ceven automatically import my workflows from Dust?
No, Ceven does not support automatic import of workflows from Dust. You will need to manually rebuild your workflows in Ceven, which often results in fewer, more capable workflows.
How long does it typically take to migrate from Dust to Ceven?
The time it takes to migrate from Dust to Ceven depends on the complexity and number of your workflows. Generally, it can take anywhere from a few days to a few weeks to complete the migration process.
What should I do if I encounter issues during the migration?
If you encounter issues during the migration, Ceven's support team is available to assist you. Additionally, running both Dust and Ceven in parallel allows you to identify and resolve any issues before fully transitioning to Ceven.