How to Migrate from Lorikeet to Ceven
Migrating from Lorikeet to Ceven involves rebuilding your AI customer support workflows on Ceven's platform. This guide will walk you through the process, ensuring a smooth transition.
Lorikeet resolves complex support cases by tapping into systems like Zendesk and Stripe. Ceven, on the other hand, connects to over 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.
Migrate from Lorikeet to Ceven in 6 steps
Inventory Your Workflows
Start by listing all the workflows you have in Lorikeet, focusing on the outcomes they achieve rather than the specific steps. This will help you understand what you need to rebuild in Ceven.
Connect the Same Apps in Ceven
Ceven supports a wide range of integrations, so you can connect the same apps you used in Lorikeet, such as Zendesk and Stripe. This ensures continuity in your data flow.
Rebuild Your Workflows in Ceven
Describe the outcomes you want to achieve and rebuild your workflows in Ceven. This is not a one-for-one recreation but an opportunity to streamline and enhance your processes. Use Ceven's AI steps and human-approval gates to handle complex cases more effectively.
Add AI Steps and Approval Gates
Where Lorikeet might have been brittle, add AI steps and human-approval gates in Ceven to handle exceptions and ensure accuracy. This will make your workflows more robust and reliable.
Validate in Parallel
Run both Lorikeet and Ceven in parallel on real data to ensure that the new workflows in Ceven are functioning as expected. This will give you confidence in the transition.
Schedule and Cut Over
Once you are confident in Ceven's workflows, schedule the cutover and gradually phase out Lorikeet. Ensure you have human-approval gates on writes to systems of record to catch any issues early.
Why teams switch from Lorikeet to Ceven
Teams often switch from Lorikeet to Ceven because Ceven offers a more comprehensive and flexible platform for automating workflows. While Lorikeet excels in resolving complex support cases, Ceven can handle a wider range of tasks, including scheduling, reporting, and integrating with over 1,000 tools. This makes Ceven a more versatile choice for teams looking to streamline their operations.
Additionally, Ceven's ability to run end-to-end workflows on a schedule, with AI steps and human-approval gates, provides a level of automation and control that is not available in Lorikeet. This ensures that your workflows are not only efficient but also reliable and adaptable to changing needs.
What moves over and what doesn't
When migrating from Lorikeet to Ceven, the actual workflows and automations do not move over automatically. You will need to rebuild these workflows in Ceven, which can be an opportunity to consolidate and enhance your processes. The data and integrations themselves, such as connections to Zendesk and Stripe, can be reconnected in Ceven, ensuring continuity in your data flow.
What doesn't move over is the specific configuration and steps of your workflows in Lorikeet. Ceven's platform is designed to be more flexible and powerful, so you will need to describe the outcomes you want to achieve and rebuild your workflows from scratch. This can be a bit of work, but it will give you the chance to optimize and improve your processes.
Avoiding the common pitfalls
One common pitfall is trying to recreate your workflows in Ceven exactly as they were in Lorikeet. Instead, focus on the outcomes you want to achieve and use Ceven's advanced features to streamline and enhance your processes. Another pitfall is not validating the new workflows in Ceven thoroughly before cutting over. Run both systems in parallel on real data to ensure everything is working as expected.
Finally, make sure to use human-approval gates on writes to systems of record. This will help catch any issues early and ensure that your data remains accurate and reliable. By following these best practices, you can avoid common pitfalls and ensure a smooth transition to Ceven.
Frequently asked
Can Ceven automatically import my workflows from Lorikeet?
No, Ceven does not offer an automatic import feature for workflows. You will need to rebuild your workflows on Ceven, which can be an opportunity to consolidate and enhance your processes. Usually, this results in fewer, more capable workflows.
What if I encounter issues during the migration process?
If you encounter issues, Ceven's support team is available to assist you. Additionally, running both systems in parallel on real data will help you identify and resolve any issues before fully transitioning to Ceven.
How can I ensure a smooth transition to Ceven?
To ensure a smooth transition, validate your workflows in Ceven thoroughly before cutting over. Run both systems in parallel on real data and use human-approval gates on writes to systems of record to catch any issues early. This will give you confidence in the transition and ensure that your data remains accurate and reliable.