What are the known limitations of Plesk Migrator extension?
Below is the list of known limitations for Plesk Migrator extension:
Migration is possible only to the same or newer version of Plesk
Unless explicitely explained, Plesk Migrator extension does not migrate Extensions, neither 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. Port 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 the 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 configuration (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 remote database server manually on destination server as the default database server and the value in 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.
WordPress Toolkit automatic login link is not migrated.
Only SSL certificates installed on domain directly in Domains > example.com > SSL/TLS certificates will be migrated. Certificates from Tools & Settings > SSL/TLS certificates are not migrated.
Global cron tasks from Tools & Settings > Scheduled tasks (Cronjobs) are not transferred.
The settings of the Plesk DNSSEC extension cannot be transferred.
Two or more migrations from different source servers cannot be performed at the same time.
- The Mail Usage Statistics are not transferred, these will be automatically calculated one day after migration.
Also note that:
- Websites PHP Performance settings seem to get migrated
- Websites PHP Common settings are NOT migrated, you need to check these if they are still compatible
This is also valid when switching between different PHP versions (eg. atomic-php56 to plesk-php56).
@Stéphan, thank you for the additional information, I'll double check that with developers and update an article with results.
Beware: Plesk Migrator won't migrate (without notice): MySQL routines, events, triggers, user-specific permissions, event scheduler status
I think points 10,11,12,13 are easy to implement. 15 and 18 may be handled with some sort of renaming feature, like you already do for databases with conflicting names.
About point 11, these settings may be migrated if PHP major and minor version match (for example having PHP 5.3.19 on target server and PHP 5.3.21 on destination server).
>Beware: Plesk Migrator won't migrate (without notice): MySQL routines, events, triggers, user-specific permissions, event scheduler status
As for events, they are supposed to be migrated since 2.9.2 version of Plesk Migrator which was released on 07 June, 2017. Refer to Plesk Change Log.
As for stored procedures, stored procedures are supposed to be transferred. Can you please clarify the following information:
- Plesk and OS version of both source and destination server
- versions of MySQL on both source and destination servers
As for user-specific permissions and event scheduler status, can you please provide more details? Do you mean that you set some custom permissions for db user through Plesk interface on source server and they were transferred incorrectly?
@Bulat, I retried the migration multiple timesbut the following objects weren't transferred: routines, functions, AFTER triggers.
Plesk is version 17.5.3 Update #25 on both servers. Plesk Migrator is version 2.11.4-0 on both servers.
O.S. is CentOS 6.7 with MySQL 5.6 on target server, Ubuntu 16.04.1 LTS with MySQL 5.7 on destination server.
> Do you mean that you set some custom permissions for db user through Plesk interface on source server and they were transferred incorrectly?
Yes, exactly. For user-specific permissions I mean GRANTs you can set from Tools & Settings > Database Servers > phpMyAdmin > User accounts (screenshots: https://snag.gy/5j4OFb.jpg - https://snag.gy/KXseUE.jpg). They weren't transferred at all.
As for Event Scheduler status I mean the global option you can enable from Tools & Settings > Database Servers > phpMyAdmin > (select a database) > Events (screenshot: https://snag.gy/gkS1ba.jpg). As you know, event scheduler should be enabled when you want to run events, so it's advisable to transfer the value of that setting. Actually, it wasn't transferred.
> I think points 10,11,12,13 are easy to implement. 15 and 18 may be handled with some sort of renaming feature, like you already do for databases with conflicting names.
> About point 11, these settings may be migrated if PHP major and minor version match (for example having PHP 5.3.19 on target server and PHP 5.3.21 on destination server).
As for these statements, it would be great if you provide your suggestions how Plesk migrator extension can be improved with your vision how it can be implemented at Plesk Uservoice. The top-ranked suggestions are likely to be included in future product updates.
@Marco, I've just checked that in test environment and indeed they were not transferred. I am going to report it to developers.
Our development team has investigated the issue and confirmed that it was caused by a product defect. A bug has been created: PMT-4065: Plesk Migrator does not transfer MySQL events, global user privileges, stored routines, event scheduler status. Thank you for bringing this to our attention!
We will do our best to fix the issue in one of the next Plesk Migrator updates. You may subscribe to this article to be notified when the bug would be fixed:
@Konstantin this issue affects restore of databases from backups too
Thank you for bringing our attention. This is predicted behavior and it will be fixed in scope of the same bug.
I didn't expect transferring a plesk data to a new server would be that time consuming!
I thought it would be less tedious.
On some other control panel this process could be done on one shot.
This migration tool is good but when we need to migrate some domains or a domain, but not good when we want to migrate the whole Plesk data to a new server, what if a company has 10 servers and need to migrate to a better hardware, will they have to keep on fixing issues and installing the required modules on the new Plesk servers to migrate?
I just need a replica Plesk server because I am migrating to a better hardware server, why Plesk can't migrate every thing and configure every thing the way the original server is configured?
Hello @Fouad Ahmed Fouad,
Thank you for sharing your thoughts about Plesk Migrator.
> what if a company has 10 servers and need to migrate to a better hardware, will they have to keep on fixing issues and installing the required modules on the new Plesk servers to migrate?
Yes, you are correct, it will be required to have required components installed on a target server.
> I just need a replica Plesk server because I am migrating to a better hardware server, why Plesk can't migrate every thing and configure every thing the way the original server is configured?
Plesk Development Team is constantly working on improving functionality and adding new features. However, for now, there are limitations described in the article.
I hope the extension will be able to migrate every thing in the future as you know anybody may have to migrate his Plesk server to a better one as I did recently, for a better hardware resources server.
I just noticed something, after resync mails form original server to the new server I got errors about missing email addresses on the new server, this happens twice after I resync from migration extension, the old server is Centos 6 with Onyx and the new server is Centos 7 with Onyx, this issue just solved by only running this after re-syncing mail!
Another issue I am still searching for a solution online which is, on the new server after migrating all domains, yes all are working fine! but Wordpress toolkit not showing all wordpress installations on its interface, only shows 3 wordpress instances from about 65 instances of wordpress. use scan for wordpress button didn't solve the issue, also there is no error I get back from scanning.
1. There is a possibility that such issue is caused by inconsistency in mail database. You have applied the correct solution.
2. It is expected that WordPress instances are not displayed in WordPressToolkit after migration. Scan process should be used to detect such installations.
However, in your case, this does not work. What are the versions of Plesk and WordPress instances, which are not detected?
Nothing worked BUT reinstalling Wordpress tool kit extension, afterwards scanning worked fine!
@Fouad Ahmed Fouad
Hello! Thank you for sharing this with us. Something wrong was with WP toolkit itself in this case. If you face a similar issue again, please create a ticket so we could find the reason for such behavior: https://goo.gl/Mn6Jpe
When this article states, "Custom webmail configurations like personal folders, address books and so on are not transferred", does that mean that any user's Horde Webmail address book (for example, from Plesk 11 on CentOS) will not be copied to the new server? I can't imagine this is the case.
Hello @Bob B,
Thank you for the feedback. Indeed, address books are not transferred.
Consider voting for this feature request: https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/32263882-improve-the-migration-manager-for-horde-identities
I'd just like to verify -- regarding Horde folders -- that it is only a Horde / webmail issue. When you say "personal folders" would an example of this be like adding a folder "new-clients" and putting all new client emails in that folder? If so, does all that email end up in their inbox after the migration, rather than a folder? And clients using an email client like Outlook, who have folders established, won't notice any changes. Is that correct?
Sorry for the late response.
Please, could you submit a ticket to Plesk Support?
To prepare an answer it will be required to perform tests and possibly involve the Development team for clarification.
Thank you for understanding.
I finished the migration a few weeks ago. I had my Horde clients save folders in the .mbox format which they could then import once the migration was complete. They also exported contacts. Horde folder emails must have ended up in their inbox, although i never confirmed that.
Hi Jeffrey Zeunert , please open a support ticket with us so we can investigate right away: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
Julian - thanks for your offer for me to submit a support request.
I was just looking for clarification on line 21 from your article on known limitation with migration:
"21. Custom webmail configurations like personal folders, address books and so on are not transferred."
The old server is gone at this point. So I don't think there would be a reason to open a support request.
Please sign in to leave a comment.