This is the complete onboarding task flow for migrating mailboxes from G Suite to Office 365.
Introduction
Communication Strategy
Scoping
Preparing the Source
Recommended Actions
The following sections are recommended to ensure that the migration of all data is possible and to prevent failures.
Preparing the Destination
Licensing
Create A Mailbox Project
Global Options
- Set to use impersonation at the Destination. Checkmark the Use impersonation at Destination box. Read the How do I migrate to Exchange or Office 365 using impersonation? article for more information.
- Under Filtering, add:
(^All Mail$|^All Mail/)KB005626
Notes:
- Under Support/Support options, add:
StoreOverflowGooglePropertiesInNotes=1KB005056 - Under Support/Support options, add:
StoreOverflowGooglePropertiesInNotesPrefix="enter your text here"KB005056 - Under Support/Support options, add:
SuppressReminderDays=XKB004203
The following section will explain the additional steps required if your are changing the domain name with your migration.
Changing the Domain
The below Recipient Mapping option is recommended for most G Suite to Office 365 migrations while changing the domain name. Recipient Mapping is a very important step for this migration scenario. It ensures that emails have the ability to be replied to, even after the Full (Delta) migration has occurred because they will be mapped to the new destination domain name, rather than using the old sourcedomainname.com domain name.
IMPORTANT: When performing a migration and you are changing your domain name, it is required the the Recipient Mapping option is adding to your migration project before performing any type of migration.
RecipientMapping="@sourcedomainname.com->@destinationdomainname.com"
- The RecipientMapping above is just an example; do not copy this verbatim. It needs to be changed to reflect the sourcedomainname.com account name and the customer destination domain name.
Run Migration
Remove the All Mail filter from project Advanced Options, and run one final (Full) migration pass.
- Under Project Advanced Options > Filtering section, delete:
(^All Mail$|^All Mail/)KB005626 - Select the users > Click the Start button from the top, select Full Migration > Click Start Migration.
Comments
13 comments
Did this guide used to have something regarding time of the MX cutover?
Hi, Kristian:
Thanks for the feedback.
We'll take a look and make the appropriate updates.
Larry
How can we migrate an group email address from G Suite to Office 365?
Hi André Monveux LONDE MINDOUDI,
According to the article link below, Google Groups migrations are not supported at this time.
https://help.bittitan.com/hc/en-us/articles/115008254468-
I'm migrating from G Suite to Office 365.
I have created some 365 Groups in the 365 admin portal, which has same name/e-mail adress as some excisting G Suite users.
Is it possible to migrate these G Suite users email to the respective newly created Office 365 Group with same name?
Hi Tobias Thaastrup-Leth,
According to the article link below, MigrationWiz does not migrate Google Groups at this moment.
The article was last updated 1 month ago unless something has changed, this should still be true.
I am currently also performing Google Suite to Office 365 migration, and a few months ago, I got the same question.
Hope my answer will help.
Regards.
https://help.bittitan.com/hc/en-us/articles/115008254468-
Hi
It mentions that only a certain verion of GSuite for Business can be used with Mig Wiz, can personal Gmail accounts be migrated to Office 365?
A company we are looking to migrate have 9 employees which are all using personal GMAIL accounts.
Many thanks
is there a way to schedule the migration or make it sync automatically
if there are any changes?
Hi Mustafa,
You can absolutely schedule a migration to start at a specific time. We have instructions in our KB here: Scheduling a migration.
With regards to syncing, MigrationWiz is not a syncing solution. If a migration has been run, then a user moves items around in the mailbox, and then the migration is run again, this usually can result in duplicate items because MigrationWiz sees the items in a new location and assumes that they are new items.
It's best to either run the mailbox in one migration pass (for small mailboxes or if you need to move in a shorter amount of time), or use pre-stage migrations to move older items that are less likely to be changed by the user, followed by a full migration pass at the time of cutover to move newer items.
I hope that helps!
Anne
Why did you remove the OAUTH guidance from the GSuite source section of the guide? It won't work without it?
Is the previous version of this guide still available? There used to be a lot of GSuite specific information available, specifically regarding setting up the API Authentication, which is now removed and I don't see any links to separate articles to sort this out.
Edit: I found a link to the article required to complete setup of the GSuite Endpoint.
https://help.bittitan.com/hc/en-us/articles/115008106967
Hello Anthony,
Thank you for bringing this to our attention. I will reach out to the Knowledge Management team to get the issue resolved.
Regards,
Nicholas
Anthony I ran into the same problem. The information you are looking for is in the "Related Articles" section but it won't work without it.
Enable access to G Suite (IMAP) using OAuth 2.0
Please sign in to leave a comment.