Moving email to a new mailbox, hosting account, or control panel can be done safely if you plan the transfer in the right order. The main goal is to keep both the old and new mailboxes active long enough to copy all existing messages, receive any mail that arrives during the move, and then switch users over only after the final sync is complete. This approach works well for business mail, whether the mailbox is managed in Plesk, another hosting control panel, or an external email service.
If you migrate email too quickly, the most common problem is missing messages. That usually happens when DNS is changed before all mail is copied, when the old mailbox is closed too early, or when people continue sending to the old address during the transition. A careful migration process avoids these issues and keeps business communication intact.
Why email migration can lose messages
Email is often delivered over more than one system during a migration period. Some messages may still arrive at the old server while others go to the new one, depending on DNS propagation, MX records, and sender cache. If the old mailbox is deleted or stops accepting mail before the final sync, those messages may be lost.
Common reasons for missing mail during migration include:
- Changing MX records before copying all existing mailbox content.
- Stopping the old mail service too early.
- Not performing a final sync after the DNS change.
- Using POP3 instead of IMAP during the move.
- Mailbox quota limits on the new server causing sync failures.
- Rules, filters, or forwarding settings on the old account interfering with delivery.
- Temporary delivery delays while DNS changes are spreading across the internet.
For business email, the safest method is usually IMAP-to-IMAP migration, with both mailboxes online until the transition is finished.
Best migration method for keeping all messages
When possible, migrate email by copying the full mailbox contents from the old IMAP account to the new IMAP account. IMAP stores messages on the server, so it is the most reliable way to preserve folders, read/unread status, and sent items.
Recommended approach
- Prepare the new mailbox first.
- Lower the DNS TTL before the switch, if you control DNS.
- Copy all existing mail from the old account to the new account.
- Keep the old mailbox active during DNS propagation.
- Run a final sync to catch newly received messages.
- Update users’ mail clients and confirm delivery.
If the mailbox is managed in a hosting control panel such as Plesk, you can usually create the destination mailbox first, verify storage limits, and then migrate content with an email client or a server-side migration tool.
Before you start: migration checklist
Good preparation prevents data loss and reduces downtime. Before moving the mailbox, check the following items.
- Mailbox size: Make sure the new account has enough space for all messages and attachments.
- Access details: Confirm IMAP/SMTP settings, usernames, passwords, and ports for both old and new accounts.
- MX records: Identify where inbound mail is currently delivered.
- DNS TTL: Lower TTL values a day before migration if possible to speed up DNS changes.
- Folder structure: Check whether Sent, Archive, Junk, and custom folders need to be preserved.
- Mail client settings: Note any rules, signatures, and forwarding settings that need to be recreated.
- Backup: Create a backup of the old mailbox if your platform supports it.
It is also useful to test login to both accounts from a desktop mail client before starting the transfer. This confirms that IMAP access works and helps you catch authentication problems early.
How to migrate email without losing messages
Step 1: Create the destination mailbox
Set up the new mailbox before making any DNS changes. Use the same address if you are moving the mailbox to a new host, or create the new destination address if the domain is changing mail platforms. Make sure the mailbox quota is large enough and that the account can receive mail immediately.
If you are working in a hosting control panel, verify:
- Mailbox name and domain are correct.
- Password is strong and saved securely.
- IMAP access is enabled.
- Spam filtering and antivirus settings are active.
Step 2: Copy existing messages from the old mailbox
Use an email client such as Outlook, Apple Mail, Thunderbird, or another IMAP-capable client to connect to both the old and new mailboxes. Then drag and copy folders from the source account to the destination account. For large mailboxes, server-side tools or migration plugins are often faster and more reliable.
Important points during the initial copy:
- Copy all folders, not only Inbox.
- Include Sent, Drafts, Archive, and custom folders.
- Wait for the client to finish syncing before disconnecting.
- Check for errors related to quotas, authentication, or timeouts.
If the mailbox contains thousands of messages, migrate in batches. This reduces the chance of interruption and makes it easier to confirm progress.
Step 3: Switch DNS only after the first sync is complete
Once the bulk of the mailbox has been copied, update the MX records so that new incoming email is delivered to the new server. Do not remove the old server from service yet. During DNS propagation, some senders will still reach the old mailbox.
To reduce the risk of missing mail:
- Keep the old mailbox active for at least 48 hours, and longer if possible.
- Leave forwarding in place temporarily, if your setup supports it.
- Monitor both mailboxes during the transition.
If you manage DNS in a control panel, confirm that the MX record priority is correct and that the domain’s mail routing points to the new destination.
Step 4: Run a final sync
After DNS changes have had time to spread, perform a final synchronisation. This catches emails that arrived at the old mailbox during the transition window. The final sync is one of the most important steps in preventing message loss.
Check these folders again:
- Inbox
- Sent
- Archive
- Trash, if it contains items that should be retained
- Custom folders created by the user or business application
If you are using a mail client, re-open the source and destination accounts and make sure the copy operation has completed successfully. For server-side migration, re-run the migration job or incremental sync if available.
Step 5: Verify delivery and authentication
After the migration, send test messages from an external address to confirm inbound delivery. Also send a reply from the new mailbox to verify outbound SMTP is working correctly. This is particularly important if the new hosting platform uses a different mail server name, SPF record, DKIM signature, or SMTP port configuration.
Test the following:
- Receiving mail from Gmail, Outlook, and another external provider.
- Sending mail to external recipients.
- Folder synchronisation in desktop and mobile clients.
- Access via webmail.
- Spam folder placement and deliverability.
How to avoid message loss during DNS propagation
DNS propagation is the period when different mail systems may still use old cached records. This can create a split-delivery situation, where some messages go to the old mailbox and others go to the new one.
To avoid losing mail during this stage:
- Lower MX record TTL before the migration.
- Keep both mailboxes live during the transition.
- Check the old mailbox frequently for missed messages.
- Use forwarding from the old mailbox to the new one, if available.
- Do not delete the old account until you are sure all mail has been received.
Remember that TTL changes do not update instantly everywhere. Some providers cache DNS information longer than expected, so a cautious overlap period is still needed.
Using Plesk or another hosting control panel for migration
In a managed hosting environment, email migration is often simpler because mailbox settings, quotas, and DNS records can be controlled from one interface. In Plesk, for example, you can create the new mailbox, check mail routing, and configure forwarding or antivirus settings in the same panel.
Typical control panel tasks during email migration include:
- Creating the destination mailbox.
- Adjusting mailbox size limits.
- Updating MX records or mail routing.
- Checking spam filtering and anti-malware features.
- Managing SPF, DKIM, and DMARC alignment.
- Reviewing logs if mail delivery fails.
If the platform provides an email migration utility, use it when possible. These tools often preserve folder structure better than manual copy methods and can be rerun for incremental updates.
What to do if messages are missing after migration
If users report missing email after the move, the problem is usually recoverable if the old mailbox has not been deleted. Start by checking whether the message was delivered to the old server during the DNS transition.
Troubleshooting steps
- Check the old mailbox Inbox, Spam, Sent, and custom folders.
- Review MX records to confirm where new mail should be delivered.
- Verify whether forwarding or catch-all settings were active.
- Look at mail logs on the old and new server, if available.
- Check whether the new mailbox quota was exceeded.
- Confirm that mail clients are connected to the new IMAP account, not an outdated POP3 profile.
If the missing message was still on the old server, copy it manually to the new mailbox and continue monitoring for a short overlap period. If the message never reached either server, ask the sender for a resend and check for SPF or DNS issues that may have caused rejection.
Common mistakes to avoid
- Using POP3 for migration: POP3 downloads and removes messages from the server, which increases the risk of loss.
- Deleting the old mailbox too soon: This can permanently remove late-arriving mail.
- Skipping the final sync: New messages often arrive during DNS propagation.
- Ignoring Sent mail and custom folders: Business users often need more than just Inbox data.
- Not testing outbound mail: Delivery problems may appear after migration, not during it.
- Forgetting aliases and forwarding: These can affect where messages are routed.
How long should you keep the old mailbox?
As a rule, keep the old mailbox active long enough to cover DNS propagation and any delayed mail delivery. For many business migrations, 48 to 72 hours is a practical minimum, but longer is safer for high-value mailboxes or organisations with global senders.
For critical accounts, it is sensible to keep the old mailbox read-only for a short period after the switch. That gives you a fallback location for late mail without allowing day-to-day use of the old account to continue indefinitely.
FAQ
Can I migrate email without downtime?
Yes, if you keep the old mailbox active while copying data to the new mailbox and only switch MX records after the first sync is finished. A short overlap period is the best way to reduce disruption.
Is IMAP better than POP3 for email migration?
Yes. IMAP is better because messages stay on the server and can be synchronised between the old and new mailbox. POP3 is less suitable because it downloads messages locally and can miss server-side folders.
Will changing MX records move old messages too?
No. MX records only control where new incoming mail is delivered. Existing messages must be copied separately from the old mailbox to the new one.
What if my mailbox is too large to copy in one go?
Use batch migration, server-side transfer tools, or incremental sync. You can also reduce mailbox size by archiving old mail before the move, as long as the archive is also transferred or backed up.
Do I need to update SPF and DKIM after migration?
Usually yes, if the sending server changes. SPF, DKIM, and DMARC should match the new mail platform so outbound mail is authenticated correctly and less likely to be flagged as spam.
Can forwarding alone protect against lost mail?
Forwarding can help during a transition, but it should not be the only protection. Keep both mailboxes active and run a final sync, because forwarding may fail for some messages or introduce delays.
How do I know the migration is complete?
The migration is complete when all mailbox folders have been copied, test messages are arriving at the new mailbox, outgoing mail is working, and no new mail is appearing in the old mailbox after the overlap period.
Final checks before closing the old account
Before you deactivate the old mailbox, complete one last review:
- Confirm that no new messages have arrived in the old mailbox for at least one full propagation window.
- Verify that the new mailbox contains all expected folders and recent messages.
- Check that all users have updated their mail clients and mobile devices.
- Make sure aliases, forwarding, and catch-all settings are correct.
- Keep a backup of the old mailbox if your policy allows it.
If any doubt remains, keep the old mailbox available a little longer. In email migration, a short delay is much safer than losing business correspondence.
Conclusion
The safest way to migrate email without losing messages is to use IMAP, prepare the new mailbox first, keep both mailboxes active during DNS propagation, and complete a final sync before shutting down the old account. In a hosting or control panel environment, this process is easier when mailbox quotas, DNS records, and mail routing are checked in advance. With careful timing and verification, you can move business email cleanly and preserve every important message.