How to Move a Website Between Hosting Panels
Before you start the move
If you need to move a website between hosting panels, treat it like a controlled handover, not a simple copy-and-paste job. Check what the old account contains, what the new panel supports, and which parts depend on DNS, email, or server-specific settings.
Most moves fall into one of three buckets: shared hosting to shared hosting, shared hosting to VPS, or one control panel to another on a VPS or dedicated server. If you are still choosing the destination, compare the workload first. Our Hostperl VPS plans work well when you need root access, predictable resources, and room for mail or app traffic that has outgrown shared hosting.
Before you touch DNS, make this checklist:
- Export the current site files and database.
- Note the PHP version, cron jobs, and any custom .htaccess rules.
- List every mailbox, forwarder, filter, and autoresponder.
- Check whether SSL is a free certificate or a paid wildcard.
- Confirm the new panel is using the same document root structure.
If you want a broader planning view first, our migration testing guide shows how to verify a copy before you point a live domain at it.
Map the old hosting account correctly
The quickest way to break a migration is to assume the old panel only holds website files. It often includes email, DNS, SSL, scheduled jobs, and parked domains too. Spend a few minutes mapping the account before you export anything.
In cPanel, check File Manager, MySQL Databases, Email Accounts, Zone Editor, and Cron Jobs. In Plesk or DirectAdmin, look for the same functions under their equivalent menus. Your goal is a small inventory, not a guessing game later when pages stop loading.
Use this simple rule: if you changed a setting manually, write it down now. That includes SPF records, PHP limits, redirects, and any cache plugin settings tied to a specific path.
Copy files and database without breaking paths
Most websites fail after migration because the files copied correctly, but the path changed. If your app expects /home/username/public_html and the new account uses /var/www/vhosts/example.com/httpdocs, you may need to adjust config files or panel-level document roots.
For shared hosting moves, use the built-in backup or migration tools where possible. For VPS or dedicated servers, copy the site files, then restore the database, then update the configuration file that connects the two. If the site is WordPress, check wp-config.php. For Laravel or similar apps, check .env for database names, cache settings, and mail credentials.
After the copy, open the site on the temporary hostname or server IP before you change DNS. If images are missing or the theme loads with CSS errors, the file copy was incomplete or the web root is wrong.
Handle email before you switch DNS
Email is where many migrations get messy. Website traffic can live with a short DNS delay. Mail cannot.
Move every mailbox, alias, forwarder, and autoresponder first. If the old hosting package still delivers mail while DNS is changing, users may see messages split across two servers. That is especially common on shared plans, where mail and web live together but DNS propagates at different speeds.
For practical guidance on mail on shared plans, see Email Hosting on Shared Plans: What Matters in 2026. If your customers rely on inbox delivery, also review Shared Hosting vs VPS Email Deliverability in 2026 before you decide where mail should live after the move.
A practical mail checklist:
- Create the same mailbox names on the new server.
- Copy existing messages if the business needs historical mail.
- Update MX, SPF, DKIM, and DMARC records.
- Send a test message to Gmail, Outlook, and one business domain.
- Check that replies are not landing in spam.
If you need panel-specific help, Hostperl has a step-by-step cPanel email deliverability guide that covers the usual causes of mail rejection and poor inbox placement.
Update DNS with a short overlap window
Once the new site and mail are working, lower the DNS TTL on the live zone before the final cutover. A TTL of 300 seconds is a sensible temporary value for a migration. Leave it there for a day or two before you move, then restore a longer value afterward.
If your domain is managed elsewhere, make sure the nameserver records are correct and the zone file has all required entries. If you need a clean refresher, the SSL, DNS, and Email Setup Checklist for Hosting Customers page is a useful pre-flight reference.
At this stage, change only what you need. That usually means the A record for the website and the MX records for mail, not a full-zone rewrite. Smaller edits are easier to reverse if one service misbehaves after propagation.
Test the new panel before you point real users at it
A temporary URL or hosts-file test is worth the extra ten minutes. Open the site, log in to the admin area, upload a file, submit a form, and send a password reset email. You are not looking for perfection yet. You are checking for obvious issues while the old site is still live.
For WordPress, verify these items in sequence: homepage, one internal page, login, media upload, and the contact form. For custom apps, check the login session, database connection, and any scheduled task that runs from cron. If the new server is a VPS, compare the active PHP version and memory limits with the old environment before you troubleshoot deeper.
If the destination is a bigger plan, this is usually the point where customers decide whether they need to stay on shared hosting or move up. Our shared hosting to VPS guide and hosting plan comparison help with that decision.
What to check after cutover
Once DNS points to the new server, keep both environments available for a short overlap window. That gives you time to catch straggling mail, missed uploads, or a forgotten redirect.
Use this post-move checklist:
- Open the site from mobile and desktop.
- Confirm HTTPS loads without certificate warnings.
- Send and receive mail from at least two external providers.
- Check error logs for PHP notices, 404s, and permission errors.
- Verify backups are scheduled on the new account.
If something fails, revert one service at a time. For example, if mail is broken but the website is fine, keep the web DNS change and fix the mailbox records first. You do not need to roll back the whole migration for one missing MX record.
Common problems and fast fixes
Blank page after the move: the PHP version or memory limit probably changed. Check the panel and match the old environment first.
Login fails: the database connection string, session path, or cookie domain may still point to the old server.
Images 404: the upload directory is wrong or file permissions changed during transfer.
Mail stops arriving: the MX record still points to the old host, or the mailbox was not recreated on the new server.
SSL warning: the certificate did not issue for the new hostname, or the old certificate stayed attached to the wrong domain entry.
If you are moving between panels, Hostperl also has panel comparison material that helps you avoid surprises before the next switch. See cPanel vs Plesk vs DirectAdmin and cPanel vs Plesk migration guidance if your current and future servers use different control panels.
If you want help moving a live site with less risk, Hostperl can support the process with the right hosting setup and a practical migration plan. Our shared hosting and VPS hosting options are built for real site transfers, not just fresh installs.
For businesses that care about email, uptime, and a clean handover, that support can make the difference between a smooth cutover and a long night.
FAQ
How long does it take to move a website between hosting panels?
Small sites can move in under an hour once backups are ready. Business sites with email, multiple domains, or large databases usually need a longer overlap window.
Will my email stop working during the transfer?
It should not, if you copy the mailboxes first and switch MX records carefully. Keep the old account active for a short period so no messages are lost.
Do I need a VPS to move between panels?
No, but a VPS gives you more control if the site needs custom PHP settings, special packages, or separate mail handling. Shared hosting works fine for smaller sites.
What is the safest time to change DNS?
Choose a quiet period for your audience, then lower the TTL before the cutover. That reduces the waiting time before visitors reach the new server.
Can Hostperl help with a panel migration?
Yes. If you are moving between cPanel, Plesk, or DirectAdmin, Hostperl support can help you choose the right destination and avoid common cutover mistakes.
If this move is a step toward a larger setup, review our VPS vs dedicated servers guide before you commit. The right platform depends on traffic, mail volume, and how much control you want after the migration.
