Running Migration

Migrating from Plesk > Migrating Data > Running Migration

Running Migration

Go to System > Migration Manager > Migration Projects, and click Start Migration.

start-migration-from-plesk

Subscriptions Preview

Before starting migration, check the subscriptions and migration settings you selected, and make sure that the proper service plans are specified.

Migration Mode

If you are performing a takeover migration, the Migration Manager selects the production migration, so you do not need to select anything in this step of the wizard.

If you are performing a full migration, select the migration mode:

Test without content. Use this mode if you want to check whether all business objects and settings of the source system can be accommodated in the business model of Odin Automation. In this mode, accounts and subscriptions will be imported, but the content will remain on source hosts; DNS will resolve to the source system. This mode takes less time than the test with content.
Test with content. Use this mode if you want to check if migration can be carried out successfully, before proceeding to the production migration. In this mode, accounts, subscriptions, and content will be copied to Odin Automation; DNS will resolve to the source system. You will be able to check whether the migrated websites are operable.
Production mode. All user data and settings will be copied to Odin Automation. DNS will be switched to resolve to Odin Automation and the billing system will be switched as well. The source system will be ready for the decommissioning.
We recommend that you first run migration in the Test with content mode, then verify the migrated objects in Odin Automation, and re-run migration in the Production mode to finalize the transfer. Because most of the time-consuming operations were carried out in the Test with content step, subsequent running of migration in the Production mode will require less time. When you repeat the migration, the objects that were already migrated are not recreated in Odin Automation.

Warning: After running migration in any of these modes, the selected objects will be created in Odin Automation and in Billing, and you will not be able to change the assignment of service plans and subscriptions if you choose to re-migrate the same items later.

Running the Pre-migration Checks and Resolving Issues

We recommend that you run the following checks before starting migration.

Infrastructure checks

Check whether it is possible to connect to source hosts.

If this check results in errors, do the following: ensure that the servers are running, and there are no network issues or firewall rules that may block connection to the servers. To learn how to resolve the issue, see the section Resolving Issues.

Check whether it is possible to authenticate at the source hosts using the specified username and password.

If this check results in errors, go to System > Migration Manager > Source System > host name > Update Password and check if the correct password is specified.

Check whether the source hosts are in the bridged network mode.

This is applicable only to Plesk servers running on Virtuozzo virtual private servers. If this check results in errors, configure the network interfaces of Virtuozzo servers to operate in the bridged mode.

License checks

Check whether the license in Odin Automation is installed and provides the necessary amounts of resources.

If the check reports that a license is not valid or is not installed, obtain a valid license from Ingram Micro or one of its affiliate partners, and install it.

Check whether the license is installed in the source system.

If the check reports that a license is not valid or is not installed, obtain a valid license and install it.

Source data checks

Check the integrity and correctness of the account data exported from the source system.

There might be issues with user account data that are (1) missing from the source system but are required for migration to Odin Automation, or (2) contain too short, too long, or incorrect values of names, addresses, and telephone numbers, which are not accepted by Odin Automation.

If this check results in errors, resolve the issues as advised by the on-screen recommendations in the Migration Manager.

Note: In Plesk, the usernames of auxiliary user accounts are the same as their email addresses. If the data check reports about an invalid username, you need to correct email addresses of auxiliary user accounts in Plesk.

Service plan checks

Check whether the resources required for migration are present in service templates.

If this check results in errors, resolve the issues as advised by the on-screen recommendations in the Migration Manager.

Check whether the assigned service plans are present in Odin Automation.

If this check results in errors, resolve the issues as advised by the on-screen recommendations in the Migration Manager.

Check whether the assigned service plans are applicable to domains.

If this check results in errors, resolve the issues as advised by the on-screen recommendations in the Migration Manager.

WebHosting Plesk checks (available only for shared hosting migration)

Check whether hosting nodes in Odin Automation are available and ready for migration.

If there are any issues reported by the check, resolve them as advised by the on-screen recommendations in the Migration Manager.

Check whether there are subscriptions belonging to the administrator.

If there are subscriptions belonging to the administrator, you need to assign them to customer accounts in the source system and then retry the migration.

IP address checks (not available for takeover migration)

Check if a range of IP addresses was assigned to the hosting nodes in Odin Automation.

If you plan to migrate subscriptions that use dedicated IP addresses, make sure that a range of dedicated IP addresses is assigned to hosting nodes in Odin Automation. Otherwise, all migrated subscriptions will be assigned the same shared IP addresses that are used by hosting nodes.

Resolving Other Possible Issues

During the course of migration, you might encounter the following issues:

An error while restoring the database user <name>: mssqlmng failed: Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.

To resolve this, disable the password complexity requirements on the target web hosting service node:

If you are using the Classic View of Control Panel, go to Start > Control Panel > Administrative Tools > Local Security Policy. Otherwise, go to Start > Control Panel > Performance and Maintenance > Administrative Tools > Local Security Policy.
Once inside the Local Security Policy console, expand Account Policies, select Password Policy, and set the policy security setting of Password must meet complexity requirements to Disable.

Checking the Migration Progress

To check the migration progress, go to System > Migration Manager > Migration Projects > Running tab > <migration project name>. When the migration is completed, a record about it is shown in System > Migration Manager > Migration Projects > Completed tab.

Refreshing Data About Accounts and Subscriptions

As migration might be a lengthy process, and the source system is not decommissioned, it is possible that new user accounts were created in the source hosting platform after you had planned and started migration from it. To update information about the newly added accounts and subscriptions, go to System > Migration Manager > Source Systems, and click Refresh Subscriptions List.

Note: If a domain or a subdomain was added to a source subscription after you migrated it in a test mode, you need to update information about it with Refresh Subscriptions List and then create a new migration project.