No more typing reviews! Try our Samantha, our new voice AI agent.
Josselin Fatah-Roux - PeerSpot reviewer
Ingénieur de production at a tech vendor with 10,001+ employees
Real User
Top 20
Nov 11, 2026
Workflow orchestration has transformed daily reporting and now streamlines multi-environment DevOps
Pros and Cons
  • "For me, it is the best tool currently available."
  • "Aspects of Control-M that could be improved today include maintenance."

What is our primary use case?

Control-M is used to run processing tasks needed for applications. At Europcar, I mainly used it for various applications where processing steps had to be executed in a certain order. For CNAM, it was the same: processes that had to run in a certain order, but with Kubernetes in parallel. There, it was mainly to generate very important files and user files that were critical and had to be generated regularly, then sent via SecureTransport. For Rexel, it is the same thing: processing for various applications that must run either to generate reports or to execute various commands on the servers.

A specific example of a process I orchestrate with Control-M is for CNAM, where it was about generating reports that provided complete tracking for each user, that is, each patient who had an illness, and doing that daily. Once the processing had been done on Kubernetes, a file would be generated, and I then checked with Control-M that this file was indeed present, using File Watchers, and then sent it via command line using SecureTransport.

Currently, I could say that at Rexel we use Control-M in a DevOps way, meaning that to move from one environment to another we use Azure DevOps through the Control-M API. I export the JSON definitions to Azure DevOps from a first pipeline, then map this first JSON to transform it for another Control-M Server that will be on another environment. I have a second pipeline that does that, and a third one that sends it again to the new Control-M Server but with the JSON mapped to the variables of the new environment, allowing us to have something fairly automated with Control-M.

We have financial chains and indeed logistics chains; for example, at Rexel, there are chains like Kinsale, which is really pure logistics. We have financial chains with various applications and various domains.

Control-M supports our DataOps and DevOps initiatives primarily through its integration with Azure DevOps, which allows us to map JSONs between environments and, for the CNAM client, it has been useful alongside Kubernetes to run processing in containers.

For orchestration across multiple environments, I use Control-M with Azure DevOps to do environment mapping, allowing us to have identical chains whose values differ based on the mapping file I've specified.

How has it helped my organization?

Control-M positively impacts our organization through easy-to-follow scheduling, thanks to the graphical interface. Another point is the Control-M API, which really makes it possible to move from one environment to another with DevOps tools, facilitating collaborative work because each application team that wants to move its job chains from one environment to another can do so automatically.

Regarding time savings, the Control-M API has really allowed us to quickly map chains from one environment to another, leading to significant time savings because we do not have to rework the JSON manually. As for errors, we use EasyVista in parallel for monitoring, and we also have ELK, which allows us to quickly visualize job executions, contributing to considerable time savings which I could not estimate exactly, but it is quite significant.

Control-M helps business users gain visibility and control over their processes with its interface, which centralizes all users and allows collaboration between different teams that are not necessarily from the same company. For me, it is the best tool currently available.

What is most valuable?

The best features that Control-M currently offers include basic scheduling, along with all the plugins in parallel that enable connections to various applications, whether databases, VMware, etc. The main strength compared to other schedulers really is all of these plugins that work alongside Control-M.

The plugins I use the most are the database plugins because I have a lot of databases, whether at Europcar or at Rexel. I also use the VMware plugins to restart VMs using VMware jobs. I currently use JMS too, but I have learned that unfortunately Web Services Java will reach end of life in 2027. I have seen that there are quite a lot of plugins available, for example for SAP, Denodo, etc.

Regarding the governance and security offered by Control-M, security is very effective in the sense that I can install certificates, whether in zone 1, zone 2, zone 3, or LDAPS.

I mostly use Control-M's policy management, approval, or risk-limitation capabilities during maintenance periods, especially when I have to restart Control-M, and I have used Workload Policies for that. For security, I regularly use LDAPS with roles.

Integrating Control-M with our DataOps and DevOps technologies is currently quite easy. As I mentioned earlier, I use Azure DevOps in parallel with Control-M to manage the different chains between environments and to handle mapping of variables and values between environments.

In terms of governance, Control-M has its own audit features that allow me to track who modified what and when, especially with job history.

What needs improvement?

Aspects of Control-M that could be improved today include maintenance. Currently, upgrades are done in completely different ways from one version to another, and there can be .zip files, .tar.gz files, or .Z files. Every time I have to upgrade Control-M, there are a lot of prerequisites instead of just having a single package that would do everything.

For improvements to make on-prem deployment or maintenance easier, I would recommend having one single package that handles deployments with no separate .zip files for patches and no different formats. Everything should be done from a single package that performs the entire upgrade itself.

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,774 professionals have used our research since 2012.

For how long have I used the solution?

I have been using Control-M for a little more than 6 years. I started first with the first client, which was Europcar, which ran on average around 5,000 jobs daily. Then I used Control-M for CNAM, where we ran around 150 jobs per day. Finally, I have used Control-M for Rexel, which is the client I am currently working on, where the number of jobs is around 2,000 for now, but it keeps evolving because we are doing a migration from Dollar Universe to Control-M.

What do I think about the stability of the solution?

Control-M is stable but can experience bugs. During maintenance, I have noticed that some patches did not clear certain data, especially logs, and on some commands, for example, PowerShell still appears in the output even though it had been removed.

What do I think about the scalability of the solution?

Currently, I would say that for the current client, we have about thirty users of Control-M, around 30 to 40 people. For other clients, it is around 10 to 20, and these are mainly people who are either operators or administrators like me.

For now, I use Control-M regularly, but I do not plan to increase its usage in the future.

Control-M rates perfectly for scalability since I can add as many Control-M Servers and EMs as needed, and it also supports High Availability to maintain consistent performance.

How are customer service and support?

Customer support for Control-M is very fast in responding, very effective, and takes into account everything I report.

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

For the current client, we are doing a migration from Dollar Universe to Control-M, as Dollar Universe did not meet all the requirements and needs we had.

How was the initial setup?

I currently deploy Control-M on-premises because I prefer to manage it myself the way I want. At the moment, deployment is done by level 3 teams, which I am part of, and similarly, maintenance and upgrades are handled by our level 3 teams who do everything on-prem.

I try to install it such that the EM is on its own dedicated server, the Control-M Server on another dedicated server, and at least one Control-M Server per environment to ensure workload is handled as well as possible.

Currently, for the client I am working with, we do not have cloud and we do not use cloud. We are still on-prem, but for Europcar we started a migration to the cloud where we had some agents and a Control-M Server in the cloud to move chains one by one from on-prem to the cloud.

What about the implementation team?

For the various clients I have worked with, at Europcar we were just two people. At CNAM we were two as well, and currently for the current client we are about three to four.

What was our ROI?

Time savings from Control-M comes from its DevOps capabilities that allow for mapping and automating the promotion of chains from one environment to another, along with time savings from all the plugins that prevent custom development for managing databases or VMware.

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

The sales teams on the client side handle that. I know that for the first client, licensing was based on the number of daily jobs limited to about 5,000 jobs per day. For the second client CNAM, it was limited to 700 jobs per day, and for the current client, the license is based on the number of agents, about a hundred agents across all environments.

Which other solutions did I evaluate?

For the current client, there was a competition between Control-M and VTom, and in the end, Control-M won because of its additional features, particularly the plugins and visualization that convinced the client.

What other advice do I have?

Control-M is currently a very effective tool that has a lot of features, but there are still some points for improvement, particularly regarding Control-M upgrades, and I think additional features would be needed for certain specific applications.

I would like to install Control-M's AI, and I am currently studying how the installation is done and what impact the AI might have on Control-M. For now, I would like to test it only in non-production to see what it might do in production and to ensure that the AI does not go beyond what I ask it to do.

For those considering using Control-M, my advice is to get proper training because it is a very effective tool with many features, so best practices and consulting documentation and the Control-M community are highly recommended.

Which deployment model are you using for this solution?

On-premises
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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Last updated: Nov 11, 2026
Flag as inappropriate
PeerSpot user
IT Specialist at VicRoads Registration & Licencing
Real User
Top 20
Oct 21, 2026
Automation has simplified overnight data processing and has reduced effort across critical workflows
Pros and Cons
  • "Control-M visualizes from point A to point B on the screen similar to how Google Maps shows routes, providing easy navigation so users understand what to do next and where to look to find problems easily."
  • "The web interface of Control-M needs improvement."

What is our primary use case?

The main use cases in Control-M for the organization involve moving from the old infrastructure to the new infrastructure. The organization previously operated on mainframe systems and went through a transformation to modernize the mainframe, which is where Control-M came into the picture. The organization was using an old product called CA 7, and it has been migrated to Control-M. The mainframe itself has been migrated to AWS on Linux. Control-M is primarily used for processing all data overnight, around 800 jobs, of which 500 are critical, making it important for operations.

Currently, AI is not being used in Control-M, but the organization is planning to use AI in the future through Jet in Control-M. From research, Jet is already included in the SaaS version, but the organization is running a standalone version that requires additional configuration. The organization has identified that Jet could be utilized going forward, with some configuration required. Enabling Jet would be the first step to using AI in Control-M, which would help not only from a creating perspective but also provide insights about the schedule and assist in managing the batch.

In terms of integrating Kubernetes or cloud-native workflows with traditional batch processing, Control-M plays a role as the organization is in the process of identifying what else is running outside Control-M. There could be a cloud-based scheduler, a bot-based scheduler, or an RPA-based scheduler. Control-M has different connectors that could be used going forward. The organization is gathering information to identify which other schedulers can be taken into consideration, and a plan will be created to move those into Control-M eventually. The goal is to see everything in Control-M as a one point of orchestration. Control-M has many features and connectors that can connect to existing legacy or systems running schedules, such as CloudWatch or JAMS, which is another scheduler. RPA can also be migrated to Control-M, and Control-M assists in this integration.

How has it helped my organization?

The current organization has realized many benefits since implementing Control-M, including significant cost savings in the sense that the amount of work required to achieve something has been reduced because the number of processes required to define has reduced significantly compared to the old system. In terms of hiring extra people, that has also been reduced because Control-M allows fewer people to manage complex systems. The old system required involving more people because of more complexity and more manual tasks to be completed. Control-M is also quicker than the old system in terms of efficiency.

Estimating in terms of percentages, at least 20 percent more efficient has been achieved in terms of cost savings. Approximately 50 percent time saving has been realized. About 50 percent reduction in labor required has also been achieved.

What is most valuable?

The main feature of Control-M is the interface itself, which is quite easy to navigate. When managing thousands of automation programs, the layout in Control-M makes navigation really easy. A tree view, network view, and flow diagram are available for different perspectives. The second most important feature is the viewpoint that helps identify the critical path of the whole process. Multiple tools in Control-M can map out the critical path easily, allowing identification of the most critical jobs needed to get from one point to another. Control-M can isolate everything else and show a filtered view so focus can be placed on the critical path. The third most important feature is reliability. Control-M works as designed approximately 99 percent of the time. The time feature also allows going back in time to see what happened, which enables pinpointing where problems occurred.

The importance of the first two features mentioned is because they make navigation easier. Control-M visualizes from point A to point B on the screen similar to how Google Maps shows routes, providing easy navigation so users understand what to do next and where to look to find problems easily. The user-friendly interface makes work easier.

In terms of managing the integration and sequencing of data processing across diverse data platforms and cloud environments via Control-M, File Watcher is used, which is an innovative feature of Control-M. File Watcher makes work easier because multiple parameters can be defined to determine whether the file or data has been received. Multiple things can be done around it and customization can be completed per requirements. As soon as something is managed by File Watcher, it has the ability to pass on to the next process. The organization has been using File Watcher, and it is working well and is quite stable.

In terms of compliance requirements such as SOX, audit trails, or regulatory reporting, Control-M plays a significant role. The main feature used from Control-M is Control-M reports, which is a built-in feature, and any report can be pulled out as needed. Actions can be tracked to see what was done during the time, and logs can be pulled out from Control-M to help with auditing. If any changes were made to the schedule, the version history feature of Control-M can be used to track changes and determine what went wrong or what happened in the past at specific times of the day or year.

What needs improvement?

There is always room for improvement. The web interface of Control-M needs improvement. When comparing the web interface versus the desktop interface, the web interface lacks many things that the desktop interface has. If Control-M and BMC could examine the desktop version of Control-M versus the web application and attempt to match those things, that would be a significant achievement.

For how long have I used the solution?

Control-M has been used since 2008, totaling 18 years of working with this product. Each time working with this product, it feels like a perfect match in terms of how things should work and personal interests, which are all part of the role and the product.

What do I think about the stability of the solution?

In terms of stability and reliability of Control-M, it is at approximately 99 percent reliability. Control-M has hardly ever crashed, and most of the time if there is a problem, it comes down to either the system, a network issue, or some other issue not related to Control-M in most cases. Control-M uptime is more than 99 percent, making it highly reliable. In terms of stability, Control-M is on a quite high scale.

The architecture of Control-M is designed to be most stable because it has three different components: the enterprise manager, the server, and the agent. Due to this design, it functions as a fail-safe where if one thing goes down, it does not affect the other thing. There is hardly a situation where all three things would go down, making Control-M pretty stable by design.

What do I think about the scalability of the solution?

Control-M scales quite well with the growing needs of the organization. At one previous employer, 15,000 jobs were running at one point. At another, the team had 8,000 jobs, but the overall organization had a total number of jobs of approximately half a million.

In terms of scalability, Control-M is enterprise-level. That is the reason most Fortune 500 companies have adapted Control-M as an automation tool. Control-M is definitely scalable and improving every day, with each new version containing many features.

What was our ROI?

Although not directly looking at the accounting side of things in Control-M, from what is known, it has paid off in terms of career development and inclination towards Control-M. There is always more inclination towards Control-M because all repetitive tasks can be automated and Control-M is one of the best tools that has been worked with. Control-M is the only tool that has so far matched expectations or actually exceeded expectations in terms of automation. From that perspective, it has definitely rewarded in terms of career investment into Control-M.

What other advice do I have?

I would rate Control-M at nine out of ten on a scale of one to ten. Nothing is perfect in this world, and there is always room for improvement. The web interface definitely needs improvement, and there may be other areas like a Batch Impact Manager that need improvement as well. In terms of reliability and user experience, Control-M is ten out of ten, but in terms of the overall product, it is nine out of ten because it has room for improvement.

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
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,774 professionals have used our research since 2012.
Co Founder & CEO at Sylkane
Real User
Top 20
Jan 20, 2026
Centralized scheduling has streamlined complex production plans and supported multi‑cloud operations
Pros and Cons
  • "The best features and what I appreciate about Control-M are the power of the tool, the ability to manage different applications, and to have a comprehensive overview of the production plan."
  • "In terms of scalability, I would give it a seven. The reason for my seven rating is due to the challenges when I have various environments across different continents and countries."

What is our primary use case?

The use case for my clients involves everything, as it depends on the customer environment and the platform. I have managed around 60 business cases during the last five to seven years. My customers use Control-M for the management of the production plan to manage other internal applications, cloud services, or infrastructure services. The minimum infrastructure I integrate or manage is around 1,000 jobs per day, and the maximum is around 200,000 per day.

Integrating data ops and DevOps processes for my clients is straightforward.

The scale I work with depends on the service. In the Silkan organization, we have six different houses with different practices. For time and materials services, integration is relatively easy because we work with the customer's technical team to advise and implement the tools based on the previous production plan. The customers I deal with are generally from the CAC 40 in France and are typically very large companies like those in the SBF 120 or SBF 250. For managed services, I engage with companies that have between 500 to 5,000 employees and just below 2 billion in turnover per year.

I work with all industries and do not have a specific sector.

What is most valuable?

The best features and what I appreciate about Control-M are the power of the tool, the ability to manage different applications, and to have a comprehensive overview of the production plan. Another aspect that my technical team appreciates is the continuous improvement of the tool because we know that more than 200 developers enhance the tool every year. Additionally, I have skills for other schedulers, but my main partner is truly BMC for the quality of the support, the tools, and the relationship with the alliance team.

Deploying Control-M is straightforward, and while the installation can be completed in less than one day, the migration and full integration require visibility on the production plan to estimate the time needed effectively. For different volumes, such as a production plan for 1,000 or 100,000 jobs, the time management varies significantly.

Maintaining Control-M is easy, and it does not require complex updates or renewals.

What needs improvement?

The area for improvement pertains to the next generation of scheduling tools, particularly integrating the capacity to translate business team feedback into technical jobs. A large part of my role today is transforming business team feedback and needs into technical jobs. However, my main value is to accompany the customer in their technical journey to migrate and manage their enterprise's critical applications. Therefore, the scheduler is primarily a tool for organizing production plans. If it becomes possible for business teams to directly interact with Control-M through an LLM to automatically create jobs with just a review by an engineer, I believe it would save significant time for managed services providers and enhance Control-M's perception among business teams.

For how long have I used the solution?

I have been working with Control-M for 15 years.

What do I think about the stability of the solution?

I would rate the stability of Control-M as a nine, as I find it to be stable with minimal bugs, glitches, or downtime.

What do I think about the scalability of the solution?

In terms of scalability, I would give it a seven.

The reason for my seven rating is due to the challenges when I have various environments across different continents and countries. I have to duplicate environments and handle multiple issues. Network problems, even short cuts, can cause some complications. Scalability involves delivering services globally, which customers demand, and while synchronization works well when confined to a single country with one or two environments, more complex arrangements can introduce challenges.

How are customer service and support?

I would rate the vendor's technical support as an eight.

How would you rate customer service and support?

Positive

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

When comparing BMC Control-M with other products, I note that there are other technologies I manage, such as Vtom and Dollar Universe. However, I focus on managing alliances, so BMC remains my only partner for scheduler tools, although I know the technical team oversees various schedulers.

How was the initial setup?

Control-M setup is straightforward.

What about the implementation team?

I do not typically work with the BMC technical team to create migration strategies, as my experts manage, design, and implement the tools for my customers independently. My relationship is mainly focused on licensing pricing, daily sales meetings, and an annual technical summit to discuss features and future developments of Control-M.

What was our ROI?

Control-M represents good value. It is important that you understand my limits on Control-M because I sell it for my customers. I have some knowledge about the licensing and the relationship with the partner team of BMC. The main people who manage the alliance with BMC are my associates, including Antoine Bitran, who will have more information about Control-M. Regarding the technical part, I have a few people internally, around 15 experts who are Control-M certified, who handle the technical aspects. On my side and regarding my job, it is more about the relationship, the knowledge, and the feedback about customer satisfaction.

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

I would recommend trying the BMC cloud environment as the best way to experience Control-M. Implementing a few jobs using a free demo license for a few days or weeks is advisable, though it really depends on the customer's maturity, size, complexity, and criticality of the application, making it a nuanced recommendation.

Which other solutions did I evaluate?

Overall, I would rate BMC Control-M as a nine.

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?

Other
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. The reviewer's company has a business relationship with this vendor other than being a customer: MSP
PeerSpot user
Siraj Shaik - PeerSpot reviewer
Workload Automation Engineer at a retailer with 10,001+ employees
Real User
Top 5
Nov 5, 2026
Job scheduling has become reliable and unified while complex data pipelines run smoothly
Pros and Cons
  • "What I appreciate most about Control-M is its stability. It is stable and usually does not go down."
  • "What I dislike about Control-M is that until very recently, and even now, it was not containerized or stateless."

What is our primary use case?

My use cases for Control-M primarily involve scheduling, especially with applications like SAP, database plugins, and mostly OS.

How has it helped my organization?

Using Control-M has made it simpler to create, integrate, and automate data pipelines. We used Airflow to run data pipelines at one point, but it lacked many features that Control-M offered. Fortunately, Control-M had a plugin for Airflow, so we could use Airflow for data pipelines but schedule them via Control-M jobs, which gives us a native, feature-rich scheduling environment and integrates with data pipelines along with Airflow.

BMC keeps up well with the technologies and developments out there.

What is most valuable?

What I appreciate most about Control-M is its stability. It is stable and usually does not go down. The consistency when the application restarts is flawless, and there is no usual data loss with Oracle as the backend. It is dependable based on my experience as an administrator using BMC across organizations.

Control-M is easy to integrate with other applications and technologies because it provides plugins for the latest solutions by default. If not, there is an Application Integrator built for that purpose, and there are community-driven integrations. From an alerting perspective, BMC had a very good affinity to its own tools, and it did not have ServiceNow integration, which is the most popular ITSM tool. We ended up using ancient SNMP calls to get the alerts out to custom tools. Other than that, integrations are good.

What needs improvement?

What I dislike about Control-M is that until very recently, and even now, it was not containerized or stateless. It is a stateful application, which is what I still dislike about it. It prefers its host, tries to maintain the connection, and lives on the host. It is not fully containerized or split into microservices, and it cannot be installed on anything with a database connection to start working. It prefers the host on which it was originally installed, and the statefulness of the application is what I do not like.

For how long have I used the solution?

I have been using Control-M overall for 19 years.

What do I think about the stability of the solution?

Control-M is stable. Only heavy upgrades require downtime of approximately 30 minutes for the Enterprise Manager and Control-M server applications every year or every six months. Other than that, it runs continuously.

What do I think about the scalability of the solution?

Control-M likes its nodes and is stateful. You cannot just add multiple nodes. It operates on active-passive high availability and does not scale horizontally much. Though capacity-wise it is good, at a given point in time, an instance runs on one VM, not ten. If that goes down, it can switch over to another, but that statefulness is what I do not like about scalability.

It works, but it does not feel scalable. One node at a time is not scalable.

How are customer service and support?

Control-M's technical support is good. For priority cases, they are quick. P1 and P2 cases respond at the earliest, while P3 takes some time based on the time zone you are in and the time zone you are signed up for. They have always been helpful and go out of their way to get things done for me.

I would give Control-M's technical support a score of nine out of ten.

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

I migrated from Tandem to Control-M as my organization used Tandem earlier. They brought in Control-M because they had mainframe and CS-7, and I believe that is how it started for the current organization. In the previous one, some brought it for SAP, some brought it because of the mainframes. We had cron before Control-M or the mainframe had JCLs being scheduled by the mainframe itself, and then we brought in Control-M in the 1990s.

How was the initial setup?

The initial deployment of Control-M, from what I did hands-on with migrations from the OS and new projects, was seamless. I did not bring Control-M into any organization as such. I went when it was already there. I enhanced, refactored, and migrated everything. In a development environment, it is seamless. You might still sometimes need to call support, but the documentation and a case here and there, along with a little bit of experience using it, works adequately.

Open source tools like Rundeck are more straightforward and easy to install, set up, and manage for someone starting, but Control-M still needs expertise in this area to get it started and working since it has its own configs and the way it works.

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

Control-M has gotten better at its pricing and with the latest offer for minimal jobs, it is acceptable given the value it provides. Mainframe is a bit expensive regarding the mainframe components, but I believe that is the way for any of the mainframe components. For distributed scheduling, non-mainframe, Unix, and Windows, it is reasonably priced.

Which other solutions did I evaluate?

I have used alternatives like Rundeck, and people use cron. I have also used Airflow, which provided some other functionality. Rundeck and Airflow are alternatives, and I regard Rundeck as an alternative.

I prefer Control-M more than the alternatives. It is a paid tool, but it is worth it.

What other advice do I have?

I started working in my current field overall with Control-M after my first year in IT, so that would be 18 years.

Control-M requires maintenance on my end for patches when there are vulnerabilities, which are usually released by Control-M. Other than that, everything can be automated.

Control-M takes care of all scheduling jobs, and when you have Control-M, you do not need to use any other tools. If one application has a single server running a couple of jobs, I would still suggest using cron as that would be more suitable. If complexity arises, you can better use Control-M. Because it is not free and not unlimited, you pay per job license. Whenever something simple can be triggered by cron and easily managed, I would personally use cron on a single server with a handful of jobs. If I need alerting, monitoring, a GUI, integrations, and audit and compliance, I would switch to Control-M even if I have to pay per job. Competing scheduling tools are not usually required as Control-M will suffice with data transfer, mainframes, distributed, and everything.

My relationship with BMC is balanced between transactional and transformative. It has been good, but it depends on the organization's priorities. There was a push towards going to open source schedulers, wherein we as an organization had to wind down the job licenses. The licensing calls are always tricky and handled by the vendor management team. They have their own logistics. I am a purely technical person making technical decisions, and I probably push something if it is good, but then it would go that way. BMC genuinely tries to help their customers. They have built us plugins, but at the same time, it is about the money.

Overall, I would give Control-M a rating of eight out of ten because it is not vertically scalable, and they did not fully containerize it or make it into microservices. For that reason, I would give it an eight. If not for those issues, I would give it a nine.

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: Nov 5, 2026
Flag as inappropriate
PeerSpot user
Lead Solution Architect (Americas) at Tech Mahindra Limited
Real User
Top 20
Nov 10, 2026
Workflow automation has transformed data pipelines and supports complex AI and change workflows
Pros and Cons
  • "Control-M provides full clear visibility of all processes with centralized visibility so that multiple platforms, multiple orchestrators, and different functionalities across departments can all be visible from a single pane of glass."
  • "Regarding pricing, Control-M is expensive compared to the competition, but it is worth it. Even though Control-M is expensive, pricing could be brought down slightly."

What is our primary use case?

My use case is workload automation. Control-M adapts to my environment by using data pipelines that are orchestrated through Control-M, providing all the data needed for machine learning initiatives.

Regarding specific machine learning operations workflows, I have orchestrated them by integrating Control-M with tools such as MLflow. I have primarily focused on integrations and DataOps. Beyond MLflow, I have also integrated Snowflake and Vortex. Snowflake executes SQL commands and handles data format and data transformations. Once data transformations are completed using Snowflake, Kafka, and Vortex, multiple integrations are performed through API with agents, and Vortex is also utilized.

For ITSM and change management tools, I have integrated Control-M with these systems.

For change management workflows, I create scenarios such as user creation in Active Directory, where the workflow executes and calls API scripts or automation for Active Directory to create the users. These workflows have been created for release management. Once a change is approved internally within the ITSM system with all necessary approvals from the CAB, it is critical to ensure the release happens according to the change guidelines. This requires a sophisticated and reliable system with robustness. Control-M allows me to perform the change and ensure that the data is returned to the ITSM.

How has it helped my organization?

The benefits I have seen from implementing Control-M include increased productivity by ensuring jobs are completed based on prerequisites. Control-M reduces my complete total cost of ownership through increased visibility, which reduces multiple tool sprawl and results in cost reduction. I have achieved increased productivity, better SLA management, and ensured that SLA records, SLA points, and SLA metrics meet KPIs. Control-M provides automated failure recovery so that remediation is also taken care of.

Moving into DataOps operations, Control-M ensures that my AI infrastructure and AI initiatives are all supported. The advantages include reduction in cost, increase in productivity, and ensuring compliance.

What is most valuable?

The best features I find in Control-M are its robustness and job visibility of complex job dependencies and status. When I have a mesh of jobs, Control-M can clearly identify and update and also run all these multiple jobs while providing clear output. Control-M offers robustness, visibility, and scalability.

Control-M helps with policies, approval, and risk gating capabilities. It is very robust in handling workflow approvals within my organization with multiple levels of approvals, even with stable rollbacks and clear status updates. Notifications are proper and informative. Control-M is the right fit for my needs.

Regarding visibility, Control-M provides full clear visibility of all processes. It has centralized visibility so that multiple platforms, multiple orchestrators, and different functionalities across departments can all be visible from a single pane of glass.

What needs improvement?

Control-M sits on top of many orchestration tools that are available in the market. One area for improvement is that I still have dependency on orchestration tools. If Control-M develops or acquires an orchestration tool and builds that capability within Control-M as a complete orchestrator, similar to Ansible or Terraform, my dependency on external orchestrators would reduce and I would use Control-M more extensively as a complete end-to-end tool. Building a full-fledged orchestrator inside Control-M would be ideal and would be a wonderful value addition.

Aside from an orchestrator, there might be value in performing some functions without headless architecture. An orchestrator capability should provide that ability. Control-M is bringing AI and LLM integrations, which is positive. The orchestrator capability is the main area for improvement at this time.

For how long have I used the solution?

I have been using Control-M for more than five years. Throughout my five years of association with Control-M, I have found it to be successful when dealing with complex workload automation tasks.

What do I think about the stability of the solution?

Control-M is very stable. I rate its stability as a nine out of ten.

What do I think about the scalability of the solution?

Control-M handles very large numbers of jobs, going beyond 10,000 jobs. My organization has many BMC Control-M specialists, and I have implemented Control-M organization-wide. My clients are large organizations, very large. My organization has 150,000 people. Control-M is very much scalable. I rate its scalability as a nine out of ten.

How are customer service and support?

I rate the technical support at nine out of ten.

What was our ROI?

The return on investment I see is at least something like 30% easily.

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

Regarding pricing, Control-M is expensive compared to the competition, but it is worth it. Even though Control-M is expensive, pricing could be brought down slightly. One more improvement I was looking at from a pricing perspective is that SaaS pricing is too expensive. On-premises pricing has no limitation on the jobs and licenses, but when moving to SaaS, there is a big impact.

Which other solutions did I evaluate?

Control-M is fantastic because of its support, which is number one. The ability to scale up and the best implemented solution across the globe make Control-M stand out. There are competitors such as ActiveBatch and other companies, but Control-M is still the number one in workload automation.

What other advice do I have?

My business role is as a partner and system integrator. I have Control-M deployed in every mode, both cloud and on-premises as well as in private cloud. For cloud services, I use prominently Azure and AWS.

My relationship with BMC is strategic and transformational. I would describe Control-M as positioned for performance in building, scheduling, and managing workflows. My final rating for the solution overall is around nine out of ten.

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: 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. The reviewer's company has a business relationship with this vendor other than being a customer: Integrator
Last updated: Nov 10, 2026
Flag as inappropriate
PeerSpot user
Senior Systems Administrator at a consultancy with 501-1,000 employees
Real User
Top 20
Aug 6, 2026
Job scheduling has simplified cross-platform workflows and supports complex dependencies
Pros and Cons
  • "From a stability perspective, I have been using Control-M for 24 years, and we have only experienced one major issue with it during that entire time."
  • "Control-M does not allow us to build a new server to scale up our environment to a different OS or anything of that nature."

What is our primary use case?

My use cases for Control-M involve it being a job scheduler that can accomplish many things for our organization. It includes a large number of dependencies and many different types of jobs. We run jobs on Windows and Linux, and we have ARO pods, so it is a significant part of our environment.

What is most valuable?

What I appreciate most about Control-M is that once you become familiar with it, it is very easy to use. When jobs run, the application displays pretty colors so you can quickly determine whether a job is successful, running, or unsuccessful. It is very easy to follow what is happening on the screen. The ease of use is what I value most about the product.

What needs improvement?

What I dislike about Control-M is that sometimes things can become very complicated with certain job setups. I am not certain if that is really Control-M's fault, but setting up complicated dependencies with difficult scheduling and the Control-M New Day time can become very complicated, especially with the New Day feature.

Regarding scalability, I do have a concern with it. When we change OS versions and want to do an upgrade, that is the one time I have an issue with the product. Control-M does not allow us to build a new server to scale up our environment to a different OS or anything of that nature. We have to build the new server, migrate our configuration over with the same application version, and then upgrade. This is a major issue for me, and there should be an option to build a new server and upgrade by simply putting the new version on it.

For how long have I used the solution?

I have been working with Control-M since approximately 2002, which makes it 24 years.

What do I think about the stability of the solution?

From a stability perspective, I have been using Control-M for 24 years, and we have only experienced one major issue with it during that entire time. I would give it a 10 out of 10 for stability. The server never crashes because of Control-M, and we never have any CPU or memory issues since the product is very stable.

What do I think about the scalability of the solution?

Regarding scalability, I do have a concern with it. I have never needed to scale it out much due to not having a large environment. However, when we change OS versions and want to do an upgrade, that is the one time I have an issue with the product. Control-M does not allow us to build a new server to scale up our environment to a different OS or anything of that nature. We have to build the new server, migrate our configuration over with the same application version, and then upgrade. This is a major issue for me, and there should be an option to build a new server and upgrade by simply putting the new version on it.

How are customer service and support?

Anytime I have needed help from BMC, they are very responsive. I have been working with Control-M for almost 25 years, so I do not follow up with them frequently, and I do not use their services often. However, anytime I have had questions, they are right on the ball. Their support for the product is very good.

I do not have to wait very long for them to answer me, and they usually provide a resolution very quickly. I handle several products, and in comparison to all of them, the quality and speed of Control-M's support seem to be the best. They always reply back as soon as I open a case, usually the same day within hours, regardless of the case's priority. They work on it quickly, getting me an answer within two or three days at most. There is very rarely a time I go longer than a couple of days without a response. Their support is among the best available.

How was the initial setup?

I find that the actual installation of Control-M is fairly straightforward. There are two components, so I can basically install each separately. It is not overly complicated to install. The setup can become complicated depending on how much I have to configure. Basically, my company tries to leave it out of the box for most of the configuration, so we do not do much customization after it has been installed, as Control-M does a very good job of setting proper default standards for us.

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

Control-M is on the expensive side because I know we have looked into other pricing for other products in the past, and it is on the expensive side of things.

Which other solutions did I evaluate?

The only alternate solutions I really use for comparison are Windows Task Scheduler or Cron. Those are just the basic default schedulers that come with the operating system.

What other advice do I have?

We definitely use DevOps and DataOps with Control-M. The DataOps we have integrated basically uses scripting methods to accomplish this. We do not use many of the available plugins. On the DevOps side, we have ARO pods, so we set up a pod environment, which was somewhat tricky at first because we were one of the first to start using this type of setup. Now it is much better. I have checked the documentation they have now, and it is significantly better than it used to be. In the beginning, it was quite complicated, as they pointed you to GitHub and said to look there for all the details. Now they have much better documentation, making it much easier for us.

I believe my relationship with BMC is transformative. They always keep us up-to-date on things. They have seminars and user groups, which is another significant benefit. I attend a Toronto user group basically once a year, and we get all kinds of valuable information from that. I believe it is a good relationship in that regard.

Overall, I give Control-M a rating of nine out of ten for everything, including the price.

Which deployment model are you using for this solution?

On-premises
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 6, 2026
Flag as inappropriate
PeerSpot user
Mohamed Rashid - PeerSpot reviewer
IT Manager at a manufacturing company with 1,001-5,000 employees
Real User
Top 20
Nov 11, 2026
Automation has transformed data operations and now delivers accurate, timely workflows
Pros and Cons
  • "In terms of automation, we were able to save more than 50% of headcount or full-time equivalents, which provided substantial benefit."
  • "Generative AI integration would be valuable."

What is our primary use case?

Control-M helps tremendously with operational activities and the interdependency of numerous data pipelines and data movements between inbound and outbound systems. We are a fintech company with around 155 fintech operations and more than 150,000 merchants' data, all of which flows through Control-M for every ETL and data processing activity.

This saves significant time in operational management and provides the accuracy and SLA compliance needed to meet delivery timelines. Control-M is deployed across the region, which helps us leverage workload automation to manage workloads properly within client and operational expectations without delays in report and data delivery.

How has it helped my organization?

In terms of automation, we were able to save more than 50% of headcount or full-time equivalents, which provided substantial benefit. Beyond manual work savings, the alerting, auditing, and compliance capabilities within Control-M's ecosystem provide clear visibility and governance across our operations.

What is most valuable?

Control-M helps tremendously with operational activities and the interdependency of numerous data pipelines and data movements between inbound and outbound systems. We are a fintech company with around 155 fintech operations and more than 150,000 merchants' data, all of which flows through Control-M for every ETL and data processing activity. This saves significant time in operational management and provides the accuracy and SLA compliance needed to meet delivery timelines. Control-M is deployed across the region, which helps us leverage workload automation to manage workloads properly within client and operational expectations without delays in report and data delivery.

In terms of automations, we were able to save more than 50% of headcounts or FDs within the automation, which really helped. Beyond manual work, the alerting, auditing, and compliance capabilities provide clear visibility within Control-M's ecosystem.

What needs improvement?

Generative AI integration would be valuable. Additionally, Control-M could invest in system integration capabilities that extend beyond file transfer to include API integration capabilities. A tool or product that can manage both offline and online transactions within Control-M would be beneficial.

For how long have I used the solution?

I have over 18 years of experience with Control-M.

What do I think about the stability of the solution?

When moving to SaaS, maintenance requirements change. Control-M is a very stable product, and if implemented properly, it will not experience significant hiccups and will run smoothly for at least three to four years with minimal intervention.

What do I think about the scalability of the solution?

Control-M is really scalable, depending on where you implement it. As long as you perform the right sizing and infrastructure planning, it scales effectively. The product can integrate into modern environments and works well with basic implementation approaches, which we have done successfully.

Integration in modern environments is straightforward, though it requires proper planning.

How are customer service and support?

BMC has maintained really good knowledge articles regarding known issues and other information. This documentation is well articulated and comprehensive, so issues can often be resolved by consulting these resources without even contacting support. In terms of support quality, BMC provides well-oriented documentation that allows anyone to identify and solve problems independently.

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

I have reviewed multiple alternatives, but Control-M continues to invest heavily in research and development, which translates to meeting customer demands and requirements effectively. This commitment to investment helps with customer engagement in Control-M.

How was the initial setup?

Control-M has consistently performed well in DevOps and CI/CD development. There is still room for improvement, and I am confident that BMC will continue investing in the right directions. Numerous connectors and modules are available, and as one of BMC's top products, Control-M will receive continued development investment.

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

Pricing continues from the legacy model. Control-M needs to develop different pricing variants across different workload capacities and client scopes. Competitive pricing is important as there are multiple players in the market offering tools at attractive prices and pricing models. Control-M needs to develop a pricing model that helps customers during yearly budget planning cycles.

What other advice do I have?

Control-M has been transformative for our organization. We have good interaction with BMC, which helps both us and them grow the product. This review rates Control-M a 9 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: Nov 11, 2026
Flag as inappropriate
PeerSpot user
Souparna Chatterjee - PeerSpot reviewer
Lead Engineer at Bupa Australia & New Zealand
Real User
Top 20
Oct 21, 2026
Automation of secure payments and partner file transfers has transformed daily operations
Pros and Cons
  • "Control-M seamlessly automates everything from our organization to the partners and vice versa."
  • "Control-M is doing enough to keep up with modern technologies. However, there is always room for improvement in every tool."

What is our primary use case?

Control-M has many use cases with four or five very critical use cases within our organization. The first is to manage the payment gateway and payment domain. The second is to manage the integration of end-to-end file transfer with many different critical partners because it is very critical to maintain seamless file transfer for them. Control-M uses this in a very extensive way. The third one is to obviously manage Control-M in such a way that it is up and ready for all the customers who are using Control-M. We have some end users, such as service desk who use many different applications including add user, modify user, and many other functions. All these are automated by Control-M with no human interaction. We are trying to do agent-based automation as well with Control-M, but that is something for the future.

The primary use cases are very different and vary from day to day. One of the most critical use cases is manage file transfer, which basically allows us to connect and interact with various partners and vendors who are sitting outside our organization. Everything is governed by security, but it reduces the manual effort, allowing us to automate everything, so basically no human interaction is required when it comes to sending or receiving very critical information files from different vendors. Other critical use cases include payment gateway and payment file transfer, which allows us to talk with different payment providers. The whole workflow is automated and orchestrated by Control-M.

For Kubernetes, we have not explored that part yet. However, we are moving towards Kubernetes-related deployments in Control-M. We are open to exploring that in the future.

We do use cloud-native workflows with traditional batch processing. For example, the main system of our organization, including payment and claims systems, is still running on-premise. We have many integrations moving data and information from the cloud to different environments, specifically payment providers or third-party providers.

We are not currently using Control-M to support AI or ML workloads, but we plan to. We have a dashboard feature that utilizes our own created AI which leverages Control-M automation API to provide job failure notifications. We look forward to using Control-M's workflow creation magic or JetAI whenever we transition to SaaS. Currently, we are still on-premise, but we are looking to move to a SaaS version very soon.

How has it helped my organization?

There are many benefits to using Control-M. As I mentioned before, the main use case is file transfer. Control-M allows businesses to send many information items to third parties with whom our organization has contractual agreements. However, due to security reasons, these tasks cannot be done via email or any other means when the volume is large or when manual effort is required. Control-M seamlessly automates these processes and orchestrates every file transfer with a very high level of encryption, offering a secure platform.

I estimate that we have sped up our processing via Control-M by about 80%. For example, consider a business user who is making numerous changes in a sensitive Excel sheet or CSV. They may contemplate emailing or placing it in a shared drive, but what about security? The security is nowhere; there is no encryption, no PGP encryption, nothing. Control-M can easily handle this task, ensuring security and encryption, which is very much needed in our organization, especially one dealing with many sensitive information items.

What is most valuable?

The features of Control-M that I appreciate the most include the managed file transfer protocol, which Control-M comes with as a native feature. What we basically do with managed file transfer is that our organization has many different very critical partners sitting outside it, and it is very difficult to maintain the file transfer or maintain the communication in a manual way. Control-M seamlessly automates everything from our organization to the partners and vice versa.

Control-M can easily integrate with a cloud environment. For example, we have a Microsoft Azure-based platform. We have different containers inside Azure and have a business requirement that an upstream process creates some data flow into a container, into a blob directory. We need to log into the blob directory, send the file, encrypt the file, and send it to a different business owner. Control-M can easily automate that because it has seamless integration with Azure Cloud, including service principals, allowing us to orchestrate that flow with very minimum effort.

Control-M is already operating at a very advanced level when it comes to communication between cloud-native and batch processing. The main focus is on easier connection. Control-M, with service principal access or CyberArk-related access, can easily provide different authentication methods to connect to the cloud. This makes my job as an integration engineer much easier, as a seamless connection allows us to execute many tasks effectively, making the whole organization operate in a faster environment.

Control-M has various methods for addressing compliance requirements. What we use extensively for auditing is Control-M reports. We have an external reporting vendor, and for auditing purposes, we need to comply with their requirements every six months. They come back with numerous questions, and with Control-M's reporting feature, it is so easy to generate the report and provide all critical failures and changes that happen within Control-M planning domain or Control-M database. Control-M reports is the go-to platform for us for any audit or security review.

What needs improvement?

Control-M is doing enough to keep up with modern technologies. However, there is always room for improvement in every tool. If Control-M can integrate more seamlessly with AI, which was announced at the BMC roadshow, particularly in the on-premise version, that could be a significant enhancement.

For how long have I used the solution?

I work as a Control-M integration engineer and Control-M lead. I have been working in association with Control-M for the last 12 years. I manage a team of two people who work extensively on Control-M. We use many very critical integrations in our organization, and I look forward to sharing my experience.

What do I think about the stability of the solution?

I would assess the reliability of Control-M as very robust. Control-M has a three-layer architecture, with Control-M server at its core, which is very reliable. We do not see any downtime apart from during upgrades. Our current infrastructure is managed entirely by us, so I am not counting infrastructure-level downtime for Control-M, but as a tool, Control-M remains quite robust and reliable. We have provided many end users, including business users, with access to load their own jobs and execute functions with very few complaints, mostly limited to technical issues from the code perspective rather than the platform itself.

What do I think about the scalability of the solution?

Control-M scales up really well. For example, within our technology team, we focus on integration, working on Azure integration, AWS integration, and a range of technical capabilities. With the growing demand for Azure integration, I believe Control-M can adapt well, especially since we use a data factory model. Control-M now has out-of-the-box job types that simplify orchestration, allowing leaders to be aware of minimal downtime as we transition to Control-M, thereby enhancing the platform's reliability.

How are customer service and support?

I utilize BMC support as my go-to guide. We run a critical business, particularly concerning payments orchestrated inside Control-M. If any issues arise, I raise a critical ticket with BMC support, and someone calls immediately. Just yesterday, we experienced this; support reached out promptly and we began troubleshooting the issue via a Teams call. I find that the intelligence level and technical expertise of BMC engineers are exceptional, which aligns well with our platform.

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

I have been part of our organization for eight years, and I believe Control-M was onboarded around 14 years back. Since then, there has been no looking back.

What was our ROI?

As for realizing a return on our investment, I can provide an example involving our Control-M and ServiceNow integration. ServiceNow is the ITSM platform used for generating various priority tickets. With Control-M, we manage many critical jobs, and if one fails, it can immediately escalate to a priority one incident, requiring the technology team to resolve it without leaving the room. This can be quite hectic, but with Control-M and ServiceNow integration, critical failures generate real-time incidents by calling ServiceNow API. Moreover, the L1 monitoring team can see alerts easily. Consequently, our SLA response time has significantly reduced; for instance, if the L1 team has a 50-minute SLA for a response, they can now respond within five minutes.

Which other solutions did I evaluate?

We evaluated similar solutions. We ran a few POCs with other orchestration provider tools, but Control-M consistently proved superior, particularly as an enterprise-level solution offering comprehensive integration with tools such as ServiceNow and various APIs.

We evaluated several different tools, including JAMS Scheduler and Apache Airflow. What we noticed is that while they offer orchestration capabilities, Control-M stands out due to its criticality and user-friendly GUI features. Additionally, when comparing costs, Control-M offers a competitive price for the services provided along with the package, especially as Control-M continuously evolves towards modern technologies.

What other advice do I have?

I would rate Control-M very high on a scale of 10. This is not just an emotional connection developed over 12 years, but also due to the advanced technology Control-M is implementing, including new AI, data orchestration, security standards, and governance perspectives. Control-M is innovating rapidly with technology.

I would rate Control-M as nine out of ten, leaving one point for improvement, as I believe every software has some scope for enhancement. I wish the whole Control-M team all the best. They are moving very fast towards advanced technologies, and I fully support their efforts as we look forward to utilizing all the features. My overall rating for Control-M is nine out of ten.

Which deployment model are you using for this solution?

On-premises

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

Microsoft Azure
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
Control Administrator at a financial services firm with 10,001+ employees
Real User
Top 20
Jan 14, 2026
Workflow orchestration has automated complex scheduling and large file transfers across regions
Pros and Cons
  • "Control-M is exceptionally useful for building, scheduling, managing, and monitoring production workflows."
  • "For improvements, there is some slowness in terms of logging, as Control-M can be a heavy tool that could benefit from reducing file size."

What is our primary use case?

My main use case for Control-M is working as an administrator and scheduler, setting up AFT jobs with respect to their AFT and OS jobs. Apart from that, I also work on connection profiles and their respective connection setup between two servers, troubleshooting Control-M agents and their respective configurations.

For example, if I want to schedule a specific job for a specific day, Control-M is very useful, allowing me to schedule or set up a job with respect to either a monthly, weekly, or daily basis while considering specific holidays configured on that particular calendar. In addition, if I want to run some script, I can use OS jobs to run a specific script on that server. I can also transfer files between two servers using Managed File Transfer or AFT, transferring files by setting up their configuration on both ends. These are the major tasks I typically work with.

I use these scheduling and file transfer features daily as part of my workflow. I mostly set up jobs in production and non-prod environments, organizing the respective job setups in different categories. For AFT jobs, I typically transfer files from an S3 bucket to a Windows Server or a Unix server to a Windows Server or Unix to S3 bucket, using various platforms such as server to server, server to shared drive, or shared drive to server. In AFT file transfer, I set up connection profiles between two servers for host one and host two, ensuring both hosts communicate properly using Control-M Configuration Manager, also known as CCM. Once the connection is set up, I configure the job using the same Control-M connection profile. I provide details such as source and destination path using that configuration for proper communication.

Managing a Control-M agent is one key part; in case Control-M agent fails, I troubleshoot it using basic troubleshooting skills, such as selecting the troubleshooting option on the agent to reflect the initial level of error. Additionally, I check the library and error log for a specific agent. I also review the new day process (NDP) to ensure that all jobs load daily to avoid production failures. Calendar setup can also be beneficial for any job scheduling. I work on creating new Control-M jobs that operate under the planning and are created concerning the workspace. Furthermore, I track jobs that flashback from the regular cycle. If there are issues with different Control-M servers across my environments in the UK, US, and Asia Pacific, I troubleshoot any server outages or failures.

Regarding measurable improvements since using Control-M, when jobs fail due to specific errors, I am notified promptly, which is essential for handling issues in the production environment. Instead of manually checking all failed jobs, I configure notifications based on priority, enhancing my time-saving efforts across job management.

The biggest lesson learned from using Control-M is understanding how jobs get scheduled within minutes and can function independently without intervention. I have gained insights into configuring job properties such as command jobs, file transfers, file watchers, SAP jobs, and more. My extensive experience of over nine years with Control-M offers me great opportunities, and I look forward to improvements, particularly in AI features relevant to Control-M.

What is most valuable?

In my experience, the best feature Control-M offers is the File Transfer capability, especially useful for larger sizes. I am currently working on a project transferring files larger than 6 GB, which is easy to accomplish. Additionally, the File Watcher job type is valuable as it checks for files in a specific path and triggers actions based on file availability.

For the File Watcher feature, it helps me keep an eye on specific files, triggering transfers as soon as they become available. When setting up a File Watcher job, I ensure specific configurations, such as file availability time and run cycles. The job detects file availability on the platform; once the file is available, the File Watcher job triggers, triggering its successor job. This eliminates the need for constant monitoring of file availability, allowing me to focus on other tasks. Additionally, AFT file transfer for larger volumes is smooth and efficient; other tools take a lot longer for significant file transfers. Control-M lets me track the percentage completed during file transfers as well, enhancing my monitoring. CCM allows me to track all Control-M components effectively, including agents, servers, and add-ons.

Control-M is exceptionally useful for building, scheduling, managing, and monitoring production workflows. It allows me to set up jobs promptly and test them collaboratively with input from my operations and development teams without delays. Control-M enables my IT personnel to refocus on critical operations once jobs are set up for recurrent activities such as monthly or daily runs. For example, one of my teammates established a payroll job that now runs automatically, reducing manual effort and allowing for more focus on different project requirements.

What needs improvement?

For improvements, there is some slowness in terms of logging, as Control-M can be a heavy tool that could benefit from reducing file size. Overall, the tool is great, but it would be helpful if it were lighter and easier to use in my daily operations. In my non-prod environment, I notice significant lag, making it difficult to work effectively. Enhancing the tool's speed and perhaps integrating AI-related features could significantly benefit daily activities.

I choose nine because once the tool is available in a lighter version, it would be even more useful. The features are excellent, but the heaviness of the tool makes it take longer to open and close, causing frequent hangs during multiple activities. For instance, switching from monitoring to history can cause significant delays. This impacts productivity, especially in a production setting where speed is crucial.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Control-M is indeed stable.

What do I think about the scalability of the solution?

Regarding scalability, Control-M scales well, allowing me to operate in four different environments across four regions without concerns.

How are customer service and support?

Customer support from BMC is excellent; whenever I create a case, they respond promptly, ensuring there are no issues. I would rate customer support a perfect ten.

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

Previously, my organization used tools such as OPC and Tivoli before switching to Control-M, as my organization recommended it. The GUI in Control-M is significantly more user-friendly for managing daily activities and job setups.

How was the initial setup?

The deployment of Control-M servers takes about one to two hours on the AWS platform.

What about the implementation team?

For deployment and maintenance, I find that two to three people suffice for maintaining a single server. However, if I need to manage multiple servers across different environments, more staff will be necessary. The requirement really depends on the configuration size and deployment needs.

What was our ROI?

Although Control-M is costly, it does yield a return on investment for larger organizations, but it is not suitable for small teams or individuals. The pricing is quite high, which can be a disadvantage for smaller groups, although the efficiency gains do save time and money overall.

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

Regarding pricing, setup costs, and licensing, I am not heavily involved in those areas, as that falls under my network team. However, the pricing for Control-M seems high compared to other tools, and licensing can be complex, with annual renewals required. The cost has been substantial compared to similar tools I have encountered.

Which other solutions did I evaluate?

Before selecting Control-M, I evaluated other scheduling tools such as Tivoli and Mainframe job track but decided to stick with Control-M for my long-term needs.

What other advice do I have?

For those considering using Control-M, I would advise it is an excellent choice for managing workflows and orchestrating jobs as per project demands. I have been using Control-M in various roles over the past 10 plus years, and I recommend it, provided you understand processes and setups. I give this review a rating of 9.

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.
PeerSpot user
Microsoft Azure Practice Head- MS Azure BU- Global at a tech vendor with 10,001+ employees
Real User
Top 20
Oct 28, 2026
Automation has transformed hybrid workflows and now drives faster incident resolution and SLAs
Pros and Cons
  • "Control-M allows all the necessary data for ISO to SOX compliance to be available."
  • "Customer support is satisfactory."

What is our primary use case?

My main use case for Control-M involves numerous automation workflows. For example, if I want to provision any services in Azure or run a job, I use Control-M to orchestrate. For provisioning, I have multiple workflows which come into the picture starting from the request to the approval to the auto-provisioning, where Control-M helps me automate. The second part involves jobs, where a lot of batch jobs we run is where we use Control-M.

In addition to my use cases, the new thing which we are working on as of now is adding an agentic layer with our Control-M workflow. When there is an event or incident triggered, the workflow works along with an agent for triaging the request, and the workflow helps me create a proper governance and escalation path. The triaging agent, which is an AI agent that is part of Control-M, helps me identify the resolution path for the identified incident or issue. For example, if anything has happened on the server, it gives me the steps to help my support engineer resolve it faster and helps me reduce the MTTR, Mean Time to Resolve.

In my organization, Control-M is deployed in a hybrid cloud configuration, and in my current role, I also sell Control-M to customers where I have to monitor and manage their hybrid cloud and multi-cloud environments.

I manage integration and sequencing of data processing across diverse data platforms and cloud environments by using Control-M, a workflow orchestrator.

While we are currently not using Control-M for AI or ML workloads, we are in discussions about using it in the near future.

Regarding integrating Kubernetes or cloud-native workflows with traditional batch processing, I design solutions using Control-M to orchestrate across different environments and heterogeneous applications, and I propose and design this for multiple organizations or customers as well.

To address compliance requirements like SOX, audit trails, or regulatory reporting, we have very stringent audit and security requirements as a company with 230,000 employees, using Control-M vigorously across all phases.

Control-M allows all the necessary data for ISO to SOX compliance to be available. During audits, we turn to Control-M to gather all data, and the information is readily available and is easy to customize as per our needs.

How has it helped my organization?

Control-M has positively impacted my organization in several ways. I am a solution architect where I solution the operations transformation for any deals with customers who want multi-cloud and hybrid cloud operations management, using Control-M as the core engine for my end-to-end operations management, starting from incident management to operations to knowledge management to SLA management, reporting, and workflow management.

This solution has helped me secure a lot of new wins, and currently, I am managing many customers using Control-M. Monitoring, management, and IT operations and support is a core part of our business and a major revenue earner for us. All customer environments I manage better lead to many benefits in terms of positive responses from customers. We are proactively able to resolve issues, which makes my customers happy, and in this way, I add much more revenue to my business.

My SLA has reduced, and my Mean Time to Resolve has reduced, allowing me to aggressively support customers by committing to a shorter resolution time for P1 incidents. I'm able to take one to two hours to resolve incidents based on the requirement, and the beautiful features that enable me to commit to smaller SLAs to my customers are possible because of Control-M.

What is most valuable?

The best features Control-M offers, which stand out for me, include the workflow, the orchestrator, and the inbuilt automation, plus the ability to schedule tasks. Some processes which run based on events and triggers are core features, and I can schedule it, orchestrate it, and integrate it with any of the workflows, whether it's SAP workload, cloud infrastructure, or processes running on a messaging queue or service bus.

If I want to do anything on the workflow, such as verification and validation, which is one of my cases for my banking customer where there was a fraud detection use case added, the workflow was able to initiate a process that checks on the validity of the content and the document before processing the loans. The new features which are adding a lot of agent-based, AI-based capabilities are really exciting.

Regarding Control-M's AI capabilities, the most important aspect is governance. We discuss governance with almost all customers, and this is where BMC stands out. Governance and reporting are crucial, and we have seen detailed audits and logs generated by Control-M, which allow me to assure my customers that all incidents, records, logs, and resolutions are thoroughly documented in a knowledge repository. This enhances security, helps secure access, and provides the audits and everything necessary for customers' requests.

What needs improvement?

Regarding features, one thing I have requested the team is that there is huge data lying with BMC based on learning from their past experiences on different platforms, such as data centers, cloud, SAP, application support or workflow management.

BMC has billions of records on incidents that have happened and the resolution paths taken. I have requested them to create an ML model, train it using this data, create a dummy part, and create a trained engine which will come as a default attachment or addition to the current BMC offering. For monitoring and managing an environment, I should get a lot of intelligence generated from BMC's own capability because there is a lot of data inside which BMC has.

BMC has been a leader for a long time, so they have immense learning that should come in a model and should prompt my engineer to help him resolve issues faster to improve the SLA, which is the core of my business as I have a stringent SLA signed with my customer. BMC can play a very big role by adding that intelligence layer, agent-based or model-based intelligence that runs continuously to proactively help my engineer and my support staff resolve issues faster.

Regarding improvements for Control-M, I want to request BMC to consider a lighter version, especially when some customers have cost constraints. I understand the SaaS model exists, but a lighter version with simplified features for small and medium enterprises would help penetrate a huge market base, especially with small infrastructure setups of 100 VMs or 200 VMs.

With respect to Control-M's AI capabilities, I have utilized some features in our demo environment, not all, and I am still exploring it. I see it as promising and recognize improvements in place based on the feedback I provided. There are a lot of new features we need to add, including new agents that need to be default features in Control-M.

For how long have I used the solution?

I have been using Control-M for proposing it to a lot of my customers, and we have our own environment where we use Control-M for more than two or two and a half years. We have been using it consistently.

What do I think about the stability of the solution?

Control-M is quite stable, and my engineers are satisfied with using it.

What do I think about the scalability of the solution?

I am very satisfied with Control-M's scalability. Our Azure environment is growing every month, and Control-M has been able to scale accordingly without any issues, automatically recognizing and monitoring any new VMs we provision.

How are customer service and support?

Customer support is satisfactory.

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

Previously, we had a relationship with ServiceNow, utilizing their ITOM operations suite. However, based on the lucrative offer we received from BMC, we decided to switch to Control-M.

What was our ROI?

I have certainly seen a return on investment from using Control-M. It saves a lot of money in terms of effort, time to resolve incidents, triaging, workflow, and approvals. Within one and a half years, I have seen an ROI concerning the cost incurred to set up and start managing complex multi-cloud and hybrid environments, and that is why we have had significant success in selling BMC to our customers.

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

My experience with pricing, setup cost, and licensing includes providing feedback that I need a lighter version with more attractive pricing and setup. There's professional support we leverage a lot, and I look forward to automating and reducing costs going ahead because I have requested Control-M to create a standard SOP and a no-code, low-code integration model, which will expedite my processes and help reduce my costs.

Which other solutions did I evaluate?

We evaluated ServiceNow and ManageEngine among others before selecting Control-M.

What other advice do I have?

The reason I choose nine out of ten for Control-M is that it stands out in terms of flexibility and support I receive from BMC when proposing it to any customer, along with the professional support during implementation, which I find to be the most beautiful part of it. The only point missing from a perfect 10 is on the cost front, where I would like BMC to help me reduce it further for medium to large customers with a VM base of 300 to 500. A lighter SaaS version would assist me a lot.

We have a strong partnership with Control-M. Our company and Control-M have been partners for years. We procure it directly from Control-M or BMC rather than through any other channel.

The advice I would give to others looking into using Control-M is that the beautiful part of Control-M is the orchestrator, the automation engine, and the ability to manage AI and other workloads as well.

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?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner and reseller
Last updated: Oct 28, 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.