Single node in-place upgrade
- Last Updated: April 14, 2026
- 3 minute read
- MOVEit Automation
- Version 2025.1
- Version 2025
- Documentation
Follow these instructions to upgrade MOVEit Automation on the same server.
Prerequisites
- Carefully review the Release Notes for your current and target versions. Release Notes for all supported versions are available here: MOVEit Automation.
- Review the Plan your upgrade topic.
- Download the MOVEit Automation installer package and activation code. For information about how to locate and download the license file, see Download license file.
- You should be confident in your backup strategy, and that you can restore your current environment with a recent set of data in a timely fashion.
- You will experience downtime during the upgrade process. Consider the impact of the outage and your operational schedule.
Windows authentication with remote SQL
If MOVEit Automation is configured to use Windows authentication with a remote SQL Server, additional permissions are required to complete an in‑place upgrade.
Beginning with MOVEit Automation 2025.0, the installer uses
a dedicated SQL login named moveit_installer to perform database
upgrade operations.
During installation or upgrade to version 2025.0 or later:
- The installer creates the
moveit_installerSQL user and assigns the required database permissions. - For subsequent upgrades, the installer first attempts to authenticate to SQL
using the
moveit_installerSQL login.
If authentication using moveit_installer fails, for example, if the
password was changed or the SQL Server is no longer configured for Mixed Mode
authentication, the installer falls back to using the Windows account that is
running the installer. When the installer falls back to Windows authentication, the
Windows account running the installer must have db_owner
permissions on the MOVEit Automation database.
If the Windows account does not have the required permissions, the upgrade will fail.
If the moveit_installer account password has been changed since the
last successful upgrade, update the password in the MOVEit Automation Config Utility
(Database tab) and then re‑run the upgrade.
To upgrade a single MOVEit Automation node in-place
- Stop the scheduler using the Web Admin .
- To avoid tasks running before the upgrade is complete, select the Start with scheduler disabled check box on the MOVEit Automation Config Utility General tab. This allows you to test your server in a controlled environment. After testing is complete, re-enable the scheduler.
- Copy the MOVEit Automation installer package to the MOVEit Automation server.
- To run the installer from the local server, right-click and select Run as administrator.
- Enter the appropriate licensing information.
To use an activation code to activate the product, enter the 23-character activation code when prompted.
If you downloaded the installer from the Progress Customer Portal, that code is embedded in the file name and is automatically entered.
To use a license file to activate the product, select Activate using a MOVEit License file and follow the prompts to load the license file you downloaded from the Progress Customer Portal.
- If prompted for a service account, enter your MOVEit service account password.
- During an upgrade, you may be prompted to enter the Web Admin URL. This is required to allow the MOVEit Automation service to communicate with Web Admin.
- To complete the upgrade, select Upgrade.
Post upgrade
After the upgrade procedure is complete, post-upgrade/migrate activities should be performed to verify that all data was imported and to test the system to ensure that all functionality is working as expected.
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, they will ask for your install logs.
For information about how to locate install or other log files, see Locate MOVEit log files.