• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Summary thread for all the broken things in migration manager?

HostaHost

Regular Pleskian
Is there one? If not, can we start one? So far we've encountered, or seen in this forum:

* Migrations from older versions to 10 misses all imap folders other than inbox
* Migrations from older versions to 10 misses files that begin with period in the httpdocs folder, such as .htaccess
* Migrations from older versions to 10 miss forwards and aliases on email addresses

It's really quite impossible to understand how the migration manager can't be fixed; it has been broken ever since Plesk 9 came out. There has not been a single version of Plesk released since 8.6 where the migration manager did not mess things up in one way or another, whether it be missing files, not assigning the SSL certs, ignoring permissions on the directories under /private that are migrated, etc. How hard is it to use tar or rsync to produce a perfect copy of at least the files that move to a new server? Obviously there's more involved in extracting the non-file stuff out of the psa database but seriously, it can't even copy files correctly?
 
Back
Top