This migration guide contains the necessary steps to perform the actual migration, but there are many steps to preparing for migration. If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices.
To discover what items are moved with MigrationWiz in this scenario, and which items will not be moved, see Moved Items. Note that these items will vary by source and destination, so check the proper environment listings carefully.
MigrationWiz is a migration tool, not a syncing tool. If changes are made at the source after migration, they will not sync to the destination, nor will changes made at the destination sync to the source. We do not have “live” monitoring of changes (as with a sync agent) and we cannot handle scenarios such as conflict resolution without user interaction.
Important: Migrating from a G Suite/Gmail endpoint requires an administrator email address which matches the end user domain.
Preparing the Source
Recommended Actions
The following sections are recommended to ensure that the migration of all data is possible and to prevent failures.
Set up API scopes with OAuth
BitTitan products use OAuth 2.0 to authenticate to G Suite and utilize the G Suite (IMAP) endpoint in MigrationWiz. This is applicable to both mailbox and document migration projects. In order to obtain access to your G Suite data, it is necessary to add specifically allowed API scopes to the MigrationWiz project.
Notes:
- These steps must be followed whenever there is a migration project either to or from G Suite that will utilize the G Suite (IMAP) endpoint. For instructions on using the Gmail API endpoint, see MigrationWiz - Mailbox Migration - Set up Google API for migrating mailboxes.
- Enabling access is required for both G Suite mailbox and Google Drive document migration projects.
- Mailbox migration projects require that a G Suite administrator grant access to the BitTitan client ID and scopes listed in this article.
- Document migration projects require that a G Suite Super administrator grant access to the BitTitan client ID and scopes listed in this article and enable the API access. The steps to do this are included at the bottom of this article.
Steps in the G Suite Admin Console
Complete these steps to grant BitTitan client ID access to the appropriate scopes:
- Go to https://admin.google.com and authenticate as a Super Administrator.
- Click Security.
Note: If you do not see the security icon on your admin console home page, you do not have the necessary rights on your account to make these changes. Request Super Administrator access from the customer to implement these changes. - Click Advanced settings.
Note: Google limits accessing and changing this setting to only G Suite Super Administrator accounts. - You will now have one of two options, depending on whether your tenant has been updated to the new Google API or not.
-
Old Google Tenant:
- Go to the G Suite admin page at google.com
- Click on Security
- Click on Advanced Settings
- Click Manage API Client Access.
OR If your account shows the latest UI updates from Google, as shown below:
- Go to the G Suite admin page at google.com
- Click on Security
- Click Advanced Settings
- Under ‘Domain-wide delegation’, click Manage domain-wide delegation
- On the Manage domain-wide delegation page, click Add new
- Click MANAGE DOMAIN WIDE DELEGATION.
- Click Add New.
- Enter 113321175602709078332 into the Client ID field.
- Enter one of the following groups of scopes into the OAuth Scopes (comma-delimited) field, depending on whether G Suite is the Source or Destination.
- G Suite as the Source (read-only scopes):
https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/, https://www.googleapis.com/auth/gmail.settings.sharing, https://www.googleapis.com/auth/gmail.settings.basic - G Suite as the Destination (full scopes):
https://mail.google.com/, https://www.google.com/m8/feeds, https://www.googleapis.com/auth/contacts.readonly, https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/admin.directory.group, https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/drive, https://sites.google.com/feeds/, https://www.googleapis.com/auth/gmail.settings.sharing, https://www.googleapis.com/auth/gmail.settings.basic
- G Suite as the Source (read-only scopes):
- Click Authorize.
Note: The client name is 113321175602709078332 (make sure there are no leading or trailing spaces, as this may cause the error "URL ends with an invalid top-level domain name."). This will grant BitTitan products access to the appropriate scopes.
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 (Replace "enter your text here" with your message. Please see KB005056) - Under Support/Support options, add:
SuppressReminderDays=XKB004203 (Replace "X" with a value from 1 to 365. Please see KB004203)
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.