What action should be done to avoid errors during migration?
All Plesk components that are used on the source server should be installed on the destination server as well. For example, if the source server has Postgres or Mailman, these packages must be installed on the destination host, too. Otherwise, these components' data will not be migrated.
Plesk license on the destination server must meet all requirements that exist on the source server.
Check if free disk space on the source server is enough to dump the data. The free disk space should be at least the data size you wish to migrate.
The destination server must contain free disk space at least twice the size of the data being migrated. The extra space is needed to store the dump on the destination server and extract data from it.
Make sure the default MySQL character set is
latin1. This encoding is used by MySQL by default. However, if it was redefined in
/etc/my.cnf, it is better to switch it back to avoid the problems with database restoration.
Current default characters that are set can be found with the following command:
# MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -u admin -e 'status' | grep characterset Server characterset: latin1 Db characterset: latin1 Client characterset: latin1 Conn. characterset: latin1
If the resulting number of domains hosted on your server will be more than 300, check the following article:
#113974 - How to increase the number of sites that can be hosted on a Plesk for Linux server
If there are any domains on the server with databases hosted on a remote database server, make sure you follow this article:
#114045 - Unable to migrate domains with databases on a remote database server.
For more details, refer to the following guides:
121368 Plesk migration and transfer guide
113590 Plesk for Windows: Migration Best Practices and Use Cases
113586 Plesk for Linux: Migration Best Practices and Use Cases