Skip to content

Hosting panel migrations

Change panels. Keep everything.

cPanel to HestiaCP. Enhance to cPanel. Plesk, DirectAdmin, Virtualmin and the rest. We move the sites, mail, DNS and the fiddly bits, and prove it all works before anything switches.

See what moves

Fixed quote · Rehearsed before cutover · Tested rollback

Why switch

Why people change panels

Usually one of two letters: a licence renewal, or an end-of-life notice. Occasionally it's realising the new panel was a mistake and wanting the old one back.

The usual reasons

Licence bills that creep up at every renewal. A panel that quietly stopped getting updates years ago. An operating system going end-of-life underneath it. Or you tried the new thing and it turns out your team, your tooling and your muscle memory all live in the old one. Moving back is allowed.

The honest bit

No two panels map one to one. Sites, databases, mailboxes and DNS move cleanly. Panel-specific plugins, webmail preferences and the odd exotic mail filter sometimes don't. We list what carries over and what needs rethinking before we touch anything, so nothing surprising turns up mid-move.

Routes we handle

Any panel to any panel, in either direction

These are the moves we get asked for most. If yours isn't here, it almost certainly still fits.

cPanel to HestiaCP

The classic move away from per-account licence fees, onto an open-source panel that does the job. Sites, mail and DNS across without your users noticing.

Enhance to cPanel, and back

Providers modernising onto Enhance's container model, and teams heading back to cPanel because their staff and tooling know it. We do both directions, without judgement.

VestaCP to HestiaCP

VestaCP stopped moving years ago; HestiaCP is the maintained fork and the migration path is well-trodden. The longer this one waits, the hairier it gets.

Plesk and DirectAdmin

In or out, to or from anything else on this page. Often prompted by the same licence-renewal letter that prompts everyone else.

Virtualmin and Webmin

Frequently the panel nobody remembers configuring. We work out what it's actually doing, then move it somewhere the next person can understand.

Panel to no panel

Sometimes the right panel is none: a plain nginx or LEMP stack, managed by us. Less surface, fewer moving parts, nothing to licence.

Panels we work with regularly:

cPanel / WHMPleskDirectAdminHestiaCPEnhanceVirtualminWebminCyberPanelCloudPanelISPConfigaaPanelVestaCPInterWorxFroxlorRunCloudGridPanePlain LAMP / LEMP

Not listed? Ask anyway. If it holds sites, mail and DNS, we can almost certainly get them out of it.

What moves

The whole account, not just the files

A panel migration is only partly about websites. The pain lives in everything around them. This is the checklist we work through for every account, every time.

Websites and filesDatabases and usersMailboxes and mail historyForwarders and filtersDNS zones and recordsSSL certificatesCron jobsFTP and SSH accountsPHP versions per siteRedirects and rewritesPackages and reseller structuresBackup schedules

Migration process

Rehearsed first. Switched second.

Every migration runs as a copy before it runs for real. Nothing cuts over until the copy demonstrably works.

The audit is always free
  1. Audit

    [free]

    We inventory what's actually on the server: accounts, sites, mailboxes, DNS, PHP versions, the cron jobs nobody documented. Then we tell you honestly what maps cleanly and what doesn't.

  2. Build and rehearse

    [tested]

    We stand up the new panel and migrate copies of everything. Each site, database and mailbox gets checked against the original before anyone is asked to care about it.

  3. Cutover

    [out of hours]

    TTLs come down, a final sync runs, DNS switches. Usually overnight. If anything looks wrong, there's a rollback plan we've actually tested, not just written down.

  4. Aftercare

    [included]

    We watch mail deliverability, error logs and the odd edge case for the fortnight after. The old server stays untouched until you agree nothing still needs it.

Pricing

Quoted per move, fixed before we start

No rate card, because it would be a guess. The honest price depends on what's actually there: how many sites, what they're built on, where they live now, and how much mail and history comes with them. Ten small WordPress sites is a quick job; ten of anything with years of mailboxes behind them is not.

So we look first, then quote. The audit is free, the quote is fixed, and it doesn't grow mid-move.

Hosting company? We do white-label, per-account migrations at fleet scale

Batched overnight moves, your brand on the emails, priced per account. See what we do for web hosting providers.

Best fit

Who this tends to suit

Anyone with a server full of things that matter and no appetite for finding out mid-move what the old panel was quietly holding together.

Hosting providersAgencies with a server of client sitesResellersAnyone on a panel that stopped updatingAnyone staring at a licence renewal

Tell us what you're on. We'll tell you what moving involves.

Your current panel, a rough count of sites and mailboxes, and where you'd like to end up. We'll come back with what maps cleanly, what doesn't, and a fixed price. No pressure to proceed.