• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Domains and Client are not migrated from Plesk 10 to Plesk 11.5

SalvadorS

Regular Pleskian
Hello,

I have and old server with Plesk 10 and I want to migrate some domains from this old server to a new server (Debian 7.x) with Plesk 11.5.30

I went as always to the migration tool, select one client and their domain, started the migration and I did´t have any error. In the control panel of the new server I can see that the migration result was OK. However the client is migrated but not the domain. I have a client with no domain.... Tested with three different clients and domains.

If I migrate only the domain name I can do it without any problem, so then I have to add the domain to the client so I have to do two migrations (one for the client, one for the domain) instead only one.

Anybody can help me with this?

UPDATE

After a lot of testing I found the problem (and is not my fault) When the username of the control panel is the same as the username of the FTP the domain is not migrated. I have to change the username of the control panel, migrate the user and the domain and then change again the username of the panel. PLESK can you check this?
 
Last edited:
Yes, it is known issue and we have already submitted request to developers regarding this issue (PPP-6466 for your reference).
Developers are working on it.
 
Only one possible workaround now - change customer's login before migration.
 
Yes, I did that, change, then migrate, then change again to the old name in the new server and works perfect.

Thanks again.
 
Back
Top