IT platform engineer at Infosys via consign Space Solutions pvt ltd
MSP
Top 5
Jun 28, 2026
Cutover is primarily used in my organization for automation purposes, mainly through the Cutover page.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.
Associate Director - AI Initiatives at OLA Krutrim
Real User
Top 20
May 8, 2026
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.
Disaster Recovery as a Service ensures business continuity and data protection by securing business-critical operations through cloud-based disaster recovery solutions. Organizations are constantly seeking effective solutions to maintain uptime and recover quickly from disasters. Disaster Recovery as a Service offers a cloud infrastructure to back up and replicate crucial data and applications. It seamlessly integrates with existing systems, ensuring minimal downtime and stringent data...
Cutover is primarily used in my organization for automation purposes, mainly through the Cutover page.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.
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.