Tips on migrating to a (dv) 4.0 from a (dv) 3.x
Migration instructions and tips
We recommend reading this article before proceeding with your migration: Migrating your websites to the (dv) Dedicated-Virtual Server.
Verify your site's compatibility
The (dv) 4.0 has all new software and hardware. You will want to verify that your existing site is compatible with the updated software. In most cases, it will be. Here's a handy chart of the software versions:
| (dv) | Apache | MySQL | Plesk Panel | PHP | Perl | Python | Ruby |
|---|---|---|---|---|---|---|---|
| 4.0 | 2.2.3 | 5.1.54 | 10.4.4 | 5.3.5 | 5.8.8 | 2.4.3 | 1.8.5 |
| 3.5 | 2.2.3 | 5.0.45 | 8.3 / 8.6 | 5.2.6 | 5.8.8 | 2.4.3 | |
| 3.0 | 2.0.52 | 4.1.20 | 8.21 | 4.3.9 | 5.8.5 | 2.3.4 |
Use the Plesk Migration Manager
Using the Plesk Migration Manager has detailed instructions on how to use this automated tool for a relatively simple migration.
When you provision the (dv) 4.0, select a primary domain that is distinct and different from your previous primary domain. For example, you should choose something like new-example.com that is not a subdomain to the primary domain on your old server.
Please pay attention to the troubleshooting section in the article. In particular, look out for the Unique FTP users error and the No migration agents found error. These are both issues that could affect (dv) 3.5 migrations.
Note:
You must disable FastCGI on the 3.5 server prior; if FastCGI is enabled on a (dv) 3.5, you will encounter errors when using the Plesk Migration Manager.
Note:
You must disable FastCGI on the 3.0 server prior; if FastCGI is enabled on a (dv) 3.0, you will encounter errors when using the Plesk Migration Manager.
Migrate email contacts from Horde to Atmail
Please follow these two articles to export your contacts from Horde and then import them to Atmail:
TIP:

(mt) Media Temple offers assited migrations with our new SiteMover product. To learn more, please visit: SiteMover.
Navigating the new Plesk control panels
When you migrate from Plesk 8.6, the version of Plesk on the (dv) 3.58.21, the version of Plesk on the (dv) 3.0, to Plesk 10 (on the 4.0), you will notice some differences.
Server Administration Panel
The main difference is that all the functions which used to be in the single Plesk panel are now spread across three different panels. The default panel when you log in with your admin user is the Server Administration Panel. It has the equivalent of the Server tab and the Clients tab from Plesk 8.68.21.
If you click on the Domains tab from here, you will find a link to the Control Panel (if you have at least one domain set up). This panel has all of the webmaster tools that were previously under the Domains tab. It is also possible to configure a user to log into this panel directly - see Control Panel user.
Finally, you can access all of your resource-monitoring tools and other high-level Container features from the Power User Panel. You can reach this panel from the administration panel by going to Tools & Utilities, then Manage Your Container. Or, you can access it directly at https://example.com:4643/.
For more information and screenshots from the new Plesk panels, please see: Three Plesk panels.
Plesk 10 also introduces new types of users who have varying levels of access to the different panels. These users replace the "Clients" feature in Plesk 8.68.21. To learn more about these users, see: Plesk users explained.
Customers
Customer is a new name of client. Unlike clients, a customer does not have own resource pool or privileges - limits, permissions, and IP pool. These settings are incapsulated into subscriptions. It provides a greater level of flexibility that lets you block some customer's resources while allowing access to others. For example, if a customer runs two hosting subscriptions and one of them is expired, the customer still has access to the second one. The customer account never expires whereas the subscriptions do.
Parallels resources
Parallels has provided documentation on the differences between Plesk 10 and earlier panels.
Turn off named
Unless you are using the named service to run private nameservers, you should turn it off. The 64-bit version of named is quite the resource hog, and Plesk automatically turns on the service when you add your first domain.
Please see Enable or disable named (bind) on your (dv) for instructions.
Revert the PHP5 upgrade
If you upgraded your (dv) 3.0 to PHP5, you will need to revert this. Your site will break. Please see: Reverting PHP5 for (dv) 3.0 after a migration.