Donaldson R F
Servers & Hosting (Plesk, CloudPanel, Linux)
Plesk to Another VPS Migration
Move an entire Plesk server — every domain, database, mailbox and setting — to a new VPS.
The Problem
A full server migration touches dozens of moving parts at once: every domain, every database, every mailbox, SSL certificates, cron jobs — and a single missed piece means a client site or mailbox going down.
About this problem
Moving an entire Plesk server is a different scale of risk than moving one site — every domain, mailbox, database and certificate on the box needs to arrive intact and working, and a single missed mailbox or domain is how a client site or inbox goes down without warning. Plesk's own migration tools help, but they don't replace checking the result domain by domain.
This usually comes up when changing VPS providers entirely, consolidating multiple old servers, or needing more resources than the current box can offer.
What's Included
- Full inventory of every domain, database and mailbox on the current server
- Migrating everything to the new VPS using Plesk's migration tools plus manual checks
- Recreating SSL certificates and DNS-dependent settings
- A full verification pass before final DNS cutover
What's NOT Included
- Provisioning or paying for the new VPS
- Upgrading Plesk versions as part of the move (can be scoped in)
- Extended downtime beyond what's unavoidable for DNS propagation
How It Works
- Take a full inventory of every domain, database, and mailbox on the source server before touching anything.
- Use Plesk's migration tooling to transfer accounts to the new server, supplementing with manual checks where it falls short.
- Recreate SSL certificates and any DNS-dependent settings that don't transfer automatically.
- Verify every domain and mailbox individually on the new server, not just a sample.
- Plan the DNS cutover with minimal propagation risk before decommissioning the old server.
In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.
Frequently Asked Questions
- Can Plesk migrate itself to a new server automatically?
- Plesk has built-in migration tools that handle much of the transfer, but they don't guarantee every domain, mailbox and setting arrives correctly — manual verification afterwards is essential.
- How much downtime does a full server migration cause?
- With careful DNS planning, individual sites can have minimal to no downtime, though the migration project itself (inventory, transfer, verification) takes longer than a single-site move.
- What happens to email during a full Plesk server migration?
- Mailboxes are migrated along with everything else, but mail is one of the areas most worth verifying individually afterwards since missed mailboxes are a common, disruptive gap.
- Should I upgrade Plesk versions during a server migration?
- It can be done as part of the same project, but it adds risk and testing surface — it's usually safer to migrate first on a matching version, then upgrade separately once stable.
- How long does migrating an entire Plesk server take?
- It scales with how many domains and mailboxes are on the server — a handful of sites might take a day, while a server with dozens of accounts needs more thorough planning and verification time.
- What happens to the old server after migration?
- It's kept running until the new server is fully verified and DNS has propagated, then it's your decision when to decommission it.