How to Move a Hosting Site Between Panels in 2026
Start with the panel, not the server
If you need to move a hosting site between panels, the first question is not which copy tool to use. It is what kind of move you are making. A cPanel-to-Plesk transfer, a DirectAdmin move, and a shared-to-VPS migration each change the order of work, the DNS timing, and the cleanup after cutover.
For most Hostperl customers, the safest path is straightforward: inventory the site, copy the data, test it on a temporary hostname, then switch DNS only after mail, SSL, and panel settings line up. If you are still deciding whether the destination should be shared hosting or VPS, the comparison in cPanel vs Plesk vs DirectAdmin for Hosting Buyers in 2026 is a useful starting point, especially if several sites or clients will live on the new account.
For the destination account, Hostperl’s Hostperl VPS plans give you room to stage the migration properly. That matters when you need a test copy, mail validation, or more PHP memory before launch day.
Make a migration sheet before you touch anything
A clean migration starts with a sheet, not a transfer button. Write down the current panel, domain, DNS host, mailbox count, database names, PHP version, cron jobs, SSL status, and any third-party services tied to the site.
- Website files: public_html, application folders, media uploads, theme files
- Databases: MySQL or MariaDB name, user, and size
- Email: active mailboxes, aliases, forwards, catch-alls
- DNS: A, AAAA, CNAME, MX, TXT, and any custom records
- Special settings: PHP handlers, SSL force-redirects, cron tasks, and cache rules
This step saves time later. It also gives support teams something concrete to check if the site behaves differently after the move.
Prepare the destination account first
Do not copy files into a half-finished account. Set up the destination hosting space, create the domain or subscription, and confirm the panel version before migration. If you are moving a small business website, use a staging hostname such as staging.example.com or a temporary preview URL so you can test without affecting visitors.
If you are creating the new site in a control panel, follow the workflow in How to Set Up a New Hosting Site in cPanel or Plesk. That guide lines up the document root, databases, and domain settings before any import begins.
For WordPress or other PHP sites, make sure the new account has the same or newer PHP release than the source. In 2026, many migration issues come from version drift, not from the file transfer itself.
Copy the site in the right order
Files first, then the database, then configuration. That order keeps you from chasing errors that really come from missing credentials or the wrong document root.
- Copy the web files. Use the panel backup tool, File Manager, FTP/SFTP, or your host’s migration service.
- Export the database. Keep the export compressed if the database is large.
- Import the database on the new host. Verify the table prefix and collation if the app is older.
- Update config files. Check
wp-config.php,configuration.php, or app-specific env files. - Test locally on the new host. Load the temporary URL before you touch live DNS.
If you need a controlled panel-to-panel transfer, use How to Move a Hosting Site Between Panels in 2026 as your main checklist. For customers who want the move done without a visible interruption, Move a Hosting Site Between Panels Without Downtime covers the DNS overlap approach in more detail.
Handle email separately from the website
Email is usually the part that causes the most trouble after a migration. Website files may load fine while mail still points to the old server, which is how people end up with missing messages or duplicate inboxes.
Before cutover, lower the DNS TTL on MX and related records to 300 seconds if your DNS host allows it. Then confirm the mailboxes, forwarders, and catch-all addresses exist on the new panel. If your business depends on outbound mail, check SPF, DKIM, and DMARC before you switch MX.
Hostperl has separate guidance on the mail side in Shared Hosting vs VPS for Email: What Actually Changes. That article helps you decide whether the move should include a mail upgrade as well.
As a practical test, send one message from an external address to each mailbox and confirm it lands in the right inbox. Then reply from the new server and check that the sender line, DKIM signature, and return path are all correct.
DNS cutover: keep the change small and reversible
Once the site works on the destination host, update DNS. For most migrations, you only need to change the A record, maybe the AAAA record, and the MX records if mail is moving too. Leave the rest alone unless the new environment needs a different TXT or CNAME entry.
Use a short change window and keep the old hosting active for at least 48 hours if possible. That gives delayed DNS resolvers time to catch up and lowers the chance of lost mail or stale content.
If DNS management feels messy, especially after a registrar change, Hostperl’s domain and DNS support can help you separate the hosting move from the domain move. That makes the migration easier to troubleshoot.
Test the live site before you announce the move
Do a full pass through the pages users actually visit. Do not stop at the homepage.
- Open the contact form and submit a test message.
- Check login, checkout, or booking flows.
- Load image-heavy pages and confirm the paths still work.
- Verify SSL on the new hostname and the live domain.
- Check admin areas, cron-driven tasks, and password resets.
If the site is WordPress, compare the front end and admin dashboard after the cutover. If it is a custom PHP app, watch for hardcoded URLs in the database or config files. A single old hostname in a settings table can make the site look half-migrated even when the files are fine.
For customers moving from a shared plan to a larger environment, How to Move from Shared Hosting to VPS in 2026 is worth keeping open beside your migration notes.
Troubleshoot the three most common breakpoints
Most post-migration problems fall into three buckets: wrong document root, wrong database credentials, or DNS that has not fully updated. You can check all three quickly.
grep -R "DB_NAME\|DB_USER\|DB_PASSWORD" /home/username/public_html/dig +short example.com Acurl -I https://example.comIf the site loads on the temporary hostname but not on the live domain, DNS is usually the issue. If the homepage loads but logins fail, the database or session path is usually wrong. If images or CSS are missing, check the document root and file permissions.
Panel-specific behavior matters too. cPanel, Plesk, and DirectAdmin store site settings differently, so do not assume the old paths map cleanly to the new account.
Finish with a clean rollback plan
Never delete the source server the same day you migrate. Keep the old account active until the new site has handled normal traffic, incoming mail, and at least one business cycle. That is the simplest rollback plan you can have.
When the move is stable, update your internal notes with the final DNS host, panel login path, PHP version, backup schedule, and any changed mailbox settings. Future support calls become much shorter when someone can see what actually changed.
If you want help moving a live site with less guesswork, Hostperl can stage the destination, verify DNS, and keep the old service available during the handover. For customers who want room to test before cutover, our VPS hosting and shared hosting plans both work well for migration projects.
Our team handles real launch timelines, mailbox checks, and panel-to-panel transfers, not just file copies.
FAQ
How long should I keep the old hosting after a panel move?
Keep it for at least 48 hours. If email is involved or your audience is global, 72 hours is safer.
Should I migrate email and website at the same time?
Only if you have tested both sides. If email is business-critical, moving the website first and mail second is often easier to control.
Do I need to change my SSL certificate after moving panels?
Usually yes. Reissue or renew it on the new host so the certificate matches the live domain and the new server setup.
What is the best way to test the migration before DNS changes?
Use a temporary hostname or hosts-file preview and confirm pages, forms, logins, and mail flow before you update live records.
Can Hostperl help with this kind of migration?
Yes. If you are moving from shared hosting to VPS, or from one panel to another, Hostperl support can help you plan the cutover and reduce downtime.
