Moving from POP3 or IMAP to Microsoft Exchange Online for Professional Business Email
Summary
This guide helps you troubleshoot and resolve: Moving from POP3 or IMAP to Microsoft Exchange Online for Professional Business Email. Follow the steps below to fix the issue.
Common Causes
Moving from legacy POP3 or IMAP email to Microsoft Exchange Online transforms how your organisation communicates. Unlike older protocols that store messages locally on a single device or download them without synchronising, Exchange Online keeps your email, calendars, and contacts in the cloud. This allows every device to stay in sync and enables professional features such as shared mailboxes for accounts@ and sales@ addresses, shared calendars, and enterprise-grade authentication. It also improves deliverability, reducing the risk of your internal emails landing in client junk folders.
Why Upgrade from POP3 or IMAP?
POP3 and IMAP were designed for an era when most people checked email from one computer. They do not support true collaboration or modern security standards. Exchange Online provides:
- Real-time synchronisation across desktop, mobile, and web
- Shared mailboxes without requiring individual licences for every alias
- Delegated access so assistants or managers can send on behalf of a shared address
- Shared calendars and contact lists for better team coordination
- Enterprise-grade spam filtering and authentication to protect your sender reputation
- Support for multi-factor authentication (MFA) and modern authentication
Quick Fix Steps
- Purchase the appropriate Microsoft 365 Business licence for each user.
- Verify your domain ownership in the Microsoft 365 admin centre.
- Create user mailboxes and shared mailboxes such as accounts@ and sales@.
- Migrate existing email data while your old MX record still points to the legacy server.
- Update DNS records, including MX, SPF, DKIM, and DMARC, during a planned maintenance window.
- Configure Outlook profiles and mobile devices to connect to Exchange Online.
- Export and back up local PST or OST files before decommissioning the old POP3 or IMAP service.
Detailed Instructions
Step 1: Purchase Licences and Verify Your Domain
- Sign in to the Microsoft 365 admin centre.
- Purchase the appropriate Microsoft 365 Business licence for each staff member who requires a mailbox.
- Navigate to Settings > Domains.
- Select Add domain and enter your business domain name.
- Follow the prompts to add a TXT or MX record to your DNS host to prove ownership.
- Return to the admin centre and select Verify.
Step 2: Create User Mailboxes and Shared Mailboxes
- Go to Users > Active users in the Microsoft 365 admin centre.
- Select Add a user and assign a licence to each staff member.
- To create a shared mailbox, go to Teams & groups > Shared mailboxes.
- Select Add a shared mailbox and enter the address, such as sales@yourdomain.com.au.
- Add members who need access and assign permissions such as Send as or Send on behalf.
Step 3: Migrate Email Data
The migration method depends on whether your current service uses IMAP or POP3. Do not update your MX record yet; keep it pointing to your legacy server so new email continues to arrive during the migration.
For IMAP Accounts
- Sign in to the Exchange admin centre.
- Navigate to Migration > New migration.
- Choose IMAP migration.
- Enter the connection details for your existing mail server, including the IMAP server address, port, and encryption method.
- Map source mailboxes to the new Exchange Online mailboxes.
- Start the migration and monitor progress in the migration dashboard.
For POP3 Accounts
POP3 does not support server-side migration of existing email through the Exchange admin centre IMAP migration tool. Existing mail stored locally must be handled manually:
- Open the legacy email client (such as Outlook, Thunderbird, or Apple Mail) configured with the POP3 account.
- Export the mailbox data to a Personal Storage Table file (
.pst) or archive format. - Save the
.pstfile to a secure location. - Use the Import/Export feature in Outlook or a third-party migration tool to import the
.pstdata into the corresponding Exchange Online mailbox. - Alternatively, engage a third-party migration provider to perform a direct POP3-to-Exchange migration.
Step 4: Update DNS Records During Cutover
Schedule this change during a planned maintenance window outside of business hours. Notify all staff and clients before proceeding, as email delivery will be briefly interrupted while DNS changes propagate.
- In the Microsoft 365 admin centre, go to Settings > Domains > select your domain.
- Review the required DNS records provided by Microsoft.
- Update your MX record to point to Microsoft Exchange Online.
- Add or update the SPF record to authorise Microsoft as a sender for your domain.
- Add the DKIM records to digitally sign outgoing email.
- Add a DMARC record to tell receiving servers how to handle unauthenticated mail.
Step 5: Configure Outlook and Mobile Devices
- Install Microsoft Outlook from the Microsoft 365 portal or app store.
- Open Outlook and enter the user's full email address and password.
- Outlook will automatically detect Exchange Online settings using Autodiscover.
- When prompted, enable multi-factor authentication (MFA) if it is required by your organisation's security policy.
- On iOS, open the Outlook app or Mail app and add an Exchange account using modern authentication.
- On Android, use the Outlook app for the best calendar and contact synchronisation.
Step 6: Export Local Data and Remove Old Profiles
Before decommissioning the old POP3 or IMAP service, ensure no data remains only on the local computer.
- Open the legacy email client and export any remaining local folders to a
.pstor.ostbackup file. - Store the backup file on a secure network drive or cloud storage location.
- Confirm that all folders, emails, calendars, and contacts are visible in the new Exchange Online mailbox.
- Remove the old POP3 or IMAP account profile from Outlook and mobile devices.
Step 7: Email Signatures and Shared Calendars
Microsoft 365 does not include a native server-side signature designer under Mail flow. Centralised signatures require Exchange transport rules or a third-party signature management tool. As an alternative, users can create signatures directly in Outlook.
- Open Outlook and go to File > Options > Mail > Signatures.
- Select New and create a signature for new messages and replies.
- For shared calendars, open Outlook, right-click the Calendar folder, and select Sharing Permissions.
- Add colleagues and assign appropriate access levels.
Troubleshooting
Migration Batch Fails or Stalls
- Check the migration dashboard in the Exchange admin centre for specific error codes.
- Verify that the source mail server credentials are correct and that the account has access to all mailboxes.
- Ensure the legacy server allows IMAP connections from Microsoft 365 IP ranges.
- Restart the migration batch or create a new batch for failed mailboxes.
Duplicate Items After Migration
- Avoid running the same migration batch multiple times without removing completed mailboxes.
- Use Outlook's Clean Up tool to remove redundant messages from conversation threads.
- If duplicates are widespread, consider exporting affected mailbox data and re-importing after clearing the destination mailbox.
Migration Throttling
- If migration slows significantly, reduce the number of concurrent mailboxes in the batch.
- Throttling may be applied by the legacy mail server or by Exchange Online. Wait and resume the batch later.
- Check the migration logs for throttling warnings and adjust the schedule accordingly.
Emails Landing in Junk Folders
- Confirm that SPF, DKIM, and DMARC records are correctly published in your DNS.
- Use the Microsoft Remote Connectivity Analyser to test inbound and outbound mail flow.
- Check the Message trace tool in the Exchange admin centre for delivery status.
Shared Mailbox Not Appearing in Outlook
- Ensure the user has been granted Full Access permissions to the shared mailbox.
- Restart Outlook to refresh folder synchronisation.
- Check that the shared mailbox has an active licence if it exceeds 50 GB.
Calendar Not Syncing Across Devices
- Confirm the device is using an Exchange account, not a legacy IMAP profile.
- Remove and re-add the account on the affected device.
- Verify that calendar sharing permissions are correctly configured in Outlook on the web.
If you encounter issues during your migration or need assistance configuring shared mailboxes and DNS records, Open a Ticket with our Brisbane support team.
Still Having Issues?
💻 Open a Ticket