Fortra's GoAnywhere MFT Reviews

Pretty much everything we've needed to connect to has been done fairly seamlessly. The only issue I've had with connectivity, database or otherwise, revolved around an SSH key. I tried to create a key, but it was incompatible with a vendor's SFTP. And when that vendor has tried to create a key and share it with me, I have not been unable to import it into GoAnywhere. I had to use a third-party app to create the key and find something that was mutually compatible. I've submitted tickets on that to GAMFT for consideration. They could possibly improve the error handling on jobs. Whenever it generates error logs, sometimes the error is very generic. It takes a little work to diagnose what's really going on. It may just say "IO Exception" and that doesn't really tell you much.

File monitors are one of the most valuable features. We have about 400 file monitors running in GoAnywhere. They monitor the NAS locations where files arrive, and they kick off workflows. When a file arrives, GoAnywhere will identify that the file is there, move it to a consumption zone, then reach out to our enterprise scheduler through a REST API call. The solution helps centralize the exchange of data between systems, employees, customers, and trading partners. It's very central and that's pretty important. We generally move about 3,000 files a day, between our partners and internal workflows. My team really likes the intuitiveness of GoAnywhere's user interface. For example, my automation team has a file coming in from a bank, a file that needs to be unzipped, reformatted, re-zipped up, and then put into another folder where another team is going to consume it. Because of all the progressive elaboration—the project started a year ago—the format of the file is not the same. We addressed it with GoAnywhere instead of having the producer of the file change the format. That's how flexible it is for us. And looking at the comprehensiveness of GoAnywhere's workflow features, we use it pretty extensively for working with files. Stonebranch is our enterprise automation platform, but we don't really do any file work with Stonebranch. We chose to use GoAnywhere, our MFT tool, to move and manipulate files. The solution also connects to popular ICAP servers and that's pretty important to our security guys when it comes to preventing malware and other malicious content from entering our organization. The connection to popular ICAP servers, so that content is inspected for sensitive information like credit cards, is pretty important. We're a financial institution and a lot of the data we work with has PAN data and card numbers in it, coming in from partners.

It doesn't need much improvement, other than tiny idiosyncrasies. I've run into one or two things for which I've put in change requests to the software developers at GoAnywhere, but they are very minor things, the types of things that don't come up much. We've created in the neighborhood of 80 to 90 projects in GoAnywhere and, out of all of those, there have only been a couple where we've run into something and that made us say, "I wish they could improve this little thing here." For example, when it comes to interacting with files, there is a function referred to as write CSV, to write a general text file. In this scenario of creating a simple text file, I ran into a situation where, if the product saw a quote or a double-quote in the data, it started wrapping all the text fields in double-quotes. The request I put in asks them to provide a feature that leaves my data alone and does not interpret anything. If I don't want double quotes, please don't put them in. It should have the option, on certain write CSV operations, of not inferring anything.