Article ID: 2112, created on Aug 22, 2007, last review on Jun 17, 2016

  • Applies to:
  • Plesk for Linux/Unix
  • Plesk 12.0 for Windows


What action should be done to avoid errors during migration?


  1. 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.

  2. Plesk license on the destination server must meet all requirements that exist on the source server.

  3. 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.

  4. 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
  5. 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

  6. 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.

Additional information

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

Search Words


Preparing a Parallels Plesk Panel server for migration

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 29d1e90fd304f01e6420fbe60f66f838 ed7be2b984f9c27de1d2dc349dc19c6d 85a92ca67f2200d36506862eaa6ed6b8 a766cea0c28e23e978fa78ef81918ab8

Email subscription for changes to this article
Save as PDF