Abstract: A method, system and computer product for a migration of a shared hosting environment with an IP change is provided. Migration is performed with the help of a special tool—the migrator. For each migrated domain on the source server, the TTL (time to live) values are decreased on the source DNS server. If possible, for a database server, a replication between the source and the target servers is set up for migrated databases. The migrator creates configuration of web sites and mail service on the target server and copies files and mail messages from the source to the target server; the migrator creates databases (if replication is not available) on the target server; and the migrator creates DNS zones with DNS records pointing to the target server. Once administrator checks that site works well on the target server, the migrator performs content sync and sets DNS zone on the source server as slave to DNS zone on the target server.

Abstract: Mail server migration. For each mailbox, a migration utility is started on a target server to get a list of message IDs that have already been migrated. The command “listmessage-ids” is executed. The migration utility is started on the source server in a backup mode. The “backup” command is executed. Then, the migration utility is started on the target server in a restore mode. A “restore” command imports the messages. The migration utility on the source server provides mail messages to a standard output. The migration utility on the target server accepts mail messages on the standard input and restores them. RPC agent transfers data via TCP once it gets it from the migration utility on the source server. The migration module receives data from the RPC agent and puts data to the standard input of the migration utility on the target server as soon as it receives it.

Abstract: A method for migration of hosting environment, includes creating a base workflow as a tree of leaf and compound actions; detecting a control panel type on a target machine; applying workflow extensions to the base workflow for the control panel type on the target machine, to generate an extended workflow; detecting a control panel type on a source machine, wherein the control panel type on the target machine may be different from the control panel type on the source machine; applying additional workflow extensions to the extended workflow for the control panel type on the source machine, to generate a final workflow; and executing the final workflow to migrate a hosting environment from the source machine to the target machine and from the control panel type on the source machine to the control panel type on the target machine, using one of four execution modes: sequential, sequential-batch, parallel and parallel-batch.

Abstract: Mail server migration. For each mailbox, a migration utility is started on a target server to get a list of message IDs that have already been migrated. The command “list-message-ids” is executed. The migration utility is started on the source server in a backup mode. The “backup” command is executed. Then, the migration utility is started on the target server in a restore mode. A “restore” command is executed. The migration utility on the source server provides mail messages to a standard output. The migration utility on the target server accepts mail messages on the standard input and restores them. An RPC agent transfers data via TCP once it gets it from the migration utility on the source server. The migration module receives data from the RPC agent and puts data to the standard input of the migration utility on the target server as soon as it receives it.