G2

Jon A.

Systems Engineer

Enterprise (> 1000 emp.)

7/31/2026

"Flexible, XML-Driven Automation Across SFTP, Azure Blob, S3, and SMB"

4.5/5

What do you like best about GoAnywhere MFT?

What I like best about GoAnywhere MFT is the XML backend - it makes it a lot easier to understand and build out job logic compared to a pure GUI-only tool, since you can actually see and control the task flow directly. I also like how flexible it is across protocols, being able to handle SFTP, Azure Blob, S3, and SMB transfers all within the same platform makes it easy to standardize jobs even when the vendor or destination changes. Review collected by and hosted on G2.com.

What do you dislike about GoAnywhere MFT?

What I dislike about GoAnywhere is that some of the built-in functions and attributes aren't well documented or don't behave the way you'd expect - things like CurrentDateTime() not actually existing, or sizeFilter being unreliable enough that you have to work around it with FileInfo() checks instead. It leads to a lot of trial and error that shouldn't be necessary. I also find the error handling setup to be a gap - just having a notifysysadmin module in the XML doesn't mean it actually fires, you have to explicitly wire it with onError on every task, and it's easy to miss that during job builds or reviews. Review collected by and hosted on G2.com.

What problems is GoAnywhere MFT solving and how is that benefiting you?

GoAnywhere MFT solves the problem of having a centralized, automated way to move files between us and all our vendors and partners without relying on manual transfers or one-off scripts scattered across servers. It benefits me by giving a single platform to build, monitor, and troubleshoot jobs across SFTP, Azure Blob, S3, and SMB, so when something fails I'm not chasing it down across different systems, I can go to one place and trace it through the job history and logs. It also makes onboarding new vendors more consistent, since I can reuse validated job templates instead of building transfer logic from scratch every time. Review collected by and hosted on G2.com.

Response from Chris Bailey of GoAnywhere MFT

edit

Jon,

Thanks for the review!

I appreciate the detailed feedback on the built-in functions, documentation, and error handling. Having to work around things like CurrentDateTime() or sizeFilter, or add onError handling task by task to make sure notifications actually fire, adds friction that should be easier to avoid. If you’re seeing behavior that appears inconsistent or unreliable, I’d also encourage you to reach out to our Support team so they can investigate the specific case.

It’s good to hear the XML-driven approach and flexibility across SFTP, Azure Blob, S3, and SMB are helping you standardize and reuse jobs across different vendors and destinations.

The link I attached below lets you vote on some features being considered for GoAnywhere and submit ideas for new features (button in top right). There is also a link to book a time to chat with me about our roadmap, any issues with our customer service, or any ideas you have. Looking forward to hearing from you!

See how GoAnywhere MFT improved