This topic describes how to migrate from a Windows server running a control panel not on the list of supported source platforms, or one with hosting but no control panel. The following scenarios are supported:
Note: Migrating from servers with custom hosting can only be done via the command line, and not via the Plesk interface.
If you have administrative access to the server, follow these steps:
hosting-description.[yaml/json]
, depending on the chosen format, and place it in the %plesk_dir%admin\plib\modules\panel-migrator\backend
directory. The file must contain the list of clients, subscriptions, addon domains, mailboxes, etc. to be transferred from the source server. You can find sample hosting description files here.config.ini
and place it in the %plesk_dir%admin\plib\modules\panel-migrator\backend
directory. The file must include the configuration and access information for the source server. Use the sample configuration file found here for reference.%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat generate-migration-list
The resulting file will be named migration-list
and will be placed in the %plesk_dir%admin\plib\modules\panel-migrator\backend\
directory. The migration list is a list of objects (customer and reseller accounts, service plans, domains, and so on) to be migrated.
"%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" validate
You can read more about hosting description file validation here.
%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat transfer-accounts
%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat copy-content
This makes sure that changes to hosting content that may have happened on the source server while the migration was running are mirrored on the destination server. If you want to re-sync only specific types of content, use the plesk-migrator.bat copy-web-content
, plesk-migrator.bat copy-mail-content
, or plesk-migrator.bat copy-db-content
commands.
%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat test-all
If you do not have administrative access to the server, follow these steps:
hosting-description.[yaml/json]
, depending on the chosen format, and place it in the %plesk_dir%admin\plib\modules\panel-migrator\backend
directory. The file must contain the list of clients, subscriptions, addon domains, mailboxes, etc. to be transferred from the source server. You can find sample hosting description files here.config.ini
and place it in the %plesk_dir%admin\plib\modules\panel-migrator\backend
directory. The file must include the configuration and access information for the source server. Use the sample configuration file found here for reference.%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat generate-migration-list
The resulting file will be named migration-list
and placed in the %plesk_dir%admin\plib\modules\panel-migrator\backend\
directory. The migration list contains the list of objects (customer and reseller accounts, service plans, domains, and so on) to be migrated.
"%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" validate
You can read more about hosting description file validation here.
%plesk_dir%admin\plib\modules\panel-migrator\backend\plesk-migrator.bat transfer-accounts