Move first. Change DNS when you're ready.
KLYRN reads a cPanel or DirectAdmin backup, or connects to the old server over SSH. Nothing is installed there, and it keeps serving until you change DNS. Moving from cPanel or DirectAdmin is part of Pro. Copying a site over SSH is free.
It works with what you have.
You give KLYRN one file or one SSH login. The password or key is used for the job and never stored.
- A cPanel backup archive.
- cPanel over SSH, as root.
- cPanel over SSH, as the account, without root.
- A DirectAdmin user backup.
- Any server over SSH, with an ordinary Unix login.
How a migration runs.
Nothing is written until you have read the plan.
klyrn import cpanel /root/backup-acme.tar.gz
klyrn import show 1 # the plan
klyrn import apply 1 # the first thing that writes- AnalyseEvery domain, database, cron entry and mailbox becomes a plan.
- CopyFiles, databases, mailboxes and cron jobs. Database passwords stay the same.
- VerifyEleven checks, and a preview of every site on the new server.
- Cut overThe exact DNS records to change.
Check every site before DNS.
The imported site is live on the new server while the old one still serves the public. The checks run against the new server only, so compare the two pages yourself.
Mail comes across.
Mailboxes arrive with their existing passwords. Forwarders come too, from cPanel and DirectAdmin. KLYRN never changes an MX record for you.
What is proven.
It was run on a production DirectAdmin server with 48 domains and 48 mailboxes. The cPanel route has so far been tested against archives KLYRN wrote itself.
Migration is in Free.
Install KLYRN on a fresh Ubuntu server and bring one site across.