This article provides best practices and use cases for troubleshooting issues with a Plesk for Windows migration. Each section of this article cross-references the relevant Plesk Knowledgebase (KB) articles for that particular stage of the migration process.
NOTE: Helpful information regarding Plesk for Linux can be found here:
- 113586 Plesk for Linux: Migration Best Practices and Usecases
If you prefer to let Plesk professionals handle the migration or upgrade job for you please check out Plesk professional services options on our website: https://www.plesk.com/professional-services/
Migration & Transfer Manager
Since Plesk 12.5 the new Plesk Migrator was implemented.
For more information refer to Migration Guide.
Migrating between different versions of Plesk
123844 A website does not function after migration to modern IIS
- 115705 [FAQ] Is it possible to migrate from Plesk for Windows to Plesk for Linux and vice versa?
Manual migration tips and hints
If a manual transfer is required, refer to the following sources:
- 123170 How to restore a Plesk installation on the new server after a disaster
Logs and log collector
To troubleshoot log issues, refer to this article:
- 9679 Structure of Plesk Migration Manager (PMM) logs and PMM logs collector
Sometimes, migrating to another server is not possible due to connectivity problems between servers. Refer to the following articles to check whether this is the case:
- 122615 Connection strings after migration from external SQL servers
From time to time, you may encounter difficulties with migration due to missing elements. In these cases, the following articles may be helpful:
- 122157 Some MS SQL tables are missing after migrating from Plesk 8.6 with external MS SQL database server
- 120806 Data transferring from Plesk 8.6: Unable to find the 'packagename' package on the source server or in the APS catalog
- 123841 MySQL migration failed: Not all content may be restored
- 121568 MSSQL database migration: Timeout expired
- 121393 Cannot dump database of type 'mssql'
- 122923 Remote MS SQL backup failed
115730 Unable to create a dump during migration due corruption of siteapppackages table
Cannot dump site app with id '2' and prefix 'joomla'. However, all the app-related content should be transferred correctly.[Cannot find package in the database]
123139 Migration error mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1'
Error: domain "domain.tld" Cannot dump database content 'wordpress_3' of type 'mysql' Error: Cannot backup content of database 'wordpress_3'. The mysqldump utility has returned '2'. STDERR: mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_QUOTE_SHOW_CREATE=1' at line 1 (1064)
122167 Failed deployment of database while migrating a domain with MSSQL DB
Warning: psadumpagent.InformationalException: Unable to restore MS-SQL database 'Dtabase_Name' to MS-SQL server 'localhost'. Error info: The media family on device 'C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp62960.tmp\8513' is incorrectly formed. SQL Server cannot process this media family. RESTORE FILELIST is terminating abnormally. ---> System.Data.SqlClient.SqlException: The media family on device 'C:\Program Files (x86)\Parallels\Plesk\PrivateTemp\tmp62960.tmp\8513' is incorrectly formed. SQL Server cannot process this media family.
114835 Backup fails - The given key was not present in the dictionary
ERROR: Unable to initialize agent on remote host. The given key was not present in the dictionary
121675 ASP-based websites show 404.17 after migration
HTTP Error 404.17 - Not Found The requested content appears to be script and will not be served by the static file handler.
121048 Cannot create domain in Plesk: There are no available resources of this type (domains) left. Requested: 1; available: 0
Error: There are no available resources of this type (domains) left. Requested: 1; available: 0.
115598 Default value of MySQL global variable "wait_timeout" on Source and/or Destination server can interrupt migration with error "MySQL server gone away"
MySQL server gone away
123841 MySQL migration failed: Not all content may be restored
Domain hosting creation failed:
An error occurred during domain update: An error occurred during changing of hosting settings: System user update is failed: User %username% already exists.