Moving business email to a new host is usually straightforward, but it needs careful planning if you want to avoid lost messages, interrupted mail flow, or missing folders. The safest approach is to keep both the old and new mail systems active during the transition, copy existing mailboxes, update DNS records at the right time, and verify that every account works before you close the previous service.
If your organisation uses email addresses tied to a domain name, the migration process affects more than just inbox contents. You also need to consider MX records, SPF, DKIM, and DMARC, because these records control where mail is delivered and how your messages are authenticated. For businesses using a control panel such as Plesk, the move can be even smoother because mailbox creation, forwarding, and DNS management are easier to coordinate from one place.
What you need to prepare before moving business email
Before changing hosts, gather a full list of the email services currently in use. This includes all mailboxes, aliases, forwards, catch-all addresses, shared mailboxes, and any application-specific accounts used by websites, invoicing systems, or CRM tools. Missing even one account can break a login, stop notifications, or cause a failed password reset.
Checklist for the migration plan
- List every mailbox and email alias using the domain.
- Record current DNS settings, especially MX, SPF, DKIM, and DMARC.
- Check mailbox sizes and total storage used.
- Confirm whether users access mail via IMAP, POP3, webmail, or a mobile client.
- Identify any shared addresses used for contact forms or automated system alerts.
- Set a migration window and notify users in advance.
If you manage hosting through a panel like Plesk, review how mail is currently configured for the domain. Some domains use local mail hosting, while others route mail externally. Knowing this in advance helps prevent duplicate delivery rules or unexpected mailbox creation on the wrong server.
Choose the right migration method
The best method depends on how many accounts you need to move and how much email history must be preserved. For a small team, manual migration may be enough. For a larger business, a staged IMAP migration is usually safer because it copies messages without changing the user experience too much.
Common migration options
- IMAP sync: Copies folders and messages from the old server to the new one while keeping mailbox structure intact.
- Manual export/import: Useful for a few mailboxes, but more time-consuming and prone to missed folders.
- POP3-based migration: Less ideal for preserving server-side folders, because POP3 usually downloads mail into a client rather than mirroring the mailbox.
- Hosted-to-hosted transfer tools: Some hosts and control panels provide migration assistants that automate part of the process.
For most business email moves, IMAP is the preferred option because it copies folders, sent items, archives, and other server-stored data. If your old provider only supports POP3, you may need to export mail from the email client first or use a third-party migration utility.
Step 1: Set up the new mailboxes first
Create all required mailboxes on the new host before moving any data. This includes standard accounts such as sales@, support@, and info@, as well as personal staff mailboxes. Make sure mailbox names, passwords, quotas, and aliases match the intended setup.
If you are using Plesk or a similar hosting control panel, this is usually done from the domain’s mail settings. Set the correct mailbox size according to the expected usage. Users who work with large attachments or long retention periods may need more storage than a basic inbox.
Do not forget these details
- Email aliases and forwarding addresses
- Autoresponders and out-of-office replies
- Catch-all addresses if they are used intentionally
- Mailbox permissions for shared access
- Mobile device access and app passwords if applicable
It is also a good time to create the DNS zone on the new host if DNS management will move with the email service. Having the zone ready means you can update records quickly once the migration is complete.
Step 2: Copy existing email to the new host
Once the new mailboxes are ready, start copying messages from the old host. For IMAP migration, point your migration tool or mail client at both servers and sync each mailbox one by one. This process copies folders and email content while leaving the original mailbox unchanged.
During this stage, users can usually continue working as normal. Any new messages arriving on the old server before the final DNS switch will remain there, so you should plan a second sync later to catch recent mail.
Best practices during data transfer
- Start with the largest mailboxes first so you can estimate total transfer time.
- Test one mailbox before migrating all accounts.
- Check whether special folders such as Sent, Drafts, Trash, and Archive are copied correctly.
- Verify that message dates and folder hierarchy remain intact.
- Keep an eye on server limits, connection timeouts, and authentication errors.
If you see missing folders after the transfer, it may be because the email client or migration tool is hiding non-subscribed IMAP folders. Resyncing the mailbox or changing folder subscription settings often resolves this.
Step 3: Update DNS records at the right time
DNS changes decide where new incoming mail goes. The most important record is the MX record, which tells the internet which server accepts email for your domain. When you are ready to switch, update the MX record to point to the new host.
Before doing that, lower the TTL of your existing records if possible. A shorter TTL can help DNS updates propagate faster. This does not guarantee instant change everywhere, but it reduces the time users may receive mail on the old system after the switch.
Records to review during the switch
- MX: Directs incoming mail to the correct server.
- SPF: Authorises approved mail servers to send on behalf of the domain.
- DKIM: Adds a digital signature to outbound mail.
- DMARC: Defines policy and reporting for authentication failures.
- A or CNAME records: Needed if webmail or mail hostnames change.
After the MX record is updated, some senders may still reach the old server for a short period due to caching. That is why keeping both systems active temporarily is essential. This overlap reduces the risk of bounced or misplaced messages.
Step 4: Keep mail flowing during the transition
A common mistake is turning off the old mailbox too soon. Even after DNS is updated, the old host may still receive mail for a while. To avoid loss, keep the old account active and continue checking it until traffic has fully moved over.
In a managed hosting environment, you can also configure forwarding from the old server to the new one during the transition. This adds another safety layer, especially when external senders have cached the old MX record.
Practical transition approach
- Perform the initial IMAP sync.
- Update MX records to the new host.
- Keep the old mailboxes active for at least several days.
- Run a final sync to capture late-arriving messages.
- Ask users to update email clients if server settings change.
For organisations with contact forms, newsletter tools, or system alerts, also check the SMTP configuration of each application. These services often continue sending through the old provider unless you update the outbound relay settings.
Step 5: Reconfigure email clients and mobile devices
After the migration, users may need to update their mailbox settings in Outlook, Apple Mail, Thunderbird, or mobile devices. If the new host uses the same domain name for both incoming and outgoing mail servers, the user experience can stay almost unchanged. If server hostnames differ, each client will need the new IMAP, SMTP, or webmail settings.
Settings users should confirm
- Username, usually the full email address
- Password for the new mailbox
- Incoming server name and port
- Outgoing SMTP server name and port
- Encryption type such as SSL/TLS or STARTTLS
If the account was set up as POP3 on the old host, this is a good opportunity to move to IMAP. IMAP keeps mail on the server and synchronises folders across devices, which is better suited to modern business use.
Step 6: Test deliverability after the move
After the new host is live, send test messages to and from several external providers. Test both personal and business-to-business delivery, because filtering behaviour can vary. Make sure replies are received, sent mail appears in the Sent folder, and messages are not landing in spam.
Check the email headers if you suspect a delivery issue. Headers can show whether SPF, DKIM, and DMARC passed, which server handled the message, and where delays occurred. This is especially useful if a new host is configured correctly but the domain authentication records still point to the previous setup.
Deliverability checks
- Send from the new mailbox to Gmail, Outlook, Yahoo, and another business account.
- Reply to each test message and verify receipt.
- Confirm that outbound mail is signed with DKIM.
- Check whether SPF includes the new sending server.
- Review DMARC reports if you use them.
Common problems when moving business email
Even when the migration is planned carefully, a few issues are common. Most are related to DNS timing, authentication, or folder sync rather than a failure of the new host itself.
Messages still arrive on the old server
This is usually caused by DNS propagation or cached MX records. Keep the old mailbox active and continue monitoring it until traffic settles. If needed, create forwarding rules from old to new during the overlap period.
Some folders are missing
This often happens when the migration tool did not subscribe to every IMAP folder or the old client stored messages locally. Re-run the sync and check folder visibility in the email client.
Outgoing mail goes to spam
Verify SPF, DKIM, and DMARC on the new host. If you switched providers but left the old sending servers in the SPF record, the policy may be incomplete. Also confirm that the sending IP has a good reputation and the domain identity is consistent.
Email clients show authentication errors
Update passwords, server names, ports, and encryption settings. If a control panel like Plesk is managing the mailbox, confirm that the mailbox exists and that login credentials match the account settings in the client.
Website forms stop sending mail
Update the website’s SMTP settings to use the new mail host. Avoid relying on default PHP mail delivery if authenticated SMTP is available, because authenticated sending is usually more reliable and easier to troubleshoot.
How Plesk and hosting control panels can help
When email is managed through a control panel, the migration becomes easier to track. You can create mailboxes, aliases, autoresponders, and forwarding rules from one interface. In Plesk, for example, the domain mail section can help you confirm which accounts exist and whether local mail handling is enabled.
Control panels also make it simpler to compare old and new configurations. That is useful when you need to match mailbox names, recreate forwarding, or check the mail routing mode for a domain. For teams moving multiple addresses at once, this consistency saves time and reduces mistakes.
Useful control panel tasks during migration
- Verify mail-enabled domains and mailbox lists.
- Check mail routing settings before and after DNS updates.
- Reset passwords for end users in a controlled way.
- Recreate aliases and forwarding addresses quickly.
- Monitor whether local or remote delivery is active.
Recommended migration timeline
A staged timeline helps avoid surprises. For a small business, the full process may take only a few hours. For a larger organisation, plan for a few days so that you can test, sync, switch, and monitor properly.
Example schedule
- Day 1: Audit accounts, DNS, and mailbox sizes.
- Day 2: Create mailboxes on the new host and start the first sync.
- Day 3: Update MX records and monitor traffic.
- Day 4: Run final sync and reconfigure users.
- Day 5: Check deliverability and retire the old service only when safe.
This approach is especially helpful if the domain also powers a website, contact form, or booking system. Email and web services often depend on each other, so it is best to change them in a controlled order.
FAQ
Will business email stop working during the move?
It should not, if you keep the old and new systems active during the transition. The main risk comes from shutting down the old mailbox too early or updating DNS before the new account is ready.
Do I need to move my website to change email host?
No. Email hosting and website hosting can be separate. You can move mail to a new host while leaving the website on the current server, as long as DNS records are updated correctly.
Is IMAP better than POP3 for migration?
Yes, in most cases. IMAP preserves folders and keeps mail synchronised across devices, which makes migration easier and reduces the chance of missing data.
How long does DNS propagation take?
It depends on TTL values and external caching, so changes can appear in minutes for some users and take longer for others. That is why keeping the old server available for a few days is recommended.
What should I do if old emails do not appear in the new inbox?
Check whether the mailbox was fully synced, whether all folders were included, and whether the email client is using the right IMAP subscription settings. If the old account used POP3, some messages may only exist locally on a device.
Can I migrate shared mailboxes and aliases too?
Yes. These should be recreated on the new host as part of the preparation stage. Aliases, forwards, and shared addresses are often just as important as user mailboxes.
Final checks before closing the old host
Do not cancel the old email service until you have confirmed that new mail is arriving on the new host, all users can sign in, and recent messages have been copied. Review any old forwarding rules, website SMTP settings, and external tools that send mail on behalf of the domain.
When everything is stable, keep a backup of the old mailbox data for a short period if your retention policy allows it. This gives you a fallback option if a late issue appears after the migration.
A careful business email migration is mostly about sequencing: prepare first, copy data, switch DNS, verify deliverability, and only then retire the old service. With the right process, moving email to a new host can be completed with little disruption and without losing important messages.