Articles in this section

See more

How to migrate from a Linux server with custom hosting to Plesk?

Avatar
Alexander Tsmokalyuk
Updated
Follow
kb: how-to ext: migrator Plesk Obsidian for Linux ABT: Group B

Applicable to:

  • Plesk Obsidian for Linux

Question

How to migrate from a Linux server with custom hosting to Plesk? 

Answer

In case of migration from the following platforms, consider contacting Plesk Professional Services for assistance on a paid basis:

- HDE Controller 6
- H-Sphere
- Interworx
- ISPmanager 4 Pro
- ISPmanager 5 Business
- PPA (Plesk Automation or Parallels Plesk Automation)
- WebControl Panel

Otherwise, follow the instructions below.

Note: Migrating from servers with custom hosting can only be done via the command line, and not via the Plesk interface. It is not possible to automatically generate hosting description file.

If you have administrative access to the source server

  1. Log in to the destination Plesk server via SSH
  2. Install Plesk Migrator if it is not installed yet
  3. Prepare hosting description file. Name the file hosting-description.[yaml/json], depending on the chosen format, and place it to /usr/local/psa/admin/sbin/modules/panel-migrator directory. The file must contain the list of clients, subscriptions, addon domains, mailboxes, etc. to be transferred from the source server. Sample hosting description files can be found here.
  4. Prepare migrator tool configuration file. Name the file config.ini and place it in the /usr/local/psa/admin/sbin/modules/panel-migrator directory. The file must include the configuration and access information for the source server. Sample configuration file can be found here.
  5. Generate the migration list:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator generate-migration-list

    The resulting file will be named migration-list and will be placed to the /usr/local/psa/var/modules/panel-migrator/sessions/migration-session/ directory. The migration list is a list of objects (customer and reseller accounts, service plans, domains, and so on) to be migrated.

  6. Edit the migration list. Remove the domains you do not want to migrate, assign domains you want to migrate to service plans, or re-assign them between customer accounts.
  7. (Optional) Validate the hosting description file:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator validate

    Read more about hosting description file validation here.

  8. Start the migration:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator transfer-accounts

  9. (Optional) Perform an additional content sync:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-content

    The changes of hosting content that may have happened on the source server while the migration was running are transferred on the destination server. If you want to re-sync only specific types of content, use the plesk-migrator copy-web-content, plesk-migrator copy-mail-content, or plesk-migrator copy-db-content commands.

  10. (Recommended) After the migration is finished, check the operability of the migrated objects on the destination server:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator test-all

If you do not have administrative access to the source server

  1. Log in to the destination Plesk server via SSH.
  2. Install Plesk Migrator if it is not installed yet
  3. Manually copy web and mail content from the source server to the destination. For web content, copy the document root directories of the domains you want to migrate with all included subdirectories and files. The content can be placed anywhere on the destination server.
  4. Create dumps of the databases belonging to the websites you want to migrate, then manually copy them to the destination server.
  5. Prepare the hosting description file. Name the file hosting-description.[yaml/json], depending on the chosen format, and place it to the /usr/local/psa/admin/sbin/modules/panel-migrator directory. The file should contain the list of clients, subscriptions, addon domains, mailboxes, etc. to be transferred from the source server. Find sample hosting description files here.
  6. Prepare configuration file. Name it config.ini and place to the /usr/local/psa/admin/sbin/modules/panel-migrator directory. The file must include the configuration and access information for the source server. Sample configuration file can be found here.
  7. Generate the migration list:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator generate-migration-list

    The resulting file will be named migration-list and placed to the /usr/local/psa/var/modules/panel-migrator/sessions/migration-session/ directory. The file will contain the list of objects (customer and reseller accounts, service plans, domains, and so on) to be migrated.

  8. Edit the migration list. Remove the domains you do not want to migrate, assign domains you want to migrate to service plans, or re-assign them between customer accounts.
  9. (Optional) Validate the hosting description file:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator validate

    Read more about hosting description file validation here.

  10. Start the migration:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator transfer-accounts

Comments

0 comments

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles