IMAP to Office 365 Shared Mailbox Migration
Migrating emails from an IMAP server to Office 365 Shared Mailboxes is a common requirement for organizations looking to streamline communication and strengthen team collaboration. While IMAP provides standard email access across multiple devices, it does not offer the advanced collaboration capabilities or administrative control available with Office 365 Shared Mailboxes. Shared Mailboxes allow multiple users to access and manage one mailbox, making them well suited for business addresses such as support, sales, or info@ email addresses within a business environment.
EdbMails provides a specialized IMAP Migration Tool designed to make the entire migration process simple and efficient. It supports multiple IMAP-enabled email services including Gmail, Outlook, Yahoo, Zimbra, and more, enabling direct migration of emails to Office 365 Shared Mailboxes. During migration, the tool preserves the original folder hierarchy, email metadata, and attachments, and also includes advanced filter options to move only the required data. With a user-friendly interface, even non-technical users can complete the migration smoothly while maintaining complete data security and accuracy throughout the process.

The following section covers migration planning, prerequisites, step-by-step procedure, post-migration activities, and the benefits of using EdbMails for IMAP to Office 365 Shared Mailbox migration.
Why Migrate IMAP to Office 365 Shared Mailboxes
- Centralized Team Communication: EdbMails migrate IMAP mailboxes to Office 365 shared mailboxes. After migration, Microsoft 365 Shared Mailboxes enable centralized team access and communication.
- Enhanced Security and Compliance: Migrate emails from any IMAP server to Office 365, strengthens data protection, access control, and compliance with organizational policies.
- Simplified Administration: Shared Mailboxes are managed centrally through the Microsoft 365 admin center, making it easier to control access.
- Scalability without extra Licensing: By migrating to shared mailboxes, businesses can reduce licensing costs, as shared mailboxes under 50 GB do not require a license.
IMAP to Office 365 Shared Mailbox Migration Planning
Planning is one of the most important steps before you begin your IMAP to Office 365 Shared mailbox migration. Here is a brief checklist of points to consider before you migrate.
- Remove unused mailboxes, mail items and duplicate files from the source.
- Make an inventory of items before you make the move. These should include but are not limited to the following items.
- User accounts, email addresses and login credentials
- The source and target details, browser and operating systems used
- Network settings, DNS configurations, MX records, firewall settings
- Licensing plans on your current source server
- Active Directory configuration and other dependencies associated with it.
- Determine the size of the data and number of mailboxes you want to migrate.
- Decide if you want to migrate everything at once (cutover migration) or plan to migrate your data in stages (staged migration).
- Based on the preceding factors, estimate the approximate time that may take for the migration.
- Create appropriate user mailboxes on Office 365 and assign licenses to them.
- Ensure you have enough network capacity and bandwidth to migrate.
- Consider the throttling and message size limits on Office 365.
- Communicate the migration plan and changes to your end users and stakeholders.
- Perform a test migration before you start the actual one.
- Start the actual migration, verify the endpoints and update the MX records.
- Check for correct mail flow and configure Outlook for all the users.
- Plan for decommissioning unused apps and their settings post migration
Pre Migration activities for IMAP to Office 365 Shared Mailbox Migration
On source IMAP server:
- Ready with your IMAP server hostname, port number, email address, and password.
- To migrate multiple users, download the sample CSV file from the EdbMails application and update the details such as IMAP server hostname, port number, email address, and password for each user's mailbox you want to migrate.
- If you are connecting to Gmail, create an app password and use it instead of your regular password.
On Office 365 server:
- Prepare your target Office 365 tenant. See tenant roadmap for Microsoft 365.
- Purchase a suitable Office 365 licensing plan. You can also sign up for a 30 day free trial and decide to go with a suitable one later. Compare Office 365 business plans and Compare Office 365 enterprise plans
- Before migrating from IMAP server to Office 365, ensure that you create mailboxes for your user. You can choose EdbMails to automatically create mailboxes on target servers. However, if you want to create the mailboxes manually, refer to the links below
- If you plan to migrate to public folders and shared mailboxes on Office 365, ensure that you create and configure them on the target server.
- Ensure that you have a global admin account with a mailbox for Auto Registration of EdbMails application on your Entra ID (Azure Active Directory). However, you can use either a global admin account or any user account with full access rights in the Manual Registration method.
- If you have a custom email domain to which you want to receive emails after the migration, you must add and verify the domain on Office 365. Steps to add a custom domain to Office 365 and steps to add DNS records to connect your domain.
- Ensure that you meet the network and bandwidth requirements for the migration. See network and migration planning, performance factors and best practices for Office 365 migration.
- Configure Office 365 to send and receive large messages. Follow the steps to increase the message size on Office 365 to 150MB. See message size limits on Office 365 for more information.
Steps to Migrate IMAP to Office 365 Shared Mailbox
Step 1: Download and install EdbMails software
- Download and install EdbMails on your computer.
See EdbMails system requirements for IMAP to Office 365 Shared mailbox migration
- Start the EdbMails application on your computer.
- Provide your registered email ID and password, then click ‘Login’. If you haven’t created an account, choose ‘Start Your Free Trial’ to proceed with the trial version.Note: The Free Trial gives you access to all primary features and permits exporting up to 30 items per folder. To export without limits, purchase a valid license from the EdbMails website.After completing the purchase, close the application and relaunch it. Sign in using the same email ID and password used at the time of purchase to activate your license.
- Select the option ‘IMAP (Gmail, Outlook & more) Migration’
- Select ‘IMAP to Office 365 Migration’.
- Use the default job name to proceed, or select ‘New Job’ if you want to change the name before continuing.
- Download and install EdbMails on your computer.
Step 2: Connect to Source IMAP Server
- To set up a single user account, choose ‘Single User / Account Migration’, select the required option like ‘Connect to IMAP Server’ or ‘Connect to POP3 Server’, and then click ‘Next’ to move forward.
- For a single-user login, choose your IMAP host name from the available list or type it in manually. Next, provide your IMAP email address and enter the corresponding password to proceed. If connecting a Gmail account, make sure to create an app password and use it instead of your regular password.
- Then, click the ‘Login’ button.
- To migrate multiple IMAP accounts at the same time, choose ‘Multiple (Bulk) Users/Accounts Migration’ and then click ‘Next’ to continue.
- Select ‘IMAP Migration CSV File’ and choose the file location from your local drive.
- Open the CSV file and enter the required details for each mailbox, such as the email address, password, IMAP server hostname, and port number.
- Once you've finished updating the CSV file with the required information, save and close it.
- Then, click the 'Load Modified CSV File' button, open the CSV file.
- Verify the mailboxes before proceeding and click ‘Next’.
Step 3: Select Source IMAP Server Mailboxes
- Select Source ‘mailboxes’ or ‘folders’ to migrate, then click ‘Next’.
Step 4: Connect to the Target Office 365 Server
- Click ‘Add New Connection’ to create a new connection to the target Office 365 account. If you prefer to continue with a previous connection, choose it from the list and click ‘Connect to Existing’ to proceed.
- Select the ‘Connect to Primary/Shared Mailboxes’ option to connect to Office 365 Global shared mailboxes, then click ‘Next’ to continue.
- Select the suitable target connection method based on the modern authentication methods
- Then, click the ‘Login’ button to continue.
- Sign in through Microsoft’s secure login portal for safe and seamless authentication.
- Select one of the methods to load the mailboxes. You can Select ‘Load Mailboxes Automatically’, 'Load Mailboxes using .CSV file' or ‘Load Mailboxes from previous list’ and click ‘Next’.
- Because of Microsoft API restrictions, the application can automatically fetch only up to 100 mailboxes. If your environment contains more than 100 mailboxes, import the remaining ones using a CSV file and then click ‘Next’ to proceed.
Step 5: Map Source and Target Mailboxes
- Choose the required mailbox mapping option
- EdbMails automatically maps source IMAP mailboxes with the corresponding Office 365 Shared Mailboxes, making large-scale migrations simple and efficient. It also allows you to manually map source and destination mailboxes whenever needed.
Step 6: Start IMAP to Office 365 shared mailbox migration operation
- After mapping the mailboxes, click the ‘Start Migration’ button and initiate the migration process.
- Click the ‘View Logs’ button to see the IMAP migration report, which provides a detailed summary of the process, including the total number of items migrated and a folder-wise item count.
IMAP to Office 365 Shared Mailbox Post-migration Activities
- Step 1: Update DNS records (MX record) to point to Office 365
Update your MX records in your DNS to start receiving messages on Office 365. This switch ensures smooth email operation with your newly migrated server. Additionally, set up the Autodiscover record for the Outlook connectivity to the migrated mailboxes.
- Step 2: Create a new Outlook profile for users in the new domain
Remove any previous instances of the email account you may have on Outlook to avoid conflicts with Office 365. Configure and recreate the Outlook profile for each user in your domain after you complete the migration.
- Step 1: Update DNS records (MX record) to point to Office 365
Troubleshooting guide for IMAP to Office 365 Shared mailbox migration
For common migration issues, check the knowledge base articles. To learn more about EdbMails IMAP Migration software and its features, visit the frequently asked questions section or contact our support team.
Benefits of EdbMails for IMAP to Office 365 Shared mailbox migration
- Single hop migration
EdbMails ensures a smooth, direct migration from IMAP to Office 365 Shared mailboxes in a single hop, eliminating the need for multiple steps. This saves time and minimizes the risk of data loss during intermediate stages.
- Automatic mailbox mapping
With EdbMails, mailbox mapping is automated, accurately matching IMAP mailboxes with Office 365 counterparts. This feature reduces manual effort and ensures that each user’s data is migrated to the correct destination without errors.
- Metadata integrity
EdbMails preserves the integrity of email metadata during migration, ensuring that crucial information like timestamps, sender details, and folder structure remains intact. This maintains the organization and context of emails after migration.
- Language compatibility
EdbMails supports migration in various languages, making it ideal for international organizations. Emails, regardless of their language or character encoding, are accurately migrated without any data corruption or loss of information.
- Free software updates
EdbMails offers free software updates, ensuring that your migration process stays aligned with the latest Office 365 features and security updates. This guarantees compatibility and up-to-date functionality for a reliable migration.

