Running Migration

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

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:

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 Operations > Migration Manager > Source System > host name > Update Password and check if the correct password is specified.

Check if the source hosts are not in the host-routed network mode.

If this check results in errors, go to the source virtual machines and switch the network mode to the bridged mode, as described in this article.

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.

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.

This will check if the proper top level domain purchase plans were assigned to domains during migration planning. If this check results in errors, resolve the issues as advised by the on-screen recommendations in the Migration Manager.

Shared hosting checks (available only for shared hosting migration)

Check whether the hosting module in Odin Automation is available and is 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.

Check if the source host is assigned at least one IP address which is not used by Plesk.

If you want to migrate subscriptions from a Plesk server and keep the same IP address after migration, assign an additional IP address to the source server making sure it is not used by Plesk and specify that IP address during the registration of the source Plesk server in Migration Manager.

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 or subscriptions 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.

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.