Self-Managed Migration
This FAQ is intended to support customers who are migrating their Plesk installation themselves from an old VM to a new VM.
The migration is performed independently by the customer using Plesk tools.
What data can be migrated?
Using the Plesk Migration Manager (Plesk Migrator), the following can be transferred:
- Websites & web files
- Databases
- Email accounts & messages
- DNS zones (if managed in Plesk)
- SSL certificates
- Subscriptions, customers & resellers
Requirements
What do I need before starting?
You must have:
- Administrator access to both Plesk servers (source and target)
- Network connectivity between both servers
- Sufficient disk space on the target VM
- Access credentials (IP, root/admin login) for the old VM
- Recommendation: Before migration, a complete backup of the old VM or via Plesk should be created
Do Plesk versions need to match?
No, but:
- The target Plesk version must be equal to or newer than the source
- The target operating system must be supported by Plesk
Migration via Plesk
How do I start the migration?
- Log in to Plesk on the new VM
- Go to Tools & Settings → Migration & Transfer Manager
- Select Plesk as the source
- Enter the IP address and credentials of the old VM
- Select the objects to migrate
- Start the migration
Can I migrate multiple domains at once?
Yes.
You can migrate:
- Complete subscriptions
- Customers or resellers
Individual domains cannot be migrated separately from their subscription.
Can I test the migration before going live?
Yes.
Recommended approach:
- Complete the migration
- Do not change DNS yet
- Test websites using the temporary IP or local hosts file
DNS & IP Addresses
Will the server IP address change?
Yes.
The new VM will usually have a different IP address.
Who is responsible for DNS changes?
The customer.
After migration, you must update:
- A / AAAA records
- MX records (if mail is handled externally)
- SPF, DKIM, and DMARC records
to point to the new IP.
How can downtime be minimized?
- Lower DNS TTL values in advance
- Perform the migration outside peak hours
- Switch DNS only after successful testing
Email & SSL
Are emails fully migrated?
Yes, if selected in the Migration Manager:
- Mailboxes
- Email content
- Forwarders
- Autoresponders
What happens to SSL certificates?
- Existing certificates are migrated
- Let’s Encrypt certificates may need to be reissued after DNS changes
- Check in Plesk → Websites & Domains → SSL/TLS Certificates
After the Migration
What should I verify?
We strongly recommend checking:
- Login to the new Plesk panel
- Website functionality
- Database connections
- Sending and receiving emails
- SSL certificate validity
- Cron jobs
- PHP versions and extensions
When can the old VM be shut down?
Only after:
- All websites and services are working on the new VM
- No emails are being delivered to the old server
Recommended: 48–72 hours of parallel operation
Responsibility & Support
Does the provider support the migration?
No.
The migration is fully self-managed by the customer.
Support is limited to:
- Availability of the new VM
- Infrastructure or connectivity issues
Official Plesk documentation on migration:
Plesk provides detailed information on how migrations work using Plesk Migrator, including step-by-step instructions: