1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Important Plesk Migrator extension

Discussion in 'Plesk Extensions' started by custer, Feb 9, 2016.

  1. Alina Dmi

    Alina Dmi Regular Pleskian Staff Member

    16
    55%
    Joined:
    Nov 26, 2015
    Messages:
    108
    Likes Received:
    19
    Plesk Migrator 2.8

    What`s new:

    • [+] 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)
     
    Dukemaster likes this.
  2. Alina Dmi

    Alina Dmi Regular Pleskian Staff Member

    16
    55%
    Joined:
    Nov 26, 2015
    Messages:
    108
    Likes Received:
    19
    Plesk Migrator 2.9

    What`s new:

    • [+] 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)
     
  3. Alina Dmi

    Alina Dmi Regular Pleskian Staff Member

    16
    55%
    Joined:
    Nov 26, 2015
    Messages:
    108
    Likes Received:
    19
    Hi all,
    Next version of Plesk Migrator(2.11) has been released just now!

    Changes:
    • [+] 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)
     
    Last edited: Sep 20, 2017
    UFHH01 and IgorG like this.
  4. Alina Dmi

    Alina Dmi Regular Pleskian Staff Member

    16
    55%
    Joined:
    Nov 26, 2015
    Messages:
    108
    Likes Received:
    19
    Plesk Migrator 2.12

    What`s new:

    • [+] Now you can run pre-migration checks in the advanced migration mode. Successfully passing all checks automatically starts a migration.
    • Performance of scanning source server contents before importing sites has been drastically improved.
    • [-] When preparing for a site import, one of the applications being unavailable resulted in failure to detect other applications and list them on the site import page. (PMT-4061)
    • [-] When transferring a subscription from Plesk Onyx, only a single scheduled task was transferred to the target server. (PMT-3894)
    • [-] When migrating a subscription from Plesk 11.5 or later, the password for site application database was not decrypted on the target server, which resulted in the application unable to work on the target server. (PMT-4026)
    • [-] When migrating from a Linux server with Plesk Onyx, pre-migration checks did not detect it when the webmail, used on the source server, was missing on the target server. (PMT-3145)
    • [-] A component, required by Plesk Migrator, was not bundled with it but instead downloaded before first site import. This could result in migration failure in case of network problems. Now the component is a part of Plesk Migrator and does not require separate downloading. (PMT-3735)
    • [-] When migrating from Plesk servers, the APS applications were transferred only as content and not registered in Plesk. (PMT-4000)
    • [-] The migration process was aborted if any customer's login name did not conform to the Plesk requirements (only alphanumeric characters and -.'%_). Now subscriptions owned by such customers are skipped during the migration. (PMT-3959)
    • [-] Migration to a server with administrator's id different than the default one (1) resulted in failure to repeatedly migrate subscriptions or synchronize their content. (PMT-3078)
    • [-] When migrating from Confixx, each transferred SSL certificate was installed as default certificate for all domains on the IP address, which resulted in all domains using the certificate of the latest migrated domain. (PMT-4043)
    • [-] When migrating a subscription with a database and ODBC DSN (Data Source Name) from Plesk for Windows of version 12.5 or later, the DSN was not migrated. (PMT-3891)
    • [-] Migration failed from a server having IP addresses with netmask set in short notation. (PMT-4048)
    • [-] When migrating a subscription with web.config containing non-ASCII characters from a server with .NET 2.0 or 3.x to a server with only .NET 4.x, adjusting the web.config to the target server failed. (PMT-4029)
     
Loading...