August 4th, 2016
  1. Log in to Plesk on the destination server as the Plesk administrator.
  2. Go to Server Management > Extensions > Plesk Migrator > Start New Migration. If Plesk Migrator is unavailable, install it following the instructions here.
  3. Specify the following:
    • The source server’s IP address. If migrating from a Linux server, specify the SSH port as well (22 by default).
    • (Linux) The login and password of a root user on the source server.
    • (Windows) The login and password of the built-in administrator accounts on both the source and the destination servers.
    • The path to a directory for storing temporary files.
  4. If migrating from a Windows-based server, specify how the RPC agent (an application enabling Plesk Migrator to gather data) must be deployed on the source server:
    • Automatically (recommended). Plesk Migrator will try to deploy and start RPC agent on the source server under the built-in administrator account. In some cases, automatic deployment may fail (for example, due to specific firewall settings, or the File and Printer Sharing or RPC services being disabled). In such cases, deploy the agent manually.
    • Manually. A link to download the RPC agent package will be provided. Download the package and install the agent on the source server manually.
  5. Specify whether you want to transfer all data related to user accounts and domains from the source server, or only specific items.
  6. If you want Plesk Migrator to replace Plesk objects (such as user accounts, domains, and so on) already present on the destination server with those being migrated from the source server, select the Replace existing objects checkbox.
  7. If you want Plesk Migrator to perform an additional sync of the migrated content after the migration is finished, select the Synchronize the content of domains after migration checkbox. Selecting this option will ensure that any changes made to the content on the source server after the migration has started are reflected on the destination server, but will increase the migration time.
  8. If you want Plesk Migrator to verify that websites and email services are operational on the destination server after the migration, select the Check the operability of services after migration checkbox.
  9. If you want Plesk Migrator to scan for the configuration files of common web applications and attempt to automatically change the database connection settings according to the destination server’s settings, select the Adjust configuration files of commonly used web applications checkbox (selecting this option will increase the migration time).
  10. Click Next to begin collecting information from the source server. This operation may take some time, so you can continue browsing the Plesk interface or close the browser window if you want. Once the information has been gathered, you can continue the migration by going to Server Management > Extensions > Plesk Migrator.
  11. If you have chosen to transfer only specific items, in this step, select the checkboxes corresponding to the user accounts and domains that you want to transfer. Also, specify the types of data (websites, email accounts, databases) to transfer.
  12. Click Next to run the configuration check. Once the check is concluded, a list of detected issues will be displayed (if any are found). These issues may affect the success of the migration, so we recommend that you resolve them all using the links available on the page before proceeding.
  13. Click Next to perform IP mapping (match the websites being migrated to the IP addresses present on the destination server). By default, IP mapping is done automatically, but you can assign the IP addresses manually if you want. You can read more about IP mapping here.
  14. Click Next to begin transferring the data.

One Response

  1. this idea is very good, help me a lot.


Leave a Reply

Your email address will not be published. Required fields are marked *