Control-M vs Jitterbit

• Control-M Advanced File Transfer is a very useful add-on, allowing for a wide variety of file transfers to be configured "out of the box" and then used as part of the standard batch flow. This module is not included in the base price but is available at a relatively small additional cost.
• Using Control-M's GUI (the Enterprise Manager) allows for efficient management of the enterprise and can tie up a lot of "loose ends". Often the first point of tracking problems is to check with the Control-M guys!
• BMC is definitely moving the product forward, the new module "Application Integrator" is very helpful in building and deploying your own bespoke Control-M jobs and allows for closer and more secure integration.
• Although Control-M does open up the enterprise in an operational sense, the security settings (should you choose to implement them) are robust.

Read full review

• UI is super easy to understand with a low learning curve so admins can figure it out and maintain it without breaking anything.
• It's FREE! There's a paid version too but I like that you can use most of the features for free and they're not pushy with buying.
• There's a great user community that you can google and ask any questions. Most problems I've encountered have been posted and answered already.

Read full review

• Single Major Action per job: this statement needs to be clarified. There are ways to do more than one action per job, and there are pre and post job commands available in most templates. Also some templates like FTP can have many instructions built in, like deleting source files after transfer (these are part of the positives). But basically you can only do one major action, like call one web service, or call one stored procedure per job. I believe this limitation is due to their licensing model, to ensure you will run as many jobs as possible.
• The only other negative is a necessary corollary of a having a powerful product. The learning curve is not simple due to the power of the product. I would recommend dedicate training for the primary operators and users of the product.

Read full review

• Migrating operations from QA to Production work well for initial deployment, however, when migrating an update to an existing job to production, sometimes certain project items are duplicated. This is not the end of the world... the duplicates can be removed, but would be nice if it was not required.
• I have not found a way to trap under-the-covers SOAP errors (for example, when a query you are running against Salesforce takes too long). You get a warning error in the operation log that the job only pulled a "partial" file, but it does not fail.

Read full review

• Troubleshooting has improved with multiple groups as they are easily able to determine if data loss/job failure is the reason for a data issue.
• Conversion took significantly longer than was originally estimated by BMC so we had to run two platforms for almost 9 months. This definitely slowed down efficiency as many users did not know which tool to utilize for data load trouble shooting for close to a year.
• Being able to communicate with users across the globe in a universal language and time reference has vastly decreased data issues and greatly improved proficiency in getting new jobs implemented quickly and without problems.

Read full review

• The time it takes to connect systems has reduced by orders of magnitude. Previously, we would custom-develop connectors between various systems and they would all be managed by different vendors. With Jitterbit speed-to-deploy and the efficiency gained by managing all connections in one dashboard has been the greatest piece of the ROI.

Read full review