Preparing for Migration

The preparation steps vary depending on how you want to migrate:

• Attach the source Plesk servers to CloudBlue Commerce service nodes. This is referred to as takeover migration.
• Move data from the source Plesk servers to CloudBlue Commerce service nodes. This is referred to as full migration.

Preparing for a Takeover Migration

If you want to attach Plesk servers to CloudBlue Commerce, you need to do the following:

1. Install and configure the WebHosting Plesk module for CloudBlue Commerce, as described in WebHosting Plesk Guide > Deploying the WebHosting Plesk Module. Make sure that you clean up the YUM repository cache on Linux-based service nodes before you attach them to WebHosting Plesk. You can do it using the yum clean all --enablerepo=* command.
2. Configure service templates and service plans.
3. Check if there are domains on the source system that meet the following criteria: they belong to the same user account and a DNS zone of one domain is a parent DNS zone of another domain or domains under the same account. This is a very rare case, but it is possible because there are different buttons in Plesk — Add Domain and Add Subdomain — and users could mistakenly use the wrong option while adding domains and subdomains. The subdomains that were added using the option Add Domain might be migrated without DNS records and might remain active in the source system after migration is finished. For this reason, we recommend that you review all subdomains and re-add all incorrectly registered subdomains by using the Add Subdomain option in Plesk.
4. Make sure that IP addresses used by the source Plesk node for communication and shared IP addresses allocated to the node are not configured as aliases on the network interface. A node can be attached in the takeover mode only by using the first IP address configured on the network interface.

Preparing for a Full Migration

If you want to migrate hosting subscriptions from Plesk to CloudBlue Commerce, you need to do the following:

1. Install and configure the WebHosting Plesk module for CloudBlue Commerce, as described in WebHosting Plesk Guide > Deploying the WebHosting Plesk Module.
2. Add service nodes and install license keys for them, as described in WebHosting Plesk Guide > Adding Service Nodes.
3. Install all the necessary Plesk components on the target web hosting service nodes, as described in WebHosting Plesk Guide > Setting Up Services on Hosting Service Nodes. You must install the same modules and components as the ones used by the source subscriptions: MySQL, Microsoft SQL Server, PostgreSQL database servers, anti-virus solutions, Apache modules such as mod_bw and mod_python, PHP and .NET handlers. You must also activate a PostgreSQL database on web hosting service nodes in CloudBlue Commerce: go to Provider Panel > Services > WebHosting Plesk > Service Nodes > Tools and Settings (in the Actions column) > Database Servers, click the gray icon in the S column (next to PostgreSQL), specify a username and a password, and click OK.
   
   
4. If you want to migrate databases from Microsoft SQL Server, you must ensure that the sqlcmd.exe utility is installed on source and destination servers. To learn more, refer to https://msdn.microsoft.com/library/ms162773.aspx. Note that migration of databases from Microsoft SQL Server 2000 is not supported.
5. Configure IP pools in CloudBlue Commerce. You need to do this only if you choose to use the same types of IP addresses as were used for the source subscriptions. Learn more in WebHosting Plesk Guide > Allocating Dedicated IP Addresses to Service Nodes.
6. If you want to migrate subscriptions and keep the IP addresses that they are using, configure each source Plesk server as well: Add an IP address to the network interface of every source server and specify this IP address during the registration of the source server in Migration Manager.
7. Configure service templates and service plans.
8. Make sure that connections to the port 29443 are allowed on Plesk service nodes, and that Plesk service nodes are accessible from the CloudBlue Commerce management node.
9. Check if there are domains on the source system that meet the following criteria: they belong to the same user account and a DNS zone of one domain is a parent DNS zone of another domain or domains under the same account. This is a very rare case, but it is possible because there are different buttons in Plesk — Add Domain and Add Subdomain — and users could mistakenly use the wrong option while adding domains and subdomains. The subdomains that were added using the option Add Domain might be migrated without DNS records and might remain active in the source system after migration is finished. For this reason, we recommend that you review all subdomains and re-add all incorrectly registered subdomains by using the Add Subdomain option in Plesk.