The following article outlines important considerations to keep in mind during the migration process from Google Workspace to Microsoft 365 using CloudM Migrate.
Drive
Potential Orphaned Files and Folders Post Migration
Behavior
If a migration has non-migrating users, external users or users who have deleted folders that house other users data, this could cause orphaned items post migration.
Recommendations
Prior to the migration, it is recommended that customers perform thorough checks of their environment to ensure that the outlined scenarios are not present.
To minimise impact:
- Verify that all source environment users owning critical data are included within the migration scope.
- Transfer ownership of externally owned items to migrating users where possible.
This ensures the integrity of the data structure is maintained post-migration.
Shared Drive Members
Behavior
Shared Drive members are not migrated.
Note: File and folder permissions are migrated.
Recommendations
Manually assign permissions at the destination before the cutover migration to ensure continued access for users.
Google Forms
Behavior
Google Forms are migrated as a ZIP file, which includes an HTML file of the report and a CSV file of the responses.
Recommendations
Manually re-create the form in Microsoft 365 to restore its functionality.
Document Creation Date
Behavior
The created date of a document is not migrated. The created date will reflect the date the file is migrated.
Recommendations
No action is required. However, it is advisable to inform end users of this change in advance.
Starred Files and Folders
Behavior
Starred files and folders will not automatically retain their starred status in the destination accounts.
Recommendations
End users should manually star their files and folders after the migration is completed.
Linked files/images
Behavior
- Hyperlinks to other Google files will become outdated, as files are assigned new URLs at the destination.
- Embedded links, files, charts, etc., will remain linked to the source domain files and must be updated to reflect the new destination domain files.
- Google Forms will no longer be linked to their response sheets.
Recommendations
Post go-live, migrated users should update links within their documents to reflect the new destination URLs.
Consider utilising Document Mappings to map the original source document to the migrated document.
Version History
Behavior
Version history is migrated. Refer to the following article for guidance on migrating version history:
Google Workspace to Microsoft 365 Document Version History
Recommendations
- If migrating document versions, follow the steps outlined in the referenced article.
- Be aware that migrating versions may significantly increase overall migration time.
Character Limitations
Behavior
File and folder names in OneDrive and SharePoint are subject to character restrictions. Details of these limitations are provided in the following Microsoft article:
Restrictions and limitations in OneDrive and SharePoint
Recommendations
No action is required, as invalid characters will be automatically replaced during the migration process.
Unowned Files in My Drive
Behavior
Files located in a user's My Drive but owned by another user will not appear in the user’s OneDrive structure post-migration. However, these files will be accessible in the Shared with me section of OneDrive, provided the file owner has also been migrated.
Recommendations
Inform users of this behaviour prior to go-live to manage expectations.
Externally Owned Files
Behavior
Externally owned files will not be migrated.
Recommendations
After go-live, external users will need to re-share their files with the migrating users.
External Sharing
Behavior
External sharing will not be migrated.
Recommendations
Documents shared externally will need to be re-shared with external parties post-migration.
Deleted items
Behavior
Files and folders in the "Bin" will not be migrated.
Recommendations
No action is typically required unless explicitly necessary. If required, a migration from Google Vault to Microsoft 365 OneDrive/SharePoint can include deleted items.
SharePoint Site Document Creation
Behavior
The creator of documents at the destination will be set to the admin account specified in CloudM Migrate for the destination connection. This does not affect document permissions.
Recommendations
Inform users of this behaviour. Consider using a temporary admin account in CloudM Migrate that can be deleted after the migration.
Orphaned Folders
Behavior
If "Migrate orphaned folders" is enabled in the Document section of the source settings, empty folders prefixed with an underscore may appear in the destination OneDrive. The extent depends on the number of orphaned folders at the source.
Recommendations
Notify users of this potential behaviour prior to the migration to avoid confusion.
Folder and Files Moves Mid-Migration
Behavior
Folders and files that are moved during a migration will not be moved in subsequent migration passes.
Recommendations
To relocate a file or folder, delete the item from the destination, clear the migration history, and then re-run the migration.
Spam Folder
Behavior
The spam folder is not migrated.
Recommendations
Inform users of this prior to the migration so they can manage their spam emails accordingly.
Labels to Folders
Behavior
When migrating from Gmail to Microsoft 365, Gmail labels are converted into folders.
- If an email is assigned a single label, that label is created as an Outlook folder, and the email is moved into it.
- If an email is assigned multiple labels, CloudM Migrate creates the folder with the shortest path (e.g. "Clients/B" instead of "Clients/A/Invoices") and places the email in this folder. The remaining labels are then added as categories to the email.
Recommendations
Make users aware of this behaviour prior to migration to set appropriate expectations.
Labels containing a forward slash
Behavior
Labels containing a forward slash ("/") will be split into two folders in Microsoft 365 after migration. For example, the label "TestA/TextB" will result in a "TestA" folder with a sub-folder named "TextB".
Recommendations
Advise users to modify any labels containing a forward slash ("/") prior to migration and revert them in the new environment post-migration.
Email Settings
Behavior
Rules, aliases, POP settings, canned responses, filters and mailbox customisations will not be migrated.
Recommendations
Users should re-apply any desired settings in their new accounts after migration.
Snoozed Emails
Behavior
Snoozed emails are migrated; however, they are no longer snoozed in the destination account, losing their snoozed status.
Recommendations
Advise users of this behaviour prior to migration to avoid confusion.
Microsoft 365 Mailbox Limitations
Behavior
Microsoft 365 mailbox limitations vary depending on the license assigned. These are outlined in the below Microsoft article.
Recommendations
If a users mailbox exceeds one of the limits mentioned int he above article, consider the following:
-
If a user’s mailbox exceeds any of the specified limits:
-
Limit the number of items being migrated (e.g., migrate only the past 3 years of emails).
-
Archive emails that exceed the limits.
-
Open a case with Microsoft support to increase mailbox capacity.
-
Change labels of some items at the source to ensure no label contains more than 1,000,000 items.
Calendar
Meetings with Meet links
Behavior
There is an option to migrate Google Meet links into the text body of the newly created Microsoft 365 meeting. However, these links will remain associated with the source Google accounts. Migrate does not automatically generate or distribute Teams meeting links to attendees.
Recommendations
- Migrate these meeting links if users still need access to external Google Meet events.
- Advise users to replace the Google Meet link with a new Teams meeting link when required.
Recurring Meetings with Meet links
Behavior
Meet links will not be migrated for recurring meetings.
Recommendations
Inform users that they will need to re-create these recurring meetings with a Teams meeting link at the destination if required.
Recurring Meetings
Behavior
Recurring meetings will be migrated, but the recurrence rule will not be. As a result, any changes to the recurring meetings will not be reflected across the linked events. All recurring meetings will be detached from the master event.
Recommendations
If linking recurring events is necessary, it is recommended to delete and re-create the recurring meetings post-migration.
Secondary Calendars
Behavior
Secondary calendars will be migrated only if the original owner can be identified during the migration.
Recommendations
- Ensure that calendar sharing settings are properly configured post-migration, especially for calendars shared with external contacts.
- Be aware that old calendars hidden before migration may become visible again. Users should review these reappeared calendar items and decide whether to hide or delete them as needed.
Calendar Sharing Notifications
Behavior
Users will receive emails indicating that a calendar has been shared with them during the migration.
Recommendations
Inform users prior to migration that they will receive these notifications.
Using Calendar between Google and Microsoft during a Phased Migration
Behavior
Users may experience difficulty managing calendar invites across platforms. It is recommended that an admin or technical resource sets up Calendar Interop to facilitate smooth operation.
Recommendations
Have an admin or technical resource set up Calendar Interop, as outlined in Google's documentation:
Chat
Google Chat History
Behavior
Old Google Hangout Chats (pre mid-2022) can be migrated as individual emails. However, new Google Chats will not be migrated.
Recommendations
Migrating older Hangout chats is not recommended unless explicitly required.
Contacts
My Contacts Vs Other Contacts
Behavior
By default, users' "Other Contacts" will be migrated into their "My Contacts" section. This ensures the user experience is replicated after migration, i.e., email addresses will be suggested when composing emails.
Recommendations
No action required.
Sites
Google Sites
Behavior
Migration of Google Sites is not currently supported.
Recommendations
Manually recreate any necessary sites at the destination.
Google Keep
Behavior
Google Keep is not migrated.
Recommendations
Users should manually copy any important information from Google Keep.