Server Migration
Whether you want to move to a new server, replace a broken one, or upgrade to more powerful hardware — these guides walk you through every step of the migration.
Which migration path is right for me?
The right approach depends on what is running on your server and whether the source server is still accessible:
| Situation | Recommended path |
|---|---|
| Plesk is installed on the source server | Migration with Plesk → |
| Linux server, no control panel | Migration with rsync → |
| Windows server, no control panel | Migration with robocopy → |
| Migrating databases only | Database Migration → |
| Source server no longer boots / no SSH access | Emergency Migration → |
| Source server completely failed — attaching drives externally (Linux) | External Drive (Linux) → |
| Source server completely failed — attaching drives externally (Windows) | External Drive (Windows) → |
Before You Migrate — Preparation
Good preparation prevents data loss and downtime. Go through these points before you start:
Create a full backup
Back up all data on the source server before you begin — files, databases, configuration files, and emails.
Prepare the target server
Install the same or a compatible operating system on the target server. Make sure SSH/RDP access is working.
Lower your DNS TTL
Set your DNS TTL to a low value (e.g. 300 seconds) 24–48 hours before the migration so DNS changes propagate quickly.
Document dependencies
Note all installed services, versions, ports, and configurations — web server, databases, cron jobs, firewall rules.
Plan a maintenance window
Choose a low-traffic time for the migration to minimise the impact on your users.
Define a rollback plan
Decide in advance when and how you would fall back to the old server if something goes wrong.