Migrate to Unicorn Panel
Move off cPanel, Plesk, or DirectAdmin
A built-in import wizard works out what your archive is, then brings each site onto the host, PHP version, and web engine you choose. No re-architecting, and nothing to unpack by hand. The wizard is still being finished, so treat this page as what is coming rather than what you can run today.
The format is worked out from the archive itself, and you can override it if the panel guesses wrong.
Import is still in development. These are the formats it will read, not a list of what works today. Check the Releases page for what has landed, or tell us what you are moving from and we will let you know when your source is ready.
How it works
Four steps, no modals to get lost in
The importer is a single page you scroll through: Source, Format, Target, Progress. Drop an archive in, or have the panel fetch it straight from a URL. It works out what the archive is, you pick where it lands, and the import reports progress as it runs rather than leaving you watching a spinner.
- Drag-and-drop an archive, or fetch it from a URL
- Reads Unicorn Panel, cPanel, Plesk, DirectAdmin, Enhance, and Duplicator archives, or a custom one
- Target any Secondary host, PHP version (5.6 to 8.5), and web engine
- Pick which databases, mailboxes, and DNS records come across with the site
What migrates
What comes across,
and what does not
The honest version, so you can plan the gaps rather than discover them. This is what the wizard is being built to do.
- Website files, ownership, cron jobs, and redirects
- Databases and their users, with grants regenerated on the new host
- Mailboxes, with folders and messages preserved
- DNS zone records
- SSL, re-issued through Let’s Encrypt on the first request
- Extra FTP logins do not come across one for one. Each site gets its own user for SFTP, so any additional accounts are recreated here
- Server-level config from the old panel, such as firewall rules and PHP-FPM tuning. That is Unicorn Panel’s job now
- Certificates from the source panel. Fresh ones are issued instead
Nothing on the old host is touched. An import that fails leaves it exactly as it was, so you can retry, bring the site across another way, and keep serving from the old server until you point DNS.
Why teams switch
What you gain by moving
Legacy sites keep working
PHP 5.6 through 8.5, swappable per site, so old WordPress, Magento, and Drupal installs come across without a forced upgrade.
Real isolation
Every migrated site lands in its own container, with its own user, its own PHP-FPM, and its own limits on CPU, memory, and disk.
One panel for many servers
Bring sites onto any host in the fleet and manage them all from one Primary, instead of logging into each box.
No per-server fees
Self-hosted licensing that doesn't charge you more for scaling out, unlike per-server Plesk add-ons.
Backups that fit
Once migrated, sites, databases, and mailboxes back up separately with the right semantics. See Backups.
White-label ready
Resellers get their own branded panel and SMTP, so customers never see a jarring change of vendor.
By source
Coming from a specific panel?
From cPanel
Drop in a cpmove archive. See the full architectural differences on the comparison page.
Learn moreFrom Plesk
Bring a Plesk backup across and manage every server from one Primary panel. How they compare.
Learn moreFrom DirectAdmin
Import a DirectAdmin backup onto a fleet-aware panel with a full REST API. See the differences.
Learn morePlan your move.
Tell us what you are running today and we will help you bring it across.