From the server machine where MOVEit Transfer is running, open the MOVEit Transfer Config Utility and click on the Status tab. Ensure MOVEit Transfer services are running as expected.

API considerations

If you have applications that "take dependencies" (call methods and create objects) based on an earlier version of the MOVEit Transfer Java or .NET API libraries, ensure that these will be upgraded to a version compatible with the upgraded version of MOVEit Transfer.

If you have existing scripts or applications that use the MOVEit Transfer REST API, note that your script or application might be limited to feature and result data from a previous version. New capabilities are added to the MOVEit Transfer REST API with nearly each new release. See the most current Release Notes and REST API Guide for more information.

Run a quick MOVEit Transfer test

This checks to make sure the upgrade has worked at the simplest level

  1. From the server machine where you installed MOVEit Transfer, open the MOVEit Transfer Config Utility.
  2. Click the General tab. Check that the version number changed to the expected version for the upgrade.

  3. Sign-on to the WebUI

  4. Check for basic indicators, such as the user list, files and folders, and some simple uploads and downloads, using whatever protocols you normally use, such as the WebUI, SFTP, or FTPS.

Run tests from your test plan

  • Run tests that are specific to your environment or configuration. Refer to the test plan that you created before the upgrade (this was mentioned in the Plan your upgrade topic and detailed in the Testing Considerations topic).

  • Make sure to run these tests from the places that your users connect from.

Test Web Farms (if used)

  • If you are a Web Farms user, pay special attention to your load balancer to ensure that it continues to route to the Web Farm nodes as expected.

  • Ensure that each node can process requests in the same way as the other nodes.

Promote to Production

Once you are satisfied the system is working to your expectations, allow users and external processes to access MOVEit. Make sure that there is no chance that any users or automated processes are accessing the older server if you had done a migration upgrade.

What to do if something goes wrong

When an issue arises in a migration, upgrade, or other install processes, consulting the install logs is a good way to begin the troubleshooting process. You may find enough information in the logs to resolve your issue. If you need assistance from our technical support team, when raising your case please include the install logs

For information about how to locate install log files, see Locate MOVEit install logs.