AppBridge Documentation : Review features and watch points - G Suite to G Suite Migration

In the review phase of a G Suite (formerly Google Apps) migration using Transformer, you will:

Supported Features

FeatureSupportedWatch Points
Gmail
Copy emailYesRefer to watch points regarding email throughput and invalid data header issue.
Copy labelsYes 
Copy label structureYes 
Copy starsYes*Stars - Email
Copy attachmentsYes 
Copy trashYes 
Copy spamYes 
Copy chat contactsNoChat migration is not supported by the Google API
Copy chat historyNo 
Copy signaturesYes 
Copy vacation responder settings (OOO)Yes 
Copy FiltersYes 
Copy forwarding settingsYes*External domain forwarding is not supported
Copy "send as" settingsYes*External domain aliases are not supported
Copy email delegationYes 
Copy IMAP settingsYes 
Copy POP settingsYes 
Mapping - LabelsYes 
Mapping - LinksComing soonLink Correction - Email
Filtering - EmailYes 
Filtering - LabelsYes 
Google Contacts 
Copy personal contactsYes 
Copy personal contact groupsYes 
Mapping - ContactsYes 
Google Calendar 
Copy primary calendarsYes 
Copy secondary calendarsYes 
Copy external calendar eventsYes 
Copy calendar permissionsYesUsers 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.
Copy calendar settingsYes 
Copy calendar event settingsYes 
Copy recurring eventsYes 
Copy calendar event attachmentsYesCalendar Attachments are linked to Google Drive files, and permissions are granted to event attendees.
Copy calendar color settingsYes 
Mapping - Calendar attendeesYes 
Filtering - CalendarsYes 
Filtering - Calendar eventsYes 
Google Resources  
Copy Google ResourcesYesResources are provisioned in the target domain and reattached to all events.
Copy Google Resource calendarsYes 
Mapping - ResourcesYes 
Filtering - ResourcesYes 
Google Drive 
Copy unlimited files to a single Google Drive accountYes*Google Drive performance optimization
Copy Google folder structuresYes 
Copy Google native filesYes 
Copy Google native file commentsYesGoogle comments
Copy Google native file revisionsNoRevisions are not supported by the Google API
Copy non Google-native files (.docx, pdf, etc)Yes 
Copy non Google-native file versionsYes 
Copy orphaned filesYes
Copy Google folder and file metadataYesFolders, files, and versions have modified dates and last modified user metadata preserved.
Copy Google Drive sharingYes 
Copy Google sharing for external usersYesInternally owned objects shared with external users
Copy Google sharing for external email addressesYesInternally owned objects shared with external email addresses
Copy externally owned filesYesExternally owned objects shared with internal users
Copy StarsNoStar migration is computationally not possible within reasonable migration timelines.
Link Correction - Google native filesNoLink correction - Google native files
Link Correction - non Google-native filesNoLink correction - non Google-native files
Mapping - User and group sharingYes 
Mapping - Folder and file locationsYes 
Filtering - Folder and file attributesYes 
Google Sites 
Copy Google SitesYes 
Copy Google Sites pagesYes 
Copy Google Sites sharingYes 
Copy Google Sites filesYes 
Mapping - Internal Google Sites linksYesLink correction - Google Sites
Filtering - Google SitesYes 
Google Groups 
Copy Google GroupsYes 
Copy Google Group membershipYes 
Copy Google Group settingsYes 
Copy Google Group email history and archiveNoGoogle Group emails and archives cannot be read through the Google API
Google Tasks 
Google TasksYes 
Google Recurring TasksYes*Only the primary recurring task is migrated
3rd Party Apps 
LicensesN/A3rd party vendors must be contacted to determine license transfers between domains.
Google+
Currently unsupported
Google Keep
Currently unsupported

Watch Points

Watch pointDescriptionBest Practice
Gmail
Throughput - EmailTo 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.
Stars - EmailEmail stars can only be migrated if the source Gmail account has been used by an external application (like the Gmail Android app) at least once in the past. Stars become labels upon connection to an external application.Ensure that users are aware of this limitation prior to starting the production migrations, and that all Gmail accounts that require migration of stars have been connected to external applications.
Link correction - EmailLinks in email messages that point to source Google Drive documents or folders become broken after migration.

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 an email link correction feature in any upcoming build that automatically corrects links in emails to their new target objects. Please contact support@appbridge.io if you have any questions about this feature.

Google Drive
Google Drive performance optimizationA large number of files written to a single Google Drive account can cause significant performance degradation.Transformer provides the ability to migrate unlimited numbers of files to a single Google Drive account without performance degradation. Please review the Shard Sets documentation for configuration details.
Google commentsAdding Google comments sends emails to followers of the files that the comment was added to. Mentions within comments (Format: +username) cause emails to be sent to the mentioned users.Configure email routing rules that disable comment emails to internal users during the production migration. Transformer provides the ability to migrate external mentions in comments, but we recommend disabling this functionality unless your policy allows for external users to receive emails during the migration.
Internally owned objects shared with external users

Internally owned folders and files that have been shared with external users from internal users can be migrated with all external sharing intact.

If sharing with external users is migrated, external users will see migrated objects appear in the "Shared with me" folder. Source objects will still exist in the original location until the source user account is removed or the permissions on the source object are stripped.

Surveyor provides the Permissions by Object report to identify externally shared objects prior to migration. Using this report can help to define a migration and communication strategy to external users with access to objects that will be migrated.

If external sharing must be migrated, it should be migrated during the final incremental execution to avoid providing premature access to external users.

Internally owned objects shared with external email addresses

Internally owned folders and files that have been shared with external email addresses (users that do not have a Google account) from internal users can be migrated, but external users will receive emails during migration.

Transformer can preserve email-based permissions during migration if necessary.

If external email sharing must be migrated, it should be migrated during the final incremental execution to avoid providing premature access to external users.

Externally owned objects shared with internal usersExternally owned folders and files that have been added to internal user Drives should be considered as a potential problem for collaboration.

Surveyor provides the Shared Objects by User Report to identify externally owned objects added to internal user Drives prior to migration. Using this report can help to establish a change management process to inform internal users of which documents will no longer be available post migration, and the external user that owns them.

Transformer provides the ability to migrate externally owned documents to the target domain, but ownership will be transferred to the first user to encounter them during migration.

Link correction - Google native files

Link correction within Google-native files is not supported. Because of this, Google Forms will no longer be linked to response sheets.

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 Google native file link correction feature in an upcoming build. Please contact support@appbridge.io if you have any questions about this feature.

Link correction - non Google-native filesLink 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 support@appbridge.io if you have any questions about this feature.

Google Sites

Link correction - Google Sites

Links present within the scope of the migration are automatically corrected to new values within Google Sites. Links outside the scope of the migration cannot be automatically corrected without a mapping file.Read the URL Maps documentation for details on how to configure link correction of links that are out of scope of the migration.

 

Next: Preparation - G Suite to G Suite Migration