Centralized Job Management and Secure File Transfers Made Easy
What do you like best about the product?
I like that Control-M keeps all our billing, reporting, and data transfer jobs in one place. It moves files securely, shows clear job status, and helps us make sure key tasks like invoicing and reconciliations finish on time.
What do you dislike about the product?
When many jobs are added, the screens can feel crowded and it takes longer to find what you need. Some features need training, and costs can rise if you add more modules.
What problems is the product solving and how is that benefiting you?
Control-M cuts manual work, reduces missed runs, and makes it easier to fix issues quickly. It helps our team run revenue workflows smoothly and keeps month end tasks more predictable.
Empowers CI/CD with Jobs as Code and Robust Automation
What do you like best about the product?
I value that Control-M supports Jobs as Code and an Automation API, so we keep job definitions in source control and deploy them from CI pipelines. That makes workflows repeatable and testable.
What do you dislike about the product?
Getting Automation API, agents, and integrations running takes planning. The platform is feature rich but not lightweight, and licensing can add cost as you add modules.
What problems is the product solving and how is that benefiting you?
It replaces fragile ad-hoc scripts with managed, auditable workflows and centralizes file transfers (MFT), which reduces manual fixes and speeds recovery during incidents. That improves reliability across on prem and cloud environments.
Centralized Job Management Made Simple and Efficient
What do you like best about the product?
I like that Control-M brings all scheduled jobs into one place. It makes it simple to build workflows, set dependencies, and track how systems connect. The visual view helps me understand issues quickly, and the API support lets our team manage job changes through version control.
What do you dislike about the product?
Large environments can feel crowded, and searching for specific jobs sometimes takes time. A few screens are complex and need training. Pricing can also rise when adding extra modules.
What problems is the product solving and how is that benefiting you?
Control-M reduces manual scripting, keeps workflows consistent, and makes troubleshooting much easier. It gives clear logs, reliable file transfers, and one dashboard to check the health of all scheduled tasks.
Clear Job Visibility and Seamless API Integration
What do you like best about the product?
I like that Control-M gives me a clear view of all scheduled jobs in one place. The visual flows and logs make it easy to track failures, understand what went wrong, and share details with developers. It also supports job changes through the API, which helps keep deployments consistent.
What do you dislike about the product?
It’s a powerful tool, but it can feel heavy at first. Managing many jobs and modules takes time, and new users need training to use all features. Costs can also go up if you add more components.
What problems is the product solving and how is that benefiting you?
Control-M reduces manual work, keeps workflows consistent, and helps us fix issues faster. It centralizes job monitoring and file transfers, which makes support work much easier and more predictable.
Centralized Job Scheduling Made Easy with Cloud Convenience
What do you like best about the product?
Control-M lets me schedule and run jobs from one place, so small teams can stop running manual scripts and avoid missed tasks. The cloud/SaaS option makes it easier to get started without heavy servers.
What do you dislike about the product?
It can feel more complex than a simple scheduler. There is setup work and some learning needed, and the Starter Pack SaaS has a noticeable monthly cost for small businesses.
What problems is the product solving and how is that benefiting you?
It automates routine batch jobs and file moves so my team spends less time on manual runs and troubleshooting. Built-in logging and managed file transfer make audits and secure file handling easier.
Saves significant weekly effort by automating job scheduling and ensures immediate task transitions
What is our primary use case?
Control-M is used to run Oracle scripts with scheduled jobs including monthly, weekly, and yearly schedules. Around 50 or more jobs are run every week. Control-M connects to the database, triggers all procedures, performs the operation, and generates the final report. The log is sent to mailboxes detailing how the process went, any issues, or any errors. If there are issues, the mailbox is checked; otherwise, a message indicating successful completion is received along with statistics such as how much time the process took and which processes were run. Jobs are scheduled once, Control-M jobs are created, timing is set up, and the jobs fire automatically at the particular time.
Control-M is used to connect to Oracle products, and through Control-M, a Tableau dashboard is maintained. Most of the scheduling jobs use Control-M to schedule. Control-M helps all products, making it a utility that can be used wherever scheduling features are needed. It is not just for DevOps, databases, or front-end applications; it can be used anywhere without manual intervention to perform particular activities. Wherever there is an opportunity for scheduling jobs, Control-M is the first option.
For migration, Control-M is considered very good. Once all the source and target details are configured in Control-M, it can automatically migrate data. It requires proper configuration and specifying the necessary changes for target technology along with the source system scripts. If properly configured, the complete migration can be triggered end to end. Data migrations and reporting, along with all scheduling activities, can be efficiently managed.
What is most valuable?
The best features in Control-M include sending emails to mailboxes after the process is completed and providing proper acknowledgement reports. The timing is impressive; it connects very fast and performs activities efficiently. The UI is very friendly, making it easy to configure jobs in Control-M. If core technology scripts are available, creating Control-M jobs is a five-minute task. The GUI is very friendly, which simplifies task assignment, scheduling, canceling, and all these operations, making it easily navigable.
Every week, 50 jobs are run using Control-M. If those 50 jobs were being run manually, it would take more than a week. Through Control-M, the jobs are able to be scheduled within two days, saving around five days of effort.
Before Control-M, jobs would be run on Friday evening so that the process would end by Sunday night, allowing the business to start on Monday. Without Control-M, everything would have to be run manually throughout the week. Thanks to Control-M, around five days are being saved. Otherwise, old data would be received for the current week's business, but now the latest data is received.
What needs improvement?
Control-M has room for improvement in displaying dashboard-like graphical reports once processes are completed. For example, after scheduling 50 jobs, if a dashboard showing the completed scripts, status, and time taken is displayed within Control-M itself, it would be very helpful. Currently, mailboxes are checked for reports; if it were in Control-M, anyone could check it. Only those configured with specific mail IDs receive emails, so if a few members are not set up, they will not see the reports. If it were available in Control-M, those users could directly check the dashboard.
For how long have I used the solution?
Control-M has been used for the last two years from the beginning of the project level. Earlier, it was already there in Control-M that the client was using.
What do I think about the stability of the solution?
The same score for stability is a nine out of ten.
What do I think about the scalability of the solution?
Control-M is capable of handling a large volume of processing if the necessary memory space is provided to the server.
How are customer service and support?
Great support is received, with a rating of nine out of ten.
How would you rate customer service and support?
What other advice do I have?
Control-M would definitely be recommended because it saves a lot of time. If everything were being done manually, it would take a lot of time to run and validate scripts. If everything is configured in Control-M, even non-experts like front-end staff can trigger jobs, making it simple. It is a one-time configuration, and anyone can trigger it. That is the best part; significant time is saved, and there is no waiting time; the next process starts immediately once the current one is completed. If dependencies are set in Control-M, it starts the next task automatically. That is why Control-M is highly recommended for scheduling.
The client is a big enterprise client.
Control-M requires occasional maintenance, maybe yearly or once every six months for upgrades. A Control-M team manages activities such as maintenance every six months or once a year, including cleaning up scripts or memory.
Around 15 members are using Control-M.
The overall review rating for Control-M is ten out of ten.
Robust Security and Centralized Control for Enterprise Workflows
What do you like best about the product?
I like that Control-M has solid security controls. It lets us manage access, track every action, and encrypt file transfers. The audit logs are clear, which helps during reviews or investigations. It brings all jobs into one place, making it easier to keep processes safe.
What do you dislike about the product?
Setting up all the security rules takes time, and managing large environments can feel heavy. Some screens are complex, and you need strict standards to avoid mistakes. It can also get expensive when you add more modules.
What problems is the product solving and how is that benefiting you?
Control-M helps us automate jobs securely, reduce manual errors, and keep sensitive workflows protected. It gives us clear logs, controlled access, and a dependable way to manage scheduled tasks across different systems.
Reliable and Efficient Workflow Management with Control-M
What do you like best about the product?
I really appreciate how Control-M simplifies the management of complex workflows. The centralized dashboards are extremely valuable to me, enabling a comprehensive view of all my jobs, dependencies, and SLAs in one location. This centralization significantly improves my efficiency by providing quick access to critical information. I also love how swiftly I can troubleshoot failures thanks to the clear logs and alerts, which save me a lot of time. Overall, Control-M makes my batch processes more reliable, automated, and predictable. These features collectively streamline my operations and ensure that our workflows are both reliable and highly efficient.
What do you dislike about the product?
I feel that the user interface of Control-M is a bit heavy and not very intuitive, especially for new users. This complexity sometimes leads to creating complex workflows requiring more clicks than anticipated. Additionally, the logs provided can be overly detailed, which makes identifying the exact error line time-consuming. While the platform is reliable once familiar, these initial challenges can be a hurdle.
What problems is the product solving and how is that benefiting you?
I use Control-M to automate and monitor workflows, minimize manual errors, ensure timely batch processing, handle dependencies, and swiftly resolve failures, enhancing the reliability and efficiency of our operations.
instrument for overseeing daily operations
What do you like best about the product?
Managing tasks across various systems without switching between tools is made simple with Control-M. The timeline view makes it easier to keep track of what's pending, what's running, and potential delays. Additionally, it provides unambiguous alerts, making it simple to respond before a problem impacts workflow.
What do you dislike about the product?
When establishing new workflows, some configuration steps seem a little onerous. In some places, the interface might use some updating. Because the platform is so feature-rich, it also takes time for new users to comprehend all of the options.
What problems is the product solving and how is that benefiting you?
Control-M minimizes manual labor and scheduling errors by assisting in task coordination across various applications. It makes it simpler to locate bottlenecks by centralizing all job monitoring in one location. This keeps things running smoothly and increases the overall stability of our processes.
Effortless Scheduling That Saves Time
What do you like best about the product?
I like how it allows me to schedule jobs all on one. It gives me full visibility
What do you dislike about the product?
It looks really old and blocky, not good ui and not intuitive
What problems is the product solving and how is that benefiting you?
Apps on my team rely on scripts, or separate pipeline tools. Hard to track, no central view, and easy to miss failures. I don’t need to log into multiple servers to understand batch behavior. It saves time debugging because everything is in a single pane of glass.
