Performing Migration

To migrate accounts and websites with applications from other hosting servers:

1. Log in to Parallels Plesk Panel 10 on the destination server.
2. Go to Tools & Utilities > Migration Manager (in the Tools group).

   If you do not see the Migration Manager link, it means that this component is not installed. You can install it as described in the chapter Preparing for Migration from Plesk-managed Servers.

3. Click Synchronize to check if there are any updates for Migration Manager components. This is recommended, especially, if you are migrating data from hosting platforms other than Plesk.
4. Click Start New Migration.
5. Leave the Transfer data from another server option selected, and specify the following:
   • The source server's address and port number (on Linux/Unix systems). Specify either the IP address or the host name of the server, from which you want to transfer data.

     If the source server is on an IPv6 address, then you should specify the server's host name instead of IP address.

   • The login name and password of the administrator of the source server.

     Note: The option Transfer data already processed by the migration agent and located on the local host can be used to import data from a file, as described in the section Troubleshooting Migration Issues. This is another way to transfer data, which can be used in cases when the source server is offline, and you have previously gathered data from it.

6. If you use Parallels Plesk Panel for Linux, you can also specify the directory on the source server where the migration agent should be uploaded.
7. Specify the path to the directory where temporary files will be stored.
8. Specify whether you want to transfer all data related to user accounts and domains from the source server, or only specific items.
9. If you use Parallels Plesk Panel for Linux, select the Use rsync transport checkbox. This reduces the amounts of disk space, bandwidth, and time required to perform migration.
10. Click Next. The migration manager will connect to the specified server and gather information about the business objects of the source hosting platform.
11. If you have chosen to transfer only specific items, at this step, select the checkboxes corresponding to the user accounts and domains that you want to transfer. Also, specify what types of data should be transferred:
    • All settings and content.
    • All settings and content except mail.
    • Only mail accounts with e-mail messages.
12. Click Next.
13. Once the data are retrieved from the source server, specify the new IP addresses that should be used. If you have a great number of IP addresses, at this step, you can download the current IP mapping file, correct it in a text editor or by running a custom find-and-replace script, and then upload it back to the server.

    The syntax of the IP mapping file is shown in the following example:

    10.10.10.10 192.168.1.2

    Where 10.10.10.10 is an IP address used on the source server and 192.168.1.2 is a new IP address that should be used on the destination server. There is a white space between the two IP addresses. When compiling the list of addresses, place each mapping entry on a separate line.

14. Click Next. The data transfer process should start immediately; however, if some of the selected items cannot be transferred because of possible configuration or resource usage conflicts, you will be taken to the next step and prompted to specify the conflict resolution policies.
15. If prompted, specify how to resolve the following types of conflicts:
    1. Timing conflicts that occur when an item to be transferred already exists on the destination server and has a more recent modification date. You can choose any of the following options:
       • Use the configuration and data from the source server. This will overwrite the configuration and data currently present in the destination server with the configuration and data retrieved from the source server.
       • Use the configuration from the destination server, and the data from the source server.
       • Do not transfer items with timing conflicts.
    2. Resource usage conflicts that occur when an item to be transferred would exceed the resource usage limits defined on the destination server for this type of items. You can choose any of the following options:
       • Transfer the item and allow resource overuse.
       • Do not transfer the item.
    3. Configuration conflicts that occur when the settings of an item to be transferred are neither allowed nor available on the destination server. You can choose to:
       • Transfer the item and allow the required configuration options and settings.
       • Do not transfer the item.
16. Click Next.
17. When migration is finished, click OK to exit the wizard.

Please send us your feedback on this help page.