• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Important Plesk Migrator extension

custer

custer

Administrator
Staff member
Hi everyone,

We have released the new version of Plesk Migrator extension - v1.8. Changes include:

[+] If XML API RPC on the source Plesk server is not available, migration is still possible.
[+] Plesk Migrator installation on Windows became more easy and intuitive because of adding installer, automatic firewall configuration, and other improvements.
[+] Plesk Migrator user interface was translated to all languages supported by Plesk.
[+] Administrator now can perform migration from Helm 3 using the Plesk Migrator user interface.
[-] Migration from Helm 3 failed if some of the source servers did not exist anymore. (PMT-2315)
[-] Migration from cPanel failed in case of broken "shadow" file for some domain on the source server.(PMT-2432)
[-] Migration of the whole server could not be performed without replacement of existing domains. (PMT-2538)

Let us know what you are waiting for the most in the upcoming versions of Plesk Migrator!
 
Last edited:
Hi all,

Next version of Plesk Migrator 1.8.4 has been released just now!

Here are the changes:

[-] If a customer email information was not identical on the source and the target servers, it was impossible to re-migrate such customer or synchronize its content. (PMT-2606)
[-] (On Linux) During migration from Confixx, the mail quota value was migrated incorrectly. (PMT-2531)
[-] (On Windows) Migration failed, if several subscriptions on different service plans were selected within single reseller. (PMT-2608)
[-] (On Linux) Migration from Confixx failed if Perl configuration was broken on the source server. (PMT-2613)
[-] Not clear error message was displayed when installing Plesk Migrator via the Plesk extensions catalog. (PMT-2583)
[-] Migration finished with errors when a subdomain with the "Subdomain on subfolder" hosting type was migrated. (PMT-2593)
[-] (On Windows) Improved logging of commands executed by Plesk migrator. (PMT-2544)
[-] (On Windows) Migration failed if the "rsync" folder was removed from the source server. (PMT-2546)
[-] (On Linux) The migration "debug.log" file could not be downloaded in UI if too large and exceeded PHP limits. (PMT-2552)
[-] Migration failed when a subscription with a subdomain was migrated from dedicated to shared IP address. (PMT-2473)
[+] Post migration checks were added for a custom migration module. (PMT-2498)
[+] (On Windows) Speed up of the step when Migrator pulled objects from Helm 3 and displayed them for choosing. (PMT-1300)

If you have any wishes about further Plesk Migrator improvements, just let us know.
 
We have released new version of Plesk Migrator 1.9.7!

The changes are:

[+] Migration from Parallels Pro Control Panel for Linux to Plesk 12.5 is now supported.
[+] Migration from Plesk to Plesk works correctly if the virtual hosts directory location differs for source and destination servers.
[-] Migration of customers with diacritical symbols in login names failed. (PMT-2625)
[-] If a hostname of a local Microsoft SQL database on the source server contained port number, the database content could not be migrated. (PMT-2638)
[-] Helm 3: Migration from Helm3 for parked domains with no web hosting failed and a wrong error message was displayed. (PMT-2609)
[-] Helm3: Domains with forwarding enabled could not be properly migrated. (PMT-2611)
[-] Subscription restoration via command line could stuck in case some specific errors were returned. (PMT-2140)
[-] Confixx: Catch-all mail addresses were not migrated correctly. (PMT-2644)

You are welcome to post here any questions or suggestions.
 
Hi All,

New version of Plesk Migrator 1.10 has been released!

Many issues were fixed based on feedback from customers.

What's new:

[+] Upgrading the Plesk Migrator component is now blocked if a migration is in progress or if some files in the panel-migrator/backend/ directory are locked.
[-] If a reseller was selected for migration, customers belonging to the administrator were migrated as if they belonged to a reseller. (PMT-2697)
[-] Migration from Plesk on Linux hanged if two or more subscriptions with system user names present on the destination server were being migrated. (PMT-2716)
[-] If the Backup Manager component was not installed on the source Plesk server, some critical objects were not restored after migration. (PMT-2696)
[-] Warnings displayed on the pre-check screen persisted even after fixing the root cause and clicking Refresh. (PMT-2632)
[-] Custom error documents were not transferred during migration from Plesk for Windows servers with .NET Framework 2.0 installed to Plesk servers with .NET Framework 4.0. (PMT-2586)
[-] When key-based authentication was used during migration, Plesk Migrator generated a new pair of keys. (PMT-2548)
[-] Custom error documents could not be restored after migrating domains with virtual directories pointing to the domain's httpdocs directory. (PMT-2636)
[-] Webmail was enabled for a subscription on a destination server after migration even if it was disabled on the source server. (PMT-2688)
[-] The behavior of the "Transfer the following configuration and content" option was not described clearly in the Plesk Migrator user interface. (PMT-2642)
[-] Descriptions of resellers, customers, subscriptions, and mailboxes were not transferred during migration from Plesk. (PMT-2630)
[-] If a migrated subscription could not be created in Plesk, the post-migration check report was not generated. (PMT-2527)
[-] Migration stopped if a subscription included into the migration list was absent from the source server. (PMT-2659)
[-] No error messages were displayed in the Plesk Migrator user interface if there were no available IP addresses on the destination server. (PMT-2596)
[-] In some cases the migration could fail because the pre-migration check calculated the number of available domains on the destination server incorrectly. (PMT-2532)
[-] Content placed in folders excluded from the migration was lost. (PMT-2637)
[-] Migration could not be started if a source panel type was selected incorrectly during the first attempt to start a migration. (PMT-2683)
[-] If the migration was performed with the "Adjust the configuration files of commonly used web applications" option disabled, the migration report contained an empty "Adjusted applications" section. (PMT-2681)
[-] The description of the "ssh-key" option in the samples of configuration files was unclear. (PMT-2671)
[-] Parallels Pro Control Panel: During migration of IDN web site from Parallels Pro Control Panel for Linux, language-specific characters were migrated in Punycode. (PMT-2650)
[-] Helm: During migration from Helm 3, the private files of a domain were migrated to a directory with a duplicated domain name in the path. (PMT-2658)
[-] cPanel: During migration from cPanel, unprocessed Apache access log files were not transferred to Plesk. (PMT-2475)

If you have any thought on how to improve Migrator, please share.
 
Migrator 1.10.5 has been released!

There was only bugfix in this build:

[-] Migrations from Windows servers sometimes failed due to the TCP connection timeout if an individual operation took too long to complete. (PMT-2741)

Please share if you see how we can improve Migrator.
 
Migrator 1.11.1 has been released!

Here is what's new:

[+] During migration on Windows, the provided user accounts on source and target servers are now validated to have enough privileges to perform all required operations. On the migration settings screen, it is possible to select if the RPC agent should be installed automatically or manually.
[+] During migration from Confixx, cPanel, and Helm 3, a warning message is displayed if the user passwords hashing methods do not conform to the MySQL settings on the target server.
[-] Migration was blocked if a target server had a default MySQL server on a non-default port. (PMT-2743)
[-] Additional users were not transferred after migration of a customer or a subscription belonging to a reseller. (PMT-2728)
[-] In some cases, the number of subscriptions that were migrated unsuccessfully was calculated incorrectly. (PMT-2773)
[-] In case of source Plesk database inconsistency, DNS records could be duplicated during migration on Linux. (PMT-2462)
[-] Migration stops if there were no shared IPv6 addresses on a target server and a source server contained a shared IPv6 address.(PMT-2785)
[-] Copying of all DB and mail content did not start unless file content copying is finished.
[-] The keep alive time of RPC agent could not be configured, so the idle RPC agent connections could be dropped while executing of time consuming operations on the source server. (PMT-2753)
[-] Migration log accessible via the Plesk user interface contained suggestions to perform some operations via CLI. (PMT-2576)

Please share if you see any other possible improvements to Migrator.
 
Last edited:
I am glad to announce release of Plesk Migrator extension v.1.12

Changes:

[+] Microsoft SQL database migration improvements: now the dump of the source server is created by means of Microsoft SQL and the interaction with the database server is performed from the source server, thus solving the problem of connection from the remote servers.
[+] Improvements of mail content migration on Windows: copying of mail content is now faster, the content is synchronized during the repeated migration so that only new emails are copied.
[+] Migration of subscription permissions on Windows was optimized for better performance in case of large amount of directories.
[+] Hosting description samples were added to the Plesk Migrator extension. (PMT-2732)
[-] Plesk Migrator user interface could become unavailable in case of problems of migration session directory. (PMT-2953)
[-] Migration failed if a subscription contained additional users with passwords in wrong Base64 encoding. (PMT-2933)
[-] Confusing error messages were displayed after removing of the Plesk Migrator extension (PMT-2912)
[-] Migration of Microsoft SQL database failed in case when Microsoft SQL server was running under a custom user. (PMT-2888)
[-] Migration from Confixx was blocked in case when some binary data was present in database fields on the source server. (PMT-2884)
[-] Error reporting was unclear in case of Plesk migration for some non-English Windows localizations. (PMT-2877)
[-] Migration from custom hosting: Post-migration checks were applied for all subscriptions and not only for those that were selected for migration. (PMT-2876)
[-] The check-infrastructure command in CLI failed if it was run before the check command. (PMT-2874)
[-] After migration from Plesk on Windows some temporary data remained on the source server. (PMT-2873)
[-] If business model for a domain was not converted after upgrade from Plesk 9.5 to Plesk 10.1 on a source server, such a domain was not included into a migration list. (PMT-2867)
[-] Migration from custom hosting: Plesk Migrator tried to add the "www" prefix to a domain with wildcard in name when this option was not allowed by Plesk. (PMT-2865)
[-] In case database is switched from source to target without actual data transfer (DB assimilation), no any messages about this were included into the info.log file during migration. (PMT-2860)
[-] In some cases additional users of subscription could get wrong email address after migration. (PMT-2859)
[-] Migration on Linux failed if the “root” user's home directory pointed not to /root. (PMT-2856)
[-] Migration from Confixx failed if a domain contained several subdomains with forwarding from one to another by chain. (PMT-2852)
[-] Migration list generation is blocked if a subscription is associated with absent add-on service plan or if add-on service plan belongs to another owner. (PMT-2837)
[-] Migration failed for a subscription with dublicated DNS records. (PMT-2829)
[-] Migration of a protected directory from Confixx failed if the directory name contained spaces (PMT-2826)
[-] Every next call of the dump agent cleared the logs of a previous call of dump agent in the migration session directory. (PMT-2822)
[-] In case DNS service was turned off on the source server Plesk Migrator still verified if it is enabled on the target server. (PMT-2821)
[-] Migration on Windows failed if the Windows dump agent output contained some garbage caused by third-party DLLs. (PMT-2799)
[-] Migration on Windows failed when IPv6 was used for connection to a target Plesk server. (PMT-2794)

You are welcome with any suggestions on further improvement.
 
Last edited:
Migrator 1.14.4 has been released!

Changelog:

[+] It is now possible to migrate mail content from remote mail servers.
[+] Increased log level for operations related to hosting structure created on target server. The logs now include such operations as creation of domains, DBs and mail accounts. Error reporting has been improved.
[-] Migration was blocked if the "authorized_keys" file on the source server was corrupted. (PMT-2995)
[-] Content synchronization after migration worked too slowly in case of many subscriptions. (PMT-2989)
[-] Rare issue with accessing destination Plesk server by API appeared on Windows 2012 R2. (PMT-2988)
[-] Unable to configure interaction with target Plesk server API via HTTP. (PMT-2980)
[-] Reseller accounts with no subscription at source server could not be migrated. (PMT-2964)
[-] Capability check failed when DB at source Plesk server was inconsistent. (PMT-2963)
[-] Migration on Linux failed if migrator was run under user with user name other than root but with root privileges. (PMT-2401)

As usual, you are welcome with suggestions on further Migrator extension improvements.
 
Migrator 1.14.6 has been released

Changelog:

[-] Repeated migration failed for a domain if its name was in IDNA (ASCII) form on the source server. (PMT-3028)
[-] Migration failed for mail accounts of an add-on domain if the mail service was not described in the hosting description file. (PMT-3022)
 
Migrator 1.14.8 has been released

Here is what's new:

[-] Migration was blocked if the minimum password strength was set to strong or very strong on the target server. (PMT-3034)
[-] Migration of a mailbox on Windows to MailEnable or IceWarp mail server from some other mail server failed in case when a mail message contained too long message ID in the mail header. (PMT-3031)
 
On Sept 19 Migrator 1.14.11 was released

What's new:

[-] An external ID of a subscription, customer, or reseller was missing on the target server after migration. (PMT-3035)
[-] Migration was performed incorrectly if a subscription was mapped to a private IP address associated with a public IP address on the target server. (PMT-3049)
[-] Error messages were displayed after migration of a subscription not synced with a service plan on the source server if the default limits of the service plan where exceeded on the target server. (PMT-3050)
 
Migrator 2.0.2 just has been released!

What's new:

[*] Plesk Migrator interface improved drastically. Many features enabled in UI that previously had been present in CLI only.
[-] After removing migrated subscriptions from the source server, associated MySQL databases hosted on a remote MySQL server registered both in the source Plesk and the destination Plesk were removed as well. (PMT-3077)
[-] When migrating multiple subscriptions to a Plesk for Windows server with a Microsoft SQL Server installed locally and one or more remote Microsoft SQL Server instances registered in it, all Microsoft SQL Server databases associated with the subscriptions being migrated were created in the Microsoft SQL Server set as default on the administrator level, even if one or more subscriptions were assigned to a service plan which had a different Microsoft SQL Server specified as default. (PMT-3045)
[-] When migrating from Confixx, a confusing error message was logged if Plesk Migrator was unable to retrieve DNS server settings on the source server. (PMT-3021)
[-] Migration failed if the IP address and port of the Microsoft SQL Server on the destination server were separated by a comma in the database server properties. (PMT-3056)

Your feedback about new look & feel is much appreciated.
 
Last edited:
Plesk Migrator 2.1 has been released!

What's new:

[*] Multiple GUI improvements for migration to Onyx.
[-] User role permission settings were ignored during migration. (PMT-3137)

Your feedback is greatly appreciated, as usual.
 
Last edited:
when will the "ImportError: No module named yaml" issue be fixed on Onyx? Fresh CentOS 7 + Onyx install and latest version of extension.

STDERR:
Traceback (most recent call last):
File "/usr/local/psa/admin/sbin/modules//panel-migrator/plesk-migrator", line 16, in <module>
from parallels.core.cli.migration_cli import run
File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/migration_cli.py", line 7, in <module>
from parallels.core.cli.common_cli import Command, CommandTypes, \
File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/common_cli.py", line 21, in <module>
from parallels.core.utils.log import Log
File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/utils/log.py", line 4, in <module>
import yaml
ImportError: No module named yaml
 
IgorG said:
Make sure that package plesk-py27-pyyaml is installed on your server.
Click to expand...

not available in the repo's and hasn't been installed by the installer. There is a plesk-py27-devel that is available but doesn't help.

====================================================== N/S matched: plesk-py27 =======================================================
plesk-py27.x86_64 : An engine for run Plesk migration scripts
plesk-py27-devel.x86_64 : Development files for Plesk migration scripts
plesk-py27-pip.x86_64 : The PyPA recommended tool for installing Python packages
plesk-py27-setuptools.x86_64 : Easily download, build, install, upgrade, and uninstall Python packages
plesk-py27-virtualenv.x86_64 : Virtual Python Environment builder
 
You must log in or register to reply here.

Similar threads

S
Apache does not apply .htaccess directives for certain files after migration through Plesk Migrator
Replies
2
Views
728
NewGate
N
EnriqueR
Resolved Problem when migrating subscription. Unhashable type list
Replies
8
Views
686
abdulsemiu
A
T
Resolved Plesk Migration: critical error: Object of type filter is not JSON serializable
Replies
11
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
L
Issue Migration problem
Replies
8
Views
687
Kaspar@Plesk
Kaspar@Plesk
K
Issue Plesk Migrator - Obsidian 18.0.56 - Errors / unable to migrate
Replies
4
Views
3K
salvis
S
Back
Top