Fifty accounts at once. What that actually means.
Nobody wants a migration feature. They want a Friday that ends with fifty accounts working and nobody emailing them. That is a queue with a log per account, not one big button — and the routes differ in how much of the queue the panel runs for you.
Bulk is real, but it is per route.
Two of these are genuinely bulk. One is a queue you drive. The difference is worth ten minutes before you start.
| Route | Bulk behaviour | What you do |
|---|---|---|
| KarnakPanel to KarnakPanel Account Transfer | Genuinely bulk. Tick many accounts, a live bar each, one cutover for the lot | Pair once, tick, cut over together |
| Fresh server Whole-server move | Everything in one bundle, with a version gate and a refusal to overwrite a box that already has customers | Run once, as root, on an empty target |
| From cPanel backup, API token or SSH | One job per account. Each has its own progress and its own log, and detaches so it can outlive the panel's 15-second script limit | Queue them, verify each |
| From HestiaCP | One job per account, from a backup or over SSH | Queue them, verify each |
If both ends are KarnakPanel, stop here: Account Transfer is the bulk path and the rest of this page is about the harder case. If you are coming from cPanel, the queue is what you are buying, and it is worth understanding before you start.
The 15-second problem, and what replaces it.
The panel runs privileged scripts under a sudo wrapper that kills anything still running after 15 seconds. A real import takes minutes. So the import is built to detach and report through a log, rather than blocking a web request.
- Start it, walk away. The job backgrounds itself under
/var/log/karnakpanel/, and the Migrate page shows its progress. Closing the browser does not stop the import. - One account, one archive, one log.
cpmove-import.shtakes a single cPanel backup plus the panel user and domain it belongs to. Fifty accounts is fifty jobs, queued rather than merged into a single transaction, so one bad archive does not take the batch with it. - The target must exist first. The importer writes into an existing panel user and domain. Create the account, then import into it — this also lets you set the package and limits before any data lands.
- Queue depth is your judgement. Several jobs can run at once, but each one unpacks an archive and then copies it into place, so it needs room for both. Watch disk and load, and let a batch finish before starting the next rather than firing all fifty.
# <tarball> <cpanel user> <panel user> <domain> — into an EXISTING account $ cpmove-import.sh /root/cpmove-bob.tar.gz bob bob example.com
Every script the panel ships is documented with its arguments and its detach behaviour on the script reference, so you can check the command above rather than reading it here and hoping.
An order that survives fifty accounts.
Most failed bulk migrations fail in the same four places. None of them are the importer.
- 1 · Take your own copy of the source. Before anything: a full backup from the old server, somewhere you control. The panel never deletes the source, but a migration is the day you find out whether your old backups were real.
- 2 · Move the quietest account first. Import one, then open the site, connect to the database, count the mailboxes and send mail in and out. That is your reference for whether the other forty-nine worked.
- 3 · Batch by domain, not alphabetically. Mail and DNS failures are per domain. Moving all accounts on one domain together lets you fix MX and DKIM once instead of discovering the same problem five times.
- 4 · Leave cron paused until the end. Imported schedules were written for the old server and will fire on the new one. Read them, then start them deliberately.
- 5 · Verify each account the same way. Site answers, database connects, mailbox count matches, mail flows both directions. A spreadsheet with one row per account beats memory at account thirty.
- 6 · Change DNS per domain, and check it. Certificates issue after public DNS points here, and a large batch of domains means a large batch of certificate requests. Certificate authorities rate-limit big bursts, so sequence the domains rather than switching forty at once.
What a real bulk move looks like.
Account Transfer is the only route here where fifty accounts is fifty in one operation, so it is worth knowing what it does that a queue does not.
- Pre-flight before the copy. Each ticked account is checked first, so a blocked account is reported before anything is transferred.
- Two servers, both live. Sites keep serving from the old server while the encrypted pull runs, with a progress bar for each account in the batch.
- One cutover for the batch. Holding page, mail held on the old server, a final copy of whatever changed, mail passed by IP while DNS propagates, cron and daemons starting here, DNS repointed on both sides, certificates reissued once public DNS answers with the new address.
- One rollback for the batch. Anything failing before mail moves puts the old server back as it was, so the batch fails together rather than leaving you with thirty-nine accounts and a mystery.
- A DNS check afterwards. Per name, what Cloudflare, Google, Quad9 and the server's own resolver answer, how much cache time is left, and where each domain's nameservers live.
The full sequence, including pairing and the three check words, is on the migration page. It is the same machinery a single account uses; the batch simply repeats it per account and moves the cutover to the end.
What will still be manual at fifty.
Not a disclaimer. The list of things a queue cannot do for you.
Asked by everyone moving a batch.
Short answers.
Can I queue fifty cPanel accounts in one go?
You can run them as a sequence of jobs, each with its own progress and log. What you should not do is start all fifty simultaneously: every job unpacks an archive and then copies it, so it needs disk and I/O for both. Batch them, and check the disk between batches.
What happens if one account fails halfway?
That job fails alone and the rest of the queue is unaffected. From cPanel, the account is simply not imported and you retry it after fixing the archive. On an Account Transfer batch, the rollback is for the batch, because the cutover is a single step.
How long does fifty take?
It scales with data, not with account count: one large mailbox can take longer than twenty small sites. The honest planning method is to time your first three and multiply, then add the DNS window — which is cache time, not panel time.
Do I need to keep the old server running?
Yes, until the last domain has answered correctly from here for a week. The panel never deletes the source, and it never cancels a licence for you either — that is on the cPanel pricing page if you are working out when the saving starts.