In the review phase of a Microsoft Exchange to G Suite (formerly Google Apps) migration using Transformer, you will:
|Feature||Target Object||Supported||Watch Points|
|Copy User Mailbox||User Mailbox||Yes|
|Copy Group Mailbox||Yes|
|Copy Shared (delegated) Mailbox||Yes|
|Copy Mail||Yes||Throughput - Email. Invalid data header issue - Email.|
|Copy Mail - Read State||Mail - Read State||Yes|
|Copy Mail - Priority||Gmail Importance||Yes|
|Copy Folders||Labels||Yes||System sub-labels will be reorganized.|
|Copy Folder Hierarchy||Label Hierarchy||Yes||System sub-labels will be reorganized.|
|Copy Mail Category||Labels||Yes||Only categories in use will be migrated.|
|Copy Mail Attachments||Yes||Large attachments will be added to Google Drive.|
|Copy Mailbox Archive||Google Vault||Coming Soon|
|Copy Calendars||Calendar - Primary||Yes|
|Copy Calendars - Secondary||Calendar - Secondary||Yes|
|Copy Calendar Events||Calendar Events||Yes|
|Copy Calendar Events - Recurring||Calendar Events - Recurring||Yes|
|Copy Calendar Attachments|
Google Drive Files (link embedded in Calendar event)
|Yes||All attendees on the event are granted access to the file in Google Drive.|
|Copy Calendar Events - External||Calendar Events - External||Yes|
|Calendar Event attendee responses||Calendar Event attendee responses||Yes||Responses can optionally be disabled to improve migration performance.|
|Calendar Permissions||Google Sharing||Yes||Users will receive emails indicating that Calendars have been shared with them during migration. It is possible to configure a content compliance rule to ensure that these emails are filtered.|
|Calendar Reminders||Reminders||Yes||Reminders can be migrated as Google Calendar reminders.|
|Copy Public Folders||Google Group Mailbox||Yes|
|Copy Address Books||Contact Groups||Yes|
|Distribution Groups||Google Groups||No|
|Google Tasks||Tasks||Yes||Task sub-folders are migrated to separate task lists.|
|Rooms and Equipment|
|Copy Meeting Rooms and Equipment Calendar Events||Google Resources Calendar Events||Yes||Migrating to Google resource calendars.|
|Settings - Filters||Gmail Settings - Filters||Yes||Not all Exchange rules and actions have Google equivalents.|
|Settings - Signatures||Gmail Settings - Signatures||Yes|
|Settings - Vacation Responder||Gmail Settings - Vacation Responder||Yes|
|Settings - Forwarding||Settings - Forwarding||Yes||Setting up a forwarding address can prompt a message to the recipient of the messages.|
|Settings - Send As||Settings - Send As||Yes|
|Watch point||Description||Best Practice|
|Throughput - Email||To avoid duplication and errors, Emails being written to the target domain must be analyzed. Emails that have been forwarded or migrated to the target environment prior to the production migration may create issues for Transformer.|
Transformer provides the ability to significantly increase the speed of migration by using the Accelerate Old Messages setting for Gmail migration.
If email forwarding is used, the Insert Before Date field should be set to the day before forwarding was turned on.
|Invalid data header issue - Email|
We have discovered a problem that occurs when source emails have invalid headers for their Dates. These emails may appear as having arrived at a specific time on the source system, but the data for the email itself does not accurately include the delivery time. In this case, the messages will appear in the target mailbox as having arrived at migration time.
The issue is caused by emails that have Date headers that don't conform to the RFC 2822 standard for emails.
|AppBridge is currently investigating options for dealing with this issue. We have found that it can occur on multiple types of email servers.|
|In Gmail, system labels cannot have sub-labels. Exchange supports sub-folders under all folders. Therefore, some folders from Exchange may need to be reorganized. Essentially, the sub-folders will be created outside of the system labels. Both the system label and the new custom label will be applied.||Communicate this change to end-users in advance.|
|Large attachments||By default, all attachments over 25MB will be added to Google Drive. In the body of the email, a link to the attachment replaces the file. The size threshold and destination folder name are configurable.|
When migrating Exchange Meeting Rooms, Transformer supports updating resource calendars in the target Google environment based on events. This works a little different than the G Suite to G Suite case.
For G Suite to G Suite, we migrate the calendar for the resource itself. Due to source API limitations, we cannot use that approach for Exchange. Instead, we create events on the resource calendars when we migrate the event for the organizer.
For that flow, you should map the room or equipment email in Exchange to the email for a Resource in the Google environment. When we migrate the calendar of the organizer of an event that uses that room or equipment, we will map the attendee email to the Google Resource email. We will then write the event to the Resource calendar explicitly.
|Filters that don't have Google equivalents.|
The following actions and conditions do not have an equivalent mapping in Gmail.
Actions: Forward as attachment to recipient; Permanent delete; Send SMS alert to recipient; Server reply with message; Stop processing rules.
Conditions: Category; Flagged for action; From connected account; Importance; Is approval request; Is automatic forward; Is automatic reply; Is encrypted; Is meeting request; Is meeting response; Is non delivery report; Is permission controlled; Is read receipt; Is signed; Is voicemail; Item class; Message classification; Not sent to me; Sensitivity; Sent cc me; Sent only to me; Sent to me; Sent to or cc me; Within date range
|Link correction - non Google-native files||Link correction within non Google-native files is not supported.|
Transformer maintains a link correction dictionary for all objects migrated, which can be exported from the software. This dictionary can be used post-migration to identify and repair broken links.
AppBridge will be releasing a limited non Google-native file link correction feature in an upcoming build. Please contact firstname.lastname@example.org if you have any questions about this feature.