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