The new and improved Plesk Migrator user interface covers features previously available in CLI (Command Line Interface) only, giving your migrations **heightened stability** and **improved performance**. Gain control by seeing exactly what is migrated and what stage it's at. No need to call command line utilities to perform migrations. Enjoy a **more granular process**, with different phases per subscription, completely for free! - Ability to run various operations within migration of a subscription: pre-check (software compatibility), post-migration check (validates that major services of subscription are up and running on destination after migration completed), **subscription data synchronization**, objects synchronization (in case some changed on source server while migration in progress). - **Detailed queue status** for subscriptions selected for migration, showing operation in-progress for all selected subscriptions. - Variety of cool new features: **subscriptions mapping** to other client / reseller / plan / IP on destination server before migration started. - "Finish migration feature" - gracefully end migration of all subscriptions that started being migrated. - Simple mode: lets to do bulk migration of many subscription at once. - Advanced mode: lets you customize the process for each subscription.
# 2.11.4 (20 September 2017) * [+] Plesk Migrator now supports importing websites with Joomla, Drupal, and Prestashop installed (with certain limitations, to learn more, read Migration Guide for details). * [+] Users can now view the migration log in real time and search the log for key phrases in the Plesk Migrator interface. * [*] The reliability of migrations from servers with non-English locale has been improved. * [-] Re-syncing a subscription that was reassigned to a different owner during migration flooded the migration log with PHP notices, and could corrupt the Plesk Migrator interface if the `display_errors` PHP option was enabled. (PMT-3887) * [-] Migration from Plesk failed if one or more customer passwords on the source server decrypted to 'none'. (PMT-3876) * [-] When migrating from Ubuntu or Debian to CentOS or RedHat Enterprise Linux (or vice versa), subscriptions with files owned by the web server that contained non-UTF-8 characters could be assigned to incorrect owners. (PMT-3860) * [-] Migration could not be started if one or more secret keys in the Plesk database could not be decrypted correctly. (PMT-3298) * [-] When migrating from Helm via the command line, the shallow-dump.xml file was created anew during each migration stage, which considerably prolonged the migration. (PMT-3921) * [-] Migration from Helm failed if one or more packages had enabled features whose parent plan was deleted. (PMT-3912) * [-] The post-migration report did not contain information about missing DNS records for domains whose names contained IDN characters. (PMT-3906) * [-] Migration from Helm failed if one or more identical IP addresses were registered as both shared and dedicated on the source server. (PMT-3878) * [-] Under specific circumstances, copying of mail content for individual mailboxes could fail. (PMT-3868) * [-] Copying of mail content could fail when migrating MailEnable accounts with a large number of mails. (PMT-3866) * [-] On servers with the Chinese locale, under specific circumstances, syncing Microsoft SQL Server databases could result in an error. (PMT-3832) * [-] Migration from a server with Japanese locale could fail with a misleading error message when copying website content. (PMT-3705) * [-] When importing an application to Plesk for Windows, the import could fail if the application had an exceedingly large number of files. (PMT-3975) * [-] Plesk Migrator could not set the correct permissions for statistics and logs directories. (PMT-3934) * [-] Migration from Plesk failed if MariaDB 10.0.32 or later was installed on the source server. (PMT-3916) * [-] When migrating a subscription with Magento installed, the Magento configuration file was not updated if the Magento database was renamed during migration. (PMT-3513) * [-] When migrating a subscription with Prestashop, the Prestashop configuration file was not updated if the Prestashop database was renamed during migration. (PMT-3520) * [-] When importing an application, the contents of all application files were lost if the specified domain name belonged to a domain already hosted on the target server. (PMT-3967) # 2.10.10 (20 July 2017) * [+] A running site importing can now be stopped. * [*] When importing directories, the path on the target server is shown on the import screen. * [*] When migrating from Plesk versions 11.0 to 12.5, if a certain password can not be decrypted, migration does not stop, but a new random password is generated instead. * [*] Sample configurations for migrating from and to Plesk servers with remote SmarterMail were added. * [-] When migrating from Plesk 17.0 or later, encrypted passwords of additional FTP accounts were replaced with new random passwords. Now such passwords are migrated without changing. (PMT-3689) * [-] If the target server's Plesk license did not include reseller accounts, migrating accounts with reseller privileges resulted in errors. Now Plesk Migrator handles such accounts in the following way: * all customer accounts, belonging to the reseller, become regular customer accounts; * all subscriptions, belonging to the reseller, are assigned to the administrator account; * the reseller account itself is not migrated. (PMT-3795) * [-] Plesk Migrator failed to find the document root of an IDN subscription, which resulted in website import failing with an error. (PMT-3809) * [-] Report about failure to transfer a file by FTP during site importing contained unnecessary information from program logs. Now only a short report is shown with a list of such files. (PMT-3713) * [-] Java applications could not be migrated between Plesk servers. (PMT-3779) * [-] A customized subscription expiration date was not migrated from Plesk 17.0 or later. (PMT-3843) * [-] After consecutively running Switch DNS and Revert DNS on a migrated subscription, the subscription's checkbox on the advanced mode screen was still selected. (PMT-3835) * [-] Migrating to Plesk Multi Server configured to use a non-standard SSH port resulted in failing to copy content with an 'Unable to connect' error. (PMT-3816) * [-] The results of post-migration checks were always marked as 'Errors', even when all checks succeeded. (PMT-3820) * [-] The websites' files with names, starting with a dot, were not imported. (PMT-3817) * [-] If an attempt to perform DNS Switch with UI failed due to some problem, the following attempts resulted in errors even if the problem was resolved. (PMT-3845) * [-] When migrating from DirectAdmin, some subscription limits could be migrated incorrectly. (PMT-3794) * [-] When migrating to Plesk Multi Server, skipping pre-migration checks for a subscription resulted in failure to migrate such subscription. (PMT-3822) * [-] When migrating websites from a Confixx server, the SSL certificates were transferred to the subscription's certificate pool and were not available for the subscription's domains. As a result, after any webserver reconfigration the websites became unable to use their certificates and had to use the default Plesk certificate. (PMT-3818) * [-] If the source server was configured to produce any output in a non-interactive shell (such as an SSH welcome message), migration failed with an error. Now Plesk Migrator detects such configurations and shows a comprehensive message, explaining how to fix the issue. (PMT-3823) * [-] When migrating from a server with Horde webmail to a server with different webmail, Plesk Migrator attempted to restore the mail address book, which resulted in an error. Now Plesk Migrator detects such situations and does not try to restore the address book. (PMT-3806) * [-] On Windows servers, if the source system had services with names or descriptions, containing non-ASCII characters, the whole server migration failed with message 'Failed to remove missing Python and Perl scripting options from backup dump'. (PMT-3704) * [-] If a subscription on Helm 3 server had a mail service enabled, but no mail IP available, migration of the subscription failed. (PMT-3856) * [-] When migrating from Helm 3, subscriptions of customers with login name longer than 15 characters were skipped without notification. (PMT-3849) * [-] On Windows servers migration GUI missed a link for downloading the RPC Agent installation package. (PMT-3829) * [-] On Windows servers, under certain circumstances, dumping MySQL databases when migrating IDN subscriptions failed with 'Unicode Encode Error'. (PMT-3825) * [-] Synchronizing or repeated migration of subscription's business objects (like databases, email accounts or domains) to a server with remote SmarterMail failed. (PMT-3819) * [-] Restoring MS SQL databases on IDN subscriptions failed. (PMT-3840) * [-] Subscriptions migration from Helm 3 servers failed, if the subscriptions were using web forwarding and had mailboxes and/or databases. (PMT-3859) * [-] Migration from Windows 2003 x64 servers with non-English locale failed while copying files with message 'Failed to copy web files for subscription'. (PMT-3027) # 2.9.2 (07 June 2017) * [+] An option to migrate a reseller with all accounts and subscriptions has been implemented. * [+] Now when a subscription, owner or subscription plan is already migrated, it can be hidden from the 'List of subscriptions' tab. * [+] When migrating from cPanel, there is an option to choose whether to migrate subdomains and domain aliases as addon domains, thus preserving the related email accounts. * [*] The DirectAdmin migration agent now checks the data consistency on the source side. It correctly performs migration even when there are errors in the configuration of some domains. The overall fault tolerance of the agent has been improved. * [*] The 'List of subscriptions' tab was added to the migration screen. It replaces the 'Add subscriptions' tab in simple mode, or the 'Subscriptions list' tab in advanced mode. * [-] When migrating sites from cPanel, the Plesk Migrator detected a single WordPress instance as two separate instances. (PMT-3672) * [-] MySQL events were not transferred during migration. (PMT-3677) * [-] In certain circumstances it was impossible to import a website, if its webspace had files with names, containing non-ASCII characters. (PMT-3703) * [-] Now, if the target database has earlier version and does not support some features of the source database, a comprehensive message is shown at the end of migration. (PMT-3241) * [-] MySQL databases could not be migrated if a database's admin password did not match the password stored in the PSA database. (PMT-3778) * [-] Migration of mail content from cPanel failed, if the home directory on source was different from `/var/home/` (PMT-3212) * [-] Several domain aliases, created by cPanel for internal purposes, were migrated as domain aliases in Plesk. Now Plesk Migrator recognizes and ignores such technical aliases. (PMT-3506) * [-] Plesk Migrator did not set a password for the source server's user that it creates for copying content. Some servers' configurations forbid SSH authorization of such users, thus making copying unavailable. (PMT-3558) * [-] Additional Apache and nginx directives of subscriptions were not transferred. (PMT-3072) # 2.8.7 (24 May 2017) * [+] When importing sites, databases, or directories, the actual status of each item is displayed. If import of an item failed or generated a warning, a detailed list of issues is available. * [-] Removing an additional domain that was previously imported from another server resulted in an error in Plesk panel. (PMT-3701) * [-] In case of a database name or database user name conflict during site import, if there were additional spaces between the names and values of corresponding variables in the `wp-config.php` file, the WordPress application did not work after import. (PMT-3673) * [-] Passwords for accounts with names, containing Unicode characters outside of ASCII range, could not be decrypted after migration. (PMT-3667) * [-] If the source FTP server did not support TLS, this negatively affected the performance during import site. (PMT-3643) * [-] When migrating from Plesk Onyx, an error in decrypting a password for an account could result in resetting passwords for all accounts. (PMT-3604, PMT-3605) * [-] Extension data on the target server could be overwritten by data from the source server. Now by default the server-wide extension settings are not migrated. (PMT-3586) * [-] Overuse policy for reseller accounts was not migrated and instead was reset to 'Overuse of disk space and traffic is allowed'. (PMT-3469) * [-] Database import failed if the PHP process had no write permission on the source server. (PMT-3682) * [-] Copying a MySQL database from Plesk Onyx on a Linux server failed if the database server password was stored in plain text format. (PMT-3759) * [-] Protected directories on subdomains were not migrated from DirectAdmin. (PMT-3764) * [-] When using PureFTD on the source server, the site import performance was lower than expected. (PMT-3679) * [-] Under certain circumstances, migration from a Plesk for Linux server could fail with an error message "Cause: 'int' object has no attribute 'isdigit'". (PMT-3621) * [-] SSL Certificate Authority certificates were not migrated from DirectAdmin. (PMT-3613) * [-] When migrating mail messages to Plesk for Linux via IMAP, if a mailbox name contained an uppercase character, the messages in it were not migrated. (PMT-3607) * [-] When migrating from DirectAdmin, a cron task with a certain syntax could not be parsed. (PMT-3544) * [-] When migrating from DirectAdmin, if a mailbox had an automatic reply set up, but the corresponding template file did not exist, the migration could not be performed. (PMT-3542) * [-] When migrating from or to a Plesk server with a remote SmarterMail server: the type 'A' DNS records for mail (`mail.*`) were migrated incorrectly. (PMT-3725) * [-] When migrating from Plesk with a remote SmarterMail server to Plesk with a local SmarterMail server, or vice versa, the webmail settings for hosting plans and subscriptions were not converted as intended. (PMT-3723) # 2.7.9 (27 April 2017) * [-] Site migration was blocked if the source web server rejected requests without the User-Agent header. (PMT-3698) * [-] Subscriptions migration failed and the subscriptions were marked as migrated with errors during migration from Plesk for Windows 8.6, 9.5 or 10.4. (PMT-3702) # 2.7.7 (20 April 2017) * [-] When migrating to a Plesk server using a non-English locale, a confusing error message was displayed if the name of one or more files or directories on the source server contained national characters. (PMT-3294) * [-] The lack of notifications or a progress bar during post-migration checks could confuse the user. (PMT-3309) * [-] Migration could fail if multiple perl versions were installed on the source server and the PATH environment variable pointed at a custom perl version. (PMT-3376) * [-] Web content was not copied if SSH access to the source server was limited to specific users and the users 'plesk-migrator*' were not allowed access. (PMT-3385) * [-] PostgreSQL databases could not be migrated if PostgreSQL server version 9.5 or later was installed on the source server. (PMT-3391) * [-] Under specific circumstances, the "Failed to remove temporary user" error was displayed during migration even if the temporary user was removed. (PMT-3399) * [-] Entries in the subscription log were not sorted by date. (PMT-3525) * [-] Microsoft SQL Server databases could not be migrated if the Microsoft SQL Server instance on the source server was configured to use a nonstandard port. (PMT-3547) * [-] The header on the migration screen was corrupted if the Plesk interface language was set to Italian. (PMT-3548) * [-] When migrating from DirectAdmin, quota for mailboxes was set to 100 MB even if it was set to unlimited on the source server. (PMT-3550) * [-] Trying to re-sync business objects after deleting a mail account on the source server produced a confusing error message. (PMT-3552) * [-] During site migration, WordPress sites using a remote database were not re-configured to use the database migrated to the destination server's MySQL server. (PMT-3562) * [-] Removing the session folder created after initiating a site migration resulted in empty session folder and configuration file getting created. (PMT-3579) * [-] If during migration names of some databases and database users were changed, after upgrading Plesk Migrator to the latest version and restarting the migration, the name changes were not preserved. (PMT-3582) * [-] When migrating from DirectAdmin, if a mailbox and a forwarder with the same name were present on the source server, only the forwarder was migrated. (PMT-3585) * [-] When migrating from Plesk Onyx, extension files stored in the "/usr/local/psa/var/modules/" directory were assigned incorrect ownership. (PMT-3587) * [-] Migration from DirectAdmin failed if a DNS zone contained a white space character as a separator. (PMT-3600) * [-] When migrating from Plesk, the "Restrict the ability to follow symbolic links" hosting plan setting was disabled on destination server even if it was enabled on the source. (PMT-3602) * [-] Migration from DirectAdmin failed if a protected directory created in DirectAdmin was not physically present on the file system. (PMT-3618) * [-] Migration from DirectAdmin failed if one or more mail users on the source server did not have a home directory configured. (PMT-3645) * [-] Migration to Plesk Onyx could fail if one or more customers on the source server had unicode characters in their name. (PMT-3646) # 2.6.11 (29 March 2017) * [-] Migration of folders from a web site failed if an FTP server on the source server returned relative paths in the list of the folders. (PMT-3563) * [-] The list of folders for migration could not be obtained by Plesk Migrator if "." or ".." were present in the folders list returned by the FTP server. (PMT-3569) * [-] Migration of a web site content failed if the FTP connection was unexpectedly closed on copying the content. (PMT-3567) * [-] Migration of a web site content failed after upgrading Plesk Migrator from version 2.1 or earlier to a later version. (PMT-3568) * [-] The database of an imported WordPress site could not be migrated if the time of files migration exceeded the IDLE timeout of the source FTP server. (PMT-3575) * [-] A WordPress site could not be migrated if redirection was enabled on the source domain. (PMT-3571) * [-] Website migration could be blocked if the session folder was deleted after the migration. (PMT-3576) * [-] Website migration failed with an uninformative error message if the document root could not be detected automatically. (PMT-3574) * [-] The migration progress dialog got stuck if an error occurred while retrieving data from the source server. (PMT-3573) # 2.6.3 (23 March 2017) * [+] Migration of files, databases, and WordPress sites from any server available via FTP is now supported. * [-] Database content could not be synchronized in Plesk for Windows when different remote Microsoft SQL servers were used by the source and the target servers. (PMT-3509) * [-] A database was duplicated during second migration of a subscription having capital characters in name. (PMT-3535) * [-] During migration from DirectAdmin, content of administrator's subscription became unavailable if the owner of the document root folder was incorrect. (PMT-3508) * [-] Migration from DirectAdmin could not be started if a customer with non-unicode symbols in the name was present on the source server. (PMT-3540) * [-] Migration from DirectAdmin could not be started if a mail auto-reply had been created for a domain on the source server and then the file with the auto-reply message had been deleted. (PMT-3542) * [-] Migration from DirectAdmin was blocked if a cron task on the source server could not be parsed. (PMT-3544) * [-] After migration from a custom panel, the Apache error log file could not be opened in the Log Browser because of incorrect permissions. (PMT-3460) * [-] MySQL server databases could not be migrated from DirectAdmin if a remote MySQL server was used on the source server. (PMT-3545) # 2.5.4 (02 March 2017) * [+] Migration from DirectAdmin 1.51 is now supported. * [*] Migrated databases are automatically renamed before restoration to avoid conflicts in cases of the same names of databases and database users. * [*] Administrator can now configure the depth of checked web site links in post-migration checks. * [-] Migration from Plesk 11.0 failed when a custom button with an icon in PNG format was configured on the source server. (PMT-3458) * [-] Migration on Windows could not start if the path to the 'plesk' utility was not specified in the PATH variable of the target server. (PMT-3452) * [-] Migration on Windows could not start if no PHP handlers were installed on the target server. (PMT-3472) * [-] MySQL databases could not be migrated if an incorrect or empty password was set in the MySQL configuration file. (PMT-3394) * [-] Adjusting application settings could work infinitely in case when the parent folder of a web site on the source server contained symbolic links. (PMT-3412) * [-] If an additional domain's IP address differed from the subscription's IP address, the DNS records of the additional domain could not be migrated. (PMT-3445) # 2.4.9 (20 January 2017) * [+] During migration of mail content from a custom panel, it is now possible to define configuration settings like for a subscription content. In particular, it is possible to specify files or directories that should be excluded from copying or to define advanced file mapping. * [+] Plesk Migrator on Windows can now be configured to detect the scriptiong settings (PHP version, ASP.NET version, ASP) of a subscription on the source server and migrate them properly. * [-] A subscription belonging to a reseller could not be synchronized with an add-on service plan after migration. (PMT-3413) * [-] Post-migration checks did not detect error messages or warnings on a web page in case when the HTTP code and the title of the web page were identical on the source server and on the target server. (PMT-3388) * [-] During migration from a custom panel, post-migration checks were run for an enabled subscription with disabled main domain. As a result, error messages were reported. Now no post-migration checks are run in this case. (PMT-3378) * [-] During migration from a custom panel, post-migration checks failed if a subscription had an add-on domain with an IP address other than the subscription’s IP address. (PMT-3371) * [-] Post-migration checks did not detect some typical PHP error messages or warnings on web pages. (PMT-3389) * [-] Migration could not be started on CentOs 5. (PMT-3417) * [-] An unclear error message was displayed during migration if the configuration files of migrated applications contained non-unicode symbols. As a result, the adjusting of all other applications of the migrated subscription failed. (PMT-3398) * [-] An unclear error message was displayed during migration if WordPress configuration files contained non-UTF-8 symbols. As a result, the adjusting of a particular WordPress instance failed. (PMT-3400) * [-] Migration from a custom panel failed if the hosting description contained binary data in password fields of hosting description. (PMT-3390) * [-] If the web.config file of a web site contained XML namespaces, the web site could stop functioning after migration. (PMT-3387) * [-] Migration could fail if many (more than 10000) application files were changed during adjusting. (PMT-3409) * [-] After migration from a custom panel there were no write permissions in the document root of a migrated subscription, it these permissions were not set explicitly in the hosting description. Due to this issue, the permissions settings sometimes were lost during migration from Plesk Onyx to Plesk Onyx. (PMT-3407) * [-] Web Presence Builder was not registered in Plesk after migration to Plesk for Windows 12.5 or Onyx. (PMT-3369) * [-] Some errors related to Microsoft SQL Server were not reported in Plesk Migrator log. (PMT-3362) * [-] If migration of a Microsoft SQL Server database failed, Plesk Migrator added a database dump to an existing dump file during each new attempt to migrate, thus increasing the size of the dump file. (PMT-3411) # 2.3.2 (22 December 2016) * [+] A new mode was added to migration from Confixx so that mail users will be able to log in to their mail accounts on the target server with their original usernames and passwords. * [+] During migration from cPanel, it is now possible to change the document root of a migrated domain. * [+] It is now possible to migrate mail content to/from Plesk Onyx using a remote SmarterMail server. * [-] Domain alias could not be migrated if its name was present in the DNS template. (PMT-3340) * [-] During migration, long FTP user names (with 16 or more symbols) were truncated to 15 symbols. Now the maximum length for FTP names is 16 symbols that corresponds to the limitation of Plesk. (PMT-3320) * [-] An error occured during adjusting application files after migration if the file names contained non-ASCII symbols. (PMT-3334) * [-] The description of copy content options in Plesk Migrator user interface was insufficient. (PMT-3330) * [-] Migration of additional users associated with a subscription was performed incorrectly. As a result, the corresponding subscription could fail to migrate.(PMT-3351) * [-] Web content could not be migrated from cPanel, Confixx, or Parallels Pro Control Panel for Linux, if CageFS was enabled on the source or target server. (PMT-3333) * [-] Mail users having the permission to log in to Plesk on the source server could not log in to Plesk on the target server after migration. (PMT-3354) * [-] Mail flags and folders were lost during migration from hMailServer 3. (PMT-2943) * [-] Migration to/from Plesk failed if the Plesk database had a name other than ‘psa’. (PMT-3329)