A hosting move can put your business email at risk long before your website goes offline. If your domain email is managed through your old hosting account, changing nameservers or canceling the old plan too soon can stop new messages from arriving. The good news is that learning how to switch hosting provider without losing email is mostly about planning the email move before changing DNS.
Your goal is simple: keep the old email service active, build the new email service, copy existing messages, and then point your domain to the right place. Done in that order, most visitors and senders will never notice the change.
First, Find Out Where Your Email Is Hosted
Do not assume your email is hosted wherever your website is hosted. Many small businesses use cPanel email accounts provided by their host, but others use Microsoft 365, Google Workspace, Zoho Mail, or another dedicated email service.
Check the email settings in the app you use for mail, or review your domain’s DNS records. The MX records tell other mail servers where to deliver your email. If they point to a third-party provider such as Microsoft or Google, moving your website hosting usually will not require an email migration. You still need to protect those DNS records when updating the domain, but your mailboxes and stored messages remain with the email provider.
If your MX records point to your current host, your email needs to move. This is common when addresses such as [email protected] and [email protected] were created inside cPanel.
Make an Email Inventory Before the Hosting Move
Email problems often happen because a mailbox or setting was overlooked. Before opening a new hosting account, write down every active email address, including addresses that forward mail to another inbox.
Review the old account for mailbox sizes, aliases, forwarders, autoresponders, mailing lists, spam filters, and email filters. Also note any catch-all address, which receives messages sent to misspelled or uncreated addresses at your domain. These settings do not always transfer automatically with a website backup.
Download or save copies of important contacts, calendars, and address books if they are stored in webmail. Email messages can be copied through a migration tool, but contacts and calendars may require a separate export depending on the service you use.
It also helps to lower the DNS TTL, or time to live, 24 to 48 hours before the move. A lower TTL tells internet providers to refresh DNS information more quickly after you change records. Set it to 300 seconds if your current DNS provider allows it. This does not eliminate propagation time, but it can shorten it.
Set Up the New Hosting Account Before Changing DNS
Create your new hosting account while the old one is still active. This overlap is not wasted money. It is the safest way to avoid lost mail and gives you time to test the website, SSL certificate, and email setup without pressure.
In the new cPanel account, create every mailbox using the exact same email address and password where practical. Matching passwords can reduce confusion for employees who need to update their mail apps. Set mailbox quotas high enough for the messages you plan to transfer.
Also recreate forwarders, filters, autoresponders, and mailing lists. If you use a catch-all address, decide whether you still need it. Catch-all mailboxes can collect legitimate inquiries, but they can also attract a large amount of spam.
If you are moving to a cPanel host, ask support whether it can perform a full cPanel transfer. A full account migration may copy website files, databases, email accounts, and existing messages. It is often the easiest route for a standard shared hosting move, though you should still confirm exactly what is included. Large mailboxes, custom DNS settings, and third-party email platforms may need additional work.
Copy Existing Email Messages Safely
Creating empty mailboxes at the new host protects future delivery only after DNS changes. It does not bring over your old inbox, sent mail, folders, or archived messages. Copy those separately before you cancel the old hosting service.
For cPanel-to-cPanel moves, a full account transfer can usually preserve mailbox contents and folder structure. Another option is IMAP migration, which copies messages directly from the old mail server to the new one. You can use a supported migration tool, or ask your new host’s support team about available options.
A desktop email application can work for small accounts. Add both the old and new mailboxes through IMAP, then copy folders from one account to the other. This method is slower for large inboxes and requires your computer to stay connected, but it gives you direct control over what is moved.
Do not rely on POP-only email downloads as your only backup. POP may store messages locally and remove them from the server, which makes it harder to verify that everything was copied. Before changing DNS, compare folder names, message counts, and important attachments in both accounts.
Update DNS Without Breaking Email
This is the step that deserves the most care. Your website and email can use different DNS records, and a nameserver change can replace all of them at once.
If you switch your domain to the new host’s nameservers, copy every required DNS record first. At minimum, review the MX records, SPF record, DKIM records, and DMARC record. These records control where mail is delivered and help receiving servers verify that messages from your domain are legitimate.
An incomplete DNS update can create two common problems. Missing MX records cause incoming mail to fail or bounce. Missing SPF, DKIM, or DMARC records can send legitimate business messages to spam folders, especially when you use forms, newsletters, invoices, or a third-party sending service.
You can also keep DNS where it is and update only the website records, such as the A record or CNAME. This is often the lowest-risk choice when your current DNS zone already has working email records. It depends on your setup and whether you want the new host to manage DNS going forward.
After updating DNS, test delivery from an outside address such as a personal Gmail or Outlook account. Send a message to each key business address, reply from webmail, and confirm both directions work. Check spam folders as well. Test contact forms on your website, since form notifications may use a different sending method than regular mailbox email.
Keep the Old Account Active During the Transition
DNS changes can take time to reach every network. Most changes are visible within a few hours, but some providers and devices may continue using old information for up to 48 hours. Keep the old hosting account active for at least 48 to 72 hours after the DNS change.
During that window, check both old and new inboxes. If a message arrives at the old server, copy it to the new account or forward it as needed. A final IMAP sync after the DNS change helps capture messages that landed during the transition.
Do not cancel the old account until you have confirmed that your website loads from the new host, every mailbox can send and receive, SSL works correctly, and no critical DNS records are missing. Take a final backup before closing the old service.
Common Mistakes That Cause Lost Email
The biggest mistake is changing nameservers before documenting the DNS zone. The second is canceling old hosting the same day as the move. Both decisions can turn a routine transfer into a recovery project.
Another frequent issue is forgetting that email apps need new server settings. After the migration, update incoming and outgoing server names, ports, encryption settings, and passwords on phones and computers. Use SSL or TLS whenever available. If you use a provider such as Visiba with cPanel hosting, the account’s email configuration details can guide you through the correct settings.
Finally, do not treat successful website loading as proof that the migration is complete. A site can be live while email delivery, authentication, and form notifications are still misconfigured.
A careful hosting move takes a little overlap and a few checks, but it is far less stressful than recovering missed customer messages. Keep your old service active, verify email before and after DNS changes, and give the internet time to catch up before you close the previous account.