Planning MOVEit Migration

This document is NOT all encompassing, it is intended to assist with planning the basic approach before beginning a migration. It is intended to serve as the starting point to plan a successful migration. It is important to note that EVERY migration is different, just as all environments are different, and Project Managers or Administrators will need to customize their plan beyond this document to meet all of your specific needs. If you need assistance developing, or reviewing, a custom plan our Professional Services team can be engaged to assist further. [Link to PS Engagement KB]

Sep 14, 2022
Knowledge

Title

URL Name

Planning-MOVEit-Migration

Article Number

000205408

Information

Important Items to consider:

Current version of MOVEit and what version of MOVEit you plan on migrating too in your environment.
Upgrading from a Sunset or Obsolete version of MOVEit to latest version (Contact Technical Support) - https://community.progress.com/s/life-cycle-file-transfer.
- https://docs.ipswitch.com/ review the release notes for the version of MOVEit that you are upgrading too. (Critical)
- In many cases, depending on the age of the version, it may be required to perform multiple upgrades to interim versions in between an obsolete version, to get to the current version.
  - It is absolutely critical that the migration be done on a clean windows installation and that the Operating System and Physical Hardware meet the specifications required for the version and environment you plan on using.
    - Please see the article (Critical) Upgrading a MOVEit server's OS
      - https://knowledgebase.progress.com/articles/Knowledge/upgrading-a-moveit-server-s-os (Critical)
Physical Hardware and Storage (Highly recommended that in a larger scale deployments to not go with minimum hardware requirements. Minimum hardware requirements are the basic requirements to get the system running.
Plan on the size and complexity of your sFTP Infrastructure to grow as more users find out about its availability and ease of use it is quite common to see demand increase.
Size of your database (MySQL-should be kept below 2 GB whenever possible and if you find yourself often going over or pushing up against this you may need to consider using a separate instance of MS SQL Server.
- Needs to be a version of MS SQL that is supported for the version you are looking to run MOVEit on.
Skillset necessary to perform a successful upgrade or migration
Cost of attempting upgrade or migration in house and potential of increased downtime vs. benefits of working with Professional Services (Experts in dealing with these scenarios)

Clarifying Information

If you are performing a migration from a version that is outside of the bounds of the linked chart below, have a webfarm, or use Ipswitch Failover, we highly recommend engaging our Professional Services team. The first step in pursuing an upgrade and migration project with PS is to obtain a pricing quote for PS assistance by contacting your account representative. This requires that you complete the form attached below and submit to your Account Manager who will contact Professional Services

Additional Information

If you do choose to perform an migration from a Sunset or Obsolete version of MOVEit it can NOT be stressed enough the importance of the following.

Backup your database before beginning, and where possible restore it to verify you have a good copy of your backup. If the backup is corrupt or can't be restored there is NO fallback option and you will need to start from scratch.
Make certain that you have all the relevant passwords that you will need including the following:
- Sysadmin - Primary MOVEit User account create to manage the Global Settings with MOVEIT Transfer across Organizations.
- Root Password - default account that is the owner of the MySQL database.
- MOVEit Service account - typically it is the .\moveitsvc account used in Windows Services to run MOVEit processes
- MS SQL - SA account which is basically the "Root" user for the MS SQL database.
Make certain to take a snapshot of the Server/VM before beginning to make any changes and ideally you can use this to spin up a VM and restore it and your backup and make sure that the server does not have any outside connections or access to production database.
At each stage along the way, repeat the process as often as necessary and if it fails after your 3rd or 4th upgrade this may prevent you having to go back and start from the beginning again. (Dependent on storage space)
If you do run into any errors, you will be prompted about a failed installation or error was thrown during the upgrade and it it succeeds or fails it should provide you information on the source of the log file and it is vital that you keep copies of the log files mentioned for troubleshooting purposes and please attach to any case (s) that you may open via the https://community.progress.com/s/ for customers with support contracts.
Also, you can check on any Security and Vulnerabilities for CVE Planning and get all possible hotfixes that may not be contained in the General Release via the Progress Community Portal listed in the bullet point above.
- MOVEit Transfer - Vulnerability Scanner, Penetration Testing, and Hardening FAQ's

Environment

Last Modified Date

9/14/2022 1:16 PM

Disclaimer

Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information. Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.