How to Migrate from Relay.app to Ceven
Relay.app is a powerful automation platform that allows you to build multi-step automations with AI steps and human approval. Ceven, on the other hand, is an AI workflow automation platform that connects to 1,000+ tools, runs end-to-end workflows on a schedule with AI steps and human-approval gates, and can build & host no-code pages/apps.
This guide will walk you through migrating your workflows from Relay.app to Ceven. Note that there is no automatic import, so you will need to rebuild your workflows and reconnect your apps. We recommend running both systems in parallel on real data and switching only once the Ceven version is proven.
Migrate from Relay.app to Ceven in 6 steps
Inventory your automations
Start by listing all the automations you have in Relay.app. Organize them by outcome rather than by the sequence of steps. This will help you identify which workflows to rebuild first and where you can consolidate steps.
Connect your apps in Ceven
Ceven connects to 1,000+ tools, so you should be able to connect the same apps you use in Relay.app. Start by connecting these apps in Ceven and setting up the necessary permissions.
Rebuild your automations
In Ceven, describe the outcomes you want to achieve, rather than recreating each step one-for-one. Use Ceven's AI steps and human-approval gates to handle tasks that were brittle or error-prone in Relay.app. This is an opportunity to streamline and improve your workflows.
Add human-approval gates on writes
For any automation that writes to a system of record, add a human-approval gate. This ensures that any issues are caught early and prevents data loss or corruption during the migration.
Validate in parallel
Run both Relay.app and Ceven in parallel on real data for a period. This allows you to validate that Ceven is working as expected and gives you time to make any necessary adjustments.
Schedule and cut over
Once you are confident that Ceven is working correctly, schedule a cutover date. Communicate this to your team and stakeholders, and make the switch. Monitor the system closely after the cutover to ensure a smooth transition.
Why teams switch from Relay.app to Ceven
Teams often switch from Relay.app to Ceven for several reasons. Ceven offers a broader range of integrations, with over 1,000 tools available out of the box. This means you can connect more of your existing tools and automate more of your workflows. Additionally, Ceven's AI steps and human-approval gates provide more flexibility and control over your automations, allowing you to handle complex workflows with ease.
Ceven also offers the ability to build and host no-code pages and apps, which can be a significant advantage for teams looking to extend their automation capabilities beyond simple workflows. This makes Ceven a more comprehensive solution for teams looking to automate complex processes and build custom applications.
What moves over and what doesn't
When migrating from Relay.app to Ceven, the workflow logic and the connected apps are the main components that need to be rebuilt. Any custom scripts or complex logic will need to be reimplemented in Ceven. Note that while the outcomes of your automations can be replicated, the specific steps and sequences may differ due to the differences in the platforms.
Data stored within Relay.app, such as logs and historical data, will not transfer over to Ceven. Make sure to export any necessary data before beginning the migration process. Additionally, any Relay.app-specific settings or configurations will need to be manually set up in Ceven.
Avoiding the common pitfalls
One of the most common pitfalls when migrating from Relay.app to Ceven is trying to replicate the old workflows one-for-one. Instead, take the opportunity to streamline and improve your workflows. Use Ceven's AI steps and human-approval gates to handle tasks that were previously error-prone or complex.
Another common issue is not validating the new system in parallel with the old one. Running both systems simultaneously on real data ensures that any issues are caught early and allows for a smoother transition. Always add human-approval gates on writes to systems of record to prevent data loss or corruption. Lastly, ensure that you have a solid plan for cutting over, including clear communication with your team and stakeholders.
Frequently asked
Can Ceven auto-import my workflows from Relay.app?
No, Ceven does not support auto-importing workflows from Relay.app. You will need to rebuild your workflows in Ceven, which usually results in fewer, more capable workflows.
How long does the migration process take?
The time it takes to migrate from Relay.app to Ceven 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.
What happens to my data during the migration?
Your data stored in Relay.app, such as logs and historical data, will not transfer over to Ceven. Make sure to export any necessary data before beginning the migration process. Additionally, any Relay.app-specific settings or configurations will need to be manually set up in Ceven.