Migrating Between Modules of Odin Automation > Migrating from Windows Shared Hosting to WebHosting Plesk > Migrating Data > Planning Migration

Planning Migration

To perform migration, you first need to create a migration project. To do this, go to System > Migration Manager > Migration Projects > Plan New Migration.

Services to Migrate

To migrate from Windows Shared Hosting to WebHosting Plesk, click the tile Windows Shared Hosting: Migrate Windows Shared Hosting to WebHosting Plesk.

Websites and content of subscriptions selected for migration will be moved from a Windows Shared Hosting node to a Windows-based node managed by WebHosting Plesk. The migrated subscriptions will be assigned other service plans suitable for WebHosting Plesk.

Hosting Subscriptions

Specify how you want to migrate data: by servers, by accounts with subscriptions, or by subscriptions. Select the checkboxes next to the servers, accounts, or subscriptions that you want to migrate.

Mapping of Service Plans

For each migrated Windows Shared Hosting subscription, select a WebHosting Plesk service plan from Odin Automation and click Assign to Subscriptions. All service plans shown in the menu are suitable for the migration of the selected source subscriptions to WebHosting Plesk.

Mapping of PHP Versions

You can choose any of the following options:

• Use the same PHP version as on the source system. This option is recommended. If the PHP version on the source system is earlier than the minimal version supported by Odin Automation, the nearest later version will be used. For example, if a subscription used PHP 5, then PHP 5.3 will be assigned to the subscription during migration.
• Use the PHP version that is configured in the assigned service plan.

Mapping of ASP.NET Versions

You can select any of the following options:

• Use the same ASP.NET version as on the source system. This option is recommended. If the ASP.NET version on the source system is earlier than the minimal version supported by Odin Automation, the nearest later version will be used. For example, if a subscription used ASP.NET 1, then ASP.NET 4.0 will be assigned to the subscription during migration.
• Use the ASP.NET version that is configured in the assigned service plan.

Mapping of IP Addresses

During migration, new IP addresses will be allocated from IP pools attached to the target Windows-based WebHosting Plesk nodes. The types of IP addresses allocated to websites will be preserved. Because only one exclusive IP address can be assigned per webspace in WebHosting Plesk, you need to select a migration strategy for the transfer of exclusive IP addresses that were assigned to websites in Windows Shared Hosting.

Select any of the following options:

• Assign only one exclusive IP address per webspace.

  If websites in a source subscription use exclusive IP addresses or a combination of an exclusive IP address and shared IP addresses, after migration, all websites of that subscription will be assigned a single exclusive IP address.

  If all websites in a source subscription use a shared IP address, they will continue using a shared IP address after migration.

• Assign the same number of exclusive IP addresses as in Windows Shared Hosting webspaces.

  If a website in a source subscription is on an exclusive IP address, it will still be on an exclusive IP address after migration to WebHosting Plesk. In this case, one webspace of Windows Shared Hosting will be migrated to multiple webspaces of WebHosting Plesk. A separate webspace will be created for each exclusive IP address. Websites that used that IP address will be migrated into it.

  If websites in a source subscription use a shared IP address, they will be grouped into one webspace and will continue using a shared IP address after migration.

  Only the system user of the first created webspace will be migrated. The system user names for other migrated webspaces will be generated automatically.

  Only the FTP users of the first created webspace will be migrated.