Migration

Migrate from cPanel to Reqad

The Transfer Tool in the Reqad server panel moves whole accounts from a cPanel server - sites, mail, databases, cron jobs, certificates and passwords - in one background job. It only reads from the cPanel server and does not touch DNS, so your sites keep running there until you switch.

What moves

Everything an account needs to keep working

Each account keeps its user name, so database names, paths and wp-config.php stay valid.

WhatHow it moves
AccountsSame user names and the same passwords: the account's system password, every mailbox password and every database user's password keep working.
SitesThe main domain, addon domains, subdomains and aliases, each with its PHP version. A version this server does not have is mapped to one it has.
FilesThe whole home folder, with the same paths (/home/<user>/...), so configuration files keep working.
DatabasesEvery database, its users and their access. MySQL 8 collations are converted for MariaDB on the way.
EmailMailboxes with their mail and sizes, forwarders, filters, autoresponders, spam allow and block lists, and the DKIM key - so the DKIM DNS record stays valid.
WebmailRoundcube contacts and settings of each mailbox; cPanel's own contacts go into the webmail address book.
Cron jobsWith the PHP version they run on mapped like the sites'.
CertificatesCopied as they are. Free ones are replaced with Let's Encrypt before they expire; bought ones stay until you renew them.
Password protected foldersThe folders protected with cPanel's Directory Privacy, with their users.
Visitor statisticsThe AWStats history, so the account's Visitors page does not start empty.
Contact address and languageThe account's contact address (no message is sent to it) and its cPanel language.
Packages and resellersWith Hosting Pro and Reseller: packages with their limits, resellers with their limits and packages, and who owns which account.
FTP accountsWith the FTP server add-on: every FTP user with its password and folder.
DNS zonesOptional, from a separate list: every zone with its records exactly as on cPanel.
IP addressesA map of the address each site and its mail used, so the addresses can be given back after the provider moves them.

Packages, resellers and FTP accounts need the Hosting Pro, Reseller and FTP server add-ons on the new server; without them they are only listed. The Transfer Tool also moves accounts from another Reqad server.

Step by step

From the first connection to the switch

  1. Prepare the new server

    Install Reqad on a fresh Rocky Linux, AlmaLinux or RHEL 8/9 server (Installation). Install the add-ons you need: the Account Panel for your customers, Hosting Pro for packages, limits and IP addresses, Reseller for resellers, the FTP server for FTP accounts. If many sites depend on .htaccess, choose Apache behind nginx (Hosting Pro) before you start.

  2. Install the PHP versions your sites use

    PHP settings > Install PHP. You can also leave a version out and choose which version its sites get here on the PHP versions step.

  3. Choose a DNS provider (optional)

    Only if you want to copy the DNS zones: Settings > DNS Settings (PowerDNS on this server, Cloudflare or another server).

  4. Let the new server in over SSH

    Open Transfer Tool in the server panel (port 2087). It shows the public SSH key of the panel's reqad user: add that line to /root/.ssh/authorized_keys on the cPanel server. If the cPanel server has a firewall or cPHulk, allow the new server's address.

  5. Connect

    Type the cPanel server's address, its SSH port and root. The tool finds out that it is a cPanel server and lists its accounts with their domains, sizes and owners, and its DNS zones. Nothing is changed on either server.

  6. Check the PHP versions

    Each version the sites use on cPanel, and whether this server has it. For a missing one, choose what its sites get here (the nearest newer version by default).

  7. Run the pre-transfer check

    Read-only. For the server and for every account: blockers that must be solved first (an expired domain, a table type MariaDB does not have) and checks that need a look (.htaccess lines, PHP extensions the code uses, parked domains with mail, services the account runs). Solve what it finds, then run it again.

  8. Choose accounts and what to transfer

    Tick the accounts, then the parts: files, databases, email, cron jobs, certificates, and - with the add-ons - hosting packages and resellers, and FTP accounts. Tick the parked domains with mail that should become sites. For each reseller, type the address its sign-in codes go to.

  9. Start the transfer

    All accounts go in one background job, one after the other: you can close the page. Each account has its own log; lines marked ! need a look. A stopped or failed account can be started again: what is already here is kept and the rest is finished.

  10. Test before anything changes

    The sites still run on cPanel. Point your own computer at the new server with a line in your hosts file, such as 203.0.113.10 example.com www.example.com, and open the sites, the account panel and webmail. Passwords are the same as on cPanel.

  11. Copy the DNS zones (optional)

    From the accounts list, choose DNS zones: each zone is made here with its records as they are on cPanel. Nothing changes on the internet until the domains' name servers are this server's.

  12. Switch

    Either change the DNS records (lower their time to live a day before, and the pre-check shows it), or have your provider move the cPanel server's IP addresses to the new server and press Restore IP addresses (Hosting Pro): each account gets its own address back and each domain sends mail from the address it used, so DNS can stay as it is.

  13. After the switch

    Let's Encrypt certificates are issued and renewed by themselves once the names point here. Mail that reached the old server after the copy stays there: switch soon after the transfer and keep the old server a few days. Tell your customers what changes (below).

Nothing is changed on the cPanel server.

The tool reads accounts, files and databases over SSH and copies them. Until you change DNS or move the IP addresses, visitors and mail still go to cPanel, so you can test for as long as you need and start again if something is not right.

Incompatibilities

Differences to plan for

The pre-transfer check finds most of these on your own accounts before anything moves. Here is the whole list.

On cPanelOn ReqadWhat to do
.htaccess rewrite rules (sites on nginx)nginx does not read .htaccess. WordPress works as it is; other software's rewrite rules do not.Use the web server "Apache behind nginx" (Hosting Pro) or Apache with PHP-FPM for these sites, or add the rules as nginx rules in the site's Advanced Config.
php_value / php_flag in .htaccess, .user.iniNot read on nginx (the pre-check lists every line).Set them in the account panel: PHP > PHP settings.
Parked domains with mailboxesAn alias here has no mail of its own.Tick it in the transfer: it becomes a site of its own (same folder) and keeps its mail.
Default address (catch-all)Left out, because it collects spam: mail to unknown addresses is refused.Make the addresses that are really used as mailboxes or forwarders; for a domain that really needs a catch-all, the host can add a custom Exim filter.
Domain forwarders, backup mail server (backup MX)Not available.Forwarders per address; a backup MX elsewhere.
Remote Mail ExchangerThe site's mail provider is a setting of its own.Choose the provider in Domains (Google Workspace, Microsoft 365, Zoho Mail or another one).
Mailing lists, BoxTrapper, Web Disk, Encryption keysLeft out of Reqad.A mailing list service; spam filters; SFTP or FTP; your mail app's encryption.
Calendars (CalDAV)This server has no calendar service.Ask users to export calendars from their phone or mail app before the switch.
Application Manager, CloudLinux Node.js / Python / Ruby selectorsApps are not set up by the transfer; Ruby is not available.Add Node.js and Python apps in Deploy & apps after the transfer (their files are already there).
Programs started outside cPanel, Apache settings outside .htaccess, ProxyPass to local portsNot transferred (the pre-check lists them).Move them by hand, then check the site.
Remote MySQL hostsNot transferred.Add them again in Databases > Remote access (per user, database and address).
CloudLinux limits (LVE)Not transferred.Set the limits in hosting packages (Hosting Pro).
A shared IP addressNot given to one account: every site answers on every address of the server.Nothing to do; dedicated addresses can be given back with Restore IP addresses.
POP3 message idsMade differently on some servers, so POP3 programs could download every message again.The pre-check compares the two servers and warns you.
Old mailbox password hashes (MD5-crypt)Still accepted, so nobody is locked out.Ask the owners of old mailboxes to change their password.
Domains that expired or are not registeredStop the pre-check (nothing to transfer).Renew them, or leave them out.

For every feature, side by side: Reqad Account Panel vs cPanel.

Your customers

What account owners notice

Same sign-in

Same user name and password, at https://your-server:2083/. Each of their sites sends /cpanel to it, so old bookmarks keep working.

Same webmail

Roundcube on port 2096, with the same mailbox passwords, contacts and settings.

Same mail settings

Mail apps keep working when the server's name stays the same; otherwise the new settings are on the Email accounts page, with a QR code for phones.

A different panel

Most tools have familiar names, and the search box at the top finds every one. Help in the menu opens the guide.

Want help with the move?

Help with migrations comes with Premium. With Managed, we install Reqad on your server and move your sites, email and databases for you.