BETANot production ready yet. Testers wanted: apply · report a bug
KarnakPanel
Backups & migration / From cPanel

Leaving cPanel? Here is what actually moves.

Three import routes, what each one carries, and the order to do it in. This page is the sequence rather than the sales pitch: the parts you still have to do yourself are listed in the same detail as the parts the panel does for you.

Routes

Three ways in, depending on what you have.

All three run from the panel's Migrate page, with live progress. None of them needs anything installed on the old server first.

RouteNeeds on the sourceBest forCarries
Full backup uploadA backup file downloaded from cPanelAccounts you can archive before the move; no ongoing access to the old serverFiles, databases, mailboxes, forwarders
Remote importcPanel login plus an API token — no rootHosts without root on the old boxFiles, databases, mailboxes, forwarders, sub and addon domains, autoresponders, filters
Root importRoot SSH to the source serverServers you own outrightThe same, generated as a real pkgacct archive
HestiaCPRoot SSH, or an uploaded backupLeaving HestiaCPSites, subdomains, databases with their passwords, mailboxes, forwarders, DNS records, cron (left paused)

Mailboxes from Gmail, Yahoo, iCloud, Zoho or any IMAP host come across through a separate mailbox import, so a customer leaving a mail provider rather than a panel is not left behind. For a whole batch rather than one account, what bulk actually means on each route is worth reading first.

The inventory

What lands, and what you do next.

The honest split. Everything in the first list arrives; everything in the second is your job, and it is the part that turns a migration into a bad evening when it is skipped.

Arrives with the account

  • Files, in the account's home directory, with ownership remapped to the new account rather than copied raw.
  • Databases, so the site connects without a manual dump and restore.
  • Mailboxes and their contents, plus forwarders, and on the remote and root routes autoresponders and filters.
  • Domains: subdomains and addon domains on the remote and root routes; DNS records on HestiaCP sources.
  • Cron jobs, left paused so nothing fires against half-moved data.

Still yours to do

  • The registrar. Nobody changes nameservers for you. The panel shows what to change; you make the change.
  • Certificates. Reissue per domain once DNS points here. Do not assume an old certificate travelled with the account.
  • DKIM and DMARC. Check the records for every sending domain before any volume of mail leaves. Two domains with the same key is a deliverability problem, not a setup detail.
  • Cron. Read what was paused, then start it. Imported schedules were written for the old server.
  • Per-domain settings the panel has no equivalent for. Go through PHP version, redirects and SSL per domain rather than assuming everything came across.
Panel to panel

The cutover, in order.

If both ends are KarnakPanel, Account Transfer does the move while both servers stay live. This is the whole sequence, including where it can stop.

The KarnakPanel Migrate page: Account Transfer pairing steps alongside the cPanel and HestiaCP import tabs
The Migrate page on a test server, v1.5.53: Account Transfer at the top, the cPanel and HestiaCP importers beside it.
  • 1 · Pair the servers. The target shows a code; the source accepts it. Both codes are public data — the act of pasting is the authorisation — and the pairing expires after 24 hours. No passwords or private keys are copied. Both screens then show the same three check words: different words mean a different server answered, and you revoke and start again. Both servers must run the same panel version.
  • 2 · Tick the accounts. Pre-flight checks run per account and report what would block a move before anything is copied.
  • 3 · Copy. An encrypted pull runs with a live bar per account, while the sites keep serving from the old server. Nothing on the source is deleted, at any point, by the panel.
  • 4 · Cut over. One button: a holding page on the old server, mail held there, a final copy of whatever changed since step 3, then mail passed by IP while DNS propagates, cron and daemons started here, DNS repointed on both servers, and certificates reissued once public DNS answers with the new address.
  • 5 · Roll back if it stops. Anything failing before mail moves puts the old server back as it was, so the failure case is a cancelled move rather than a broken customer.
  • 6 · Check the DNS. A per-name view of what Cloudflare, Google, Quad9 and the server's own resolver answer: this server, still the old one and how long the cache has left, or another address entirely, plus where each domain's nameservers live and what to change at the registrar.
The part to plan around. Cut mail and web together. Move the website and leave MX pointing at the old server and you have two inboxes receiving the same customer's mail. The transfer holds mail on the old server precisely so this window is short, but it is not zero, and it is measured in cache time, not in the panel's speed.
Before the day

Four things worth doing first.

None of these are features. They are the difference between a cutover and an incident.

  • Drop the TTLs. A day beforehand, lower the TTL on the records you will change. It shortens the window where half the world sees the old server.
  • Move one account first. Pick the least political customer. Import them, send mail both ways, restore a backup, then move the rest with something learned.
  • Write down the rollback point. The panel can put a failed transfer back, but you should still know which account moved without trouble and which did not.
  • Do not cancel the old server. The panel never deletes the source. Cancel it when the last domain has been answering correctly for a week, not when the bar reaches 100%.
Limits

What this does not do.

Stated before you plan around it.

No registrar automation. Nameserver changes are yours to make. The panel tells you what to set and then shows you what resolvers answer.
Admin only, for now. Account Transfer is an admin action. Resellers' clients can be moved by the admin and the reseller link is remapped, but there is no reseller self-service in this release.
KarnakPanel to KarnakPanel, for the live move. cPanel sources arrive through a backup or an import, not through a live pairing.
A fresh server is a different tool. A whole-server move over SSH is for landing every account on an empty box. Account Transfer is for a server that already has customers, which is why it remaps accounts one at a time.
One server at a time. There is no clustering and no central console for a fleet.
Beta. Every mechanism is implemented and verifiable in the source, and awaiting independent review. Import a test account before you import a customer's.
Questions

The ones that decide the method.

Short answers.

Do I need root on the old server?

No. The remote import uses a cPanel login and an API token, which is the route for resellers and anyone without root on the source. Root over SSH is available when you own the box and want a pkgacct archive.

Will mail be lost during the switch?

The transfer holds mail on the old server and passes it to the new one by address while DNS propagates, so nothing is dropped in the window. Mail sent to a domain whose DNS has already moved arrives here directly. The risk is leaving MX behind on a domain you have moved, which is why the DNS check exists.

Can I move accounts without downtime?

The copy runs while both servers serve, so sites keep answering from the old one until you press cutover. The cutover itself puts up a short holding page, which is a visible few seconds to minutes rather than an outage. Certificate reissue depends on public DNS, not on the panel.

What about the cPanel licence I already paid for?

It stays with the old server until you stop using it. If the reason you are moving is the price, the numbers — including the 16 December 2026 rise — are on the cPanel pricing page.