No more typing reviews! Try our Samantha, our new voice AI agent.
Assistant Vice President at National Australia Bank
Real User
Top 20
May 4, 2026
Automation has transformed job scheduling and now saves significant time for multiple teams
Pros and Cons
  • "The main positive impact of Control-M includes time savings; we have automated many manual things that usually take six to seven hours, and now it is taking less than thirty minutes to one hour."
  • "Control-M can be improved with a dashboard that should show the job execution time, output, and execution time, including start time and end time, for at least a year, so we could monitor everything on a single dashboard, similar to what can be created on Power BI, which could be integrated with Control-M."

What is our primary use case?

My main use case for Control-M is serving as a Control-M admin user where I manage Control-M, schedule jobs in it, and maintain the execution and troubleshooting of the jobs.

A specific example of a job I schedule with Control-M includes scheduling SAP jobs, MFT jobs, FT jobs, OS jobs, and Informatica jobs. I schedule many jobs on Control-M for different asset teams.

I have automated many things that were running on Jenkins to Control-M and deployed many automation parts for the scheduling team and admin team into the Control-M domain.

What is most valuable?

The best features that Control-M offers in my experience include a very easy scheduling component, a highly interactive GUI interface, and a variety of job types that I had never seen in different tools, including competitor tools of Control-M, such as AutoSys, TWS, Tivoli, or Dollar Universe. Control-M is a very easy tool, and it is easy to learn and easy to deploy.

While the scheduling is easy and the GUI is interactive, I find that the setting of jobs and setting up a feature is very easy, and the deployment and promotion of jobs is very straightforward in Control-M.

Control-M has positively impacted my organization by helping us automate many manual things specific to the development team.

The main positive impact of Control-M includes time savings; we have automated many manual things that usually take six to seven hours, and now it is taking less than thirty minutes to one hour. We have reduced our time by almost fifty percent to eighty percent.

What needs improvement?

Control-M can be improved with a dashboard that should show the job execution time, output, and execution time, including start time and end time, for at least a year, so we could monitor everything on a single dashboard, similar to what can be created on Power BI, which could be integrated with Control-M.

While the functionality of Control-M is very easy already, there is not much to do in the feature part, but the dashboard part showing the Control-M backend could be improved.

For how long have I used the solution?

I have been using Control-M for ten years.

Buyer's Guide
Control-M
November 2026
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
921,338 professionals have used our research since 2012.

What do I think about the stability of the solution?

In my experience, Control-M is very stable.

What do I think about the scalability of the solution?

Control-M's scalability has been good, as it has met my organization's needs as we have grown; the load balancer and load scheduling are very fine.

How are customer service and support?

The customer support for Control-M is very efficient and very fast.

Which solution did I use previously and why did I switch?

Previously, we were using AutoSys, but we switched to Control-M because AutoSys is more difficult than Control-M, primarily because the GUI is very interactive in Control-M.

What was our ROI?

I have seen a return on investment from Control-M, which includes it being a money-saver and a time-saver.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing, setup cost, and licensing for Control-M has shown that compared to different scheduling tools, Control-M is definitely a cheaper option, and the licensing part is actually very convenient compared to other tools.

Which other solutions did I evaluate?

Before choosing Control-M, we evaluated other options including Dollar Universe, TWS Tivoli, and AutoSys, and then we decided to move to Control-M.

What other advice do I have?

Around one thousand users are using Control-M in my organization, with most of them coming from asset teams or different application teams, while around one hundred are from scheduling, operations, and administration.

I require about ten to fifteen staff specifically for the deployment and maintenance of Control-M, and their roles include consultant, scheduler, or administrator.

Control-M is currently used very extensively in my organization, and we do have plans to bring different asset teams onboard on Control-M, as we are helping them with ideas and features of Control-M.

The biggest lesson I have learned from using Control-M is that automation is very easy, and we can deploy almost anything into Control-M.

Integrating Control-M with technologies for my DataOps and DevOps processes has been easy, particularly with AWS and different Linux platforms.

It has not been a specific challenge to integrate Control-M with those different Linux platforms or other technologies, as Control-M already has a feature to integrate multiple types of jobs, making it easy.

My advice to others looking into using Control-M is that I would definitely suggest it because its features are very good.

I have given Control-M an overall rating of eight out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Last updated: May 4, 2026
Flag as inappropriate
PeerSpot user
Abhishek Kumar Singh - PeerSpot reviewer
Workload Automation at nab
Real User
Top 5Leaderboard
Feb 28, 2026
Automation has transformed daily job scheduling and consistently saves hours per batch run
Pros and Cons
  • "Control-M has positively impacted our organization as we have saved a lot of time and money by utilizing its features, which we found to be very convenient compared to other workload automation tools."
  • "The reporting feature has limitations with job execution, and I believe there should be integration with Power BI or any visualization tool to provide a detailed summary of each job instance on a single dashboard."

What is our primary use case?

My main use case for Control-M is scheduling jobs and maintaining the EM server and the Control-M server, along with giving support to the asset team on troubleshooting of job failures.

We typically schedule OS jobs and AFT jobs in Control-M, and we also have SAP jobs and Informatica jobs running on Control-M.

Regarding my main use cases with Control-M, we are scheduling jobs for the asset team and maintaining the architecture of Control-M.

What is most valuable?

Control-M offers several great features, with scheduling jobs being a very good feature, while the GUI feature is user-friendly and makes scheduling jobs very easy, saving a lot of time compared to other scheduling tools.

The GUI helps my team day-to-day by making job scheduling very easy, as we can use planning tabs or the back-end of the job through drag and drop, and after adding a few job details, we are ready to proceed. The monitoring tab is also very useful for monitoring daily or scheduled jobs, and the forecast feature is excellent for predicting how jobs will execute in the future.

The reporting feature serves us well for extracting reports on job executions and past executions.

Control-M has positively impacted our organization as we have saved a lot of time and money by utilizing its features, which we found to be very convenient compared to other workload automation tools.

We are saving a lot of time as earlier we had numerous manual activities that usually took four to five hours to perform, and since automating those tasks in Control-M, we now execute them within two hours, effectively saving two hours per batch execution.

What needs improvement?

The reporting feature has limitations with job execution, and I believe there should be integration with Power BI or any visualization tool to provide a detailed summary of each job instance on a single dashboard.

Control-M could have more types of jobs that could be integrated with it, but for now, the features are adequate.

For how long have I used the solution?

I have been using Control-M for the last eight years.

What do I think about the stability of the solution?

Control-M is stable in both production and non-production environments.

What do I think about the scalability of the solution?

Control-M's scalability is convenient, easy to use, and flexible with various integrations.

How are customer service and support?

The customer support for Control-M is convenient, providing us with 24/7 assistance for architecture and job execution issues.

Which solution did I use previously and why did I switch?

Previously, we were using AutoSys, but we found AutoSys not user-friendly based on feedback from the asset team, prompting us to switch to Control-M, which is better suited for our organization.

How was the initial setup?

Control-M is deployed in my organization on a private cloud.

We use AWS as our cloud provider.

What about the implementation team?

We require around five to six staff for the deployment and maintenance of Control-M, all of whom are Control-M admins assisting in deploying Control-M for various asset teams and maintaining their services.

What was our ROI?

We have seen a return on investment due to money and time saved as we automate tasks in Control-M, allowing us to reduce staff numbers as well.

What's my experience with pricing, setup cost, and licensing?

The pricing for Control-M is genuinely fair compared to other workload automation tools in the market, and its features add value, making us satisfied with its pricing structure.

Which other solutions did I evaluate?

We evaluated AutoSys before choosing Control-M as our solution.

What other advice do I have?

The biggest lesson I have learned from using Control-M is that automation is very convenient, with workload automation and job scheduling being easy and maintaining jobs in Control-M being very manageable.

My advice for others considering Control-M is that it is definitely a reliable option since it is convenient, flexible, and stable.

Control-M is extensively used as we have deployed it for many asset teams, and we plan to increase its usage as we are in discussions with different teams to migrate their manual activities into Control-M.

I would rate this review as a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Feb 28, 2026
Flag as inappropriate
PeerSpot user
Buyer's Guide
Control-M
November 2026
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
921,338 professionals have used our research since 2012.
Professional Application Designer at DXC Technology
Real User
Top 20
Jan 28, 2026
Automation has reduced manual jobs and now supports high-volume 24x7 operations efficiently
Pros and Cons
  • "Instead of managing this manually, I have automated everything related to job scheduling and job configuration."
  • "To make the solution a 10, there could be more automation."

What is our primary use case?

My use case with Control-M is for job automation and job scheduling. Instead of making 10 different technologies where we need to run jobs, automation allows us to reduce the number of people needed. Cost-cutting is significant; instead of 10 people, we can handle the work with only one or two people.

What is most valuable?

The best features in Control-M that I like the most are job scheduling and monitoring.

Earlier, I worked for many clients, and currently I am working for Zurich, Japan. There, we used different vendors such as Infosys, Cognizant, DXC Technologies, and two others. The project operates 24/7 as an insurance project where transactions happen during daytime, so we need to run jobs during nighttime as well to upload data, take backups, and complete other necessary tasks. Instead of managing this manually, I have automated everything related to job scheduling and job configuration.

What needs improvement?

The areas that have room for improvement are the GUI to make it more user-friendly. The interface is very easy, very good, and secure. Currently, I have not found any significant improvements needed. Every year the versions improve, and everything is progressing well.

For how long have I used the solution?

I have been working with Control-M for almost 16 years.

What do I think about the stability of the solution?

Control-M is a stable product, and I would rate it 10 as a stable product.

What do I think about the scalability of the solution?

The scalability is an eight out of 10. It is easy to upscale or downscale.

How are customer service and support?

I can give the technical support a nine out of 10.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

With Control-M, I compare the solution with other solutions I have worked on such as TWS (Tivoli Workload Scheduler), CA7, AutoSys, Tivoli DC (Tivoli Workload Dynamic Schedule), and Job Scheduling Console. I find that Control-M is more secure compared with the firewall system.

How was the initial setup?

Deployment is very easy with no issues.

What about the implementation team?

For the clients, they have to buy licenses, which are reasonable.

What was our ROI?

With Control-M, I would recommend implementing this product. It is a more secure solution.

What's my experience with pricing, setup cost, and licensing?

The solution requires easy maintenance because most of the time we take care of it on weekends like Saturday and Sunday, or during public holidays.

Which other solutions did I evaluate?

There is nothing difficult about integration. It is very easy to integrate technologies for data ops and DevOps processes.

What other advice do I have?

Currently, I am taking care of almost 10,000 jobs in an insurance company.

I would assess the BMC service team for helping map out migration as effective. For migrations, we perform them in development first. We configure the jobs in development, then move to SAT testing, UAT testing, and ST testing, and then to pre-production and production. If there are more jobs, we do migrations on weekends, on Saturday and Sunday, or at midnight one day before.

Deployment takes approximately one or two days and depends on the job types. Installing Control-M can take up to one or two days maximum. For scheduling, we need to configure different agents in different vendor systems such as UNIX systems, Informatica systems, or Tandem systems. For these configurations, we need to install the agents and define them in Control-M.

To make the solution a 10, there could be more automation. I would rate this review overall as a 9.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
AbhisekChoudhury - PeerSpot reviewer
Senior Operations Analyst - II at National Australia Bank
Real User
Top 10
Jan 23, 2026
Automation has streamlined massive file transfers and scheduling and now saves critical processing time
Pros and Cons
  • "Control-M has positively impacted my organization greatly as we are running more than 5,000 jobs, including around 5,000 MFT jobs that transfer files from SharePoint to another server or between servers, helping us automate manual processes and reduce timeframes."
  • "I believe Control-M can be improved as there is news about shutting down its GUI; I believe the GUI is more impactful than the web version, so continuing to use the GUI would be more useful."

What is our primary use case?

My main use case for Control-M is scheduling jobs, monitoring the jobs, and monitoring application scripts that are working fine or not through Control-M, along with doing some automation. File transfer is the core focus of my main use case, while we have some other SAP jobs that trigger the job at a certain time frame from a SAP point of view.

What is most valuable?

The best features Control-M offers are ease of use, with everything very clear, including the agent-less scenarios, the Control-M Configuration Manager which provides a detailed view, and a very user-friendly scheduling system.

Ease of use in Control-M means we have everything on the GUI, so we do not have to jump to different locations to find out the issue or problem; we can find everything on a single screen and for scheduling, it has all the options needed, you just need to know the basics to figure out anything you want to do.

Control-M has positively impacted my organization greatly as we are running more than 5,000 jobs, including around 5,000 MFT jobs that transfer files from SharePoint to another server or between servers, helping us automate manual processes and reduce timeframes. Previously, while doing file transfers, we had to check for at least a two-hour timeline, but now through Control-M, we do it automatically with no manual intervention, reducing it to 45 minutes.

What needs improvement?

I believe Control-M can be improved as there is news about shutting down its GUI; I believe the GUI is more impactful than the web version, so continuing to use the GUI would be more useful. In addition to the GUI changes, introducing more types of jobs, such as for cloud usage, would be more helpful and versatile.

For how long have I used the solution?

I have been using Control-M for more than six years now.

What do I think about the stability of the solution?

Control-M is stable.

What do I think about the scalability of the solution?

Control-M's scalability is good; it was a very easy process and did not require much work.

How are customer service and support?

The customer support for Control-M is great.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Previously, we used Cisco Tidal but switched to Control-M due to limitations with Tidal, such as agent-less scenarios not working properly and missing functionalities.

What about the implementation team?

We have two teams using Control-M: L1, which monitors job failures and takes requests from application teams to run certain jobs, and L2, which is responsible for scheduling jobs and configuring agents from Control-M, along with L3, which creates the environments.

We require an L3 team of three people for deployment and maintenance; they mainly take care of deployments and maintenance without taking much time due to the guidelines provided by BMC, with roles including SMEs and Control-M administration experts.

What was our ROI?

I have seen a return on investment, as the MFT jobs reduce the time frame from two hours to 45 minutes, allowing us to utilize that time for other platforms, technologies, or automation processes.

What's my experience with pricing, setup cost, and licensing?

My experience with pricing, setup cost, and licensing of Control-M is that it is very minimal and optimal, making the cost good.

What other advice do I have?

My advice to others looking into using Control-M is to go for it without any hesitation or questions, as you will not regret it due to the many options for automation and the time frame reduction along with reduced manual efforts. I would rate this review at 9 out of 10.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
Senior Associate at a consultancy with 10,001+ employees
Real User
Top 5
Jan 20, 2026
Workflow orchestration has boosted productivity while DevOps integration still needs simplification
Pros and Cons
  • "I can say around twenty to twenty-five percent productivity increase has been realized, and even the margins have been increased, and I can see at least fifteen to twenty percent of the company's revenue has been increased at the infrastructure level by using Control-M."
  • "In Control-M, the area that needs improvement is related to the cost. I have checked with other customers, and the licensing cost is somewhat heavy compared to other competitors."

What is our primary use case?

I have multiple use cases in Control-M. I have used MFT, SAP R/3, SAP BW, the File Watcher, the Informatica module, and OS scripts. I have used almost most of the modules in Control-M.

I have worked with multiple companies over the past eight years. In one of the companies, we are the partner, and in one of the companies, currently we are the customer for Control-M.

What is most valuable?

In Control-M, what I appreciate the most is the visualization and the orchestration it provides to us. I have used other scheduling tools also, such as Autosys and cron jobs. Control-M has multiple features, including one in the MFT where we can perform seamless file transfer. I have not seen this kind of file transfer without a script, with just the help of a GUI. We can perform the file transfer with multiple domains, multiple platforms, and multiple servers. I feel this is excellent. We can even integrate Control-M to ServiceNow, where it is a ticketing partner. If the job fails, it will directly create incidents, P2, P1, and so on. The integration is seamless. I really appreciate these features in Control-M.

Year on year, I am seeing upgradations from Control-M. Earlier when I started my career, I was using Control-M version 7. The GUI was adequate. However, now every year, they have upgraded their tool. They have even released the web version of Control-M with browse-only access for others. I am purely the scheduler and administrator of Control-M. Control-M is my day-to-day activity. I go to clients to gather business requirements and pitch how we can integrate Control-M into their processes. I can see that Control-M is performing well. We have seen many new features. Recently, they have integrated AWS where we are performing file transfer directly from AWS S3 to other partners. I feel this is a good tool, and they are evolving. They are enabling us to evolve better as well.

I can say around twenty to twenty-five percent productivity increase has been realized, and even the margins have been increased. The resources have also been reduced with the integration of Control-M to other ticketing tools and other systems. I can see at least fifteen to twenty percent of the company's revenue has been increased at the infrastructure level by using Control-M.

What needs improvement?

With DevOps, I feel it is somewhat challenging. We have to use Control-M APIs. I do not see a simple drag and drop interface, similar to what we use for Control-M job creation. It is not that straightforward when we have to integrate with other APIs such as Git and other partners for DevOps, Snowflake, and all. I do not see it is that easy, but we can integrate. We need an API that is more user-friendly. I suggest that BMC provides plug-and-play APIs so that we can integrate with multiple applications.

In Control-M, the area that needs improvement is related to the cost. I have checked with other customers, and the licensing cost is somewhat heavy compared to other competitors. A few of the customers are transitioning away from Control-M because those tools are not yet as sophisticated. However, due to the cost and purchasing structure in their businesses, they are moving towards other tools. I recommend BMC to reduce the licensing cost. That is one of the major drawbacks of BMC. Regarding maintenance, I have heard that in the SaaS model, they are only performing administrative functions. However, the current three-layer architecture of BMC is somewhat complex. For beginners, they will not understand the Enterprise Manager, the Control-M servers, and the Control-M agent points. If BMC integrates Control-M EM and the servers in one part of the architecture, it will be helpful. It will make it easier for everyone to use Control-M.

For how long have I used the solution?

I have been using Control-M for the past eight to nine years.

What do I think about the stability of the solution?

I can rate the stability an eight. I do not see many unstable issues. I can say it is most of the time stable. If it is unstable, it is because of our Control-M server issue, not the BMC issue. Due to the high CPU utilization of our servers or any kind of network issues within our internal on-premises servers, it will go down. However, I do not see any issues from BMC.

What do I think about the scalability of the solution?

I can rate the scalability one hundred percent. It is a scalable solution. However, at the end of the day, it is a matter of licensing cost, whatever we are paying to BMC. They are charging upwards of fifty dollars per job or twenty-nine thousand dollars per year. It is a scalable solution.

How are customer service and support?

My impressions of BMC as a strategic partner or a trusted advisor are positive. They are prompt in providing solutions. Whenever we have a P1 or P2 incident raised to BMC, they will mostly resolve it within the ETA. A few things they still need to upgrade. They will send those queries to their R&D, and they will get back to us. However, overall, with the licensing or with customer interaction or those kinds of things, we can trust them for a few more years.

I can rate the technical support a seven. I rate it a seven because a few of the technical staff who attend to our queries do not have the knowledge about major issues. If there is any major impact or major issue, they will also not know about it. They will say they will check with R&D and they will get back. The ETA will be somewhat high for P2s and P3s. Only for P1s, they will come on the call and they will try to resolve. I cannot say they are the worst or the best. They are adequate.

How would you rate customer service and support?

Positive

What other advice do I have?

I one hundred percent recommend Control-M to our customers, the clients, and the multiple companies I have worked with. I will recommend BMC as an advanced scheduling tool for orchestration. There are areas of improvements for BMC as well. As the trend is going towards AI now, I have heard they are working on it, but we have not seen that in our versions of Control-M. However, as the trend is going towards more AI and generative AI, if they release anything related to AI in Control-M, such as a chatbot or something where if a job fails, a chatbot can tell how it has failed, that would be beneficial. We are spending half an hour to one hour to find the root cause of how a Control-M job has failed. If they do something about it, that would help significantly. We have multiple AI solutions coming up. If we can schedule those AI solutions through Control-M as well, it will be at par with the industry standards now. Otherwise, it will become legacy. I recommend this to all my customers because I feel this is one of the best advanced scheduling tools I have used. I can see very few competitors to Control-M as of now.

The solution was a partner purchase from one of the clients I am working for. They have purchased it. We also have an AWS module they have purchased from BMC.

The deployment has presented challenges a few times due to the compatibility issues of Control-M software with the other servers. It might be due to the Java version or some glitch in the patches we are receiving from BMC. A few times it is challenging. It is not straightforward. We need experienced resources or a proper administrator to redeploy this kind of thing.

My current relationship with BMC is both transformative and transactional. I am involved in both the licensing and technology upgrades. Recently, I have attended one of their roadshow events in Bengaluru. We are constantly in touch with the BMC customer. They have one dedicated customer support manager for our team. We will be in touch with them for any of the features or any cost or anything related to renewal of the licenses and everything.

My organization has more than one hundred employees. In only one office, it is one hundred. If I consider my overall company who are using Control-M, it is around one thousand plus employees using Control-M.

I have provided this review with an overall rating of seven.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Ramalakshmana Padala - PeerSpot reviewer
Senior Technical Consultant at a financial services firm with 10,001+ employees
Real User
Top 5
Aug 25, 2026
Automation has transformed banking batch operations and supports reliable daily payment processing
Pros and Cons
  • "Control-M is the best tool in the world where users can easily learn and implement it in their organization."

    What is our primary use case?

    My main use case for Control-M involves job scheduling and managing batch scripts.

    As we work under a bank, I use Control-M for payment processing, loan processing, and credit card processing, where all banking processing is done through batch scheduling, and those schedules run in Control-M.

    The main business use cases or services supported by Control-M include payroll, supply chain, and financing.

    What is most valuable?

    The best features Control-M offers include being easy to learn and easily managed, especially as we are running around 500,000 jobs per day, which is easily managed by fewer people with fully automated controls through automatic alerting on job events.

    Control-M is a powerful tool where we can automate everything end-to-end by running all scripts such as JavaScript, .NET scripts, or Python on shell scripts, and even the mainframe jobs are scheduled through Control-M for day-to-day banking processes and functionalities.

    The current new feature that stands out for me is using the Control-M dashboard instead of depending on third-party monitoring tools such as Splunk, which makes it easy to see job status, job counts, and view job flows all in the new dashboard.

    Control-M has positively impacted my organization as it has been in use for the past 20 years, providing substantial help for our day-to-day banking operations.

    What needs improvement?

    At present, I do not find anything that can be improved in Control-M, as BMC Software is doing a good job in enhancing new features and integrating AI, machine learning, and proactive alerting.

    For how long have I used the solution?

    I have been working in my current field for 19 years.

    What do I think about the stability of the solution?

    Control-M is stable.

    What do I think about the scalability of the solution?

    Control-M's scalability is excellent.

    How are customer service and support?

    The customer support for Control-M is excellent.

    Which solution did I use previously and why did I switch?

    I did not previously use a different solution.

    How was the initial setup?

    Based on change management, my deployment of Control-M took around 15 days to implement the change, while the installation and upgrade was completed in one day.

    What about the implementation team?

    Five people are managing all the administration tasks for Control-M.

    What was our ROI?

    Since using Control-M, I have noticed a return on investment through error reduction, as manual efforts have been reduced due to job automation and other tasks, which improves the stability and robust performance of our applications, enabling quick payment processing or file transfer functionalities within a limited time interval while providing customers a robust application.

    I am not certain about the return on investment metrics such as fewer employees needed, money saved, or time saved, as that is handled by the leadership team.

    What's my experience with pricing, setup cost, and licensing?

    I am not aware of the pricing, setup cost, and licensing as that is handled by my leadership team.

    Which other solutions did I evaluate?

    I did not evaluate other options before choosing Control-M.

    What other advice do I have?

    Control-M is the best tool in the world, and I would rate it a 10 on a scale of 1 to 10.

    Control-M is essential for day-to-day operations, as we are highly dependent on batch processing for all our banking operations.

    Control-M provides 100% accuracy in batch job scheduling and includes built-in features for high availability, eliminating dependence on OS-level HA, ensuring stability and 100% availability for users for batch processing.

    Regarding Control-M's AI capabilities, governance and security are managed in-house, so the security lies within the organization and not with external vendors or sources.

    I would tell someone considering Control-M that it is the best tool in the world, where users can easily learn and implement it in their organization with its end-to-end features.

    My overall rating for this review is 10.

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Last updated: Aug 25, 2026
    Flag as inappropriate
    PeerSpot user
    Senior Retail Tester Engineer at a outsourcing company with 1,001-5,000 employees
    Real User
    Top 20
    Nov 4, 2026
    Centralized job monitoring has improved data pipeline reliability and supports timely ETL delivery
    Pros and Cons
    • "Control-M has helped improve my organization's efficiency by making ETL job monitoring and failure identification easier."
    • "I would rate customer support as 4 out of 10 based on my support experience."

    What is our primary use case?

    The main use case for Control-M in my daily work is to monitor scheduled ETL batch jobs and check whether they have completed successfully. For example, if a data load job fails or gets delayed, I check the job status and error details, coordinate with the support team to resolve the issue, and verify that the job completes successfully after the rerun. This helps ensure data is available on time for validation and reduces manual monitoring.

    I want to add a few use cases for Control-M in my day-to-day work. Apart from monitoring ETL jobs, I use Control-M to check job dependencies, track scheduled executions, and identify failures or delays. For example, I verify that source jobs are completed before target jobs start, and I follow up with the support team if the job fails. It helps improve coordination between different teams, reduces manual effort, and ensures data loads are completely reliable and on time.

    Regarding cloud management, I use Control-M to coordinate and sequence data processing jobs across different platforms. It helps manage job dependencies, schedule workflows, and monitor execution status from a centralized view. For example, a source execution job must complete successfully before the ETL transmission and target loading jobs begin. If a job fails or is delayed, I check the status and error details, coordinate with the support team, and verify successful completion after the issue is resolved. This helps maintain the correct processing sequence and improves the reliability of data pipelines.

    To my knowledge, my current use of Control-M is primarily focused on ETL job scheduling, data pipeline monitoring, and data processing.

    How has it helped my organization?

    Control-M has helped improve my organization's efficiency by making ETL job monitoring and failure identification easier. For example, when a scheduled job fails or gets delayed, I can identify the issue quickly, coordinate with the support team, and track the job until it completes successfully. It also helps improve teamwork because everyone has better visibility into job status and dependencies. This reduces manual monitoring, helps prevent delays in downstream data validation, and improves the reliability of my data processing workflows.

    I have noticed practical improvements in day-to-day operations. For example, Control-M helps us identify failed ETL jobs more quickly, reducing the time spent on manual checks. It also makes it easier to track job dependencies and coordinate with the support team when issues occur. This helps us resolve problems faster, minimize delays in downstream data validation, and improve the reliability of the data loads.

    What is most valuable?

    There are many special features in Control-M. The features that stand out most to me are Control-M's job monitoring, automated scheduling, dependency management, and failure notifications. I rely most on job monitoring because it helps me quickly identify failed or delayed ETL jobs. For example, I can check a failed job's status and error details and coordinate with the support team to resolve the issue. Dependency management also helps ensure that source jobs finish before downstream target jobs begin. These features reduce manual monitoring, improve communication between teams, and help ensure data processing is completed on time.

    An additional feature I use in Control-M is the visibility it provides into the overall workflow and job dependencies. It helps us identify if a process has failed and understand when downstream jobs might be affected. For example, if a source job fails, I can identify dependent jobs early. I think more people should know how this visibility can help with proactive troubleshooting, better team coordination, and reducing delays in data processing.

    From my perspective, secure job execution is an important aspect of Control-M. Role-based access helps ensure that users have permissions appropriate to their responsibilities. For example, some users may only monitor job status, while other authorized support teams can manage or rerun the jobs. Audit logs are also useful for tracking job activities and supporting compliance requirements. Overall, I emphasize the importance of proper access permissions and auditability, while ensuring that sensitive data and credentials are handled securely.

    However, AI-assisted analysis can be useful for identifying potential job failures, highlighting patterns, and speeding up troubleshooting. I would still validate the recommendations against the job logs and actual execution results before taking action. I think greater accuracy in root cause analysis and more actionable recommendations could make the capabilities even more valuable for ETL monitoring and support.

    The most effective Control-M functionalities for my workflow are centralized job monitoring, scheduling, dependency management, and failure notifications. These help coordinate traditional batch processing and ensure jobs run in the correct sequence. For example, source data extraction must finish successfully before transformations and target loading jobs begin. If the source job fails, I can identify the issue, coordinate with the support team, and verify the downstream processing after the job is rerun.

    One area that can require adaptation is integrating jobs running on different platforms, particularly when they have different authorization methods, scheduling requirements, or error-handling mechanisms. Another challenge is troubleshooting failures across multiple systems where the root cause may not be immediately clear. Better error details, consistent logging, and clear dependency visibility could make the workflow easier. Overall, Control-M provides a centralized view for monitoring workflows, but successful migrations still depend on proper configuration, testing, and coordination between different teams.

    Audit trails and regulatory compliance are important considerations in my data processing workflows. Control-M's job execution history and activity tracking can help me understand when jobs run, whether they are successful or fail, and support troubleshooting and audit reviews.

    What needs improvement?

    Control-M could be improved by making troubleshooting easier by providing root cause information when a job fails. For example, it would be helpful to have more actionable suggestions for resolving common ETL job failures. Another improvement would be more customizable real-time notifications and dashboards, so teams can quickly identify critical failures and prioritize them. These enhancements could reduce troubleshooting time, improve communication between teams, and make daily monitoring more efficient.

    Apart from what I have mentioned, everything is good with Control-M.

    For how long have I used the solution?

    I have been using Control-M for the past six years and eight months, mainly for monitoring ETL jobs, checking job execution status, and identifying failures or delays. I use it to help ensure data processing workflows complete successfully and to coordinate with the support team when issues occur.

    What do I think about the stability of the solution?

    In my experience, Control-M is generally reliable for monitoring and scheduling ETL jobs. However, job failures or delays sometimes occur because of downstream systems.

    Overall, Control-M has been reliable for my daily ETL job monitoring and scheduling. When an issue occurs, the job status and execution history help me investigate and coordinate with the support team.

    How are customer service and support?

    Overall, my experience with Control-M has been positive. It makes monitoring ETL jobs, tracking execution status, and identifying failures easier. For example, when a job schedule fails, I can quickly identify the issues and coordinate with the support team. I would rate customer support as 4 out of 10 based on my support experience.

    What was our ROI?

    I do not have any exact figures for time or money saved, but Control-M helps reduce manual effort through automated scheduling and centralized job monitoring.

    Which other solutions did I evaluate?

    I am aware that solutions such as AutoSys, IBM Workload Automation, and Apache Airflow can also be used for workflow scheduling.

    What other advice do I have?

    On a scale of 1 to 10, I will rate Control-M an 8 out of 10. It is a useful tool for automating job scheduling, monitoring ETL workflows, managing job dependencies, and identifying failures. It improves operational efficiency and helps teams coordinate more efficiently when issues occur. I have not given it a 10 because there is still room for improvement in error analysis, root cause identification, and customizable alerts. Overall, it is a reliable tool that makes daily batch monitoring and support activities easier.

    Control-M can be deployed in a public cloud, where it runs in environments such as AWS or Azure. In a private cloud, it runs on a dedicated cloud environment for an organization. Hybrid workloads run across both cloud and on-premises infrastructure. On-premises means Control-M runs on an organization's own servers and data center. In my project, they use AWS and Microsoft Azure.

    I would give good advice to everyone. It has great facilities and efficiency. I would suggest Control-M to everyone.

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Nov 4, 2026
    Flag as inappropriate
    PeerSpot user
    Sre Engineer at Devoteam Management Consulting
    Real User
    Top 20
    Sep 2, 2026
    Centralized job control has saved time and now manages complex batch workflows across servers
    Pros and Cons
    • "Control-M has positively impacted my organization by saving time."
    • "The graphical interface of Control-M, although useful, needs some improvements."

    What is our primary use case?

    My main use case for Control-M is for control jobs on Linux machines. We have some shells, and I automate shell scripts on Linux machines. Control-M works similarly to a graphical crontab.

    For example, I have some scripts that I must process on batches for clients. These batches have a time-specific moment when they can be used. For example, we receive a text file and must upload it to a mainframe using a shell script to automate this process. Control-M executes this task at the specific time and works fine. I check it every day and provide reports to the customer and developers with information in emails to detect whether the job is successful or not.

    What is most valuable?

    Control-M is a good tool for managing a large number of jobs across a large number of machines. Another very important feature is cyclic jobs. For example, I have the first job, and then I have two, three, or four jobs that must run after this, and I can make these dependencies as well. It is easy to change the schedule, and this feature is very useful in Control-M. The graphical interface makes things easy.

    The cyclical jobs are a good feature that I see, along with the ease of implementation. It is very easy to put a job to run, suspend a job, or hold the job. The management is very useful and fantastic. I believe this is the main feature of Control-M that administrators decided to use it. In any project that I work on as a projectist or architect, I would suggest the use of Control-M in larger environments as well.

    Control-M has positively impacted my organization by saving time. It makes administration tasks easy. I have very accurate information in emails, and every time a job runs, the outputs are classified by time, which makes things easy as well. It is very good. I work in an environment where I have around 300 servers all working together with Control-M on my IUA. It would be quite impossible to manage all these jobs and this entire server park without this tool. The time saving is very impressive.

    What needs improvement?

    The graphical interface of Control-M, although useful, needs some improvements. It is quite old.

    The boxes in the graphical interface could be changed to get a better view. It is not useful for using on small screens. A larger screen is needed to see properly a large number of smart jobs or jobs on the screen. This organization should be improved in my view.

    For how long have I used the solution?

    In my current field, I have worked for one year, but I have worked with Control-M for more than 10 years.

    What do I think about the scalability of the solution?

    Control-M's scalability is easy because we have several servers in use, and it is quite easy to add new servers and put them under our management as well.

    How are customer service and support?

    Customer support for Control-M is nice. Because the solution is stable, there are few situations that require activating support, but the team provides good responses and support every time we need a solution.

    Which solution did I use previously and why did I switch?

    The solution was already implemented when I started, so I did not compare it to other solutions. I am not an architect in order to decide for another solution. The solution was already implemented, and I use it to manage my servers.

    What was our ROI?

    The company saved money and time and has good results with the use of this tool. We have a portal named MyCloud, and in this portal, we have the cost of each solution that I worked on. It has a cost, but it has a good benefit.

    What other advice do I have?

    The versions of Control-M that I have worked with do not have AI features, so I do not have any information about this, but in my vision, I think some tasks can be implemented through an AI agent. Some aspects of security should be required in this case.

    I use Amazon Web Services as the cloud provider for those servers.

    On my site, in my team, we use Control-M to manage around 300 servers. Increasing usage is directly proportional to the use of servers. If we implement more servers, they will have Control-M to manage the jobs. At this moment, we have a project that is stable, and we have no plans to increase it, but it is possible at any time.

    The biggest lesson that I have learned is that Control-M is useful to save time and manage extensively a structure with one console.

    At this moment, I believe that is all I have to say. The service is quite extensive, and there is a lot of information that might be useful. My overall review rating for Control-M is nine out of ten.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Sep 2, 2026
    Flag as inappropriate
    PeerSpot user
    reviewer2914152 - PeerSpot reviewer
    Business Systems Analyst at a outsourcing company with 1,001-5,000 employees
    Real User
    Top 20
    Oct 21, 2026
    Workflow orchestration has become consistent and simple for managing diverse enterprise tasks
    Pros and Cons
    • "The beauty of Control-M is that I don't have to think about managing integration and sequencing of data processing across diverse data platforms and cloud environments."
    • "The methods for transitioning workflows from the old environment to the new have not been mature or well developed, which has posed challenges, requiring discussions with BMC to find the best path forward."

    What is our primary use case?

    My main use cases for Control-M are managing file transfers and running the database management programs for the enterprise.

    When I mention connections in terms of Control-M, I'm thinking of connecting to databases to run database queries and updates, connecting to file transfer facilities to move files across the organization, and communicating with API environments using the API interface. Those are the sorts of capabilities I'm referring to.

    We haven't actually started down the path of using Control-M to support AI or ML workloads yet. Currently, I'm working on a project to upgrade and migrate our on-premises Control-M to the cloud, specifically to SaaS Control-M. The next step after this migration would be to begin integrating AI capabilities into our workflows, but that journey hasn't started yet as we need to get internal approval and review the AI offerings from BMC first. Right now, my focus is on transitioning to the SaaS platform instead of jumping straight into AI integration.

    So far, the thinking around how to use AI integrations with Control-M is not advanced. Initially, I consider utilizing AI's facilities and capabilities to help with day-to-day management of the environment. For example, a simple use case could be using AI to reduce call-outs to on-call staff because the tool will provide guidance for the 24/7 staff on how to investigate a problem or rectify issues. The capability of AI could help with triage and sorting out problems before the need to call someone to fix it, addressing the tendency of 24/7 teams to only react to failures without engaging in investigation.

    At this stage, we don't use Control-M to facilitate integration of Kubernetes or cloud-native workflows with traditional batch processing. My main focus remains on file transfer activity and simple interfaces to run batch processes for managing database updates, data extracts, and reporting.

    From my perspective, my role doesn't involve corporate compliance and auditing, but I utilize Control-M to monitor its use through audit reports and logging. I ensure I capture and retain that information for historical purposes over several years so that if there's a need to review events from six months ago, that data is available. However, I'm not involved in corporate-wide auditing and compliance aspects.

    How has it helped my organization?

    I can't provide metrics from using Control-M because I've only been with this particular organization for five years, but the biggest benefit is that it allows workflow orchestration to be done in a cost-effective manner, without the need for complex solutions or customized proprietary solutions to keep track of things or run the workflow. Control-M does that for me, and as it's a consistent interface, it allows me to deploy many different applications and tasks in one place while providing an opportunity for the business to have an easy, quick interface to determine where the workflow has progressed.

    What is most valuable?

    In my opinion, the most valuable features of Control-M are the GUI interface, which provides the facility for other parties to use the tool without a huge learning curve, as well as a very good intuitive view of my workflow that allows me to find issues and rectify them in a timely manner. With the new features, such as AI coming along, it's going to be even more exciting. I find that another aspect is the capability of the tool to connect to many different environments and be platform agnostic, so I don't have to worry about operating systems or what I'm connecting to, thanks to the built-in plug-in control modules.

    From my perspective, the beauty of Control-M is that I don't have to think about managing integration and sequencing of data processing across diverse data platforms and cloud environments. I simply have the interface, and I define the workflow to communicate with those environments using the tool's capabilities that provide that connectivity. Therefore, I'm not too concerned about the specifics of what I'm trying to achieve in the backend, as the tool facilitates that without needing to know the target tool or environment.

    What needs improvement?

    I am currently migrating to SaaS Control-M, which is BMC's software-as-a-service, and this represents an improvement because it eliminates the need to manage the platform and keep it up-to-date. However, some aspects of the new interface could be improved, which are relatively minor issues. For example, I have four environments in my SaaS Control-M setup, and there isn't an easy way to tag those environments to quickly identify which one I'm in without doing checks. I believe there should be a mechanism to allow customization of the display, whether through color or a title, to clarify my location within the environments.

    For how long have I used the solution?

    I've personally been using Control-M for over 30 years, and in my current role, I've been using it since I started with my current organization, which has been about four or five years now.

    What do I think about the stability of the solution?

    I can't fault the stability and reliability of Control-M. With 30 years of experience using the tool, I've encountered maybe one to three disasters due to product faults, with the first occurring decades ago and another about 15 years ago. Such failures are rare, and when they do happen, recovery is usually straightforward. I've never faced a situation where a Control-M database became corrupt and unrecoverable; typically, proper environment management with backup ensures a swift restoration process.

    What do I think about the scalability of the solution?

    The workload profile with Control-M hasn't changed significantly since I started. However, in other environments, I've experienced how scalability has been quite achievable. I can execute both horizontal and vertical scaling if I understand my architecture and the design of the software. I've never had issues scaling the infrastructure or application to meet increased workloads. Currently, the workload volumes in my position have not changed drastically enough to warrant performance reviews or upgrades.

    How are customer service and support?

    My experience with BMC support has been quite good overall. Although I faced some challenges during this particular upgrade and had to send assertive emails to the account manager and support teams, I must commend them for taking my concerns seriously and addressing them effectively. It seems the personnel I interacted with weren't entirely familiar with the new SaaS architecture, resulting in extensive correspondence with higher levels of support. I believe this experience will improve over time, and more recently, support has indeed been satisfactory.

    Which solution did I use previously and why did I switch?

    I can't speak to what was used before adopting Control-M for this organization because when I joined five years ago, Control-M was already in use since 2011.

    How was the initial setup?

    I'm currently migrating from on-premises Control-M to SaaS Control-M. This process involves two components: building the new environment and migrating workflows. While it's SaaS, deploying on-premises components is still necessary to run workloads. The methods for transitioning workflows from the old environment to the new have not been mature or well developed, which has posed challenges, requiring discussions with BMC to find the best path forward. Additionally, evolving security requirements have made the build and deployment processes more time-consuming than initially planned. The recent engagement with security teams shows that early involvement is essential for understanding their expectations for securing the environment, especially given the pressing concerns around cyber threats.

    What was our ROI?

    I can't quote a specific number when discussing cost-effectiveness in relation to Control-M because I'm more on the technical side and not privy to the commercial details. However, I do know that the project I'm currently working on will produce savings by doing platform consolidation, illustrating the kind of advantages Control-M allows me to achieve due to its platform-agnostic nature and comprehensive functionality. I can't provide a number regarding reduced spend with Control-M.

    What's my experience with pricing, setup cost, and licensing?

    Pricing, setup costs, and licensing for Control-M aren't truly under my purview. However, I know from my current project that the costs associated with migrating to the new tool and converting it were competitive, and that the ongoing licensing costs were very reasonable compared to my current solution, which combines Control-M with another tool.

    Which other solutions did I evaluate?

    There was no evaluation of similar tools during my time, as the current upgrade was always intended to be Control-M focused. The emphasis lies on changing the delivery model to transition to SaaS architecture rather than conducting a straightforward on-premises upgrade due to the associated costs and complexities.

    Reflecting on my experience with other tools, I recall being involved in a project decades ago to evaluate alternatives at a different organization. At that time, it involved comparing mainframe solutions, where Control-M proved to be a simpler tool to understand, while alternatives were often quite complex. Notably, I find the learning curve for Control-M to be less steep. I simply define what I want my jobs to do and link them together, while other tools require more complex workflow projections, such as ESP or CA 7, which aren't as intuitive in my opinion.

    What other advice do I have?

    Based on my migration experience, I would advise anyone transitioning to a new SaaS platform to engage the security team early in the process and involve them in the solution design. Even in a SaaS model, there's a need for an architecture accommodating on-premises components. It's also crucial to recognize that moving workflows may not be a straightforward like-for-like transition; customization and potential rewrites of flows should be anticipated, especially now with the capabilities of AI potentially allowing for automation in this process.

    I would rate Control-M an 8 on a scale of one to ten, simply because I don't believe in giving a perfect score. The reasons I don't give it a 10 include minor quirks such as the interface design in SaaS Control-M needing improvements. Some customizable features aren't easily accessible at the user level and can be somewhat global instead. Although the documentation is comprehensive, its search functionality isn't effective, making information hard to locate. I hope the emerging AI capabilities can significantly enhance this aspect.

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Oct 21, 2026
    Flag as inappropriate
    PeerSpot user
    Technology Analyst at a financial services firm with 1,001-5,000 employees
    Real User
    Top 20
    Aug 26, 2026
    Automation has transformed market workflows and reduces weekend maintenance effort
    Pros and Cons
    • "Control-M has positively impacted our organization very much because it gives all our external teams a single platform to use as a single pane of glass to view different workflows, different points of improvement, and monitor how certain processes are performing."
    • "Control-M's learning platforms need significant improvement."

    What is our primary use case?

    My main use case for Control-M is to schedule and automate workflows.

    A specific workflow that I automated using Control-M was the weekend maintenance where we bring down certain applications and conduct certain verifications, then perform maintenance and OS patching work, bring up those applications, and automate the workflows. Control-M has been very successful for this purpose and has eliminated unnecessary human hours from the workflow, providing significant convenience and automation.

    The main use case for Control-M in our organization's context is to schedule the bringing up and bringing down of the market because we work for a stock exchange. We have many applications running through the pre-open, open, during, and closing periods, as well as market close, end of day, and batching. All of these involve many applications that must run one after another along with dependencies and successors. Creating workflows in Control-M has greatly improved our workflow management.

    What is most valuable?

    The best features Control-M offers are the convenience and the reporting aspect, along with the ability to monitor current workflows and see where things are at, where they are stalling, and where abnormalities are occurring.

    For reporting and monitoring features, it is very important that we understand how long certain applications take to run and which applications are draining the memory and hard disks of our servers. Reporting helps us understand execution times, average execution times, points of improvement, and provides information for our higher management. Monitoring has been an essential part of our mission-critical applications, with a separate team utilizing the monitoring and alerting features of Control-M.

    Control-M has positively impacted our organization very much because it gives all our external teams a single platform to use as a single pane of glass to view different workflows, different points of improvement, and monitor how certain processes are performing.

    Automating the maintenance workflow changed things for our team and organization by reducing the potential risk of human errors and saving considerable time for team members who previously had to be available over weekends to work on these tasks. Overall, it has been a step towards advancement in our company to automate workflows.

    What needs improvement?

    Control-M can definitely be improved in terms of the user interface. The user interface they have been using is the same thing they have been using for the last 10 years. Control-M Web UI has not done justice to the fat client because we are forced to switch from the fat client to the Web UI. The Web UI has drawbacks, including the jobs on the monitoring page taking several seconds, from 5 to 10 to even 15 seconds, for the status to update from executing to completed stage. This is something we have to refresh the monitoring domain to see. There are a couple of inconsistencies when switching from the fat client, though I think we might get used to it over time.

    Control-M's learning platforms need significant improvement. The Control-M courses are really bad, and the exams are really bad. Nobody has really spent any time improving them or putting thought into them. It appears someone made them without much consideration. I would like those things to be eventually improved.

    I chose a rating of 8 out of 10 because Control-M has many things to improve.

    For how long have I used the solution?

    I have been using Control-M for close to three years.

    What do I think about the stability of the solution?

    Control-M is stable.

    What do I think about the scalability of the solution?

    Control-M's scalability is very good.

    How are customer service and support?

    Customer support for Control-M is not too bad, but we wish that some of the bugs would be prioritized by the development teams so that we do not have to wait until the next year for certain issues to be resolved.

    How was the initial setup?

    I am not involved in the pricing, setup cost, and licensing conversations as that is usually handled by my higher management.

    What was our ROI?

    I have seen a return on investment with Control-M, and while I do not have specific numbers, it has led to fewer employees being hands-on with the applications because of Control-M's automation.

    What other advice do I have?

    We are yet to utilize the artificial intelligence capabilities of Control-M and would not know about the accuracy and reliability of its output.

    Control-M is deployed in our organization on-premise. It is not very difficult to integrate other processors with Control-M, which is a reason why we continue using it.

    Control-M is currently used extensively in my organization, but the decision to increase usage is entirely with management. Approximately 100 people use Control-M with different roles, though I am not very aware of those specific roles.

    Our main business use cases supported by Control-M involve finance-related applications, though I am not very aware of the functional or application usage details.

    My advice to others looking into using Control-M is to learn all Control-M related features before starting the integration because there are many things you can do. If you understand everything in your initial analysis, I think you will be able to utilize 100 percent of Control-M's features.

    I rated this product 8 out of 10.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Last updated: Aug 26, 2026
    Flag as inappropriate
    PeerSpot user
    Buyer's Guide
    Download our free Control-M Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2026
    Buyer's Guide
    Download our free Control-M Report and get advice and tips from experienced pros sharing their opinions.