From the support perspective, the logging system could be improved. When MOVEit jobs fail and vendor support is needed, sometimes vendor contact details are not properly documented. This creates issues and hampers work. Documentation should be more comprehensive to ensure smooth operation of MOVEit applications. During version upgrades or feature deployments on MOVEit servers, which are handled by the sysadmin team, we encounter difficulties. The server sometimes becomes unresponsive or crashes, causing MOVEit jobs to fail and generating multiple tickets. This becomes particularly challenging because deployments are made directly to production servers without prior testing in test environments.
Support Engineer at a tech services company with 10,001+ employees
Real User
Top 20
Sep 18, 2025
In my opinion, MOVEit could be improved with some minor updates; the user interface could be more intuitive, and there could be more customization freedom and flexibility. Some configuration could be optimized, addressing any limitations that we would prefer to omit. Perhaps we would also want to add new capabilities, and incorporating artificial intelligence could be useful as well.
The solution lacks a flow view wherein you will not be able to see the integrated jobs in a flow diagram view. This becomes trickier to understand which flow is failing unless you were part of the design team. Reporting for MOVEit needs a lot more work. For example, if I have to pull a task report for a specific requirement such as its history and task attributes, the report doesn't come in a CSV format, which is consumable. It always comes in a scripted format. When you have to show the report to management, they don't understand the scripted format. They need everything in Excel. The reporting feature needs to work on having it in an Excel format. It has been pretty stable, but we were hit by malicious malware attacks in the last two years more comparatively. Depending upon the type of license that is owned and the support with the license, it is up to par with other leading marketing tools.
Senior Technical Support Engineer at a computer software company with 10,001+ employees
Real User
Top 20
Aug 29, 2025
The scheduling features need improvement as currently there are standard scheduling possibilities that could be enhanced with more options and features, such as automatically creating checksum files. Improving SharePoint connectivity usage, which has limitations, would open up considerable usage and enhance MOVEit significantly.
The product must improve its security features. Recently, there have been multiple attacks on the solution. It has ruined the reputation of clients who use the solution. The vendor must ensure that there are no cyber attacks on the transfer server. If hundreds of tasks run on MOVEit simultaneously, the system hangs.
Engineering Manager at a tech services company with 10,001+ employees
Real User
Top 5
Jul 3, 2024
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.
In future releases, MOVEit could add support for some additional protocols. For example, I don't think they supported the SFTP or FTPS protocols at the time.
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.
Sr. Software Configuration Administrator at a tech services company with 10,001+ employees
Real User
Oct 4, 2022
I know the only thing I don't know about MOVEit is that we don't use it to its full potential. My business unit, our business unit, is a small one. We only use it to upload software to clients both externally and internally so they can download it. I am not familiar with many of the features it offers, and neither are many of the administrators. We were not really trained on it. We were given this tool and left to figure it out, and that is what we did. I am not sure if there is a feature where you can hide the software instead of having to delete it, because sometimes I need to put out a release and if I want to do it the day before, I could hide it and then just flip a switch and turn it on. That's something I used to be able to do with my previous solution. That was the only thing I couldn't hide the software because I couldn't figure out how to and no one else could either. I spoke with the two admins who were dealing with it, and they, too, couldn't figure out where to hide it. If I put something out there and put it out there too soon and a client sees it, I have to quickly go in and delete it and then re-upload it instead of having a feature that lets me just check this box and hide it, that would be a good thing to have. It would be beneficial to include a feature that allows you to hide items and not be locked out if someone has made too many password attempts.
Manager - Integration (Supply Chain) at a healthcare company with 10,001+ employees
Real User
Top 20
Sep 16, 2022
We have had some challenges. Earlier when we were setting it up, a component called gateway, which runs in the DMV, was not working as expected. It was going down very often. That means most of our vendors were not able to connect using SFTP because that service was down. We had to put in a lot of monitoring to make sure if that goes down, there is some visibility instantaneously so that our system admins can go and do a restart. In addition, because it is a Java product, there seems to be a memory leak that causes system slowness and unresponsiveness at times. We had to introduce a weekly restart to flush out some memory. The restart process is still going on because we know that without that, we can't have a responsive system. These are the two things for MOVEit Transfer. Coming to MOVEit Automation, usually, when a file arrives, a job kicks in. We have jobs that look for a file, match the file, and move it to the destination. However, if a file doesn't come through at the expected time, such as on a Tuesday morning at 8:00 AM, because the job failed or somebody forgot to place that file, people want visibility into it. For this, currently, there are limited capabilities in MOVEit Automation. We can look for that error code, where it basically says that I didn't find any file to transfer. We are leveraging that capability and building some email system around it so that if that happens, we get to know, but when it comes to multiple jobs running on a particular day, such as on the 10th of every month, you get into complex scheduling. That's when this email system becomes ambiguous. Sometimes, it throws false alerts. MOVEit is not a notification system, but we expect more and better notifications. That would really add value. I would like to see connectivity to Google Cloud. At some point, it will come. They have been creating connectors for more products. Earlier, they had only Azure, and then they added AWS. Google Cloud Platform connectors are not there yet. I would like to see that capability. I would also like to see a capability where it can interact with message brokers. Currently, it can do file transfers, and it can do HTTP calls. That means you can invoke an API or download a file over HTTP or HTTPS protocol, but I would like to see it supporting the MQ protocol or AMQP. Those are some messaging protocols that will help it to become more feature-rich. We have some integrations where we have to connect to a queue, pull a message, and create a file. That capability is there in the IBM product, but I would like to see that capability built. If that capability comes to MOVEit, it would be fantastic.
With the new other vendors coming up, they come up with certain features, in addition to the file transfer. But MOVEit does not develop their product. That's why we are looking out for other solutions. There should be more control. If you transfer some files, you can even include the person to whom you are sending this file. He can copy it, print it, and make changes into the file or not, so those permissions should be granted over that particular file, which are not as of now.
Progress MOVEit Managed File Transfer provides automated file transfer management, ensuring secure and predictable delivery, with robust reporting capabilities and seamless integration. MOVEit offers automated management of file transfers, enhancing secure delivery with robust encryption and extensive reporting. Its user-friendly design supports large files with FTP access, scheduling, and macros to facilitate transformations. Security features like IP control and authentication settings...
From the support perspective, the logging system could be improved. When MOVEit jobs fail and vendor support is needed, sometimes vendor contact details are not properly documented. This creates issues and hampers work. Documentation should be more comprehensive to ensure smooth operation of MOVEit applications. During version upgrades or feature deployments on MOVEit servers, which are handled by the sysadmin team, we encounter difficulties. The server sometimes becomes unresponsive or crashes, causing MOVEit jobs to fail and generating multiple tickets. This becomes particularly challenging because deployments are made directly to production servers without prior testing in test environments.
In my opinion, MOVEit could be improved with some minor updates; the user interface could be more intuitive, and there could be more customization freedom and flexibility. Some configuration could be optimized, addressing any limitations that we would prefer to omit. Perhaps we would also want to add new capabilities, and incorporating artificial intelligence could be useful as well.
The solution lacks a flow view wherein you will not be able to see the integrated jobs in a flow diagram view. This becomes trickier to understand which flow is failing unless you were part of the design team. Reporting for MOVEit needs a lot more work. For example, if I have to pull a task report for a specific requirement such as its history and task attributes, the report doesn't come in a CSV format, which is consumable. It always comes in a scripted format. When you have to show the report to management, they don't understand the scripted format. They need everything in Excel. The reporting feature needs to work on having it in an Excel format. It has been pretty stable, but we were hit by malicious malware attacks in the last two years more comparatively. Depending upon the type of license that is owned and the support with the license, it is up to par with other leading marketing tools.
The scheduling features need improvement as currently there are standard scheduling possibilities that could be enhanced with more options and features, such as automatically creating checksum files. Improving SharePoint connectivity usage, which has limitations, would open up considerable usage and enhance MOVEit significantly.
The product must improve its security features. Recently, there have been multiple attacks on the solution. It has ruined the reputation of clients who use the solution. The vendor must ensure that there are no cyber attacks on the transfer server. If hundreds of tasks run on MOVEit simultaneously, the system hangs.
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.
In future releases, MOVEit could add support for some additional protocols. For example, I don't think they supported the SFTP or FTPS protocols at the time.
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.
I know the only thing I don't know about MOVEit is that we don't use it to its full potential. My business unit, our business unit, is a small one. We only use it to upload software to clients both externally and internally so they can download it. I am not familiar with many of the features it offers, and neither are many of the administrators. We were not really trained on it. We were given this tool and left to figure it out, and that is what we did. I am not sure if there is a feature where you can hide the software instead of having to delete it, because sometimes I need to put out a release and if I want to do it the day before, I could hide it and then just flip a switch and turn it on. That's something I used to be able to do with my previous solution. That was the only thing I couldn't hide the software because I couldn't figure out how to and no one else could either. I spoke with the two admins who were dealing with it, and they, too, couldn't figure out where to hide it. If I put something out there and put it out there too soon and a client sees it, I have to quickly go in and delete it and then re-upload it instead of having a feature that lets me just check this box and hide it, that would be a good thing to have. It would be beneficial to include a feature that allows you to hide items and not be locked out if someone has made too many password attempts.
We have had some challenges. Earlier when we were setting it up, a component called gateway, which runs in the DMV, was not working as expected. It was going down very often. That means most of our vendors were not able to connect using SFTP because that service was down. We had to put in a lot of monitoring to make sure if that goes down, there is some visibility instantaneously so that our system admins can go and do a restart. In addition, because it is a Java product, there seems to be a memory leak that causes system slowness and unresponsiveness at times. We had to introduce a weekly restart to flush out some memory. The restart process is still going on because we know that without that, we can't have a responsive system. These are the two things for MOVEit Transfer. Coming to MOVEit Automation, usually, when a file arrives, a job kicks in. We have jobs that look for a file, match the file, and move it to the destination. However, if a file doesn't come through at the expected time, such as on a Tuesday morning at 8:00 AM, because the job failed or somebody forgot to place that file, people want visibility into it. For this, currently, there are limited capabilities in MOVEit Automation. We can look for that error code, where it basically says that I didn't find any file to transfer. We are leveraging that capability and building some email system around it so that if that happens, we get to know, but when it comes to multiple jobs running on a particular day, such as on the 10th of every month, you get into complex scheduling. That's when this email system becomes ambiguous. Sometimes, it throws false alerts. MOVEit is not a notification system, but we expect more and better notifications. That would really add value. I would like to see connectivity to Google Cloud. At some point, it will come. They have been creating connectors for more products. Earlier, they had only Azure, and then they added AWS. Google Cloud Platform connectors are not there yet. I would like to see that capability. I would also like to see a capability where it can interact with message brokers. Currently, it can do file transfers, and it can do HTTP calls. That means you can invoke an API or download a file over HTTP or HTTPS protocol, but I would like to see it supporting the MQ protocol or AMQP. Those are some messaging protocols that will help it to become more feature-rich. We have some integrations where we have to connect to a queue, pull a message, and create a file. That capability is there in the IBM product, but I would like to see that capability built. If that capability comes to MOVEit, it would be fantastic.
With the new other vendors coming up, they come up with certain features, in addition to the file transfer. But MOVEit does not develop their product. That's why we are looking out for other solutions. There should be more control. If you transfer some files, you can even include the person to whom you are sending this file. He can copy it, print it, and make changes into the file or not, so those permissions should be granted over that particular file, which are not as of now.