migration manger via ssh keys ignores config in /root/.ssh/config

I want to migrate from a server I have to access via a jumphost. I have ssh config so that I can just "ssh sourceserver" at the command line. The migration manager ignores the config and cant be made to access the source server.

Would be nice to have the ability yo perform site import or migration via CLI on Plesk for Windows, currently this is only available for Linux.

It would be nice to have a timer that will show time left to finish the site transfer via Site Import extension.

ssh can be configured to listen on different port numbers. The default is port 22. It can also answer on port numbers up to 65535, but the field on the migrator only takes 4 digits. I have ssh listening on a 5 digit port. This is just bad form.

Plesk Migrator should have options for migrating Server Settings. For example, have a checkbox for migrating the server timezone, Server hostname, DNS Template, etc.

Please add the ability to store domain mail content in the domain folder like in cPanel /home/$user/mail/domain.tld/emailuser/

In this case, it will be possible manually create a backup for website and mail content just by copying /home/$user/ folder and after restore this folder on the destination server.

It would be great if transferring of generated keys and DB records of DNSSEC configuration for a domain during Migration will be implemented. Thus there would be no need to recreated them for each migrated domain.

At the moment it is possible to migrate only from the following ISPmanager versions to Plesk using a CLI method:

ISPmanager 4 Pro
ISPmanager 5 Business

Please add a possibility also to migrate from ISPmanager 6 to Plesk using a CLI method

When migrating a domain to a new server the Mattermost's data/chats present in the old server should also be migrated to the domain in the new server when Plesk Migrator Tool is used, or create a tool that makes it possible.

Please allow selecting specific mailboxes for transferring with Plesk Migrator

As above.

Currently, it just fails as it tries to create the mail account on the receiving server which already exists on the mail server.

At the least, you could allow migrations to exclude the entire mail domain and then make an account import tool to bring them into the receiving server.

Migrator should take into account the database server type (remote or local) and change user permissions accordingly. Currently, users that was set on the source with permissions to connect locally to a local database are migrated to the target with the same permissions, despite the fact, that on the target database server is set as a remote. That leads to inability to connect to remote database for that user on the source after migration and migrator change the permission accordingly.

solution idea 1. rename the index.php per default to index_.php after mirgration is done rename to index.php

solution idea 2.suspend the domain, i think than its not possibile to access it.

the cron could cause putting stuff in the database while the mirgrations of very large databases is running.

show the data syncing progress during a migration on Plesk MIgrator's log - right now if one has a large subscription to be migrated, there's no way to find out how much was synced over to the target server.

Within the "Mail Importing" section it would be helpful to show percentages of work (and other stats) and a remove button to hide old unnecessary import requests.
Best regards.

Make Plesk Migrator also migrate cronjobs for domain while migrating from cPanel. This decrease the number of manual actions that required to perform by customer after the migration.

https://support.plesk.com/hc/en-us/articles/213410369-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk-

Add the ability to convert a Plesk mail backup into .PST and other fofular formats, so the customer can quckly migrate his mail data from a non-Plesk server to Plesk server and vice versa.

Currently migration of mail messages performed when SmarterMail v100 is used performed via IMAP protocol. This is slower then simply copying file. Please add ability to migrate messages via simple copying too to speed up migration.