AWS WorkMail to Office 365 Migration

Planning is one of the most important steps before you begin the AWS Workmail to Office 365 migration. Here is a checklist of points to consider before you migrate.

• Evaluate the overall data size and determine the total number of mailboxes to be migrated to plan resources, timelines, and migration strategy effectively.
• Create a detailed list of all data and mailbox permissions in AWS WorkMail that need to be transferred to Office 365 during migration.
• Set up the necessary user mailboxes on Office 365 and assign the corresponding licenses to each account.
• Ensure you have enough network capacity and bandwidth to migrate.
• Communicate the migration plan and flow to your end users.

1. Prepare all necessary details before starting the migration, including the IMAP server hostname, port number, email address, and password, to ensure a smooth and error-free transfer.
2. For migrating multiple users, download the sample CSV file from the EdbMails application, then update the file with the IMAP server hostname, port number, email address, and password for each user's mailbox you wish to migrate.
    See how to find your IMAP server host name.
3. Ensure that Office 365 mailboxes are created and licenses are assigned to them. You can choose the option in EdbMails to automatically create Office 365 mailboxes. However, if you prefer to do it manually, refer to the links below:
    Add users and assign licenses to Office 365 users
    Assign Microsoft 365 licenses to user accounts
4. To migrate AWS Work mail to Office 365 Public folders, ensure that you create public folders and assign permissions on the target server.
    Create Office 365 Public folder and assign permission to the admin user
5. Similarly, if you want to migrate mailboxes to Office 365 archive mailbox, enable In-Place archive in target O365 server
    Steps to enable archive mailbox in Microsoft 365.
6. If you have a custom email domain from the source which you want to retain and receive emails to, 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.
7. 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.

• • Step 1: Download and install EdbMails IMAP migration software

    • Download EdbMails and install the application on your computer.

      

    • Start the EdbMails application on your system.
    • Enter your registered email ID and password, then click ‘Login’. If you’re accessing EdbMails for the first time, click ‘Start Your Free Trial’ to use the Free trial.
       Note: The trial version includes all essential features and allows exporting up to 30 items per folder. To unlock unlimited exports and remove this limitation, purchase a valid license from the official EdbMails website.

       Visit our pricing page to explore plans and purchase your license.

      

    • Select the option ‘IMAP (Gmail, Outlook & more) Migration’.

      

    • Select ‘IMAP to Office 365 Migration’.

      

    • You can proceed with the default job name or select ‘New Job’ to assign a custom name for your migration task.

      

  • Step 2: Connect to source AWS WorkMail server

    • To connect a single AWS Workmail account for migration, click ‘Single User / Account Migration’, choose the suitable connection option such as ‘Connect to IMAP Server’ or ‘Connect to POP3 Server’. Click ‘Next’ to proceed.

      

    • From the IMAP host list, select ‘AWS WorkMail’ or manually enter your IMAP server details.
    • Next, provide the necessary login details including your email address, password, and the SSL port number, which is typically 993 when SSL encryption is enabled.
    • Click on the ‘Login’ button to establish a secure connection with your AWS WorkMail account.

      

    • To migrate multiple AWS Workmail mailboxes at once, select ‘Multiple (bulk) Users/Accounts Migration’, choose the suitable connection method such as ‘Connect to IMAP Server’ or ‘Connect to POP3 Server’.
    • Then proceed by clicking ‘Next’.

      

    • Select the ‘IMAP Migration CSV File’ option to download the ‘Sample.CSV’ file. The file will be automatically saved to your local system, allowing you to access and refer to it whenever required.

      

    • Open the CSV file and provide the required information for each AWS WorkMail account you plan to migrate.
    • This includes the user’s email address, password, IMAP server name, and corresponding port number.

      

    • Once you've updated the CSV file with all the necessary mailbox details, save and close the file.
    • Then, click the 'Load Modified CSV File' button, navigate to the saved location, select your file, and upload it to continue with the migration process.

      

  • Step 3: Select the mailboxes or folders to migrate

    • Select the mailboxes or individual folders you want to include in the migration. Once you've made your selection, click ‘Next’ to move forward with the process.

      

  • Step 4: Connect to target Office 365 server

    • Click on ‘Add New Connection’ to set up a connection with your target Office 365 account.
    • If a connection has already been configured, simply select it from the list and choose ‘Connect to Existing’ to continue.

      

    • EdbMails provides versatile migration options that let you migrate primary mailboxes, archive mailboxes, and public folders using one centralized platform
    • Select your preferred connection option based on your migration requirements, and click ‘Next’ to continue with the authentication steps.

      

    • Choose any of the available options to create a secure connection using OAuth 2.0 modern authentication:
    • Select Auto Registration if you prefer a quick and smooth setup. Sign in with a Global Admin account and provide the required permissions to automatically register the application in Azure AD.
    • Or choose Manual Registration if you prefer to enter the Azure AD application details yourself. This method supports both Global Admin accounts and accounts with Full Access permissions.
    • Click ‘Login’ to proceed.

      

    • Authenticate on Microsoft sign-in page.

      

    • Once authentication is completed successfully, select any one of the following options to load the mailboxes:

      i) Load Mailboxes Automatically: After logging in, EdbMails automatically detects and lists the mailboxes, making the process quick. Due to Microsoft API restrictions, only a maximum of 100 mailboxes can be displayed. If your organization contains more than 100 mailboxes, use the alternative option given below.

      ii) Load Mailboxes using CSV file: If the automatic method does not retrieve all mailbox names, choose ‘Load Mailboxes using .CSV file’ to manually upload and load the required mailboxes.

      iii) Load Mailboxes from previous list: This option allows you to load mailboxes from a previously saved list imported in an earlier session.

    • Choose ‘Load Mailboxes Automatically’ and click ‘Next’ to move forward.

      

  • Step 5: AWS WorkMail to Office 365 mailboxes mapping

    • Choose your preferred method to map the source AWS Workmail mailboxes or folders to their corresponding mailboxes or folders on the target Office 365 account.

      

    • EdbMails lets you automatically create the required mailboxes in your target Office 365 account.
    • It also automatically maps your source AWS mailboxes and folders to the matching ones in Office 365, making large migrations easier to manage.

      

  • Step 6: Start AWS WorkMail to Office 365 migration

    • Review the mailbox mapping for accuracy, then click the ‘Start Migration’ button to initiate the migration process.

      

    • Click the ‘View Logs’ button to open the detailed migration report. This report includes comprehensive information, such as mailbox mapping, a summary of the migration process, and the item count for each migrated mailbox and folder.

      

• Step 1: Update the MX records to point to Office 365

  Update the DNS records known as MX records to enable email and receive messages on the target Office 365 server. In addition, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.

• Step 2: Create a new Outlook profile for users in the new domain

  Configure the Outlook profile for each user in your domain if Outlook has problems connecting to Office 365 mailboxes.

 For troubleshooting, visit : Knowledge Base.
 For more queries, check Frequently Asked Questions or contact support.