Migration

Takeover

Data transfer

All data are transferred from source servers to Odin Automation:

• Business-related data such as customer and billing information.
• Settings of hosting services.

Note: After performing a full migration in the production mode, subscriptions in the source system are suspended and customers can no longer use them. No data are deleted from the source servers during migration.

All shared hosting data remain on the source servers, all services on the source servers continue to operate as usual, and the source servers are connected to the WebHosting Plesk Module of Odin Automation.

Shared hosting accounts and subscriptions are created in Odin Automation, a source server with subscriptions’ data is registered as a service node in WebHosting Plesk Module, and accounts and subscriptions are linked to the data on the connected source server.

Note: After performing a takeover migration from OBAS, subscriptions in the source system are put on hold, that is, they are not billed and customers can no longer use them. If you activate those subscriptions in OBAS, then some management issues might occur with the server that was taken over.

Reuse of existing servers

To perform migration, additional servers are needed to act as new service nodes.

Source servers can be decommissioned after migration is completed.

No additional servers are needed.

Source servers cannot be decommissioned as they are still in use.

Downtime during migration

Migration can take a significant time to complete, and there can be downtime during migration.

There is no downtime during the takeover process, and the whole process takes less time.

With takeover, you can avoid data transfer and possible issues related to it.

Transfer of server settings and applications

All server settings and configurations of services such as firewall, ModSecurity, Fail2Ban, and others are not transferred. For this reason, you will need to reconfigure all such services on the new nodes after migration.

No changes to hosting settings or content are made, so there is no need to reconfigure any settings or services on the source servers after the takeover.

After migration, websites created with Web Presence Builder (or SiteBuilder) will continue to operate, but will not be manageable through Web Presence Builder.

All websites created with Web Presence Builder will remain operable and users will be able to manage them through Web Presence Builder as usual.

Resource records in the DNS zones of websites are created based on the IP address of the WebHosting Plesk service node to which websites were migrated. Depending on the services associated with the migrated sites, the NS, A, MX, and CNAME records are created in the zones. All other types of records containing custom values are not created in the zones.

Resource records in the DNS zones of websites are re-created in the DNS zone of Odin Automation.

Available migration modes

Test migration without content, test migration with content, and production migration modes are available.

We recommend running migration in the production mode after you have run it in the test with content mode.

In the production mode, subscriptions are migrated if they were not previously migrated in the test mode. After that, a billing system is switched from the source system to Odin Automation, and DNS forwarding is configured.

Only production migration is available for the takeover migration.