Unified Monitoring: A single, intuitive graphical interface allows me to track workflows across multiple platforms, which significantly reduces manual monitoring and helps prevent operational bottlenecks. Review collected by and hosted on G2.com.

Administrative Overhead: Upgrading the system and managing the underlying components (such as server services and databases) requires specialized, hands-on administrative expertise and ongoing attention. Review collected by and hosted on G2.com.

Well what I like the most and what the upsides are that it reduces manual effort and simultaneously makes efficient better. I think it's overall efficient Review collected by and hosted on G2.com.

The reporting tool still needs a lot of improvement. It was supposed to get better with the upgrade, and it really didn't get better. It needs help, because it's such a useful thing to have. It needs to be more powerful and easier to use. Review collected by and hosted on G2.com.

I like Control-M for its centralized visibility and reliability. The ability to manage complex workflows across different systems from a single interface makes operations much smoother. I appreciate its strong monitoring and alerting features, which help us quickly identify and resolve issues before they impact the business. The centralized visibility gives us a single dashboard to track all jobs and workflows across servers, applications, and environments. Instead of checking multiple systems, we can see job status, dependencies, and bottlenecks in one place. The strong monitoring and alerting features are valuable because we get real-time notifications if something fails or is delayed, allowing us to respond quickly and reduce downtime. Control-M integrates with our databases, ETL tools, and cloud platforms to orchestrate end-to-end workflows. Connecting it with monitoring and ticketing systems helps streamline operations and reduce manual intervention. The platform has proved stable and reliable once set up properly, and it's beneficial for managing complex, interdependent jobs across multiple systems. Review collected by and hosted on G2.com.

While Control-M is very powerful, there are a few areas that could be improved. The initial setup and configuration can be complex and time-consuming, especially for new teams. The user interface, although functional, can feel a bit heavy or less intuitive at times. Additionally, licensing and overall cost can be a concern for smaller teams or organizations. In Control-M, I think the user interface could be made more intuitive and modern. Navigation sometimes requires multiple clicks, and new users may find it difficult to quickly locate job definitions, logs, or dependency views. A more streamlined dashboard with customizable widgets and simpler workflow visualization would improve usability. Additionally, better in-product guidance, clearer error messages, and more contextual help would make troubleshooting easier—especially for teams that don’t have deep administrative experience. Review collected by and hosted on G2.com.

Cross-platform orchestration, complex dependency/SLA management via BIM, and modern JSON Jobs-as-Code make Control-M excellent at turning chaotic enterprise batch processes into structured pipelines. Review collected by and hosted on G2.com.

It’s an incredibly powerful tank, but sometimes you just want a nimble car. The administrative overhead and steep price tag are its biggest drawbacks. Review collected by and hosted on G2.com.

Control-M is great because it provides centralized job scheduling and visibility, making it easy to manage complex workflows from one place.

It’s also highly reliable and scalable, automating workflows across cloud and on-prem systems while reducing failures and improving SLA performance. Review collected by and hosted on G2.com.

Control-M can feel outdated and complex, with a steep learning curve and clunky UI compared to modern orchestration tools.

It’s also expensive and less developer-friendly, making version control and flexible pipeline design harder. Review collected by and hosted on G2.com.

I like Control-M’s reliability and centralized scheduling. It makes managing complex job workflows easy, provides clear monitoring, and ensures smooth, automated execution with minimal manual intervention. Control-M solves scheduling complexity, reduces manual errors, ensures reliable job automation, improves visibility, streamlines dependencies, and guarantees consistent execution across environments. Its reliability ensures my Java automation jobs run consistently without failures, building trust in nightly test executions and releases. The centralized scheduling lets me manage all workflows from a single dashboard, making it easy to track dependencies, monitor job status in real time, and quickly troubleshoot issues. This saves time, reduces manual effort, and improves overall test pipeline efficiency. Review collected by and hosted on G2.com.

Control-M’s interface can feel complex for beginners, setup requires expertise, troubleshooting sometimes lacks clarity, and licensing costs can be relatively high. Review collected by and hosted on G2.com.

I like Control-M's reliability and centralized job management, which ensures that workflows run consistently without frequent issues, providing confidence that critical jobs will execute on time. The monitoring and alerting features provide real-time visibility into job status, making it easy to track running, completed, or failed jobs. If a job fails, it quickly alerts, allowing for prompt issue identification and resolution. I also really appreciate how Control-M handles job dependencies and complex workflows smoothly, even with multiple systems and applications involved, which reduces the need for manual coordination. Overall, Control-M simplifies daily operations, reduces stress for support teams, and enhances overall efficiency by automating and streamlining workload management. Review collected by and hosted on G2.com.

While Control-M is a very powerful and reliable tool, there are a few areas where it could be improved. The biggest challenge is the initial learning curve. For new users, especially beginners, the UI and configuration options can feel a bit complex at first. If onboarding and tutorials were more beginner-friendly, it could make adoption easier. Another area is the user interface, which sometimes feels slightly dated and overwhelming due to the number of options available on a single screen. A more simplified or customizable UI would improve the overall user experience. Additionally, the licensing cost is on the higher side, which may not be ideal for small teams or organizations. More flexible pricing options would make it accessible to a wider range of users. That said, these are minor concerns compared to the stability and functionality Control-M provides in enterprise environments. Review collected by and hosted on G2.com.

Control-M is a powerhouse orchestrator that simplifies complex enterprise workflows by connecting diverse technologies into a single automated stream. I appreciate the Automation API, which treats complex enterprise workflows as simple versionable code. Treating workflows as versionable JSON code aligns automation with my React development cycle, enabling seamless CI/CD integration with peer review and instant rollback. I integrate Control-M with GitHub and Jenkins to automate deployments, ensuring my React frontend only updates once backend data pipelines successfully finish. The switch to Control-M from legacy tools like AutoSys or Tidal offers better cloud integrations and a Jobs as Code API approach. Review collected by and hosted on G2.com.

I don't like the high licensing costs, which can be a hurdle. The GUI is outdated, making it less appealing for modern and fast-moving frontend development. Also, the initial setup is complex, often requiring significant infrastructure configuration before developers can start coding workflows. Review collected by and hosted on G2.com.

Control M provides Automatic Job Scheduling and many more features like this which help me as a Data Engineer to reduce day to day task. It is nice tool for Data Engineer. Review collected by and hosted on G2.com.

Very difficult to understand for new users because we build for users if it's not understood by normal users thens it's not use so for me it's UI is not good. Review collected by and hosted on G2.com.

I use Control-M to monitor automated jobs and manage workflow, which is very helpful for scheduling tasks and handling alerts. I like that it ensures smooth and reliable application operation daily. Control-M reduces manual monitoring, prevents job failures, improves workflow visibility, and ensures timely task execution. It simplifies control with its centralized scheduling, which improves visibility and reduces errors. Automating cross-job dependencies is also done efficiently. Review collected by and hosted on G2.com.

I find the UI complexity a bit of a challenge. The licensing cost can be high, which is something to consider. There's also a steep learning curve involved, which can be daunting at first. Additionally, the limited cloud-native flexibility restricts some operations. Review collected by and hosted on G2.com.