How to Migrate from Hostinger Horizons to Ceven
Hostinger Horizons is a no-code AI builder that turns natural-language prompts into web apps with hosting, domains, and a backend included. 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, and can build and host no-code pages/apps. This guide will walk you through migrating from Hostinger Horizons to Ceven, focusing on rebuilding workflows and re-authorizing connected apps.
Please note that there is no automatic import. Migrating means rebuilding the workflows/automations on Ceven and re-authorizing the same connected apps. Always advise running both in parallel on real data and switching over only once the Ceven version is proven. Recommend human-approval gates on writes to systems of record.
Migrate from Hostinger Horizons to Ceven in 6 steps
Inventory your workflows by outcome
Start by documenting all the workflows and automations you have built in Hostinger Horizons. Focus on the outcomes and results of these workflows rather than the specific steps. This high-level view will help you understand what needs to be rebuilt in Ceven.
Connect the same apps in Ceven
Ceven connects to 1,000+ tools, so you will likely find the same apps you are using in Hostinger Horizons. Begin by connecting these apps in Ceven, ensuring that all necessary integrations are in place.
Describe the outcome to rebuild
Use the inventory you created in the first step to describe the desired outcomes in Ceven. Instead of recreating the workflows one-for-one, think about how you can achieve the same results more efficiently. Ceven allows for more complex workflows with AI steps and human-approval gates, so take advantage of these features.
Add AI steps and approval gates where needed
Identify areas in your Hostinger Horizons workflows where manual intervention was required or where the system was brittle. In Ceven, you can add AI steps to automate these areas and human-approval gates to ensure critical steps are reviewed. This will make your workflows more robust and reliable.
Validate in parallel
Run both Hostinger Horizons and Ceven in parallel, using real data to validate that the Ceven workflows are producing the expected results. This step is crucial to ensure a smooth transition and to catch any issues early on.
Schedule and cut over
Once you have validated that Ceven is working as expected, schedule the cutover. Communicate this change to your team and any stakeholders, and ensure that everyone is prepared for the transition. Use human-approval gates on writes to systems of record to minimize the risk of data loss or errors during the cutover.
Why teams switch from Hostinger Horizons to Ceven
Teams often switch from Hostinger Horizons to Ceven for several reasons. One of the primary advantages of Ceven is its ability to connect to 1,000+ tools, allowing for more integrated and comprehensive workflows. Ceven also offers advanced features like AI steps and human-approval gates, which can make workflows more robust and reliable. Additionally, Ceven can build and host no-code pages/apps, providing a more versatile platform for teams that need to create custom applications.
Another reason teams switch is the scheduling capabilities of Ceven. Ceven allows you to run end-to-end workflows on a schedule, which can be particularly useful for automated tasks that need to be performed at specific times. This feature, combined with the ability to add AI steps and approval gates, makes Ceven a powerful tool for teams looking to automate complex workflows.
What moves over and what doesn't
When migrating from Hostinger Horizons to Ceven, it's important to understand what will move over and what won't. Since there is no automatic import, you will need to rebuild your workflows and re-authorize your connected apps. This means that the specific steps and logic of your workflows in Hostinger Horizons will not automatically transfer to Ceven. However, the outcomes and results of these workflows can be replicated in Ceven, often with improved efficiency and reliability.
In terms of what moves over, any data or assets that are not tied to the specific workflows in Hostinger Horizons can be manually transferred to Ceven. This includes any custom code, scripts, or other resources that you have used in your workflows. However, the workflows themselves will need to be rebuilt from scratch in Ceven.
Avoiding the common pitfalls
One common pitfall when migrating from Hostinger Horizons to Ceven is trying to recreate the workflows one-for-one. Instead, focus on the outcomes and results of your workflows, and think about how you can achieve the same results more efficiently in Ceven. This approach will help you take full advantage of Ceven's advanced features and capabilities.
Another pitfall is not running both systems in parallel during the transition. Running both Hostinger Horizons and Ceven in parallel, using real data, will help you validate that the Ceven workflows are working as expected and catch any issues early on. This step is crucial for a smooth transition and to minimize the risk of data loss or errors. Additionally, using human-approval gates on writes to systems of record can help ensure that critical steps are reviewed and approved, further reducing the risk of errors during the cutover.
Frequently asked
Can Ceven auto-import my workflows from Hostinger Horizons?
No, Ceven does not offer an automatic import feature. You will need to rebuild your workflows and re-authorize your connected apps. However, this process often results in more efficient and reliable workflows, as you can take advantage of Ceven's advanced features and capabilities.
How long does the migration process typically take?
The duration of the migration process depends on the complexity and number of workflows you have in Hostinger Horizons. It is recommended to allocate sufficient time for rebuilding workflows, validating in parallel, and ensuring a smooth cutover. The process can take anywhere from a few weeks to a few months, depending on your specific needs and resources.
What if I encounter issues during the migration process?
If you encounter issues during the migration process, Ceven's support team is available to assist you. It is also recommended to run both Hostinger Horizons and Ceven in parallel during the transition, using real data, to validate that the Ceven workflows are working as expected and catch any issues early on. This approach will help ensure a smooth transition and minimize the risk of data loss or errors.