MOVEit Reviews

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.

I appreciate MOVEit’s capability to transfer extremely large files. One instance involved successfully transferring a 70-gigabyte file, and although we haven’t attempted anything larger, every time we've needed to process a large file, MOVEit has handled it without issue. This ability to manage such large file transfers is something I really like about MOVEit Automation.

Another feature I value is MOVEit Transfer's logging functionality. Previously, when we used a Linux-based FTP server, we had no visibility into when files were dropped, and we lacked the auditing and logging capabilities. When sending files to vendors, their systems would sometimes claim not to have received them, and we had no way to verify or trace file delivery. MOVEit, however, provides robust logging that tracks service accounts and IP addresses, showing details like multiple file downloads. You can see who downloaded a file, the system account used, and how many times it was downloaded—this level of traceability is incredibly powerful.

We've faced some challenges with MOVEit as well. During the initial setup, we encountered issues with the MOVEit Transfer Gateway component, which operates in the DMZ. It frequently went down, causing disruptions in SFTP connectivity for most of our vendors. As a result, we had to implement extensive monitoring to ensure we received instant visibility whenever the gateway failed, allowing our system admins to respond quickly and restart the service.

Another issue stems from the fact that MOVEit is a Java-based product, and it seems to have a memory leak, leading to system slowness and unresponsiveness at times. To mitigate this, we had to schedule weekly restarts to clear out memory, which remains an ongoing process because, without these restarts, we wouldn't have a responsive system. These are two key challenges we’ve encountered with MOVEit Transfer.

Regarding MOVEit Automation, a job is typically triggered as soon as a file arrives, and it looks for the file, matches it, and moves it to the destination. However, if the expected file doesn't arrive, say on a Tuesday at 8:00 AM due to a job failure or someone forgetting to place the file, we need better visibility. Currently, MOVEit Automation offers limited capabilities for this scenario. We rely on error codes that indicate when no file was found, and we've built an email alert system around this, but for complex schedules—like jobs running on the 10th of each month—the system becomes ambiguous and occasionally generates false alerts. While MOVEit is not designed as a notification system, better alerting features would be incredibly valuable.

I'd also like to see Google Cloud connectivity in future updates. MOVEit has been expanding its connectors, initially supporting Azure, followed by AWS, but connectors for Google Cloud Platform are still missing. Adding this capability would be a great enhancement.

Another improvement I'd welcome is the ability to interact with message brokers. Currently, MOVEit handles file transfers and supports HTTP calls, meaning you can invoke APIs or download files over HTTP/HTTPS protocols. However, I’d like to see support for messaging protocols like MQ or AMQP. These protocols would make the platform more versatile, particularly for integrations where we need to pull messages from a queue and create files. IBM offers this capability, and if MOVEit could add it, it would make the product even more feature-rich and useful for our needs.

I have probably been using it since early 2018. It has been about four years.

I find it stable.

We don’t run many nodes, but we keep adding a lot of jobs to the system, and so far, MOVEit has proven to be scalable. We haven’t reached a point where we needed to add significant hardware resources. The system is still running on the same setup we implemented four years ago. The only adjustment we've had to make is adding more storage. Although we use MOVEit Transfer for transient storage, people tend to drop files and forget to clean them up. Since many of these files are large, we’ve had to increase storage capacity to accommodate them.

For MOVEit Transfer, we currently have about 300 users. In contrast, MOVEit Automation has a much smaller user base—around 10 people—primarily developers who log in to create and manage automation tasks. This includes both our development and operations teams, as they are the ones who need access. However, MOVEit Transfer is widely accessible to internal and external users, with more people requesting access regularly. The user base continues to grow, as everyone finds use cases that benefit from the system. It's one of the systems in our organization that’s expanding rapidly in terms of usage.

I initially submitted a few tickets regarding MOVEit's capabilities, and our system engineers may have created a few tickets as well. Since we have separate logins, we can't view all the tickets holistically. However, I'm confident that both I and the system engineers have reached out to support. Overall, the response from their support team has been pretty good.

Positive

I haven't had much experience with FTP tools beyond MOVEit, but prior to using it, we worked with several IBM middleware tools like IBM DataPower. However, those tools couldn't manage large files effectively, which is one reason I appreciate MOVEit Automation.

Before transitioning to MOVEit, we were using a Linux-based SFTP server. Essentially, it was just a Linux virtual machine running an SFTP process, not a full-fledged tool. We simply enabled the SFTP service on the Linux machine and had others connect to it. This lightweight setup could be done on any machine. Eventually, we replaced that system with MOVEit, which has been a significant upgrade for handling large file transfers and more complex integrations.

I wasn’t involved in the infrastructure side of things, but from what I’ve seen, MOVEit is a fairly easy system to set up. We have a dedicated systems engineering team that handles installations, and from what I understand, they were able to get it up and running quickly. It’s also a tool that was easy for us to learn and use, which makes it user-friendly from that perspective.

I'm not entirely sure about the deployment timeline. By the time I became involved, the initial setup and installation had already been completed. I joined once the system was already in place, and we had a quick training session—about half a day—on how to use the tool, and that was all we needed. I’m unsure how long they had been planning the implementation or how long it took to bring it online, but it seemed like a smooth and efficient process overall.

The entire implementation of MOVEit was handled in-house.

For ongoing maintenance, we have two primary contacts responsible for it, though they aren't dedicated full-time to MOVEit. Along with managing MOVEit, they also support several other major systems. From a system engineering perspective, these two individuals handle patches and maintenance but aren’t constantly monitoring or working on the tool. They only act on issues when they arise. Based on our experience, one full-time systems engineer would likely be sufficient to support MOVEit if needed.

We saw a return on investment with MOVEit in the very first year. One of the main reasons we adopted it was that our Linux machine was located in a different data center, and we needed a solution accessible over the internet by external parties. Before MOVEit, we didn't have a tool that allowed us to host a server that was internal but also accessible to others. We had to maintain a dedicated server, and our primary SFTP server in the data center was a Linux server. Once we implemented MOVEit and decommissioned the Linux server, we effectively realized our return on investment, as we were able to shut down that entire operation.

While I can't assign a specific dollar value to it, MOVEit is clearly a better solution compared to our previous SFTP processes. Our partners are pleased with the simplified UI, and in cases where files are missing, it’s easy to check the logs and provide assistance. It’s been very convenient to prove when files were successfully placed. These capabilities have greatly improved both customer satisfaction and internal user satisfaction.

Overall, I’m really happy with MOVEit. Some users might wish for more advanced features, like file-missing notifications or more sophisticated alerts, but they may not realize how complex it is to build those capabilities. Some may think there's a better tool out there that offers everything, but no tool can do it all. Given what MOVEit already offers, we've achieved our return on investment, and it's been a solid tool for us.

MOVEit Transfer and MOVEit Automation are quite straightforward to use. For MOVEit Transfer, one key practice is ensuring users don't treat it as permanent storage. It's best to use MOVEit SFTP only for temporary storage—meaning if someone uploads a file, it should be downloaded and cleared out by the recipient. Otherwise, file storage can accumulate quickly, given the volume of data you're dealing with.

As for MOVEit Automation, it's beneficial to establish patterns. For example, if you're handling external-to-internal file transfers, build a pattern that includes alerts or any other necessary logic in a generic way. This allows you to clone and reuse the pattern for new processes, saving time by avoiding the need to configure tasks from scratch every time. MOVEit provides the ability to take an existing task, clone it, and modify only the relevant details, which is what we do. So, before setting up your first automation job, it's crucial to plan a generic template upfront, as it will streamline future tasks.

Overall, I’d rate MOVEit a nine out of ten.

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.

Using MOVEit takes time to learn and to understand how it functions. I have a background in robotics, so I have some knowledge and hands-on use and training. Unless you have really good training and guidance, you won't be able to learn it. Even our lead software engineers who have years of experience and understand the architecture, find it very cumbersome to use. I think that's where there's a lot of scope for improvement. It could be more user-friendly.

I struggled in areas where I needed multiple robot path planning where multiple robots are involved. It's very, very hard for multiple robots to work and collaborate together. I would want to see more features and more advances in the area of multi-robot motion planning.

I've been using this solution for three years. 

MOVEit is very stable compared to a lot of other ROS packages.

This is open-source software. The code and software are hosted on GitHub. If there is any problem with MOVEit, I can make a pull request on GitHub and whoever manages MOVEit generally replies within a day.

MOVEit needs to be used along with a framework called ROS, Robot Operating System. Understanding ROS is a must and deployment requires significant knowledge of that. Primarily, it's built for Linux, not for Windows or other operating systems so it requires someone who is good at using Linux, understands Linux distribution, and is able to install and set up an ROS. With all that, it's simple to implement MOVEit. With my experience, I can set it up on a computer in 20 minutes.

There are several other solutions also in this arena including Tesseract and tkArt.  Both those solutions are for motion planning. Tesseract has a more advanced algorithm in comparison to MOVEit and it has more features. However, it's a difficult product to understand and use, and they don't have good documentation. If you're looking for high-end advanced research purposes, Tessaract and MOVEit are both good, but I think MOVEit is the best of the three.

If you're new to robotics, I would suggest evaluating whether your application needs MOVEit at all because of the very steep learning curve required to use it. If you decide to go ahead, start learning the basic building blocks of how ROS works and take a look at the MOVEit tutorial page. If a simple algorithm is required, I'd recommend writing your own. 

There are no serious competitors and MOVEit has worked out well for me despite lacking some features so I rate the solution eight out of 10.

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.

Pricing can be better. That's number one. 

The DR solution (DR recoveries) needs to be enhanced, I think.

If there are any problems with connectivity failures, etc., we engage the support team.

I have been using it for five years. 

I would rate the stability a nine out of ten. The reason I'm not giving ten is because it's still a Windows product.

It is scalable, but there are multiple factors involved. It depends on your requirements. So, it is scalable.

I would rate the scalability an eight out of ten. We have different teams involved. I mainly check the infrastructures, but in terms of maintainability, there's a different team that checks. 

It's not something I had a choice to choose. This was already evaluated by someone, and I just started using it. Eventually, I ended up maintaining, streamlining, and upgrading it. 

In the process, I understood more about the product. I did evaluate a couple of other options, but MOVEit is easier to use.

It's easy to deploy. 

Deployment time:

We don't frequently deploy. I've pretty much done a couple of deployments. It takes a couple of hours.

But in the process of getting ready with the deployment, data migration and all, it actually takes a lot of time. The pure software deployment is very easy, but when it comes to data migration, it is slightly complex.

Maintenance: 

There is no maintenance required. It's been like the last four years we moved to the cloud, so there's not much to do. It's a complete load off.

We use it as a managed service. It's under complete progress control. They must use Azure because it's Windows.

I'm well-versed with all the processes. In an organization, you have different roles. When dealing with the production system, you need to make sure there are no network issues. We'll engage the networking team, database team. So, we have a critical quorum mix, service delivery, SRE. Five or six members will be around, just in case.

But in general, we don't really need them. This is purely from a proactive point of view in case of unforeseen issues.

It is very secure. The way they support the channels and the configuration is user-friendly. 

It is a configuration-driven tool. So, the product is easy to understand and configure, making customization based on workflows easy.

Overall, I would rate it a nine out of ten. 

We are using MOVEit Transfer for sharing large files with customers or vendors.

There is a lot to like. From an administration standpoint, it's very easy to manage, and I feel pretty confident in the security of the product. From an end-user standpoint also, it's very easy. It's very flexible because people can log in via a web interface if they want to. If they have more of an automated approach, and if they want to send files back and forth, they can use FTPS or FTP. So, there are a lot of good options there.

The product itself is pretty solid. Something that I would like to see is better upgrade support. We had looked at getting help with an upgrade, and to do it after hours, it was going to be $6,000. It only takes 15 minutes to do. It'd be nice if the after-hour support was a little more reasonable.

We can set up multiple environments, but it would be nice to have one place to go to manage all the environments at once. If you're an administrator, you should be able to see all the users and have everything broken out. Currently, if I want to manage the secure file environment, I have to log in there with separate administrator credentials, which is a little bit cumbersome. There should be a dashboard to manage all environments at once. There is probably something like that, but you have to have a weird password, and it's just not easy to do.

I have been using MOVEit Transfer for about two years.

It is extremely stable.

I don't see any limits. We haven't hit any limits so far. It has been very scalable. The only limitation would be of the network connection when a customer with a slow internet connection is trying to download, for example, a 400 gig file, but that's not a limitation of the product.

We have about 50 users within our internal organization. Some users use it every day. We also have automated processes that pick up files or drop off files from a location as well.

You do have to have an account to contact support. They are pretty responsive and also extremely knowledgeable about their product. I feel that everyone I've talked to has been a subject matter expert. I've asked them questions about things that are probably out of their scope, and they've always been extremely helpful. I would rate them a five out of five. It is possibly the best support I've had.

Positive

They're probably crushing it for an on-premise solution, and they're doing really well. I have used some other ones, such as Filescape, but they weren't nearly as good. For me, the main difference is just the ease of use. Everything is very easy from an administrative standpoint as well as for the end user. We've had very few end-user calls. We didn't have any issues with even external users having any problems or understanding how the product works. The reporting and logging are good and easy. It's very well thought out.

I wasn't here for the initial setup. It was already set up when I got here, but it seems straightforward because everything about the product is pretty straightforward.

In terms of maintenance, it doesn't really require much maintenance. Once you get everything configured, there are automatic cleanup tasks, and you have to do the upgrades at least once a year to stay up to date or more frequently if you want to avoid vulnerabilities.

I haven't really priced out many other products like this, but I feel it's reasonable.

Their upgrade support after hours was going to be $6,000. I just made the decision to wing it and just do it during business hours and call support if there was a problem.

I would recommend it for sure. Something that people would want to be aware of is that you can set up multiple environments. You'd still have one URL that everyone would go to, but you can have multiple environments. You could have a secure file environment that's pretty much open to everyone, and then you could have an operations environment that's more secure and locked down by IP address. Be aware of that feature or functionality and how you would like to create a security strategy around that.

I would rate it a 10 out of 10. There's nothing I don't like about it.

It's been used for different purposes. I'm not sure if there's a desktop application. However, I'm using it on the cloud. 

We are basically using VMware, the virtual machine, to get on the servers, and then we start with our work.

I've created different types of scripts in MOVEit. The files were specifically sent to a particular location, which we configure. We used the code, and we used to do the scripting part using MoveIt. The files are picked up and then delivered to a specific location whether any conversion is necessary or not. 

We are just building the scripts and maybe assigning a schedule to the scripts, like when the script should run, what time of the day and how many times, et cetera. That's the kind of work I have done. 

I am also doing the monitoring. I'm just monitoring the scripts using MOVEit, inside MOVEit, just to make sure we see if any file activities or any actual files are picked up or not. 

Especially at the time of monitoring, it's a nice way to take a look at the script and take a look at run time, which gives enough information for the files that are getting picked or not. In that way, it helps me during the monitoring process, so I can categorize the scripts that are actively running or not running. That is one thing I really like about MOVEit.

The solution is stable. 

The dashboard is very precise.

I'm not really sure what can be improved at this time. With the kind of work I'm doing, I'm able to achieve it. I'm able to achieve my goals using MOVEit. Whether someone else would like its capabilities totally depends on an individual's perspective towards using the software or the admin tool. Some people like to do free text coding or develop scripts using a free text application. 

I don't know about MOVEit, or how the server is set up, however, a lot of times, it used to go down, and I couldn't get onto the servers. I don't know if it's an internal thing or it's MOVEit servers. For example, if I'm developing a script and the scripts are really huge, it's too much to code, so sometimes, when you're in the middle of creating the script, it just goes down. When that happens, I have to wait for an hour. I'm not blaming MOVEit for this. I'm just not sure where the root cause is coming from. That is one thing I've experienced that can be a little frustrating for some users.

Since I have to monitor two times a day, it would be nice if they have script templates. 

For example, if I have 20 tasks and 20 scripts that I have to monitor every day, creating a template for the scripts would save time. I know there are templates for developing the scripts. However, I'm not sure if there are templates for monitoring the scripts.

That way, I would not have to keep track of it and manually go and copy the script name, paste it into MOVEit and see the status.

I've been using the solution for almost a year now.

It is stable., although we've had challenges before. It goes down, and it could be anything, including maybe a VPN issue, or, since we are using this on the cloud, maybe the client system. That said, as far as I know, and I've built a lot of scripts as well, it's stable enough to deal with.

The solution is kind of scalable. 

I'm not sure how many people are working on the product. 

We have a separate team that is working on it. We have an offshore team and an onshore team working on MOVEit. It's maybe 20 people in total.

Whether or not we expand totally depends on the client's scope of work. This work is outsourced to us. We are just consultants. If there's any new project or if there's anything that needs to be done, including additional workflows for setup, we are happy to do that.

We don't really have contact with support. 

We are not supposed to do this, however, whatever the client is doing something on our behalf, we cannot directly reach out. We have to reach out to the client for their network team or admin team to handle things.

I've worked in different healthcare applications, which are patient management systems. Those are the only applications and tools I've previously used.

I have this on a virtual machine where everything was set up for me, and everything was ready to go. I have to log in and start working. That's all. I haven't installed a MOVEit server on any system. All I have to do is get onto the web application and then log in and then hit the dashboard for MOVEit.

We've had some go live early, and it's quite challenging sometimes when any script is moved to a production environment. If it goes down over there, it's kind of hard to backtrack and do the whole thing again. You have to go through all the steps and life cycles to go live again. That was one thing that I heard. I haven't ever done it. However, I've only worked on the test environment.

I do monitoring and maintenance on shore, and we have a resource offshore as well. 

When we create scripts in the test MOVEit, we have to replicate the whole setup in production. That was really challenging. Sometimes reaching out to appropriate resources to ensure that we have read and write access to the file path is important. In the MOVEit script, there's a file path where the files will be picked up from and dropped to. We have to ensure that we have enough access during the go-live, so the files are written and read from that particular file location. Sometimes identifying those resources was a little bit challenging, however, whether this is an internal process or a MOVEit process, I don't know.

I don't have any details surrounding ROI.

I'm not aware of the licensing costs. It might be somewhere in the middle in terms of pricing. I'd rate it three and a half out of five in terms of affordability. There might be installation costs and then the costs surrounding renewal on top of the actual price. 

We are consultants and end-users. 

I would recommend MOVEit. It's a great integration tool, and I'm able to achieve whatever the requirements are. It's also secured since it's in a cloud environment, so there won't be any loss of information. Since this is file-based connectivity with the type of work I'm doing, it's well-secured around the workflow and everything, so there's hardly a transaction loss. For those dealing with healthcare data, like me, I would definitely recommend MOVEit.

I'd rate the solution eight out of ten.

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.

The renaming and timestamp features are great and valuable, utilizing macros. Additionally, you can add encryption and decrypt files with encryption keys set up on MOVEit. Querying when and where file movement takes place adds an easy reference point when needed. 

Communication can be improved between the product owners and users. For example, communicating patches or resolutions to known issues would be helpful if there's an issue with the software.

We have been using this solution for approximately two years and are currently using version 13.0.

The solution is stable unless a patch needs to be applied to the software. For example, an issue causes the program not to function as it usually would. However, the majority of the time, it's very stable.

The solution is scalable. We have expanded it as we have grown as a company and plan to expand this solution further as we continue to grow.

We have had a good experience with customer service and support. Their response time is pretty quick, and they stick with you until your issue is resolved.

The complexity of the initial setup depends on what the solution is used for. First, we tie it to an SQL Server database where we can render history and information about the file. For example, date/time logs, filename and size at source vs destination. Creating hosts as connections points. Encryption or custom scripts. Depending on how much information you want from the file transfer, you can make it as complex as you'd like.

Implementation took one day. Testing it, following up, and tweaking it took several days.

We have seen a return on investment. For example, if you receive 100,000 files a day, and need to move, track or view the history, MOVEit will save you a tremendous amount of time.

I cannot comment on pricing and licensing costs as I do not have this information.

Our primary use case for this solution is data analysis for bank files. For example, when we receive a file from a bank in the production region, we don't touch the production because it is a live environment. We write a pull and push script in MOVEit and rename some files when we push the files from one server to another. Additionally, Windows Scheduler is integrated with MOVEit jobs. Once there is a signal in the Zena station, MOVEit is called, and the respective pull and push of script and the execution takes place there.

The ability to select and move a file at once is very valuable. Additionally, the convenience of renaming files and using time stamps to segregate them has been very valuable.

The front end of the MOVEit should have a utility where the user can check job failures that occur when integrating MOVEit with another tool, like the ASG-Zena workstation. There should be some utility where users can have a detailed view of the failed task that is not there at the moment. Additionally, the logs of particular tasks could be included in the next release.

We have been using this solution for approximately five years and are currently using version 3.4.

The solution is stable.

The solution is scalable. Approximately 40 people use this solution in my organization.

We contacted support when we had a glitch with the system in the deployment phase and the support team reached out to us in a couple of days and resolved it.

The initial setup is a bit difficult because not all the users are techies aware of the setup of MOVEit. Since we have to create, segregate and integrate an environment for the MOVEit application, it is a bit complex. However, if a person is aware of that complexity, it'll be easy for them to work on it.

Implementation was done in-house and took approximately nine weeks.

The licensing fees are charged yearly.

We chose this solution because we needed a product to transfer files, and MOVEit is a file transfer protocol and one of the most renowned tools in the market. We decided to use it instead of other tools.

I rate this solution an eight out of ten. The solution is good but can be improved by improving the integration tools available with the product.

I primarily used MOVEit to transfer files within the company and to third-party servers.

MOVEit's best features were the number of options available, like folder creation, and user-friendliness.

There were some drawbacks with MOVEit's scheduling. In the next release, MOVEit should include the ability to check file availability.

I used MOVEit for four-and-a-half years.

At times, we had connection issues with MOVEit, and it had a tendency to reboot without any reason.

Technical support is only available with a paid license.

MOVEit is a powerful tool, but it would be even better if it could enhance a few options. I would advise anybody thinking of implementing MOVEit to go through the options available and, before using it in production, test it within their non-production servers. I'd rate MOVEit nine out of ten.