Migration with Plesk
This guide shows how to move websites, databases, email accounts and settings to a new Plesk Obsidian server with the Plesk Migrator extension – without copying files manually.
Prerequisites: Plesk must be installed and licensed on the target server, and the Plesk Migrator extension must be installed there (Extensions catalog). The source server must be reachable via SSH (Linux) or RDP (Windows). Both servers need an active internet connection.
What gets migrated?
| Content | Details |
|---|---|
| Domains & subdomains | All configured domains including DNS settings and web space |
| Databases | MySQL/MariaDB databases including users and permissions |
| Email accounts | Mailboxes, aliases, forwarders, and stored emails |
| SSL certificates | Installed certificates (Let's Encrypt certificates may need to be reissued) |
| FTP accounts | FTP users and their directory assignments |
Step 1: Open the Migration Tool on the Target Server
Launch the migration tool from within the target server's Plesk.
1.Log in to Plesk on the target server
2.Navigate to Tools & Settings → Migration & Transfer Manager
3.Click Start Migration
Step 2: Connect to the Source Server
Enter the connection details of the source server.
| Field | Value |
|---|---|
| IP address / hostname | IP address of the source server |
| Login | root (Linux) or Administrator (Windows) |
| Password / SSH key | Root password or SSH key file |
| Panel type | Plesk (if Plesk is installed on the source server) |
Step 3: Select Objects & Start Migration
Choose what to migrate and start the transfer.
1.Select the subscriptions, domains, or individual resources you want to migrate
2.Review the summary of selected objects
3.Click Start Migration — progress is shown in real time
Large amounts of data can take several hours. The migration runs in the background — you can close your browser and check the progress again later.
Step 4: Verify the Migration
Check all services and content on the target server after migration.
1.Check that all domains, databases, and email accounts are present in Plesk on the target server
2.Test your websites via the target server's IP address (before updating DNS)
3.Reissue Let's Encrypt certificates if they were not transferred
4.Update your DNS records to point to the new IP once everything is verified
Further Documentation
For detailed information on the Plesk Migration & Transfer Manager, refer to the official Plesk documentation.