Email Migration from Google

 During onboarding we copy over your emails via email migration. This includes the emails and meetings (but not the Meeting links since Google Meet cannot be converted to Microsoft Teams links). Here is an outline of how this process looks.

✉️ In summary: This project outline details the steps for migrating emails from Google to Microsoft. The process involves connecting the tool to both accounts, configuring migration settings, testing with a single user, copying over all emails, confirming domain access and scheduling a call to switch domains, exporting DNS settings, performing a 7-step domain switch process, and testing emails to ensure success.

NOTE: Other than copying over your inbox to your new Microsoft account, your information on Google Workspace (docs, sheets, etc.) will still be accessible from your original Google login. 

1. Team Atomus schedules a call to connect the tool to the Google Workspace using a “super admin” account. (Call 1)
2. Team Atomus connects the tool to the destination Microsoft account, then identifies and selects the mailboxes for migration. 
3. Make sure that all configurations of migration (data throttling limits, email format types, folders, and so on.) are setup correctly and configured.
   1. If not configured, the company might lose temporary blocking on the google workspace and not able to login to their emails online in Google. 
4. Team Atomus then tests the migration by copying over 1 user's emails. 
5. If successful, the team will then copy over all emails for all the users.
   1. The time it takes to fully migrate every user's inbox over really depends on the amount of data and the number of emails. We have seen ~40k emails in a day sometimes to ~15k emails in a day depending on the data we are pulling from the workspace. 
6. Once the emails are copied over, make sure that the company has not setup the domain from Google in a MSFT tenant ever in the past.
7. Team Atomus confirms with the company over email, as who has access to the DNS settings of the domains and ask them to be on Call 2. Please note that there might be downtime in emails, which is why we always prefer Call 2 to be around 4 PM at the company’s time zone.
8. Right before the call, we make sure to re-run the migration while making sure that only the new emails get copied over, and not duplicate the old ones, and in time to get the domain switching to be done. 
9. Once confirmed, Atomus will schedule a call to make the switch over of the domain (Call 2). 
10. On Call 2, the current DNS settings are exported to make sure that we have a copy of it before making any changes to it.
11. Team Atomus helps the company set up and verify the new domain with MSFT, then performs a complicated 7-step domain switch process to make sure to avoid as much downtime as possible, and making sure we can still have the alias of the old target if required.
12. After that Team Atomus, performs email testing with the company to mark the project as a success.
13. Once testing is finished, the email migration is complete and the project is deemed successful. 
    A successful migration includes all emails from the old inbox transferred over to the new Microsoft email and that all new emails will go to the Microsoft email.