How to Migrate Hosting Sites Between Panels in 2026
Before you move anything, map the job
If you need to migrate hosting sites between panels, start with a clear inventory of what lives on the account: website files, databases, email boxes, DNS records, SSL certificates, cron jobs, and any custom PHP settings. That list matters more than the panel brand. The real risks usually show up in mail routing and DNS timing, not the file copy itself.
For shared hosting customers, the simplest route is usually to use the source panel’s backup tools and restore into the new account. On a VPS, you may use cPanel, Plesk, or DirectAdmin migration tools, or move each piece manually if the destination is a plain Linux server. If you want a quick comparison of hosting plans before you begin, our guide on VPS vs dedicated servers is a useful checkpoint.
At Hostperl, this is usually where support teams ask one direct question: do you want the old site copied, or do you want the service moved cleanly with mail and DNS included? The answer changes the order of work.
Build a migration checklist you can actually use
Keep the checklist plain and specific. Put it next to the account details and mark each item off as you go.
- Site files: /public_html, web roots, and any subdomains
- Database dump: MySQL or MariaDB, plus the database user
- Email: mailboxes, forwards, aliases, and filters
- DNS: A, AAAA, MX, CNAME, TXT, and SPF/DKIM/DMARC records
- SSL: installed certificate or enough time to issue a fresh one
- App settings: wp-config.php, .env files, config.php, or panel-specific paths
- Scheduled jobs: cron entries in cPanel, Plesk, or crontab
If your old host handles shared email and you are moving to a VPS or another panel, read choosing between shared hosting and VPS for email before you switch. Email is where many migrations look fine at first, then fail quietly a day later.
Copy the site first, then move DNS
Move the data before you change nameservers. That keeps the old site live while you test the new one. For most customers, this is the safest order:
- Copy files to the new panel or server.
- Import the database and update the application config.
- Test the site using a temporary URL, hosts-file override, or preview path.
- Check login, checkout, contact forms, and image loading.
- Only then update DNS or nameservers.
If you need a broader walkthrough for moving between environments, our guide on moving a hosting site to a new server safely fits neatly with this process. It is especially useful when a customer has to move a WordPress site from shared hosting to a VPS without breaking email or SSL.
Use a low DNS TTL a day before the move. A 300-second TTL on the records you will change reduces cache delay during cutover. If your provider exposes DNS in the panel, update the zone there before you go live.
Handle email before customers notice a gap
Email migrations need their own pass. A website can be fixed in minutes. Missed mail usually shows up hours later, often as a support ticket.
Move mailbox contents, forwarders, autoresponders, filters, and authentication records carefully. Then verify that the new server can send mail with the correct hostname, SPF entry, DKIM key, and DMARC policy. Our tutorial on email deliverability on shared hosting covers the record checks you should repeat after every migration.
A short test list works well:
- Send to Gmail, Outlook, and one business mailbox.
- Reply from the mailbox and confirm the reply lands correctly.
- Check the message headers for SPF pass and DKIM pass.
- Confirm mail is no longer writing to the old server’s mailbox store.
Test SSL, redirects, and the page that always gets missed
After the site is copied, confirm that the certificate matches the final hostname. If the old server used AutoSSL or Let’s Encrypt, issue a fresh certificate on the new panel instead of copying an expired one. Then test the following pages:
- Homepage
- Login page
- Cart or checkout
- Contact form
- Any subdomain used for billing, staging, or mail
Most customers miss one redirect rule or one subdomain. That is where mixed-content warnings and broken logins appear. If you are working inside cPanel, Plesk, or DirectAdmin, our guide to setting up a new hosting site in cPanel or Plesk helps you verify the basics before launch.
For WordPress sites, refresh permalinks after the move and make sure the database prefix did not change. For PHP apps, confirm the PHP version, extensions, and document root are identical on the new account.
Watch for the common panel-specific traps
Different panels hide different problems. The file copy can succeed while one small setting breaks the live site.
- cPanel: check addon domains, email routing, and cron paths.
- Plesk: confirm subscription limits, PHP handler choice, and mail service status.
- DirectAdmin: review domain pointers, DNS templates, and custom PHP settings.
If you are still deciding which panel fits your team, our comparison of cPanel vs Plesk vs DirectAdmin is a better pre-migration read than a generic feature chart. It shows where each panel helps real customers, not just sysadmins.
On Linux servers, check ownership and permissions after the transfer. A common mistake is copying files as root and leaving them unreadable by the web service. On Ubuntu or Debian, the web user is usually www-data. On RHEL-family systems, it may be apache or nginx depending on the stack.
Cut over with a rollback plan
Never switch DNS without a rollback path. Keep the old hosting account active until you have verified live traffic, form submissions, and mail flow on the new server.
A simple rollback plan includes three things: the old DNS zone, the original backups, and the date and time of the cutover. If traffic or mail fails, you can point the domain back and buy time. That is a lot easier than debugging a broken launch after the old account has already been deleted.
If you have a large site or multiple domains, Hostperl can help you map the move to the right plan first. For most growing sites, Hostperl VPS gives you room for testing and post-move tuning. If the project is busier than shared hosting but still not ready for a full dedicated machine, that is often the practical middle ground.
Post-migration checks for the first 24 hours
The move is not finished when the homepage loads. Spend the first day checking the issues customers usually find too late.
- Review server logs for PHP errors, 404s, and mail failures.
- Confirm SSL renewals are active.
- Check disk usage, inode usage, and database size.
- Verify backups are running on the new platform.
- Test from mobile data and a second network, not just your office Wi-Fi.
If the site runs slowly after the move, compare PHP version, object cache settings, and image sizes before you blame the host. Many performance complaints come from old plugin settings or a larger image library carried over during migration. For buyers deciding whether they should stay on shared hosting or step up, shared hosting upgrade signals you shouldn’t ignore gives a useful reality check.
If you want help moving a live site without turning the cutover into a long outage window, Hostperl can handle the hosting side with you. Our managed VPS hosting gives you room to test, and our shared hosting plans suit smaller sites that need a careful move and clean setup.
We work with migrations, DNS changes, SSL renewals, and mail checks every day, so you are not left guessing after launch.
FAQ
How long does it take to migrate hosting sites between panels?
A small WordPress or brochure site can move in under an hour. Add more time for email, large databases, or multiple domains.
Can I keep email on the old host while the website moves?
Yes. That is often the safest choice. Keep MX records pointed at the old service until mailbox data is copied and tested.
Do I need to change nameservers during the move?
Not always. If your DNS is managed elsewhere, you may only need to change A and MX records. That gives you finer control and easier rollback.
What is the biggest mistake customers make?
They switch DNS before testing the new site and email delivery. The result is avoidable downtime and missing mail.
Should I migrate to VPS or stay on shared hosting?
If your site is small and predictable, shared hosting may still be enough. If you need more control, higher resource limits, or separate mail handling, a VPS is usually the better move.
