Key takeaways
- Plesk's own backup is for restoring on Plesk, so for another panel you move files, databases and mail one by one and keep the backup as a safety copy.
- Plesk Migrator moves sites to another Plesk, not to a different panel, so plan the manual route if your target is not Plesk.
- Lower the DNS time to live a few days ahead, test the new server through your hosts file, and switch DNS last.
- Keep the Plesk server running until mail has settled on the new one, and write down the rollback before you start.
Moving off Plesk is not hard, but it is easy to do in the wrong order. This guide is for a Plesk server on Linux and a new server that runs a different control panel. The steps are the same whichever panel you choose. The order matters more than the commands: inventory, copy, test, then switch DNS, and keep the old server until you are sure. Facts about Plesk's tools below are from its own documentation, read on 30 October 2026.
Take stock before you copy anything
Write a list of what the server really does. For every subscription note the domains and subdomains, the PHP version, the databases and their users, the mailboxes and forwards, the cron jobs, the SSL certificates and any DNS records that are not just web and mail. Note anything unusual too: custom nginx or Apache directives, a Node.js app, a WordPress toolkit setup.
This list is what you check off at the end. It is also how you decide which sites move first. Start with the smallest, least important one.
Make Plesk's own backup, as a safety copy
Plesk has a command line backup tool, plesk bin pleskbackup. Its documentation lists object types such as --server, --clients-name and --domains-name, and options such as -output-file, -split and -exclude-logs. For one subscription it looks like this:
plesk bin pleskbackup --domains-name example.com --output-file=/root/example.com.tgz
Two details from the docs matter. Exporting with -output-file removes the backup from Plesk's own backup storage (by default /var/lib/psa/dumps/) unless you add -keep-local-backup. And the format is made to be restored on Plesk. Treat this file as a safety copy that proves you have everything, not as the thing you will import into a different panel. Some tools do read Plesk backups, and the Plesk alternative page says how RespireCloud's importer does; the manual route below works for any target.
If your target is another Plesk, use Plesk Migrator instead. Its guide moves subscriptions between Plesk servers over SSH, but it is built for a Plesk destination.
Move files, databases and mail
On a default Plesk for Linux, a subscription's website files sit under /var/www/vhosts/example.com/, with the web root in httpdocs. Check your own server, because the layout can differ. Copy them with rsync from the new server:
rsync -aHAX --info=progress2 root@OLD:/var/www/vhosts/example.com/httpdocs/ /path/on/new/server/
Run it once now and again right before the switch. The second run is short because only changes move.
For databases, Plesk's command line utility can dump them:
plesk db dump DATABASE_NAME > DATABASE_NAME.sql
Load the file into an empty database on the new server, create the database user there, and update the site's configuration file. Dump again at cutover.
Mail is the part people forget. Mailbox folders on a default install sit under /var/qmail/mailnames/example.com/, one folder per mailbox, in Maildir format. Check the path on your server. Copy them with rsync as well, create the mailboxes on the new panel first, and expect to set new passwords. A database dump covers Plesk's settings, not the messages.
Do a dry run on the new server
Do not touch DNS yet. Put the new server's address in your own computer's hosts file for the domain and open the site. Log in to the admin area, place a test order, send a form, open a database page, check the PHP version and look at the cron jobs. Send a test mail to a new mailbox from outside. Fix what fails now, while nobody can see it.
Lower the DNS time to live, then switch
The time to live (TTL) is how long other networks keep a DNS answer. Lower it to a few minutes on the records you will change, a few days before the move, and wait at least as long as the old value. The full explanation is in our cPanel post and applies here unchanged.
On the day: stop changes on the old site, run the final rsync and database dump, load them, point the DNS records to the new server, and watch the first mail and visits arrive. If you also move DNS hosting, copy the zone first and compare it record by record.
Keep a way back
Until you turn the old server off, rollback is just switching the DNS records back. That only works if the old site was not changed in the meantime, so do not delete anything there for at least a week. After that, keep the safety backup somewhere that is not the server.
Final checklist
- Every item on your inventory list works on the new server.
- Mail is delivered and sent, and the sender checks (SPF, DKIM, DMARC) are set up again on the new server.
- SSL certificates are issued for each domain, and redirects from http to https work.
- Cron jobs run and write to the right paths.
- Backups are scheduled on the new panel and one file has been restored as a test.
- The old server is untouched and still holds a full copy.
If you would rather not do this by hand, our migration page explains how RespireCloud reads a Plesk backup, builds a test copy first and rolls back on request, and what it costs to have it done for you. It is the right choice if your target is RespireCloud, and not a reason to choose RespireCloud if it is not.
Questions
Can I restore a Plesk backup file on HestiaCP or CloudPanel?
Not directly. Plesk's backup is made for Plesk to restore. Move the website files, a database dump and the mail folders yourself, or use an importer that reads Plesk backups, such as the one in RespireCloud.
Does Plesk Migrator move me to another panel?
No. Its documentation covers moving to Plesk from Plesk, cPanel and a few other sources. If your target is a different panel, you need the manual steps below or a tool built for that panel.
How long should I wait before turning off the old Plesk server?
At least a few days after DNS has switched, and until you have seen real mail arrive on the new server. Some resolvers hold an old answer longer than the time to live says.
What happens to mailbox passwords?
Plan on new ones. Do not assume Plesk's stored password values can be reused by another mail server. Tell mailbox owners the day before the switch.
Do I need downtime?
No, if the old server keeps serving until the new one is proven. Freeze changes for a short while before the final sync, so no new orders or mail are left behind.
