Cutover Guided Cloud Migration Starter Package
Automation has transformed complex cloud migrations and now saves significant operational time
What is our primary use case?
In my organization, Cutover was used as a migration tool for automating many tasks that would have been executed manually, such as running a script, executing the script, and firing the commands to migrate from on-premises to AWS cloud. Cutover served as an automation tool between these processes. All tasks were integrated into the Cutover page as runbooks, and execution happened directly with just one click on the Cutover page. Everything executes automatically in the back end. That is the main use case for automation.
During migration, we used to install the agent on on-premises services. If I were to do that manually for one server, it would take approximately one to one and a half hours to install the agent on the on-premises services, which already has all the infrastructure set up. When I integrated with CMF, which is another orchestration service from AWS called Cloud Migration Factory, and integrated it with the Cutover page or Cutover runbooks, the task became completed within five minutes. It takes a little time to integrate with CMF or AWS services with Cutover, but once that integration is complete, it gets finished within five minutes. The time reduction is significant; if done manually, it would take one and a half hours, around eighty to ninety minutes. Now, that task is completed within five minutes. That is the main use case.
From my experience with Cutover for migrations, whatever inputs were fed, such as input data, it provided approximately what was expected. It shows what is happening in the back end and what output is anticipated. Cutover has great accuracy and output for artificial intelligence-related tasks.
What is most valuable?
The best feature Cutover offers, from my experience, is that any kind of task or service can be integrated to execute any kind of task.
One thing I find especially useful is the visual runbooks feature, which has a very useful user interface. I just have to click on the buttons, and a lot of tasks in the back end are executed. Many AWS cloud services, CyberArks, and cloud service providers, along with a lot of inbuilt tools in the organization, were integrated. This is the main great feature of Cutover.
Another useful feature is that Cutover can easily integrate with AWS Lambda functions, step functions, storage, and CyberArks, where credentials can be retrieved and any kind of authentication, authorization credentials, permissions, and other services can be accessed. These were integrated to enable task admins or system admins to easily fire commands and call API calls. It is very useful for calling back-end APIs specifically.
Cutover has positively impacted my organization by helping create customized runbooks for migration and has assisted with a lot of things. From a productivity perspective, I saved around seventy to eighty percent of the time where I used to do one task manually. When I used Cutover, it improved productivity by seventy to eighty percent in the migration activities.
What needs improvement?
The user interface I have used in the last twenty-one months is very good, but it could be a little more feature-rich. There are a very small number of features available in the user interface, such as user management, runbook management, and runbook creation. These are the kinds of features that could be improved with respect to the Cutover user interface. Also, regarding documentation, from what I have used online or in Google searches, I find there is limited documentation regarding how to install it locally. If a startup or small-scale organization wants to use Cutover for disaster recovery, migration, or automation, there is a lack of documentation available online. That is something that can be improved with respect to Cutover.
For how long have I used the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
Which other solutions did I evaluate?
What other advice do I have?
Cutover is the best artificial intelligence-enabled tool that can be used for automation, migration, and disaster recovery. I would really recommend others use it for runbooks, such as runbook templating and creating repetitive tasks. It will save a lot of time and increase productivity for teams. If Cutover could be made available as an open-source tool with limited users for small-scale industries or startups, it would be greatly beneficial for automation in small industries and organizations.
Regarding governance and security, while not that familiar with the governance and security perspective, I think it is very good. I believe they maintain guardrails, governance, and artificial intelligence security. As we are in the era of artificial intelligence and generative artificial intelligence, I think governance and security are being managed very well with Cutover from that perspective. My overall rating for this product is nine out of ten.
30% RTA Reduction in Our PoC — Cutover Delivers Where Manual Runbooks Fall Short
Careful migration planning has reduced manual work and compresses data center cutover timelines
What is our primary use case?
I have been using Cutover for over five years. The main use case for Cutover is shifting between tools and the data center. Cutover is a complex base which we executed for shifting between data centers. We performed a very manual process for migration and some setup for AWS workload, keeping business continuity as the priority. We created a connector between the private data center and AWS cloud, and we started shifting the workload in real time in the production environment, starting from one percent to reach 100% of the cutover, and then we shut down all the inventory or servers which were running in the AWS.
How has it helped my organization?
Cutover has positively impacted my organization by largely reducing cycle time. Cutover improved my organization's cycles by making things more efficient in terms of compressing the cutover timelines. We achieved around 30% time savings and efficiency after using Cutover.
What is most valuable?
The best feature Cutover offers is probably the guidance of the strategy. When I mention strategy, I am referring to Cutover's planning part, which includes timelines and responsibilities of POCs, logging the risk with each piece of task, and also monitoring in real time.
What needs improvement?
As of now, I believe that if an offline survey were provided, I could think of improvements for Cutover. I do not have anything regarding needed improvements or any other suggestions for Cutover at this time.
For how long have I used the solution?
I have been working in my current field for over three years.
How was the initial setup?
Cutover helped make that process smoother compared to the manual way we did it before by providing automation and predicting the impact. At the same time, we had a prediction mechanism which was very helpful.
What was our ROI?
I chose nine as my rating for Cutover because it did largely fetch all the aspects.
What other advice do I have?
I purchased Cutover through the AWS Marketplace. My advice for others looking into using Cutover is to adopt it at the initial time of the migration plan rather than putting it in at the last moment to fill the gaps. I gave Cutover a rating of 9 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Flexible and Feature-Rich Platform for Diverse Workflows
Intuitive Design and Excellent Runbook Visualization
User friendly and Streamlined Disaster Recovery Platform
We have experienced of executing seamless transition to backup env's with minimal downtime
Streamlined and collaborative project execution tool
Great user experience
.
Describe about Cutover
Collaboration and coordination
Automation and integration
Risk reduction
Cost
Integration challenges
Dependancey on runbooks
Manual error prone proccess
Faster recovery time
Better stakeholders communication
Scalability