Mail filters should also be migrated when using the plesk migrator

/var/qmail/mailnames/example.com/jdoe/sieve/*

Hello,

Please add possibility to migrate service plans (packages) during migration from cPanel.
Currently, Service plans are not automatically created on Plesk servers.

Hello,

Please add the functionality to migrate domain DNS records during the migration from CPanel to Plesk.

At the moment, Plesk apply default DNS template for these migrated domains. All additional DNS records have to be added manually.

Add the ability to ignore missing PHP on target warnings for Migrator as it is right now, when that happens, all the domains end being marked with a "Warning" and they need to be checked one by one

add the ability to parse

/var/www/vhosts/system/example.com/conf/vhost.conf

/var/www/vhosts/system/example.com/conf/vhost_ssl.conf

files for included configuration files and migrate included files.

Add feature for the Plesk Migrator to remove the content from the target server which does not exist already on the source server.
It would be nice to be able to not only add but also remove files using Re-Sync in Plesk Migrator. So that Plesk Migrator will remove the content from the target server which does not exist already on the source server.

A process to support symfony projects

Currently any customization made into AWStats configuration files (for domain /usr/local/psa/etc/awstats/* or server-wide /etc/awstats/awstats.conf), for example, language changing are not migrated. It would be nice feature to add ability to migrate such settings, so that users do no have to turn it back manually

An opportunity to migrate databases of the domains in one subscription to different database servers

After a migration from Plesk to Plesk, configured DNS slaves with the extension ***** DNS Manager are not notified about the new master of the zone for migrated domains.
It could be done while clicking on 'Switch DNS' in advanced mode with the commands rndc delzone example.com and rndc addzone example.com {etc...}.

Add an opportunity to migrate additional FTP accounts with 'crypt' password via Plesk Migrator

Right now, these accounts are not migrated because Plesk cannot store hashed passwords for system users

Hello,

Please add fucntionality to migrate only one domain from the subscription, including configuration, mail boxes and databases.

For example, If I need to migrate an additional domain from a subscription and the subscription has a lot of additional domains, the migration of whole subscription is feasible.

I would have started using plesk right away . Sorry to say I need to be able to upload a few thousand account details via CSV files

Sometimes, migration has to be quick.
But when there is a domain containing many big files (videos, big archive, ...) that will slow the migration process.
It would be a good idea, I think, to let the user exclude/include folder from migration process.
May be just add an option in the CLI command like :
plesk-migrator copy-contents --skip-folders-list=[FILE WITH FOLDER LIST]

In case of migration and the customer use 3rd party Name servers, it would be useful to be able to redirect all requests that come to old ip to the new server ip.
This will helpp to avoid downtime

I recently migrated to a new server and most went smoothly.
Alas all horde settings an especially the additional identities I had added are gone and it is a real pain to add them one by one.
So please make the migration manager aware about horde settings and migrate those properly too.

We are only able to use a FTP connection to migrate a website. It would be a nice add to be able to use SFTP and FTPS to connect to the old server,

The current website import function only allows entry of the source domain name.
I need to specify the ftp server details separately as for some hosts the ftp server is on a different ip to the website and the current import function fails as it fails to access either the website or ftp server depending on which info was entered as the source domain.

Please add to Plesk Migrator the ability to:

1. migrate all crontabs, as currently, only the last created task for a domain will migrated;


2. disable crontabs on target server before migration, to avoid unpredictable effects with those scripts that interact with the outside;


3. MySQL routines;


4. MySQL events;


5. MySQL event scheduler status on/off;


6. user permissions that you set from Tools&Settings > Database Servers > Manage via DB WebAdmin" - see https://snag.gy/HWyFRS.jpg