EdbMails software for AWS Workmail

Amazon, which began as a modest e-commerce service, has now spread its wings and made its presence felt in a multitude of sectors, including cloud services, books and accessories, digital goods, Alexa, entertainment, and even groceries. Its primary focus is cloud hosting and providing business solutions, similar to Microsoft, Google, and Apple. Amazon Workmail, for example, is used as a web email service by many businesses. However, due to many reasons users want to switch from AWS Workmail to Office 365. For instance, Microsoft has a plethora of useful collaboration apps and features such as Microsoft Word, Excel, SharePoint, and Teams, to name a few which are included in the same package. With Office 365, it is much easier to have everything under one roof rather than searching for bits and pieces all over the place. Users of Microsoft Teams can easily make a call, leave a message, start a web conference, and catch up with colleagues. Office 365 also allows you to keep your old domain for sending and receiving emails. You can transfer mailboxes from AWS Workmail to Office 365 using the EdbMails IMAP migration software. It is best suited for both small and large businesses and makes migration easier thanks to its graphical user interface. The fact that EdbMails automates the entire process with minimal user involvement is one of its enticing characteristics. It gives you the ability to directly do a migration without any complications by connecting to the source AWS Workmail and the target Office 365.

1. Pre migration activities for AWS Workmail to Office 365 migration

   1. Have admin access for the source AWS Workmail and target Office 365 server

      The admin account with all the necessary permissions is required to migrate mailboxes on behalf of all the users in your organization. Also assign the Organization Management role group and impersonation rights to the admin user on Office 365.

   2. Prepare a CSV file including a list of users to migrate from the AWS Workmail account . Download the AWS Workmail application and get the IMAP server details and the app password.
   3. Have an 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
   4. Create Office 365 mailboxes and assign licenses to them

        Add users and assign licenses to Office 365 users

        Assign Microsoft 365 licenses to user accounts

   5. 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 mailbox user

   6. 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.

   7. 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.

   8. 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.

2. AWS Workspace to Office 365 migration using Edbmails

   You can perform the migration with the following two methods.

   1. Migrate AWS Workspace to Office 365 from the Exchange admin center
   2. Migrate AWS to O365 with EdbMails IMAP migration

   • Steps to migrate AWS Workspace to Office 365 from the EAC

     • Step 1: Ensure that you are having administrator access on AWS and Office 365
     • Step 2: Create user mailboxes on the target Office 365 tenant
     • Step 3: Add email domain from the AWS Workmail to Microsoft 365
     • Step 4: Make a note of the IMAP connection details from the source account.
     • Step 5: Create a list of mailboxes to migrate to O365 in a .CSV file
     • Step 6: Create a migration endpoint and migration batch
     • Step 7: Update the MX record to route the email to Microsoft 365

     Keep in mind that this is a manual method which must be carried out using an IMAP connection from Microsoft's admin center. After you have created the .CSV file, you must manually upload it to the EAC and allow Microsoft to verify it. When the migration operation is finished, the status changes to Synced, and you can delete the migration batch and decommission your old email environment. This may be time-consuming and inefficient, with no tangible results. If you want a quick and easy way to migrate your mailboxes to Office 365, refer to the following section on migrating with EdbMails.

   • Steps to migrate AWS Workspace to Office 365 using EdbMails

     EdbMails IMAP migration to Office 365 tool can help you easily transfer your emails from Amazon Workmail to Office 365. You do not need to use manual methods or require technical expertise, and its additional filter options allow you to migrate specific folders and files. Another significant advantage of using this application is that you can migrate without disrupting your users or experiencing downtime.

     • Step 1: Launch EdbMails application

       Before you begin, download EdbMails and click 'Start Your Free Trial' to use the application for free. Select ‘IMAP migration’ to proceed.

       

     • Step 2: Connect to AWS Workmail

       As mentioned in the previous method, obtaining the IMAP server details for your AWS Workspace account allows you to connect to it and migrate your emails to Office 365. You'll need one of the details depending on which server you have your email account on.

       1. US West (Oregon): imap.mail.us-west-2.awsapps.com
       2. US East (N. Virginia): imap.mail.us-east-1.awsapps.com
       3. Europe (Ireland): imap.mail.eu-west-1.awsapps.com

       If you are unsure about the AWS server region, contact your system administrator and request the server connection information. Once you've got them, enter the Hostname or IP address as shown, Port 993, and SSL/TLS for a secure IMAP connection.

       

       To migrate multiple mailboxes, select ‘Multiple (bulk) Users/Accounts Migration’. Download the sample CSV file from EdbMails and fill in the required details such as mailbox name, password, host name and port. Load the CSV file into the application and verify the list mailboxes to continue.

       

         See steps to connect to single and multiple users in EdbMails IMAP migration

     • Step 3 : Choose mailboxes and folders to migrate

       Choose the mailboxes and folders from the left panel.

       Click ‘Migrate to Office 365’ to proceed the connection with the target server.

       See tips to optimize IMAP migration to Exchange online

       

       Tip: With the EdbMails, initial migration is always a full migration. On subsequent migrations from the same source to the target, the migration is incremental.

       EdbMails provides the following additional options to help you customize the migration task.

       • Include and Exclude Filter Options
       • Filter mail items by Date: Migrate to Office 365 by applying the Date filter
       • Filter emails by Size: Exclude emails from migration larger than a specified size.
     • Step 4: Connect to target Office 365 server

       EdbMails supports both modern and classic authentication. Connect to the target server by selecting ‘Auto’ or ‘Manual’ registration for modern authentication and the connection method as Mailboxes, Public folder or Archive Mailbox. EdbMails can automatically load the mailboxes and also you can use a CSV file to load Office 365 mailboxes

       

         Connect to Office 365 server using secure modern authentication

     • Step 5: Map the mailboxes and start AWS Workmail to Office 365 migration

       EdbMails can automatically map the mailboxes AWS Workmail and Office 365. This will save time when you’re migrating a large number of mailboxes. Start the migration and finally verify the count of migrated emails, folders and mailbox items with EdbMails text-based log report. You can also pause and resume the migration if you require.

3. Post-migration tasks

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

   If you have not done this step previously, change 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.