cPanel Migration Checklist for Hosting Customers in 2026
Before you move anything, map the cPanel account
A good cPanel migration checklist starts with inventory, not file copying. Before you touch the new server, list the domain, addon domains, parked domains, email accounts, cron jobs, SSL status, database names, and any third-party DNS records tied to the site.
If you are moving from shared hosting to a VPS, this is where many support tickets begin. People remember the website, but they forget the mailboxes, subdomains, or the DNS record that keeps a payment form working. Our shared hosting to VPS migration guide is a useful companion if your site has outgrown its current plan.
Use this quick inventory list:
- Main domain and any additional domains
- Current PHP version and application type
- Email accounts, forwards, and autoresponders
- Databases and database users
- DNS provider and nameservers
- SSL certificate type and expiry date
- Any custom PHP settings, cron jobs, or redirects
Take screenshots if the account is small. For busier sites, export the zone file or record current DNS values in a simple spreadsheet.
Prepare the destination server first
Set up the new hosting environment before you copy data. Create the cPanel account, confirm the correct PHP version, and check that disk space, memory, and inode limits fit the site.
On Hostperl VPS hosting, this is usually where customers decide whether they need a general VPS or a larger setup for email-heavy or multi-site use.
If you are still choosing a plan, the practical comparison in VPS vs Dedicated Servers: How to Choose in 2026 helps you avoid under-sizing the new server. For small business sites, a properly sized VPS is often the right first step. For high-traffic stores or agencies hosting many accounts, a dedicated server is usually easier to grow into.
On the new cPanel server, check these basics:
- Set the hostname correctly and point it to the right FQDN
- Confirm the server timezone matches your business hours
- Enable the PHP extensions your application needs
- Make sure the firewall allows web, mail, and control panel services
- Install or confirm backup software before the cutover
For customers who want a faster launch path, Hostperl shared hosting still makes sense for new brochure sites and lightweight WordPress projects. But once migrations and custom DNS become routine, VPS control is usually worth it.
Copy the site files and databases cleanly
For a cPanel-to-cPanel move, the simplest route is usually a full account backup or a home directory plus database export. If you are moving between hosting providers, ask for the cPanel backup archive, then restore it on the destination account.
When that is not possible, download the website files from public_html and export each database separately.
Use the following checks during the copy:
- Match file ownership and permissions after extraction
- Verify the database import completed without truncation
- Update application config files with the new database credentials
- Confirm the site uses the correct document root
For WordPress customers, the database connection details usually live in wp-config.php. For many PHP apps, the same details appear in .env or a config file under the app root.
If your site depends on a CMS, our set up new hosting site in cPanel or Plesk guide gives you the destination-side structure before the move begins.
Keep the old site online until you finish testing. That avoids data loss if a form submission or order lands during the transfer window.
Move email without breaking deliverability
Email is where a cPanel migration checklist succeeds or fails. A website can tolerate a short delay. Mail users usually cannot.
Recreate all mailboxes first, then migrate message data if needed, and only then switch DNS.
If your business relies on hosted mail, follow the same practical order we recommend in how to set up email on shared hosting in cPanel. The account setup flow is similar on a new server, but migration adds one extra layer: identity has to match before mail starts flowing again.
Check the following before changing MX records:
- Create every mailbox that exists on the old host
- Set aliases, forwards, and autoresponders again
- Reapply SPF, DKIM, and DMARC records
- Test SMTP, IMAP, and webmail logins
- Confirm the server IP has a clean reputation
If mail deliverability matters more than ever, it usually does, use Shared Hosting vs VPS for Email Deliverability in 2026 as your decision check. A VPS gives you more control over reputation, but only if you configure DNS and authentication properly.
Lower DNS TTL before cutover
DNS changes should not be made on the same day you discover a problem. Reduce the TTL for the main A record, www record, and MX records at least 24 hours before the move. A TTL of 300 seconds is a sensible short-term setting for most migrations.
That one step can cut waiting time after cutover from hours to minutes. It also helps if you need to roll back quickly because of a missing plugin, a broken payment gateway, or an email routing mistake.
During the cutover window, update only what needs to change:
- Point the A record to the new server IP
- Keep nameservers unchanged unless you are moving DNS too
- Adjust MX records if mail now lives on the new host
- Reissue or reinstall SSL if the certificate was tied to the old environment
If DNS is part of a wider launch checklist, pair this tutorial with the SSL, DNS, and Email Setup Checklist for Hosting Customers. It covers the order that prevents the most common post-migration support issues.
Test before you switch traffic
Testing on the new server is easier if you use a temporary hosts-file override or a preview URL. Open the site in a browser, log in to the admin area, submit a test form, and place a small test order if the business supports eCommerce.
Then check the basics that customers usually notice first:
- Homepage loads without mixed-content warnings
- Images and stylesheets resolve from the new server
- Login, cart, and checkout flows work
- Search, contact forms, and password resets arrive by email
- Pages with database content match the old site
If the site is WordPress-based, verify the site URL and home URL after the move. If it uses cPanel email, confirm the mail client settings still point to the right IMAP and SMTP hostnames.
For panel selection questions during the next move, our cPanel vs DirectAdmin for New Hosting Customers in 2026 comparison explains where each panel fits best for real hosting customers.
Watch the first 24 hours closely
After cutover, keep the old account available long enough to catch late DNS caches and missed mail. The first day is about confirmation, not cleanup.
Watch access logs, mail queues, and the ticket inbox for broken links or forgotten records.
Use this post-move checklist:
- Check the site on mobile and desktop networks
- Send and receive email from external providers
- Review SSL status and certificate expiry
- Look for 404s on high-traffic pages
- Confirm backups are running on the new host
If you are moving multiple client sites, reseller teams should document every account separately. A migration that feels simple for one business can get messy across five domains, three mailboxes, and two sets of DNS records. Hostperl customers often use the Hostperl affiliate program or reseller-style workflows when they manage several launches in parallel.
Common cPanel migration mistakes
Most problems are not technical surprises. They are missed details. The usual ones are stale DNS records, wrong PHP versions, skipped mailboxes, and database credentials that were copied into the wrong config file.
Here is a short diagnostic list you can use when something breaks:
- Blank page: check PHP version and missing extensions
- Database error: confirm host, user, password, and database name
- Email not arriving: check MX, SPF, DKIM, and mailbox creation
- Old site still showing: clear browser cache and wait for DNS TTL to expire
- SSL warning: reinstall the certificate or renew it for the new hostname
If the site is too large for careful hand-copying, you may be better off moving to a bigger plan first. The practical signs are covered in Shared Hosting Upgrade Signals You Shouldn’t Ignore, which helps you decide before a migration turns into an emergency.
If you want a migration handled like a customer job, not a guessing exercise, Hostperl can help you move with less downtime and fewer surprises. Our Hostperl VPS hosting and shared hosting plans give you room to start small or scale when the site and mail outgrow the old setup.
For businesses in New Zealand and across APAC, that extra planning time matters. It gives you a better shot at a clean launch, steady email delivery, and a rollback plan if something unexpected appears.
FAQ
How long should a cPanel migration take?
A small site can move in under an hour once the destination server is ready. Email, DNS propagation, and testing usually take longer than the file copy itself.
Should I move DNS before or after the website?
Prepare the site first, then lower TTL, then switch DNS during the cutover window. That sequence gives you time to test before visitors see the new server.
Can I keep email working during a cPanel migration?
Yes, if you recreate the mailboxes first and switch MX records only after testing. Leave the old host active for a short overlap so delayed mail still lands.
Do I need a VPS for a cPanel migration?
Not always. Shared hosting works for smaller sites, but a VPS is usually the better home when you need more control over resources, mail, or DNS.
What is the fastest way to recover from a bad migration?
Lowered TTL and a kept-alive old server make rollback much easier. If the new site fails, point DNS back, fix the missing piece, and try again with less pressure.
