I really can't imagine what is so utterly complex that after 9 months the migration manager in the 9.x series still doesn't work correctly. There's even a patch that was released for 9.2.x to fix the issues yet 9.3 gets released without the fixes in that patch for 9.2; how is that even possible?
May 12th 2009 was the first public report of the migration manager in 9.x breaking all the sites SSL certs on a given server each time it is used:
http://forum.parallels.com/showthread.php?t=90260
Seven months later a patch was released for some versions of 9.2:
http://forum.parallels.com/showpost.php?p=395046&postcount=39
A second issue which has not been discussed in the forums but which we made Parallels aware of back in September of last year via ticket 781567 is that the migration manager ruins all of the permissions of anything in the /private folder and makes all the directories and subdirectories not executable, so all must be fixed by root or recopied by hand via tar file to get them corrected.
Now 9.3 comes out and it appears the issue of resetting the SSL certs on all the sites on the server has been resolved, the permissions issue on /private is still broken, and now migration manager breaks the SSL configuration of the sites that are being migrated in a way that prevents the web server from restarting on the target machine. What appears to happen is the migration manager brings over the existing config file for a site, leaving the SSLCertificateFile set to whatever it had been on the old server instead of what it should be for the new server since evidently that unique name is not preserved. So what you end up with is apache not starting with this type of error:
Starting httpd: Syntax error on line 41 of /var/www/vhosts/domain.com/conf/httpd.include:
SSLCertificateFile: file '/usr/local/psa/var/certificates/cert-GpiNJu' does not exist or is empty
[FAILED]
To fix this you have to go to that site, set its certificate back to what it should be, turn SSL support back on and turn use same directory back on if you had it on before since migration manager fails to preserve any of those settings. Once you've done this, try to start apache back up. Oh, if you've migrated more than one site, then you're going to have to go into every single one and fix them all before apache will restart.
May 12th 2009 was the first public report of the migration manager in 9.x breaking all the sites SSL certs on a given server each time it is used:
http://forum.parallels.com/showthread.php?t=90260
Seven months later a patch was released for some versions of 9.2:
http://forum.parallels.com/showpost.php?p=395046&postcount=39
A second issue which has not been discussed in the forums but which we made Parallels aware of back in September of last year via ticket 781567 is that the migration manager ruins all of the permissions of anything in the /private folder and makes all the directories and subdirectories not executable, so all must be fixed by root or recopied by hand via tar file to get them corrected.
Now 9.3 comes out and it appears the issue of resetting the SSL certs on all the sites on the server has been resolved, the permissions issue on /private is still broken, and now migration manager breaks the SSL configuration of the sites that are being migrated in a way that prevents the web server from restarting on the target machine. What appears to happen is the migration manager brings over the existing config file for a site, leaving the SSLCertificateFile set to whatever it had been on the old server instead of what it should be for the new server since evidently that unique name is not preserved. So what you end up with is apache not starting with this type of error:
Starting httpd: Syntax error on line 41 of /var/www/vhosts/domain.com/conf/httpd.include:
SSLCertificateFile: file '/usr/local/psa/var/certificates/cert-GpiNJu' does not exist or is empty
[FAILED]
To fix this you have to go to that site, set its certificate back to what it should be, turn SSL support back on and turn use same directory back on if you had it on before since migration manager fails to preserve any of those settings. Once you've done this, try to start apache back up. Oh, if you've migrated more than one site, then you're going to have to go into every single one and fix them all before apache will restart.