If you need to move email accounts from another provider to a hosting platform, the safest approach is to migrate in stages: prepare the new mailbox, copy the existing messages, verify folders and settings, then switch DNS records only after you have confirmed that mail is working on the new service. This reduces downtime and lowers the risk of lost messages, duplicate delivery, or sync problems after the move.
This guide explains how to migrate email accounts from another provider in a hosting environment, including common mailbox types, DNS changes, and what to check in a control panel such as Plesk. It is written for business email users who want to preserve existing messages, folders, and access across desktop and mobile devices.
What you need before starting the migration
Before you copy anything, collect the details for both the old and the new email service. A successful email migration depends on having the right credentials, access method, and DNS information.
Check the current mailbox setup
Identify the type of mailbox you are moving:
- IMAP mailbox — messages are stored on the server and can usually be synchronized to a new provider.
- POP3 mailbox — messages may be stored locally on a device, which can make migration more difficult.
- Microsoft 365 or Exchange — may require a different migration method or third-party tool.
- Webmail-only account — often still IMAP-based, but confirm access details first.
If you are not sure which type you use, check the account settings in your mail client or ask the previous provider.
Gather the required information
For each mailbox, prepare the following:
- Email address and password
- Incoming mail server name
- Incoming port and encryption type
- Outgoing mail server name
- Outgoing port and encryption type
- Mailbox quota or storage limit
- List of aliases, forwarding rules, and catch-all settings
- Any existing filters or server-side rules
Also make sure you have administrator access to the new hosting control panel, such as Plesk, cPanel, or the hosting platform’s mail management area.
Choose the right migration method
The best migration method depends on the source provider, the number of mailboxes, and whether you need to preserve folders and sent mail.
Manual IMAP migration
This is the most common option when moving between standard hosting providers. You connect both mailboxes in a mail client such as Outlook, Thunderbird, or Apple Mail and drag or copy messages from the old account to the new one. Because IMAP syncs with the server, the messages are uploaded to the destination mailbox.
This method works well for small to medium migrations and gives you more control over what is copied.
Server-side migration tool
Some hosting platforms provide migration tools in the control panel. In Plesk, for example, migration extensions or mail import features may help copy mailboxes, domains, and related settings from another server. These tools are useful when migrating multiple accounts and when you want to reduce manual work.
Always review what the tool can and cannot move. Some tools transfer only mail content, while others also copy aliases, forwarding, and mailbox quotas.
Third-party migration service
For complex moves, such as Exchange to IMAP or large business email systems, a dedicated migration service may be a better choice. These services can preserve folder structure, handle large volumes of data, and automate retries if the source server is slow or rate-limited.
Set up the new mailbox first
Always create the destination mailbox before starting the transfer. This makes it easier to test access and prevents delivery gaps when the DNS records change.
Create the mailbox in the hosting control panel
In the hosting platform or Plesk mail section, create each mailbox with the required address and a strong password. Set the quota according to expected usage, and confirm that the mailbox is active.
If the domain is already hosted on the platform, also verify that:
- Mail service is enabled for the domain
- The correct MX records are in place or ready to be updated
- SMTP, IMAP, and webmail access are available
Test the new account before copying data
Log in to webmail or configure the account in your mail client. Send a test message to and from the new mailbox. This confirms that authentication, encryption, and delivery work correctly before you move the existing mail.
How to migrate email accounts using IMAP
IMAP migration is usually the easiest way to move email from one provider to another while keeping folders and message history. The basic idea is to connect both accounts in the same mail client and copy messages between them.
Step 1: Add the old and new accounts to a mail client
Configure both accounts in your mail application using IMAP. Keep the old account connected until the migration is complete.
Make sure the client is set to:
- Synchronize all folders, not only Inbox
- Show sent items, drafts, and archives
- Download headers and content for older messages if needed
Step 2: Copy folders in batches
Copy one folder at a time, starting with smaller folders. If the mailbox is large, move messages in batches instead of all at once. This lowers the risk of timeouts and synchronization errors.
Recommended order:
- Inbox
- Sent
- Drafts
- Archive folders
- Custom folders
- Trash or deleted items, if needed
After each batch, allow the client to finish synchronization before continuing.
Step 3: Verify folder structure
Some providers use different folder names for sent mail, drafts, and trash. After the copy, check that all folders appear correctly in the destination mailbox and that messages are not missing from subfolders.
If folder names are duplicated or nested incorrectly, you may need to rename or remap them in the mail client.
Step 4: Check dates, attachments, and message counts
Compare the number of messages in important folders and confirm that older mail, attachments, and inline images transferred correctly. For business mailboxes, make sure invoice threads, client communication, and archived correspondence are intact.
Migrating from POP3 accounts
POP3 migration is often more difficult because messages may have been downloaded to one or more devices and removed from the old server. If the old account was used with POP3 and “leave a copy on server” was not enabled, some messages may exist only on local computers or phones.
What to check first
- Search old computers for local mail archives
- Check whether Outlook PST files or Apple Mail archives exist
- Export messages from each device before changing accounts
- Look for backups made by the previous provider or backup software
If the mailbox still has messages on the old server, you can import them into the new IMAP mailbox using a mail client or migration tool. If not, local archives may be the only source of older mail.
DNS changes after the migration
Email delivery depends on DNS. Moving mailboxes without updating DNS correctly can cause messages to go to the old provider or bounce back.
Update MX records
Change the domain’s MX records to point to the new email service once you are ready to receive mail there. In a managed hosting environment, this is usually done in the DNS zone editor or through the domain settings in the control panel.
Before switching MX records, confirm that:
- The new mailbox is active and tested
- The domain’s mail routing is set to local or remote correctly
- The destination server can accept mail for the domain
Review SPF, DKIM, and DMARC
These DNS records help email providers verify that your messages are legitimate. After migration, update them to match the new sending environment.
- SPF should include the new mail server or sending service
- DKIM should be enabled and published for the domain
- DMARC should be checked to make sure it still aligns with your sending setup
If you skip this step, sent emails may land in spam or fail authentication checks.
Allow time for DNS propagation
DNS changes do not always take effect immediately. Depending on the previous TTL values and resolver caches, some mail may still be delivered to the old provider for a short period. Keep the old mailbox active during the transition so you do not miss incoming messages.
How to avoid losing email during the switch
The safest migration is one where both old and new accounts stay active long enough to catch delayed mail and replies sent to the previous system.
Keep the old account running temporarily
Do not cancel the old service immediately. Leave it active for at least several days, and longer if the mailbox is busy or DNS propagation is slow. This gives you time to:
- Receive delayed mail
- Forward replies from the old account if needed
- Check for forgotten aliases or contact forms
Set up forwarding if appropriate
During the transition, you can forward mail from the old address to the new mailbox. This is useful when contacts may still use the previous address. Just make sure forwarding is not creating loops or duplicate deliveries.
Change account settings on all devices
Once the new mailbox is ready, update email clients on laptops, phones, tablets, and shared devices. Use the new server settings and test sending and receiving from each device.
Migration checklist for hosting platforms
Use this practical checklist to reduce mistakes during the move:
- Create the destination mailbox in the hosting control panel
- Confirm storage quota and password policy
- Verify IMAP, SMTP, and webmail access
- Copy messages and folders from the old provider
- Check sent mail, drafts, and custom folders
- Update MX records after testing the new mailbox
- Review SPF, DKIM, and DMARC records
- Update mail clients and mobile devices
- Keep the old account active during the transition
- Confirm that no messages are missing after DNS propagation
Common problems after migration
Even when the transfer appears complete, a few issues can show up afterward. Most of them are caused by DNS, folder mapping, or account settings.
Messages still arrive at the old provider
This usually means MX records have not fully propagated or some DNS resolvers still use cached information. Double-check the MX records and wait for propagation. Keep the old mailbox available until the flow of mail stabilizes.
Cannot send mail from the new mailbox
Outgoing problems often come from incorrect SMTP settings, a blocked port, or missing authentication. Verify that the mail client uses the correct username, password, encryption method, and port number. Also check whether the hosting platform requires authenticated SMTP submission.
Missing folders or sent items
If folders were not copied correctly, the mail client may have used different folder names or skipped special folders. Reconnect the accounts and confirm that the client is set to synchronize all folders. In some cases, you may need to copy the Sent folder separately.
Authentication failures or spam issues
When SPF, DKIM, and DMARC are not updated, sending reputation can suffer. Make sure the domain’s DNS records match the new mail server and that the mail service is authorized to send on behalf of the domain.
Mailbox quota exceeded
If the new mailbox has a smaller quota than the old one, the copy may stop before all messages are transferred. Increase the mailbox size or clean up unnecessary mail before retrying.
Migrating email in Plesk
If your hosting platform uses Plesk, the mail migration process is often managed through the control panel or a migration extension. The exact steps depend on your hosting setup, but the general workflow is similar.
Typical Plesk migration workflow
- Confirm that the domain is added to Plesk
- Create mailboxes under the domain
- Import or migrate messages from the old server
- Check mailbox permissions and quotas
- Update DNS records for mail delivery
- Test webmail and client access
If the migration tool supports it, import aliases and forwarding rules as well. If not, recreate them manually after the mail content has been moved.
Best practices for business email migration
For business use, email migration should be planned carefully to avoid interruptions in customer communication and internal workflows.
- Migrate outside peak business hours when possible
- Communicate the cutover date to staff
- Use a shared checklist for all mailboxes
- Test each important address before updating DNS
- Document the old and new server settings
- Keep backups of exported mail archives
If several people use the same domain, also verify shared mailboxes, aliases, and role-based addresses such as info@, sales@, and support@.
FAQ
Can I migrate email without losing old messages?
Yes, if the old mailbox still supports IMAP access or you have local archives. Copying mail through IMAP is the most reliable way to preserve folders and message history.
Do I need to change MX records immediately?
No. It is better to create and test the new mailbox first, then switch MX records when you are ready. Keep the old mailbox active during the transition.
Will aliases and forwarding rules migrate automatically?
Not always. Some tools transfer only mailbox contents. Aliases, forwarding rules, and filters may need to be recreated manually in the new hosting control panel.
What if my old provider only offers POP3?
Check whether messages exist in local mail archives on your devices. If the old server still has mail, you can usually import it into the new IMAP mailbox. If not, the local archive may be the only source.
How long should I keep the old mailbox active?
Keep it active until you are sure that all incoming mail reaches the new provider and all devices have been updated. For busy domains, a few days may be enough, but longer is often safer.
Why do sent emails go to spam after migration?
This often happens when SPF, DKIM, or DMARC records do not match the new sending setup. Review the DNS records and confirm that the new mail server is properly authorized.
Final checks before closing the old account
Before you decommission the old provider, do one last review. Confirm that:
- All important messages were copied
- New mail is arriving at the destination
- Users can send mail from the new account
- DNS records point to the correct mail service
- Aliases and forwarding are in place
- Backups or exports have been saved
After these checks, you can safely close the old service or leave only the necessary forwarding in place. A careful migration protects business continuity and helps ensure that your new hosting email setup works correctly from day one.