Article ID: 402, created on Oct 6, 2008, last review on Apr 25, 2014

  • Applies to:
  • Plesk 7.5.x Reloaded
  • Plesk 7.1.x Reloaded
  • Plesk 7.0.x
  • Plesk 6.x


Your best bet is to move to a new server or use a temporary server to work with as a staging platform. You will need to install the same OS that is installed on the source server on the new or temporary system. Then backup the source server and dump the file to the new or temp server.

At this point there are several options:

  1. Update the platform server from Plesk 6 directly to Plesk 7.5 Reloaded skipping any other builds. Plesk 7.5 Reloaded is able to upgrade Plesk 6 and 7 systems.

  2. Clean and install the preferred OS and Plesk 7.5 Reloaded on the original source server then use the Migration Manager feature in Plesk 7.5 Reloaded now on the original server to migrate the customers from the temporary Plesk 6 platform server back to the original system.

  3. Or use a combination of these options to backup and restore data to change operating systems.

Follow procedures outlined in the Plesk 7.5 Reloaded Backup Utilities Users manual located here:

To upgrade your OS and Plesk version without a temp system follow these directions.

Backup the entire system using the Plesk Backup utilities and dump the file in a safe place (off the system) ... Wipe the system clean and install Red Hat 7.3 or 9 and reinstall Plesk 6. Restore the dump file on the server running Plesk 6 on the upgraded OS... Upgrade directly to Plesk 7.5 Reloaded.

Backup again and follow the same procedure for upgrading to a different OS. There is NO WAY AROUND this process unless you use a separate platform system as detailed above.

Note: Plesk Backups are only restorable to the same version of Plesk.
(Example: P6 can be restored on P6, P7 on P7, etc...)

6ef964a54451eeb60b9cce8b8001a1d4 aa571057eefb4e790d223bad9e05ace1 d3cd9f1770da96e5b5046d20def9f8eb 097728dc0a325f6309aa7a3997d4cacc 29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF