MOVEit Reviews

We can use the product to transfer files. I work for a bank. The files we transfer have PGP encryption by default. The data we send or receive is encrypted, ensuring that there is no data breach.

It is very easy to configure the setup. MOVEit is a reliable tool. I have not seen as many issues with it as in Globalscape. The tool’s GUI is very simple. I can do anything from the web. I need not log in to the desktop version.

The automation capabilities are brilliant. We can create and add any kind of schedule. We can create schedules and have them run on a specific day. For example, we can run the schedule on the third and fourth business days or the first seven business days. We can run schedules for every 10, 15, or 20 minutes.

When we pick a file, the tool creates a temporary directory in the MOVEit server. When the file is sent to the destination, it does not store the file inside the system. The moment the files get picked up, the tool delivers them. We did not face many challenges while integrating the tool into our environment. It is a really good product. Even if we face any issues, we can easily resolve them because the errors we see are self-explanatory.

We primarily used MOVEit for task-based file transfer. We would configure it using server details and file patterns, schedule transfers, and then monitor the results.

The automation is generally very simple that helps with operational efficiency. Since we mainly created interfaces and scheduled transfers, the tool itself handled the file transfer automation. With a good DevOps team, there's definitely potential for further automation.

We are utilizing both MOVEit Transfer and MOVEit Automation to support two primary use cases.

The first use case involves using MOVEit Transfer as an SFTP server or location, as well as for ad hoc large file transfers. In the second use case, we leverage MOVEit Automation where files are uploaded to MOVEit Transfer and then transferred between our internal systems and vice versa.

We utilize MOVEit Transfer for file exchanges by creating User accounts, allowing secure file transfers. If someone doesn't need automation and prefers to send files sporadically to external recipients, we rely on the ad hoc file transfer feature. This is particularly useful for sending large files securely, which can't be transmitted via email due to size restrictions.

Additionally, we can request file packages, which is especially helpful during acquisitions. Before the acquisition, we use the ad hoc transfer capability in MOVEit Transfer to securely transmit large files. After the acquisition, SSO based logins are used, but the instant capability to send files securely to an external party was un-parallel without them installing software on their end.

For automated data transfers we use MOVEit Automation. It supports a variety of connectors like Azure Blob and AWS S3, though we primarily use it for Azure Blob. Initially, we used custom scripts within MOVEit Automation for Azure Blob integration, but with built-in support now available, we leverage the connectors for seamless connections. MOVEit Automation is extensively used across our company and has proven to be incredibly beneficial.

We use MOVEit to upload our software for our clients to download.

The most valuable feature of MOVEit is the upload speed.

It's simple to use in creating folders, and if I need to copy or move something, it's very quick. 

It's fairly simple for me to place specific files in three or four different locations.

Whereas with my other tools, I had to go to separate locations to upload, with this, I can stay where I am and then copy over or move.

We use this solution for our motion planning for robots. The organizations that I work with are involved with robotic manipulators where the robot is required to follow a specific path of motion. We are customers of MOVEit.

The solution has a couple of nice features. Top of the list would be the huge collection of different path planning algorithms that are great and state of the art. If something isn't working very well, you can choose a different algorithm. Usually, robotic guidance takes a lot of time and effort to build, but MOVEit allows you the flexibility to switch between different algorithms and figure out which one works best for you. It's also easy to model a new robot. If a hobbyist has made a robot from scratch and wants to assimilate and see how it will perform, traditional modeling software like SolidWorks and others do not have a good path for planning algorithms supported by them. MOVEit is a very good tool for modeling a new robot from scratch.

It is mainly a gateway to receive or send files.

It supports multiple channels. We primarily rely on HTTPS and SFTP. So, it has been effective. 

The major advantage is moving files as part of a workflow. Moving files from one place to another, renaming file structures, and changing file formats on the fly. You have control, and it's easy to configure. Doing this on an application requires a lot of code and requires deployment, etc.

The configuration is user-friendly.

Our primary use case for this solution is file automation. We receive many files and use MOVEit to automate how we receive them, where they go and how they appear at their destination. We maintain it on a server, creating Host connection points which can work with SFTP, Sharefiles, Azure, etc. It's currently deployed on-premise.

This automation service works very well in placing thousands of files each day in different locations where separate ETL pipelines or packages can begin.

MOVEit is a GUI-based and very fast and reliable tool. The log findings and troubleshooting on MOVEit are pretty easy. When you go to the logs, it clearly tells you what time a transfer happened, what time it failed, what is the source path, what is the destination path, and what is the failure reason. It's pretty straightforward. If it's an authentication error, it tells you that. If the failure was because the password was incorrect, it gives you those details in the error logs.

When you download a file, it doesn't save anywhere on the local server. It creates a temporary file in the backend. MOVEit is architected in a manner where it downloads the file and immediately sends the file to the destination. So, you won't be able to reprocess the file from MOVEit itself. If you want to resend the file in case the transfer failed in between, you have to ask the source team to send the file again. So, there is a good thing and a bad thing about it. The good thing is that you don't have to worry about the disk space on the server on which you are hosting it. The bad thing is you have to go to the source team to ask to send the file again. 

If the transfers are more or the file size is big, it takes more time. It doesn't have much capacity to process multiple files at the same time. It can get stuck or take a lot of time to process the files. If the file size is in GBs or TBs, the data processing should be very fast. I want that kind of architecture and robustness. Currently, if the onboard N number of users, the server or the system automatically slows down because hundreds and thousands of files are flowing at the same time. If one user is uploading 1,000 files at the same time, it will automatically interfere with the other users which are using it at the same time. So, scalability and robustness should be there in this tool. That is one thing I'm expecting in the future in MOVEit. 

Similarly, when I want to open logs, it takes quite a long time. The way it works in the backend is that when you search a query with a file name, it goes to the backend and searches that file name in the database. Its speed is very slow. It's not that fast. It takes a couple of minutes to search those fields and get the results for a query.