How to Migrate from Dust to Ceven
Migrating from Dust to Ceven involves rebuilding your AI workflows and re-authorizing your connected tools. This guide provides a step-by-step approach to ensure a smooth transition.
Ceven offers a more comprehensive platform for AI workflow automation, including scheduling, AI steps, and human-approval gates, making it a powerful alternative to Dust.
Migrate from Dust to Ceven in 6 steps
Inventory Your Workflows
Start by documenting each of your workflows in Dust, focusing on the outcomes they achieve rather than the specific steps. This will help you understand what needs to be rebuilt in Ceven.
Connect Your Tools
In Ceven, reconnect the same tools and data sources you used in Dust. This ensures that your workflows have access to the same resources.
Rebuild for Outcomes
Instead of recreating each workflow one-for-one, design them in Ceven to achieve the same outcomes but with added flexibility. Leverage Ceven's AI steps and approval gates for better control.
Add Approval Gates
Identify critical steps in your workflows where human approval is necessary. Add these gates in Ceven to ensure that important decisions are reviewed before execution.
Validate in Parallel
Run both Dust and Ceven workflows simultaneously on real data to validate the accuracy and performance of your new workflows. This helps catch any issues before fully transitioning.
Schedule and Cut Over
Once you are confident in the Ceven workflows, schedule the final cutover. Monitor the new workflows closely to ensure a smooth transition.
Why teams switch from Dust to Ceven
Teams often switch from Dust to Ceven because of the need for more advanced automation capabilities. Ceven offers a comprehensive platform that supports scheduling, AI steps, and human-approval gates, which are essential for complex workflows.
Additionally, Ceven's ability to build and host no-code pages and apps provides a more versatile solution for teams looking to extend their automation beyond simple AI agents.
What moves over and what doesn't
When migrating from Dust to Ceven, the core functionality of your AI agents can be rebuilt, but the specific configurations and settings will need to be manually recreated. This includes reconnecting your tools and data sources.
However, any custom code or unique configurations specific to Dust will not directly transfer to Ceven. You will need to adapt these to fit within Ceven's framework.
Avoiding the common pitfalls
One common pitfall is attempting to recreate every detail of your Dust workflows in Ceven. Instead, focus on the outcomes and design workflows that achieve these goals more efficiently.
Another pitfall is not validating your workflows in parallel. Running both systems simultaneously ensures that you catch any issues before fully transitioning, minimizing downtime and errors.
Frequently asked
Can Ceven automatically import my workflows from Dust?
No, Ceven does not support automatic import from Dust. You will need to rebuild your workflows in Ceven, which often results in more streamlined and capable automations.
How do I ensure data consistency during the migration?
Run both Dust and Ceven workflows in parallel on real data to validate the accuracy and performance of your new workflows. This helps ensure data consistency during the transition.
What are the benefits of using Ceven over Dust?
Ceven offers advanced features like scheduling, AI steps, and human-approval gates, which provide more control and flexibility over your workflows. Additionally, Ceven's ability to build and host no-code pages and apps offers a more comprehensive solution.