No more typing reviews! Try our Samantha, our new voice AI agent.
Patrick Byrne - PeerSpot reviewer
Controller Administrator at a government with 10,001+ employees
Video Review
Real User
Top 20
Nov 6, 2025
Has reduced manual errors and tripled operational workflow through automation
Pros and Cons
  • "We've tripled our workflow and we are doing more in less time than we used to previously."
  • "Having more options with regards to scheduling in Control-M would improve it. There are certain scheduling features that aren't available currently in Control-M, which would be nice to be added."

What is our primary use case?

Control-M runs all of our payments, batch, and managed file transfers.

Approximately 250 people use Control-M on a daily basis. Their main roles include schedulers who create batch jobs, testers, and administrators and operators.

Control-M enables us to better support our DataOps and DevOps initiatives because we have a release system every month, which allows us to work more effectively and we're automating that system with Control-M.

Control-M orchestrates workloads across several environments. Currently, we use it across five environments.

Control-M handles complex data pipelines and analytics processes by allowing us to integrate with different services. For instance, we use it with our Power BI for our reporting tools, and for pipelines for release functions as well.

We only use on-premise for the creation and automation of data pipelines with Control-M. We don't have the cloud yet.

What is most valuable?

The main features of Control-M that we appreciate the most are the scheduling and the automation capabilities. When it works, it really works very well for us. Another feature that we appreciate is the file watching service because we interact with many different sections who drop files in various locations. It's great to have that feature to kick off batch when a file becomes available.

Control-M's performance in building, scheduling, managing, and monitoring workflows is amazing. I love Control-M and enjoy working on it. I appreciate how it has automated our workflow because before we had Control-M, it was a manual workflow that was open to user error and took much longer to complete because of the manual checks we had to do before we moved on to our next piece of batch. We've been able to automate it and this has enabled us to triple our workflow.

What needs improvement?

Having more options with regards to scheduling in Control-M would improve it. There are certain scheduling features that aren't available currently in Control-M, which would be nice to be added.

For how long have I used the solution?

I've been using Control-M for six years.

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

What do I think about the stability of the solution?

I assess the stability and reliability of Control-M as very reliable because we very rarely have any downtime. The only time we would ever have any downtime is during our reboots, which we need to do failovers for, and those are very brief. When we are actually doing our batch, I don't remember a time we've had any downtime on our production side.

What do I think about the scalability of the solution?

Control-M scales with the growing needs of my company brilliantly. It's been really good for us. We've added so much to it over the last two or three years. We've added more users, more jobs, and all different types of jobs including OS jobs, MFTs, and file watch, and it's been absolutely no problem for us to add. We've probably doubled our amount of jobs in the last two years, so we've had absolutely no problem with it. It's scaling perfectly.

How are customer service and support?

My experience with customer service and technical support has been positive. Anytime we've had a problem, which is very rarely, or we've had a question, it's always been answered very swiftly or I've looked through the community myself. The community is actually really good, and I really appreciate that side of it because I even contribute on that side. I've never had a problem.

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

We were using an in-house product for running our batch before integrating with Control-M. Control-M enabled us to automate that batch, but it also enabled us to bring in many more things that weren't currently being done by us.

What was our ROI?

The biggest return on investment for me when using Control-M is the reduced errors, quicker runtimes for our batch, and making the job easier.

Which other solutions did I evaluate?

I have not considered other solutions while using Control-M.

What other advice do I have?

Control-M's performance has improved our timing and the speed of the releases. It's halved our release speed basically in the last two years.

The measurable benefits and improvements my company has achieved with Control-M include reduced errors, which is the first big one. Before we used the previous in-house software, we would have a lot of manual errors that would have to be changed manually if there was a change in a variable or anything else. Now it's all automated, and the system runs for itself. We've tripled our workflow and we are doing more in less time than we used to previously.

Control-M has enabled new capabilities and business processes that weren't possible before. Our integration with external partners has become easier due to the MFT capability that we weren't doing before. Now we're able to connect through them. These were manual processes done through moving files manually from one server to another, through different partners, but now we're able to integrate it all as one.

Regarding licensing, we handle licensing through endpoints. We've had to increase our endpoints because we're increasing the amount of workflow we have and the amount of jobs that we have. We've had to increase the number of endpoints we've needed. It's very easy to handle the growth and it's easily done.

I haven't used the Control-M Python client, but I've used a small amount of API.

I have not been using Control-M since I've been in my company because I've been in my company since 2009, and we started using it in 2019.

The impact of the migration to Control-M on our business-critical operations has led to fewer errors and fewer failures. Our biggest success story has been the lack of errors. Even when we do have errors, having the outputs available to us allows us to clearly see what the problem is.

I would rate this review ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Director at Wipro Limited
Real User
Top 20
Oct 28, 2026
Job automation has cut manual workloads and now delivers major cost optimization
Pros and Cons
  • "Control-M has had a positive impact, saving approximately 50% of the cost compared to not using Control-M, where the manual effort increases by 50%."
  • "Regarding Control-M's AI capabilities, I think its governance and security are yet to become live, and I am waiting to see it in action."

What is our primary use case?

My main use case for Control-M is job scheduling for most of my BFSI customers. In banking, I use Control-M for job scheduling to execute day-end jobs and month-end jobs where we do the data processing.

Regarding my main use case for Control-M, it is customer-specific, which I cannot disclose, but Control-M is delivering 50% of productivity or 50% of cost optimization at a very high level, which is very useful.

How has it helped my organization?

My organization is a service integrator, and while we do have Control-M, I am not responsible for that, as I mainly support global customers and use it only for my customers.

For my customers, Control-M has had a positive impact, saving approximately 50% of the cost compared to not using Control-M, where the manual effort increases by 50%.

The cost savings from Control-M are achieved mainly because jobs are automated, so fewer staff are needed, and the primary cost is associated with staff.

What is most valuable?

The best features Control-M offers are job scheduling and job management. I also saw in the demo about the future-ready model where you can leverage orchestration, doing agentless and agentic AI, all of which is going to enable artificial intelligence infusion. I am looking forward to taking it further.

In my day-to-day work, I find job scheduling and job management the most useful because that is the foundation and that is the day-to-day responsibility.

Regarding the features, I integrate most of my customers with the BFSI systems, and for other customers, I use the SAP integrations.

What needs improvement?

For improvements, BMC is already taking a lot of steps with the agentic AI infusion initiatives, and I want to see it live. I just saw a demo, and right now, I believe BMC is going in the right direction, but once I see it in action, I can provide more detailed feedback.

For how long have I used the solution?

I have used Control-M for around three years in a hands-on capacity, after which I moved into leadership roles. I have known about it for ten years total.

How are customer service and support?

I do not have any additional improvements to add; it is all good, and BMC support is excellent with no hesitation.

What other advice do I have?

On a scale of one to ten, I would rate Control-M a nine.

I gave it a nine because there is always room for improvement; I should give it a ten, but I gave it a nine.

Regarding Control-M's AI capabilities, I think its governance and security are yet to become live, and I am waiting to see it in action.

For Control-M's AI capabilities, I think of its accuracy and reliability of output, and I need to see it in action. As of now, it is still to be evaluated.

Control-M is deployed in my organization, but I am not responsible for its implementation. However, regarding my customers globally, I have worked with all models including local implementation, on-premises implementation, hybrid implementation, and public cloud. We do all types.

For my customers who use public cloud or hybrid cloud, they most often use majorly AWS and Azure, and GCP is a little lower, to be transparent.

The advice I would give to others looking into using Control-M is that I pitch Control-M to most of my customers or most of the new opportunities where I work because, in today's scenario, cost optimization is the key, and Control-M helps us achieve that.

Which deployment model are you using for this solution?

Hybrid Cloud

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

Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Last updated: Oct 28, 2026
Flag as inappropriate
PeerSpot user
Buyer's Guide
Control-M
November 2026
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
921,774 professionals have used our research since 2012.
Ashak Ali Khan - PeerSpot reviewer
Senior Technical Manager(IT) at Financial Sector
Real User
Top 5
Oct 6, 2026
Automation has reduced manual job handling and provides centralized control for complex workflows
Pros and Cons
  • "A lot of human work has been automated through Control-M, although we do not have quantification of the exact savings."
  • "Control-M should have AI integration so that it can sense error messages and take appropriate actions instead of requiring human intervention."

What is our primary use case?

Our primary use case for BMC Control-M is enterprise job automation and scheduling. We use Control-M to centrally manage and monitor a large number of jobs across the organization, including scheduling, execution, failure handling, job resumption, and alerting. It provides end-to-end automation and centralized control of critical batch workloads.

How has it helped my organization?

Control-M has improved operational efficiency by automating and centrally managing job scheduling, reducing manual intervention, minimizing failures and downtime and providing faster alerts and recovery of failed jobs.

What is most valuable?

The features I appreciate most about Control-M are its user-friendly interface and simplicity. It is not overly complex and the built-in APIs make it easy to use and integrate with other technologies.

For DataOps and DevOps processes, integrating Control-M with other technologies is relatively easy with an overall medium level of integration complexity.

What needs improvement?

The version of Control-M I was using did not have AI capabilities. Control-M would benefit from stronger AI integration that can analyze error messages, identify the root cause and take appropriate corrective actions without human intervention. Currently, some basic errors still require manual intervention, which AI could help minimize.

For how long have I used the solution?

I have been working with BMC Control-M for more than 15 years, with my first implementation experience being for a leading Saudi telecom operator.

What do I think about the stability of the solution?

I rate the stability of Control-M as a stable 10. Control-M is a stable product.

What do I think about the scalability of the solution?

The number of users using Control-M is around 50 plus. We have a centralized administrator who has a team working with different stakeholders, making this a centralized tool.

Control-M is scalable. We can do both scale-out and scale-up. Both options are available.

How are customer service and support?

I rate Control-M support around nine out of 10.

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

We have been using Control-M since the beginning. We explored other products in parallel, but this was a fresh installation with no migration.

What was our ROI?

Regarding ROI with Control-M, we have not quantified it, but it has definitely saved manual work. A lot of human work has been automated through Control-M, although we do not have quantification of the exact savings.

Which other solutions did I evaluate?

When I compare Control-M with other solutions such as Apache, ActiveBatch, Broadcom, and HCLTech HWA , I find that Control-M stands out, particularly in terms of product support and global support capabilities.

What other advice do I have?

I definitely recommend Control-M to others and some customers have already purchased Control-M based on our recommendation. I give this review an overall rating of 10.

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: Oct 6, 2026
Flag as inappropriate
PeerSpot user
Stefan Iani - PeerSpot reviewer
Bmc Control M Administrator at WorldPay US
Real User
Top 20
Jul 22, 2026
Workflow orchestration has become deeply integrated with DevOps and simplified job deployment
Pros and Cons
  • "Regarding pricing, I consider Control-M to be the most expensive scheduling tool, however, it's worth it, as you buy something powerful and complete."
  • "In terms of improvement areas for Control-M, the only concern I've seen is some mismatch in documentation, which is not ideal."

What is our primary use case?

My use case for Control-M is that I am a Control-M administrator, and I use it for everything, starting from installing, upgrading, and configuring it, to defining jobs and file transfers, so almost everything.

What is most valuable?

The best feature of Control-M is that it has a lot of integrations with different other tools; I don't think there is any other workflow orchestrator that has so many integrations. I think it has the most, and if you don't have one, you have the possibility to create the integration with whatever tool you want. That's one of the best things I've seen in Control-M.

The ease of integrating Control-M for my DataOps and DevOps processes is actually great because it has native integration with Jenkins and CI/CD pipelines, so you don't have to work hard to integrate this. In my current company, we have Control-M integrated with Jenkins, and everything gets deployed via Jenkins without accessing Control-M, which is honestly the best way to do it.

Building, scheduling, and managing production workflows with Control-M is easy. Control-M also has a feature called Jobs as Code, so if a developer wants to create a job, they don't need to have extensive Control-M knowledge. Developers can create Control-M jobs and flows via code by scripting them in JSON files, making it not so difficult.

What needs improvement?

In terms of improvement areas for Control-M, the only concern I've seen is some mismatch in documentation, which is not ideal. You may easily find things that happen on the application, but you can spend time or have to raise a case to BMC to find out what went wrong, which is something they need to improve.

For how long have I used the solution?

I have been using Control-M since 2005, so it should be 21 years.

How are customer service and support?

My relationship with BMC is transformative rather than transactional.

BMC serves as a strategic partner and trusted advisor, helping my company map migrations and deployment. They also developed an integration module specifically for our company based on our requirements.

The integration process with Redwood was easy, didn't take long, and wasn't too complex, as there weren't many jobs involved.

I rate the technical support of Control-M as a nine.

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

I have migrated from Redwood some time ago.

How was the initial setup?

In my opinion, the deployment process is easy; it is not difficult to deploy Control-M.

The deployment of Control-M takes hours.

What about the implementation team?

Maintaining the Control-M system is easy.

What was our ROI?

I honestly have no idea about precise return on investment percentages, but I think the Jobs as Code aspect and the integration with Jenkins reduce the time of deploying things and training people to use the application to create jobs.

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

Regarding pricing, I consider Control-M to be the most expensive scheduling tool. However, it's worth it, as you buy something powerful and complete. In my opinion, despite being expensive, it is one of the best orchestrator tools available.

Which other solutions did I evaluate?

When comparing Control-M with other solutions such as Broadcom or ActiveBatch, I find that Control-M has a huge integration capability with many tools that other competitors do not have, particularly the native integration with Jenkins and CI/CD pipelines, which other tools lack.

What other advice do I have?

The easy integration of Control-M with DevOps tools has made the decision to keep Control-M as the main scheduler in my organization a straightforward one.

Control-M is deployed in a hybrid model in my organization.

Control-M is deployed on AWS.

My organization is an enterprise business using Control-M.

I would recommend Control-M to other users and suggest they take it. They can conduct a proof of concept, but I don't think they'll find anything more complex than this tool, which is expensive but has everything you need. I rate this product a ten overall.

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.
Last updated: Jul 22, 2026
Flag as inappropriate
PeerSpot user
RafaelFerreira2 - PeerSpot reviewer
Workload Automation Engineer at Mphasis
Real User
Top 20
Feb 15, 2026
Unified automation has improved cross-application workflows and simplified complex file transfers
Pros and Cons
  • "In general, the ability to check all your processes in a unified view that Control-M provides is what I appreciate the most about it."
  • "The quality of support is fast during production emergencies, but it can take longer when issues are not critical, with interactions sometimes taking several days."

What is our primary use case?

I have several use cases for Control-M. I have been implementing Control-M for a long time in several enterprises in Brazil, and then five years ago I moved to the US. I started working here in the US as well. I have several use cases for insurance companies and bank companies in Brazil, and currently, I am working with Bank Charles Schwab using this tool to transfer internal files between systems and applications.

We also have user-defined transfers to move files to business partners. Overall, I have been using this solution for 17 years and have many use cases to speak of.

When I joined Bank Charles Schwab, Control-M was already implemented, but I also work on implementing Control-M from scratch.

Recently, I did an integration involving Control-M with Pentaho and Power BI. Even though Control-M did not have the plugin for Pentaho, I managed to run a data pipeline using scripts and successfully integrate it into Power BI dashboards.

What is most valuable?

In general, the ability to check all your processes in a unified view that Control-M provides is what I appreciate the most about it.

Control-M helps to integrate processes across various applications in big enterprises, making it significantly easier since you have a single point of control and can see failures and impacts on the flow.

Now, with the new plugins that they launch every month, it is easy to integrate with technologies for my DataOps and DevOps processes.

What needs improvement?

I think they are going in the direction of managing data that Control-M orchestrates. Currently, it is hard to get data from the process that Control-M is processing.

The ease of deploying Control-M depends on the architecture chosen, as some configurations can require more setup.

For how long have I used the solution?

I have been working with Control-M for 17 years overall in my career.

What do I think about the scalability of the solution?

In terms of scalability, I think it is good. I have seen effective escalation when necessary during issue resolution.

How are customer service and support?

I have contacted BMC technical support, especially when I cannot solve certain issues myself, but I have a good handle on it due to my long experience.

The quality of support is fast during production emergencies, but it can take longer when issues are not critical, with interactions sometimes taking several days.

They have limited support for native language issues, which can create challenges for non-English speakers.

How would you rate customer service and support?

Negative

What about the implementation team?

Usually, I handle the deployment myself, but I need a team to implement large numbers of jobs after the deployment.

Which other solutions did I evaluate?

I do not have experience using alternatives to Control-M, as I was directly presented with Control-M when I started working with workload automation.

What other advice do I have?

Control-M tends to be the most expensive compared to other competitors. However, I believe it is worth the price since it delivers the most.

It requires some maintenance on my end occasionally, especially when compliance or security updates are needed.

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?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
reviewer2518842 - PeerSpot reviewer
Associate Architect at a tech services company with 10,001+ employees
Real User
Top 10
May 17, 2025
An effective solution with easy deployment, good API integration, and excellent support
Pros and Cons
  • "The most effective feature of Control-M is the API integration."
  • "Control-M improved our organization significantly."
  • "The only thing that comes to mind is the cost. If it could be more competitive, it would be great."
  • "Its cost can be more competitive. One of the main things customers look at is the cost. It's not affordable. The cost is very high, according to my customers."

What is our primary use case?

From an administrative standpoint, we are mostly engaged in upgrading, downgrading, and fixing the issues on a day-to-day basis, such as integration with the cloud functionalities. 

My only objective is that the application is up and running 99% of the time. I will make sure that it is not down, and it does not impact my application teams. If it goes down, it has a major impact on SLA, financial, and everything, so I make sure this is up and running 99%.

How has it helped my organization?

Control-M improved our organization significantly. We integrated it with our DevOps model, which saved us around 32 FTEs in resource costs. We also integrated with AWS Glue jobs or other clouds, such as Informatica. It's compatible.

Control-M supports our daily IT automation tasks. It is the blood for my entire organization, integrating with every app team, including HR.

Control-M offers pretty good REST API connectivity with other solutions.

What is most valuable?

The most effective feature of Control-M is the API integration. BMC is focusing on API integration. It's also very easy to deploy and identify issues. 

What needs improvement?

I don't see any areas where Control-M could be improved because they are doing well. The support is awesome. We have a weekly connection with our BMC tech focal, so I don't see any improvement needed. Things are going well. They are already working on GenAI integration with Control-M. The only thing that comes to mind is the cost. If it could be more competitive, it would be great.

For how long have I used the solution?

I have been using Control-M for almost 15 years.

What do I think about the stability of the solution?

The stability of Control-M has been good so far. However, the testing and development phases need to be more rigorous before releasing patches. I would rate it an eight out of ten for stability.

What do I think about the scalability of the solution?

It's scalable. I would rate it a nine out of ten for scalability.

It's used across multiple departments. There are more than 3,000 users.

How are customer service and support?

Control-M's technical support is very helpful. The immediate acknowledgment and solutions provided by BMC's support team make it stand out compared to other tools. I would rate them a ten out of ten.

How would you rate customer service and support?

Positive

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

My current organization has been using Control-M for 20-25 years, but I have used Autosys and IBM Workload Scheduler previously.

How was the initial setup?

The initial deployment of Control-M was straightforward. We started with version 6.4 and are now at 9.0.21.304.

When I started, it used to take about eight hours. We are now able to do it within 30 minutes, including the downtime.

We are using it on-premise because their SaaS solution is not capable of handling our workload. Its maintenance mostly involves upgrades.

What about the implementation team?

I handle the deployment. We have about five members involved in the deployment of Control-M from our side, including an administrator.

What was our ROI?

After implementing Control-M, there should be cost savings or efficiency gains.

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

Its cost can be more competitive. One of the main things customers look at is the cost. It's not affordable. The cost is very high, according to my customers. The licensing cost is very high, and they often consider switching to IBM Workload Scheduler or other options.

There aren't any extra expenses after purchasing Control-M. We have never paid any extra cost unless we needed additional packages, and the team was able to help us with that.

Which other solutions did I evaluate?

Nothing comes to mind regarding alternatives to Control-M, but I see all the features available in it since it is a leader. However, other solutions might be more cost-effective.

What other advice do I have?

If you want to implement Control-M in your business, the first thing is to look at your budget. Checking affordability is key. Control-M has a lot of features, more than just scheduling batch jobs. 

The biggest lesson I have learned from using Control-M is that you need to have patience. Errors or issues cannot be resolved without developer assistance, but once you get their help, you learn a lot.

I would rate Control-M a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. Integrator
PeerSpot user
Abhishek Nayak - PeerSpot reviewer
Soc L1 Engineer at Softcell Technologies Limited
Real User
Top 5Leaderboard
Nov 11, 2026
Automated security data pipelines have improved threat visibility and streamline nightly operations
Pros and Cons
  • "The standout feature of Control-M for me is its end-to-end workflow dependency mapping combined with its managed file transfer capabilities."
  • "Sometimes, brief temporary network drops trigger immediate failure notifications before Control-M's internal retry logic has a chance to kick in and successfully complete the task."

What is our primary use case?

My primary use case for Control-M is heavy-duty security data pipeline orchestration and automated workflows running strictly on-premises.

A great example of a workflow I run recently on Control-M is my automated nightly security log ingestion and threat intelligence staging pipeline for an on-premises enterprise client.

My main use case for Control-M is on-premises security data pipeline orchestration.

Control-M supports several core services and business use cases across organizations from a broad enterprise perspective.

Regarding specific workflows, while dedicated data science platforms have native pipeline tools and orchestration, ML operations across a hybrid enterprise environment often requires integrating platforms like Amazon SageMaker or Google Cloud Vertex AI directly with the broader AI and security infrastructure.

My organization utilizes Control-M as a core operational backbone for orchestrating sensitive on-premises security data pipelines, automated managed file transfer routines, and local log staging tasks that feed directly into my SIEM ecosystems like Splunk and FortiSIEM.

I use Control-M to orchestrate workloads across multiple environments, mostly on-premises and virtual.

How has it helped my organization?

The biggest positive impact I have seen from Control-M is zero pipeline blind spots because everything runs on strict dependency mapping, and log ingestion and threat intelligence syncs never fail silently.

While I don't look at the business ROI dashboards all day, from a day-to-day SOC operation standpoint, I track a few key metrics and outcomes with Control-M.

What is most valuable?

The standout feature of Control-M for me is its end-to-end workflow dependency mapping combined with its managed file transfer capabilities.

Regarding AI capability with Control-M, while my primary focus with Control-M is handling secure, on-premises data pipelines, I have also looked at AI capabilities and security.

Control-M utilizes its built-in AI assistant like Jet and Natural Language Processing to help build and troubleshoot workflows.

In my SOC and MSSP environment, I rely on Control-M's built-in approval workflows and risk gating to ensure that high-impact automation or pipeline modifications do not go live unmonitored.

Control-M smooths and modernizes workflows by shifting from traditional GUI-driven configuration to an API-first workflow-as-code model in terms of ease of integration with technology of data operations and DevOps processes.

Control-M, through the lens of business user visibility and stakeholder transparency, offers a strong bridge between raw technical execution and high-level operational outcomes.

Control-M supercharges my data operations and DevOps initiatives by bridging traditional IT orchestration and application delivery.

When integrating AI and ML operations workflows into my security operations, Control-M acts as a critical runtime governance layer in terms of integration governance.

What needs improvement?

From a SOC perspective, there are a couple of areas where Control-M could be improved for security operations.

Sometimes, brief temporary network drops trigger immediate failure notifications before Control-M's internal retry logic has a chance to kick in and successfully complete the task.

For how long have I used the solution?

I have been using Control-M for around three to four months.

What do I think about the stability of the solution?

For workflow automation, data pipelines, and MFT operations, stability is a core metric that separates Control-M from lightweight schedulers and native cloud cron tools.

What do I think about the scalability of the solution?

Control-M achieves enterprise-grade scalability through its decentralized three-tier architecture, allowing my MSSP to seamlessly scale from tens of nodes to thousands of simultaneous endpoints.

How are customer service and support?

For a mission-critical orchestration engine, Control-M customer support is vital for my MSSP SOC.

How was the initial setup?

When deploying Control-M in an MSSP or SOC environment like mine, I follow a structured phase approach focused on local control and security.

For my specific use case, I deployed Control-M strictly on-premises.

What about the implementation team?

Deploying and managing an on-premises Control-M environment within a hybrid SOC or MSSP structure requires a team highly specialized in it because Control-M acts as the foundational mission-critical platform.

What was our ROI?

The automated threat intelligence and log staging pipeline transformed my operations. Before Control-M, my MSSP SOC relied on a custom chain of scripts.

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

When evaluating Control-M from an enterprise and MSSP budget perspective, it sits firmly within the category of premium mission-critical infrastructure software.

What other advice do I have?

I gave Control-M an 8 out of 10 because it is an absolute powerhouse for on-premises security data pipeline orchestration, managed file transfer, and strict dependency mapping.

Control-M is used by a few specific roles depending on whether they are building, monitoring, or auditing the work.

When I integrate AI workloads and drive adoptions, especially around automated security data pipelines and orchestrations, I focus heavily on balancing agility with strict security controls.

Assessing the creation and automation of data pipelines across on-premises environments requires balancing infrastructure control, deterministic reliability, and strict security compliance.

My advice for engineering teams and organizations evaluating Control-M, especially those operating in high-stakes environments such as security operations, MSSPs, or complex data engineering pipelines, is to adopt a jobs-as-code approach from day one.

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: Nov 11, 2026
Flag as inappropriate
PeerSpot user
Solution Architect at a tech vendor with 10,001+ employees
Real User
Top 20
Oct 28, 2026
Automation has reduced errors and boosted data workflows for complex cloud integrations
Pros and Cons
  • "Control-M has positively impacted my organization by reducing errors and increases our productivity by reducing errors by 60% and increasing productivity by 80%."

    What is our primary use case?

    My main use case for Control-M is that we are building software products. A specific example of how I use Control-M in one of my software products is in in-building solutions for data-syncing software.

    I manage the integration and sequencing of data processing across diverse data platforms and cloud environments with various techniques using AWS integration and data security.

    My organization is currently using Control-M to support AI or ML workloads. My organization uses Control-M to address compliance requirements with audit trails.

    How has it helped my organization?

    Control-M has positively impacted my organization by reducing errors and increasing our productivity. Specifically, it reduces errors by 60% and increases productivity by 80%.

    Control-M has facilitated the integration of Kubernetes or cloud native workflows with traditional batch processing within my organization. We are working with a huge amount of data, so it is very helpful for us to integrate Control-M in our team.

    What is most valuable?

    The best features Control-M offers are security, data migration, and integration. These features help us significantly as we are creating software for industrial applications.

    I would like to add that Control-M is easy to use. Regarding Control-M's AI capabilities, I think its governance and security are very good. The accuracy and reliability of Control-M's AI output are also very good.

    What needs improvement?

    I believe there are no improvements needed; everything is good. I can confirm that there are no small improvements that could be made.

    For how long have I used the solution?

    I have been using Control-M for nearly three years.

    What do I think about the stability of the solution?

    Control-M is stable.

    What do I think about the scalability of the solution?

    Control-M's scalability is very good.

    How are customer service and support?

    The customer support is very good. I would rate the customer support a 10.

    What was our ROI?

    I have seen a return on investment. Specifically, I have achieved 60% time saved and 80% money saved.

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

    My experience with pricing, setup cost, and licensing is good.

    Which other solutions did I evaluate?

    Before choosing Control-M, I did not evaluate other options; the decision was straightforward.

    What other advice do I have?

    On a scale of one to 10, I would rate Control-M overall a 10. I chose 10 because it is good. Control-M is deployed in my organization using private, public, and multi-cloud. We use Azure and AWS as cloud providers for Control-M. My advice to others looking into using Control-M is that I recommend them to buy it. It is a 10 out of 10.

    Which deployment model are you using for this solution?

    Hybrid Cloud

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

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Oct 28, 2026
    Flag as inappropriate
    PeerSpot user
    Principal Software Engineer at a tech vendor with 10,001+ employees
    Real User
    Top 20
    Oct 28, 2026
    Modernization of batch workflows has improved cloud integration but still needs clearer guidance
    Pros and Cons
    • "Control-M has positively impacted our organization by helping to modernize the batch processes and implementing event-driven workload automation."
    • "Customer support needs improvement, as they should analyze issues before sending documentation instead of sending random documents."

    What is our primary use case?

    My main use case for Control-M is maintaining the Control-M infrastructure as part of the batch mission, where I perform upgrades, migration, automation, API integrations, and cloud-native integrations.

    A recent project I implemented using Control-M involved Kubernetes for an EKS site, where I enabled the additional integrator plugin on top of the EKS agent, the Control-M agent, and Control-M for Kubernetes, and we executed the project successfully.

    We manage the integration and sequencing of data processing across diverse platforms and cloud environments by utilizing Control-M for Lambda, AWS Batch, Step Function, and Azure, with agents deployed in EC2 instances.

    Our organization does not currently have Control-M in our roadmap for AI or ML workloads, but we are testing Control-M for AI as an initial POC, and we are looking forward to AI-native or ML functionalities for anomaly detection.

    To address compliance requirements, we follow the regular TLM and end-of-life components flagged in Fidelity and use that to ensure follow-up with BMC for necessary fixes.

    How has it helped my organization?

    Control-M has positively impacted our organization by helping to modernize the batch processes and implementing event-driven workload automation.

    The benefits of modernization and workload automation have included improvements in our SLA, more modernization of the application, and integration with many cloud-native solutions that help various business units achieve their outcomes.

    Control-M has facilitated the integration of Kubernetes or cloud-native workflows with traditional batch processing by allowing teams to deploy the Control-M agent in their applications and modernizing it with scaling features, which has resulted in cost reductions.

    What is most valuable?

    Control-M offers great features, including integrations with native cloud components.

    What I value most about the integrations with native cloud components are Control-M for EKS, Control-M for AWS Batch, Control-M for AWS Step Functions, and Control-M for Lambda.

    Flexibility in Control-M is essential, and we utilize the Automation API for taking actions on jobs, such as holding and adding conditions, and for most of the reporting.

    What needs improvement?

    One area that Control-M can improve is that some cloud-native integrations do not have the IAM role, so we face challenges due to some limitations within our organization and a lack of testing from BMC's side.

    We need clearer documentation on what is supported and what is not, including future enhancements and release dates, so we have a clear vision on when we can test that plugin.

    Currently, we are conducting the POC in Control-M AI Jet but face challenges to implement it because it requires an AWS Bedrock account with a backend Claude Sonnet model and also MCP server, which presents some difficulties.

    For how long have I used the solution?

    I have been using Control-M for the past 10 years.

    What do I think about the stability of the solution?

    Control-M is stable.

    What do I think about the scalability of the solution?

    I would rate Control-M's scalability a three, as we are on-premises and have limited options for scaling.

    How are customer service and support?

    Customer support needs improvement, as they should analyze issues before sending documentation instead of sending random documents.

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

    My experience with pricing, setup cost, and licensing is limited, as I know what is being charged for how many jobs per year or month.

    What other advice do I have?

    On a scale from one to 10, I would rate Control-M a seven.

    I chose a rating of seven out of 10 based on how we use Control-M and its ease of use, whereas I didn't give a 10 out of 10 because there need to be improvements in documentation and understanding the various organizational requirements to provide immediate solutions.

    Regarding the accuracy and reliability of Control-M's AI output, we haven't started our testing because we need to enable the AWS Bedrock account with the Claude Sonnet model, but the deployment has been done, and we have an open case with BMC that we are working on.

    My advice for others looking into using Control-M is to perform intense testing before moving anything to production, as there might be known or unknown bugs that are not documented.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Oct 28, 2026
    Flag as inappropriate
    PeerSpot user
    Software Developer at a government with 11-50 employees
    Real User
    Top 20
    Oct 29, 2026
    Unified automation has reduced issue analysis time and provides clear, centralized observability
    Pros and Cons
    • "Control-M has positively impacted my organization, as instead of having multiple chunks and segments of independent standalone products, I have been using Control-M's suite of tools, whether it is workflow automation, agent orchestration, or data orchestration from across multiple sources, helping me control and coordinate all of these in one place."
    • "Regarding features of Control-M, I think when it comes to the UI and UX, it could be made a bit more simple and sophisticated because I feel at times the people who aren't proficient in the software would find it hard to navigate through."

    What is our primary use case?

    My main use case for Control-M is workflow automations in my organization, primarily for in-house operations.

    A specific example of a workflow automation I've set up using Control-M is for lead evaluation, where I've deployed a form that passes through multiple nodes and evaluates the fit of the given candidate. If they are a potential prospect to us, that is when we get in touch with them, or otherwise we direct them to other solutions of ours. In some cases where they do not seem to fit in any of our use cases, we decline them with a humble reply.

    In addition to my main use case, after collecting raw data with Control-M, I use nodes to primarily filter and clean out unwanted information, thus helping me use it in analytical insights and train my models personally.

    How has it helped my organization?

    Control-M has positively impacted my organization, as instead of having multiple chunks and segments of independent standalone products, I have been using Control-M's suite of tools, whether it is workflow automation, agent orchestration, or data orchestration from across multiple sources. I've replaced them with a one-stop solution that Control-M offers, helping me control and coordinate all of these in one place.

    Specific outcomes I can share include that earlier, when I had to look out for services and how they had been impacted, the DevOps part, the infrastructural control, and the correlated things used to take a lot of time, as I would have to log in, debug, check out the logs, and analyze and fix if anything was needed. With Control-M, it has become much easier, cutting down the time spent on issue analysis by more than 50 to 60 percent. Earlier it took me about 20 to 30 minutes per service for analysis, but now it hardly takes a couple of minutes or maybe five to six minutes at most.

    What is most valuable?

    The best features Control-M offers include the AIOps suite of products, which is really helpful to me, and the observability part of Control-M is also pretty helpful. It helps in investigating and checking out the current status of my deployments and my infrastructure. Having a one-stop solution for all of these is pretty helpful, avoiding me navigating through multiple services, reducing wastage of time and helping me easily identify issues. The dashboards that have been provided briefly help me as well.

    Control-M's dashboards and observability features help with my daily tasks and troubleshooting, as when some service goes down, it requires me or my teammate to dive deeper and analyze if something is wrong. However, with Control-M and its centralized dashboard, it's much easier to glance through and analyze what the issue is. The ability to use Jet, the AI beacon feature available on Control-M, helps me query it in natural language and get results, thus reducing and cutting down time on resolution of issues.

    What needs improvement?

    Regarding features of Control-M, I think when it comes to the UI and UX, it could be made a bit more simple and sophisticated because I feel at times the people who aren't proficient in the software would find it hard to navigate through.

    In terms of improvement for Control-M, I think you could make use of agents on the plane, meaning it shouldn't just be restricted to a chatbot. If you ask Control-M's AI to do something, it should rather get it done instead of prompting or navigating the user through, which would be quite helpful in non-technical layman use cases.

    For how long have I used the solution?

    I have been using Control-M for about four to five months.

    What other advice do I have?

    My advice for others looking into using Control-M is that if they do not want the headache of operating and controlling multiple tools, Control-M is the best solution for them.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Oct 29, 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.