Plesk

What are the known limitations of Plesk Migrator Extension?

  • Dmitry Bystrov

    • Question

    What are the known limitations of Plesk Migrator extension?

    Answer

    Note: In case the target server does not have a valid license, contact the Licensing and Purchase team and request a full-featured trial license for migration. Refer to the article How to get Plesk Web Host edition trial license for migration for further details.

    Below is the list of known limitations for the Plesk Migrator extension:

    • Migration is possible only to the same or newer version of Plesk

    • Unless explicitly explained, the Plesk Migrator extension does not migrate Extensions, nor the configuration of the extensions from one server to another.

    • Plesk Migrator Extention should be installed on the Destination Plesk server (also referenced as Target in some documentation).

    • Plesk Migrator requires a number of Ports to be open in the firewall. Ports can be found in Migration Guide

    • Plesk Panel should be accessible locally on the Destination server through localhost (127.0.0.1).

    • Plesk Migrator requires built-in administrator credentials for the Windows Source server and root user credentials for the Linux one.

    • At least 2GB of free disk space is required on the Source server.

    • ASP.NET 1.1 is not supported on the Destination server.

    • All server-wide settings set up in Tools & Settings menu will not be transferred.

    • PHP settings on the domain level are migrated only in case if PHP handler from source persists on the destination server.

    • Additional PHP directives of the domain are not migrated.

    • Plesk Migrator does not transfer Apache modules and shows a corresponding warning. The most popular warning is regarding mod_perl and mod_python.

    • Custom configurations (e.g. permissions set not via Plesk, web server configuration changes done not via Plesk) are not transferred.

    • Client login should not exceed 16 symbols.

    • Empty passwords on the Source server cause issues for migration.

    • For database assimilation, it is required to add a remote database server manually on the destination server as the default database server and the value in the column "Host name" must match on both Plesk servers.

    • Migration of domains with long names could fail.

    • Migration from Plesk on FreeBSD does not work.

    • Migration from Parallels Small Business Panel does not work.

    • Database mapping is not implemented yet. In case if databases are located on several MS SQL databases, they will be migrated to the default one on the target server.

    • Reseller and customer accounts that do not have any domains are not transferred. Service plans with no subscriptions are not transferred as well.

    • The settings of Plesk services, such as installed PHP handlers, Fail2Ban settings, ModSecurity settings, firewall settings, SpamAssassin's Bayes database, and so on are not transferred.

    • Custom webmail configurations like address books and so on are not transferred.

    • Custom templates are not migrated.

    • Mail Enable configuration is not migrated.

    • Each domain from Source Plesk below 10x version (where the new business model had been introduced for the first time) will get a new subscription on the Destination server.

    • Subscription's backups.

    • WP Toolkit automatic login link is not migrated.

    • Only SSL certificates…

    Tweet
    Share
    Share
    Email
    0 Shares