Home > Gmail Related Codes
Export to PDFGmail Related Codes
GM-AddressOrGroupNameOfGroupIsInvalid
Issue:
The object failed in the migration with the following error:
- GM-AddressOrGroupNameOfGroupIsInvalid
Details:
Failed to create the new Google Group in the destination because the group name or email address is invalid.
Recommendations:
The Google group name can be up to 73 characters and the address up to 64. Please shorten the group name in Exchange Online and/or the destination group address in the project mapping, then try again.
GM-AdminAccountIsNotGroupAdmin
Issue:
The email failed in the migration with the following error:
- GM-AdminAccountIsNotGroupAdmin
Details:
Failed to create the mail in the destination because the destination Admin account does not have the Groups Admin role.
Recommendations:
Assign the Groups Admin role to the destination Admin account, and rerun the migration job.
GM-AdminAccountLackOfAliasPermission
Issue:
The mailbox alias failed in the migration with the following error:
- GM-AdminAccountLackOfAliasPermission
Details:
The destination Admin account lacks sufficient permissions to migrate mailbox aliases. If the destination user in the mapping has the Admin role, the destination Admin account also requires the Super Admin role.
Recommendations:
Grant the destination Admin account sufficient permissions and the Super admin role if required, then rerun the migration job.
GM-AdminAccountLackOfPermissionCalendar
Issue:
The calendar item failed in the migration with the following error:
- GM-AdminAccountLackOfPermissionCalendar
Details:
The destination Admin account does not have sufficient permissions to create the calendar item.
Recommendations:
Grant the destination Admin account with the “Make changes to events” permission to the calendar by referring to the user guide. Then, rerun the migration job.
GM-AdminAccountLackOfPermissionGroup
Issue:
The permission failed in the migration with the following error:
- GM-AdminAccountLackOfPermissionGroup
Details:
Failed to create the member in the destination because the destination Admin account does not have sufficient permissions to create the member.
Recommendations:
Grant the destination Admin account with the “Groups > Update & Read” permission to the group by referring to the user guide. Then, rerun the migration job.
GM-AdminAccountPermissionInsufficient
Issue:
The migration job failed with the following error:
- GM-AdminAccountPermissionInsufficient
Details:
The Admin account in the destination app profile does not have sufficient permissions to retrieve destination shared drives.
Recommendations:
Grant the Admin account with sufficient permissions by referring to the user guide. Then, rerun the migration job.
GM-AliasHasBeenUsed
Issue:
The item failed in the migration with the following error:
- GM-AliasHasBeenUsed
Details:
Another destination mailbox is currently using the alias.
Recommendations:
Check if the destination user needs the mailbox alias or use another alias for the current mailbox.
GM-AliasIsInvalid
Issue:
The item failed in the migration with the following error:
- GM-AliasIsInvalid
Details:
Failed to add the alias to the destination user mailbox or Google Group. The domain you configured in the user mapping either does not exist in the destination tenant or is a user alias domain.
Recommendations:
Make sure the user mapping is configured to the correct user domain in the destination tenant. Then, rerun the migration job.
GM-CalendarFolderNameEmpty
Issue:
The item failed in the migration with the following information:
- GM-CalendarFolderNameEmpty
Details:
The source calendar folder name only consists of invalid characters. Fly will remove the invalid characters from the folder name during the migration. In this case, the calendar folder name will be empty, and the folder cannot be created at the destination.
Recommendations:
Rename the source calendar folder and run an incremental or “Retry error objects” migration job to resolve this issue.
GM-CalendarFolderNotFound
Issue:
The calendar folder permission failed in the migration with the following error:
- GM-CalendarFolderNotFound
Details:
The calendar folder cannot be found in the destination.
Recommendations:
Check whether the calendar folder exists in the destination:
-
If the calendar folder does not exist, manually create it in the destination, then run an incremental or “Retry error objects” migration job.
-
If the calendar folder exists, run an incremental or “Retry error objects” migration job.
GM-CannotMigrateThisRule
Issue:
The rule failed in the migration with the following error:
- GM-CannotMigrateThisRule
Details:
Some conditions or actions in this rule are not supported for cross-platform migration.
Recommendations:
Refer to the support list for properties supported for migration.
GM-ConnectionLackOfScopeAlias
Issue:
The mailbox alias failed in the migration with the following error:
- GM-ConnectionLackOfScopeAlias
Details:
The Google service account lacks the scope for alias migration.
Recommendations:
Refer to the user guide to add the missing scope to the Google service account and rerun the migration job.
GM-ConsumerConnectionPermissionInsufficient
Issue:
The migration failed with the following error:
- GM-ConsumerConnectionPermissionInsufficient
Details:
The service account in the destination app profile does not have sufficient permissions.
Recommendations:
Grant sufficient permissions to the service account by referring to the user guide. Then, rerun the migration job.
GM-ContactAttachmentCorrupted
Issue:
The contact failed in the migration with the following error:
- GM-ContactAttachmentCorrupted
Details:
Some attachments may be corrupted and Fly was unable to read the attachment data.
Recommendations:
Please upload the attachments again and then re-run the migration.
GM-CreateFilterFailed
Issue:
The user failed in the migration with the following error:
- GM-CreateFilterFailed
Details:
Failed to create the filter in the destination. Some properties cannot be retrieved due to API limitations.
Recommendations:
Refer to the support list for properties supported for migration.
GM-DriveServiceDisabled
Issue:
The folder/file failed in the migration with the following error:
- GM-DriveServiceDisabled
Details:
The destination Drive and Docs service is disabled for users in your organization.
Recommendations:
Enable the Drive and Docs service for users and rerun the migration job.
GM-EmptySourceAttendeeEmailAddress
Issue:
The calendar item failed in the migration with the following error:
- GM-EmptySourceAttendeeEmailAddress
Details:
Some source attendees do not have email addresses.
Recommendations:
Check the item’s attendees and provide any missing email addresses. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-EventFailedDueToInlineAttachments
Issue:
The event failed in the migration with the following error:
- GM-EventFailedDueToInlineAttachments
Details:
Failed to migrate the event due to inline attachments.
Recommendations:
You can reduce inline attachments, select not to migrate attachments, or remove the existing event.
GM-EventICalUidIsNull
Issue:
The item failed in the migration with the following information:
- GM-EventICalUidIsNull
Details:
The object is failed since the event does not have a valid ICalUID which is required for an event object.
GM-FilterCanNotSetEmailForwarding
Issue:
The rule failed in the migration with the following error:
- GM-FilterCanNotSetEmailForwarding
Details:
Failed to create the filter in the destination because the mail is not configured as a forwarding address in the destination.
Recommendations:
Add this mail to the forwarding list and rerun the migration job.
GM-FilterCategoryNotSupported
Issue:
The filter is skipped in the Gmail migration report with the following information:
- GM-FilterCategoryNotSupported
Details:
Filters with the action Categorize as are not supported in the migration.
GM-FilterConditionNoSeparator
Issue:
The filter failed in the Gmail migration report with the following error:
- GM-FilterConditionNoSeparator
Details:
This error occurs in the following situations:
-
There is no separator between email addresses in the From or To rule.
-
The separator between email addresses in the From or To rule is not supported in the migration.
Recommendations:
Manually create email rules in the destination after the migration.
GM-FilterDeleteFailed
Issue:
The rule failed in the migration with the following error:
- GM-FilterDeleteFailed
Details:
Failed to delete the existing filter in the destination by Filter ID.
Recommendations:
Delete the filter in the destination manually. Then, rerun the migration job.
GM-FilterFolderIsSystemFolder
Issue:
The object failed in the migration with the following error:
- GM-FilterFolderIsSystemFolder
Details:
The destination does not support using system folders as the target folder for the Move or Copy operation.
Recommendations:
Select non-system folders as the target folder. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-FilterFolderNotFound
Issue:
The object failed in the migration with the following error:
- GM-FilterFolderNotFound
Details:
The target folder for the Move or Copy operation cannot be found by the Folder ID in the destination.
Recommendations:
Ensure the target folder exists in the destination. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-FilterFromToCanNotParsed
Issue:
The From or To filter failed in the Gmail migration report with the following error:
- GM-FilterFromToCanNotParsed
Details:
The filter cannot be migrated when the From or To filter condition value meets one of the following situations:
-
The From or To filter condition value contains these symbols or keywords: “ - “, “ +“, “ !”, ” && “, “ & “, ” and “, “ AROUND “, ;, ,, from:, to:, cc:, bcc:, subject:, list:, after:, before:, older:, newer:, older_than:, newer_than:, deliveredto:, filename:, has:, label:, is:, in:, category:, Rfc822msgid:, larger:, smaller:, and size:. (Note that symbols or keywords that are quoted by double quotes (“ “) have spaces before and/or after them.)
-
The From or To filter condition value contains email addresses and uses the fuzzy search.
-
The email addresses in the From or To filter condition begin with { or ‘.
-
The From or To filter condition uses the fuzzy search, and there is a keyword beginning or ending with {, [, (, <, ‘, or “.
Recommendations:
Manually create email rules in the destination after the migration.
GM-FilterInvalidCondition
Issue:
The From or To filter failed in the Gmail migration report with the following error:
- GM-FilterInvalidCondition
Details:
The From or To filter condition value contains cc:, bcc:, from:, or to:. In this case, the filter cannot be migrated.
Recommendations:
Manually create email rules in the destination after the migration.
GM-FilterMultipleForwardRecipients
Issue:
The rule failed in the migration with the following error:
- GM-FilterMultipleForwardRecipients
Details:
The source rule includes multiple forwarding recipients, but the destination Gmail filter can only support one recipient.
Recommendations:
Reduce the number of recipients. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-FilterNeverSpamNotSupported
Issue:
The filter is skipped in the Gmail migration report with the following information:
- GM-FilterNeverSpamNotSupported
Details:
Filters with the action Never send it to Spam are not supported in the migration.
GM-FilterQueryCanNotParsed
Issue:
The filter failed in the Gmail migration report with the following error:
- GM-FilterQueryCanNotParsed
Details:
The keywords or symbols in the Subject, Has the Words, or Doesn't have rule “ -“, “ +“, “ !”, ” && “, “ & “, “ AROUND “, from:, to:, cc:, bcc:, subject:, list:, after:, before:, older:, newer:, older_than:, newer_than:, deliveredto:, filename:, has:, label:, is:, in:, category:, Rfc822msgid:, larger:, smaller:, and size:. (Note that symbols or keywords that are quoted by double quotes (“ “) have spaces before and/or after them.)
In this case, the filter cannot be migrated.
Recommendations:
Manually create email rules in the destination after the migration.
GM-FilterStarNotSupported
Issue:
The filter is skipped in the Gmail migration report with the following information:
- GM-FilterStarNotSupported
Details:
Filters with the action Star it are not supported in the migration.
GM-FilterUnsupportedNegativeCondition
Issue:
The From or To filter failed in the Gmail migration report with the following error:
- GM-FilterUnsupportedNegativeCondition
Details:
The From or To filter condition value begins with -, +, or !. In this case, the filter cannot be migrated.
Recommendations:
Manually create email rules in the destination after the migration.
GM**-**FocusTimeNotSupported
Issue:
The item failed in the Gmail migration report with the following error:
- GM-FocusTimeNotSupported
Details:
The focus time items are not supported in Gmail Migration due to Microsoft API limitations.
GM-FolderNameContainsInvalidCharacter
Issue:
The object is failed in the migration with the following information:
- GM-FolderNameContainsInvalidCharacter
Details:
The source folder name only consists of carets (^), while carets are not supported in Gmail label names. Fly will remove carets from the source folder name during the migration. In this case, the source folder name will be empty, and the folder cannot be created at the destination.
Recommendations:
Rename the source calendar folder and run an incremental or “Retry error objects” migration job to resolve this issue.
GM-GGSharedDriveNotExist
Issue:
The email failed in the migration with the following error:
- GM-GGSharedDriveNotExist
Details:
The shared drive configured in the migration mapping does not exist in the destination.
Recommendations:
Please check the related SharePoint Online to Google Drive migration report for details.
GM-GoogleAPIResponseFailed
Issue:
The object failed in the migration with the following error:
- GM-GoogleAPIResponseFailed
Details:
An unexpected error occurred while processing your request.
Recommendations:
Try running a “Retry error objects” migration job later to resolve this issue. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.
GM-GoogleApiInternalError
Issue:
The object failed in the migration with the following error:
- GM-GoogleApiInternalError
Details:
An unknown error occurred while migrating the object.
Recommendations:
Try running the migration job later. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.
GM-GoogleAPITransientError
Issue:
The object failed in the migration with the following error:
- GM-GoogleAPITransientError
Details:
An error occurred while migrating the object.
Recommendations:
Try running a “Retry error objects” migration job later to resolve this issue.
GM-GoogleAPIUnavailableTemporary
Issue:
The object failed in the migration with the following error:
- GM-GoogleAPIUnavailableTemporary
Details:
Your request has been throttled by Google due to frequent requests.
Recommendations:
Try running a “Retry error objects” migration job later to resolve this issue. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.
GM-GoogleApiUnknownError
Issue:
The object failed in the migration with the following error:
- GM-GoogleApiUnknownError
Details:
An unknown error occurred while processing your request.
Recommendations:
Try running a “Retry error objects” migration job later to resolve this issue. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.
GM-GoogleCalendarAPIDisabled
Issue:
The calendar failed in the migration with the following error:
- GM-GoogleCalendarAPIDisabled
Details:
The Google Calendar API is not enabled in the project.
Recommendations:
Enable the Google Calendar API in Google APIs for the project. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-GoogleDriveAPIDisabled
Issue:
The mail/event attachments failed in the migration with the following error:
- GM-GoogleDriveAPIDisabled
Details:
The Google Drive API is not enabled in the project.
Recommendations:
Enable the Google Drive API in Google APIs for the project. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-GooglePeopleAPIDisabled
Issue:
The contact failed in the migration with the following error:
- GM-GooglePeopleAPIDisabled
Details:
The Google People API is not enabled in the project.
Recommendations:
Enable the Google People API in Google APIs for the project. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-GoogleTasksAPIDisabled
Issue:
The task failed in the migration with the following error:
- GM-GoogleTasksAPIDisabled
Details:
The Google Tasks API is not enabled in the project.
Recommendations:
Enable the Google Tasks API in Google APIs for the project. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-GoogleTasksApiQuotaExceeded
Issue:
The task failed in the migration with the following error:
- GM-GoogleTasksApiQuotaExceeded
Details:
The Google Tasks API quota limit has been reached.
Recommendations:
Wait for the quota to reset or increase the quota in Google Cloud Console, then rerun the migration job.
GM-GroupHasDomainMember
Issue:
The group failed in the Gmail migration report with the following error:
- GM-GroupHasDomainMember
Details:
All users in the organization is configured as a member/owner/manager of the Google group. In this case, Fly cannot migrate this group to the destination due to Microsoft API limitations.
Recommendations:
Manually create a group in the destination and add members to the group after the migration.
GM-GroupMailContentIsTooLarge
Issue:
The mailbox failed in the migration with the following error:
- GM-GroupMailContentIsTooLarge
Details:
The email is larger than 25 MB and cannot be migrated to the Google Group.
GM-GroupMemberKeyInvalid
Issue:
The group member failed in the migration with the following error:
- GM-GroupMemberKeyInvalid
Details:
The error may occur in the following situations:
-
Situation 1: The user is an external user or does not exist in the destination, and cannot be added to the destination Google Group.
-
Situation 2: The source user or group email address cannot be retrieved.
Recommendations:
For situation 1, check the user mapping for group members and make sure the destination user is correct. Then, run an incremental or “Retry error objects“ migration job to resolve this issue.
If source user is an external or guest user, you can manually enable the Allow members outside your organization setting for the destination Google Group. Then, run an incremental or “Retry error objects“ migration job to resolve this issue.
For situation 2, navigate to Projects > Project mappings > View migration report > Migration error tab in Fly to view the ID of the failed user or group in the Migration errors tab. Then, configure a mapping for the user/group using the user/group ID reported, and rerun the migration job.
GM-GroupMigrationAPIDisabled
Issue:
The object failed in the migration with the following error:
- GM-GroupMigrationAPIDisabled
Details:
The Group Migration API is not enabled in the project.
Recommendations:
Enable the Group Migration API in Google APIs for the project. Then, run an incremental or “Retry error objects“ migration job to resolve this issue.
GM-GSSharedDriveNotExist
Issue:
The email failed in the migration with the following error:
- GM-GSSharedDriveNotExist
Details:
The shared drive for the main Teams site does not exist in the destination.
Recommendations:
Please check the related SharePoint Online to Google Drive migration report for details.
GM-InvalidContactEmail
Issue:
The contact failed in the Gmail migration report with the following error:
- GM-InvalidContactEmail
Details:
The email address of the contact contains invalid characters.
Recommendations:
Make sure there is no invalid character in the email address of the contact. Then, run a “Retry error objects” migration job to resolve this issue.
GM-InvalidEmailAddress
Issue:
The attendee of event failed in the migration with the following error:
- GM-InvalidEmailAddress
Details:
The user/group is mapped to an invalid email address in the user mapping configured in your migration policy
Recommendations:
Replace the destination email address in the user mapping with a valid one, then rerun the migration job.
GM-InvalidEventTimeZone
Issue:
The Outlook calendar failed in the migration with the following error:
- GM-InvalidEventTimeZone
Details:
The source Exchange Online time zone is not supported by Gmail.
Recommendations:
Map the source time zone to a valid time zone in Gmail by configuring the timeZoneMappings=<Source Time Zone ID:Destination Time Zone ID> string, and enter the IDs of the source and destination time zones as the values. For example, timeZoneMappings=<Eastern Standard Time:Africa/Blantyre>.
To map multiple source time zones, add the feature string in the format of timeZoneMappings=<Source Time Zone ID 1:Destination Time Zone ID 1><Source Time Zone ID 2:Destination Time Zone ID 2>. For example, timeZoneMappings=<Eastern Standard Time:America/Grand_Turk><SA Western Standard Time:America/Santiago>.
For the source unsupported time zones’ IDs, you can find them in the comment of the failed calendar items in the job report. For the destination time zones’ IDs, refer to the Timezone column of the Time zones table for details.
GM-InvalidLabelName
Issue:
The item failed in the migration with the following error:
- GM-InvalidLabelName
Details:
The name of the label applied to the item is all invalid characters. In this case, Fly cannot migrate the item to the destination.
Recommendations:
Make sure you select Overwrite conflict resolution in the migration policy and the source label name contains at least one valid character. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-InvalidSourceName
Issue:
The folder failed in the migration report with the following error:
- GM-InvalidSourceName
Details:
The characters of the source folder name are all invalid. In this case, Fly cannot migrate this folder to the destination.
Recommendations:
Modify the source folder name and run a “Retry error objects” migration job to resolve this issue.
GM-InvalidTimeZoneMapping
Issue:
The item failed in the migration with the following error:
- GM-InvalidTimeZoneMapping
Details:
The mapped time zone configured in the timeZoneMappings customized feature in the migration policy is not supported by Exchange.
Recommendations:
Refer to the Timezone column of the Time zones table for the destination time zone’s ID that you can map. Modify the time zone configured in the timeZoneMappings customized feature and run an incremental or “Retry error objects” migration job to resolve this issue.
GM-InvalidTaskAttachment
Issue:
The task failed in the Gmail migration report with the following error:
- GM-InvalidTaskAttachment
Details:
The task attachment does not exist in the source.
GM-InvalidTimeZone
Issue:
The Gmail calendar event failed in the Gmail migration report with the following error:
- GM-InvalidTimeZone
Details:
The error indicates that the source Gmail time zone is not supported by Exchange.
Recommendations:
Map the source time zone to a valid time zone in Exchange by configuring the timeZoneMappings=<Source Time Zone ID:Destination Time Zone ID> feature string in the Customized Features section of the migration policy, and entering the IDs of the source and destination time zones as the values. For example, timeZoneMappings=<America/Grand_Turk:Eastern Standard Time>.
To map multiple source time zones, add the feature string in the format of timeZoneMappings=<Source Time Zone ID 1*:Destination Time Zone ID 1><Source Time Zone ID 2:**Destination Time Zone ID 2>*. For example, timeZoneMappings=<America/Grand_Turk:Eastern Standard Time><America/Santiago:SA Western Standard Time>.
For the source unsupported time zones’ IDs, you can find them in the comment of the failed calendar items in the job report. For the destination time zones’ IDs, refer to the Timezone column of the Time zones table for details.
GM-ItemNotFound
Issue:
The label/event failed with the following error:
- GM-ItemNotFound
Details:
The label/event cannot be found in the destination.
Recommendations:
Run an incremental or “Retry error objects” migration job using this migration policy.
GM-LabelNameInvalid
Issue:
The object failed in the migration with the following error:
- GM-LabelNameInvalid
Details:
The label name you entered is invalid. By default, we treat ”/“ as a character that separates labels.
Recommendations:
Update the label name and ensure that the label does not consist solely of separator characters. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-LackOfScopeWhenUpdateGroupPrivacy
Issue:
The object failed in the migration with the following information:
- GM-LackOfScopeWhenUpdateGroupPrivacy
Details:
Failed to update the Group privacy because the Google service account lacks the required scope: https://www.googleapis.com/auth/apps.groups.settings.
Recommendations:
Please add this scope to the service account to grant sufficient permissions.
GM-MailContentIsTooLarge
Issue:
The object failed in the migration with the following information:
- GM-MailContentIsTooLarge
Details:
The email is larger than 50 MB, and you do not select the checkbox in the migration policy to migrate large email. In this case, the email cannot be migrated.
Recommendations:
Select the Migrate email attachments to Google Drive for the destination user mailbox option in your migration policy. Then, run an incremental or “Retry error objects” migration job to resolve this issue. Note that if the email’s large size is mainly due to embedded content (such as inline images), neither the email nor its attachments can be migrated, even with this option enabled.
GM-MappingIsInvalid
Issue:
The object failed in the migration with the following error:
- GM-MappingIsInvalid
Details:
Failed to migrate permissions for a source internal user. The user is either mapped to a non-existent user/group, or the source user's email address cannot be found in the destination organization.
Recommendations:
Configure a user mapping for the user and map to an existing destination user/group. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-MemberIsRestricted
Issue:
The member failed in the migration with the following error:
- GM-MemberIsRestricted
Details:
Failed to add the member to the destination Google Group because the Google Group settings restrict this member.
Recommendations:
Please review and update group settings, then rerun the migration job.
GM-MembershipQueryFieldNotFound
Issue:
The dynamic group or membership rule failed in the migration with the following error:
- GM-MembershipQueryFieldNotFound
Details:
The destination tenant does not have a custom attribute with the same name as the field in the source dynamic group membership rule.
Recommendations:
Please ensure a custom attribute with the same name exists in the destination and then rerun the incremental job.
GM-MembershipQueryInvalidCategoryName
Issue:
The dynamic group or membership query failed in the migration with the following error:
- GM-MembershipQueryInvalidCategoryName
Details:
The category of matched field in destination has a numeric name, which is invalid in membership queries.
Recommendations:
Please remove this field, create it in a category with non-numeric name, and then run the incremental job.
GM-MembershipQueryMatchMultipleFields
Issue:
The dynamic group or membership rule failed in the migration with the following error:
- GM-MembershipQueryMatchMultipleFields
Details:
Multiple custom attributes sharing the same name as the field in the source dynamic group membership rule were found in the destination. Fly cannot accurately map the source field to a single destination custom attribute.
Recommendations:
Please review the custom attributes with the same name in the destination, ensure that only one remains, and then rerun the incremental job.
GM-MembershipQueryNotSupported
Issue:
The dynamic group or membership rule failed in the migration with the following error:
- GM-MembershipQueryNotSupported
Details:
The membership rule used by the source dynamic group is not supported in the migration.
Recommendations:
It is recommended to manually create the dynamic group or configure the membership query in the destination.
GM-MigrateAttachmentFailed
Issue:
The email/event failed in the migration with the following error:
- GM-MigrateAttachmentFailed
Details:
An error occurred while migrating the email/event attachments.
Recommendations:
Check the comments of the failed attachments in the migration report. After you fix the errors, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-MigrationFileNoResponse
Issue:
The object failed in the migration with the following error:
- GM-MigrationFileNoResponse
Details:
No response from Google API.
Recommendations:
You can try again later. If the error persists, contact Support and provide the migration mapping information and job ID to analyze the error.
GM-ModifyContactGroupMembersFailedDueToApi
Issue:
The object failed in the migration with the following error:
- GM-ModifyContactGroupMembersFailedDueToApi
Details:
Failed to modify members in this contact group due to a Google API issue.
Recommendations:
Try running a “Retry error objects” migration job to resolve this issue.
GM-MultipleSameNameSharedDrive
Issue:
The migration job failed with the following error:
- GM-MultipleSameNameSharedDrive
Details:
There are multiple shared drives with the same name in the destination.
Recommendations:
Make sure the destination shared drive to which you want has a unique name.
GM-NeedFolderMapping
Issue:
The folder failed in the Gmail migration report with the following error:
- GM-NeedFolderMapping
Details:
If you access the source Gmail mailbox via Outlook that uses the IMAP protocol, the error may occur in the following situations:
-
Situation 1: By default, when migrating subfolders of Gmail system folders, and the language of the source Gmail mailbox is English, Chinese, Japanese, French, German, Swedish, Arabic, Spanish, or Portuguese, the subfolder can be migrated because Fly can recognize the source system folder where the subfolder resides and can recognize which destination system folder the subfolder will be migrated to.
But if the language of the source mailbox is not any of the languages above, the subfolder cannot be migrated because Fly cannot recognize the source system folder where the subfolder resides and cannot recognize which destination system folder the subfolder will be migrated to.
-
Situation 2: The folder is a custom top-level folder whose folder name contains a “/”. The custom top-level folder cannot be migrated because Fly cannot recognize whether the folder is a subfolder or a top-level folder.
Recommendations:
Based on the cases above, you need to configure folder name mappings for the folders before the migration. Refer to the following instructions to configure folder name mappings:
-
For situation 1, the system folders that Fly can map are Chats, Drafts, Important, Sent, Spam, Starred, Scheduled, and Trash.
You can add the folderMappings=<Source Chats Name:Chats><Source Drafts Name:\Drafts><Source Important Name:Important><Source Sent Name:Sent><Source Spam Name:Spam><Source Starred Name:Starred><Source Scheduled Name:Scheduled><Source Trash Name:Trash> feature string in the Customized Features section of the migration policy, and enter the source folder names in the corresponding language as the values. For example, folderMappings=<채팅보관함:Chats><임시보관함:\Drafts><중요편지함:Important><보내편지함:Sent><스팸함:Spam><별표편지함:Starred><예약됨:Scheduled><휴지통:Trash>.
-
For situation 2, you can add the folderMappings=<Partial name of source folder:Destination folder name> feature string in the Customized Features section of the migration policy.
Navigate to Projects > Project mappings > View migration report > Migration error tab in Fly to view the comment of the failed folder in the Migration errors section. Enter the source folder name reported in the comment as the source value, and enter the same value as the destination folder name. For example, the source failed custom top-level folder name is [Gmail]/CustomA/CustomB and the folder name reported in the comment is CustomA, enter folderMappings=CustomA:CustomA.
To map multiple custom top-level folders, add the feature string in the format of folderMappings=<Partial name of source folder 1:Destination folder name 1><Partial name of source folder 2:Destination folder name 2>. For example,
folderMappings=<CustomA:CustomA><CustomB:CustomB>.
GM-OrganizerNotInternalInDestination
Issue:
The organizer of event failed in the migration with the following error:
- GM-OrganizerNotInternalInDestination
Details:
Cannot create the meeting in the destination because the mapped organizer is not an internal user in the destination tenant.
Recommendations:
Correct the mapping in the migration project, and rerun an incremental migration job or a “Retry error objects” migration job.
GM-OutOfOfficeNotSupported
Issue:
The item failed in the Gmail migration report with the following error:
- GM-OutOfOfficeNotSupported
Details:
The out of office event is not supported in Gmail Migration due to Microsoft API limitations.
GM-OwnerCannotBeGroup
Issue:
The owner failed in the migration with the following error:
- GM-OwnerCannotBeGroup
Details:
The destination mapping points to a group, and a group cannot be assigned as an owner.
Recommendations:
Correct the mapping in the migration project, and rerun an incremental migration job or a “Retry error objects” migration job.
GM-ParentFolderNotFound
Issue:
The item failed in the migration with the following error:
- GM-ParentFolderNotFound
Details:
The parent folder of the migrated item attachment does not exist.
Recommendations:
Run a “Retry error objects” migration job to resolve this issue.
GM-RateLimitExceeded
Issue:
The item failed in the migration with the following error:
- GM-RateLimitExceeded
Details:
Google has throttled your request due to frequent requests.
Recommendations:
Run a “Retry error objects” migration job after a few hours to resolve this issue.
GM-ReferenceAttachmentUnsupported
Issue:
The task failed in the migration with the following error:
- GM-ReferenceAttachmentUnsupported
Details:
This task contains reference attachments with no actual content.
Recommendations:
Remove the attachments from the task and upload them again. Then, rerun the migration job.
GM-RequestCanceledDueToTimeOut
Issue:
The object failed in the migration with the following error:
- GM-RequestCanceledDueToTimeOut
Details:
Request timeout.
Recommendations:
Run an incremental or “Retry error objects” migration job later to resolve this issue.
GM-RequestFailedDueToServerTemporaryError
Issue:
The object failed in the migration with the following error:
- GM-RequestFailedDueToServerTemporaryError
Details:
The server encountered a temporary error and was unable to complete your request.
Recommendations:
Try running a ”Retry error objects” migration job after a few minutes to resolve this issue.
GM-ReservedLabelName
Issue:
The object failed in the migration with the following information:
- GM-ReservedLabelName
Details:
The folder name is the same as a reserved label name in Gmail. In this case, the folder cannot be created at the destination.
Recommendations:
Rename the source folder or configured the EmailFolderAddSuffix=true customized feature string in the migration policy to avoid conflict. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-SelfMembershipDenied
Issue:
The object failed in the migration with the following information:
- GM-SelfMembershipDenied
Details:
The request attempted to add the group as its own member, which is not allowed.
Recommendations:
Please update the mapping and try again.
GM-ServiceAccountPermissionInsufficient
Issue:
The object failed in the migration with the following information:
- GM-ServiceAccountPermissionInsufficient
Details:
The service account in the destination app profile lacks sufficient permissions.
Recommendations:
Grant sufficient permissions to the service account by referring to the user guide. Then, rerun the migration job.
GM-SharedDriveFileLimitExceeded
Issue:
The item attachments failed in the migration with the following error:
- GM-SharedDriveFileLimitExceeded
Details:
The number of files created in the destination shared drive has exceeded the limit of 500,000.
Recommendations:
You can migrate item attachments to different shared drives.
GM-SharedDriveNotExist
Issue:
The event failed in the migration with the following information:
- GM-SharedDriveNotExist
Details:
The shared drive configured in the migration policy does not exist in the destination.
Recommendations:
Ensure the configured shared drive exists in the destination and has at least one manager. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-SkipDuplicateMail
Issue:
The email skipped in the migration with the following error:
- GM-SkipDuplicateMail
Details:
The source contained multiple emails with the same message ID. Since message IDs are unique to each email, only one was migrated, and the duplicates were skipped.
GM-SourceCalendarMigratedFromGoogleCalendar
Issue:
The calendar item failed in the migration with the following error:
- GM-SourceCalendarMigratedFromGoogleCalendar
Details:
This may happen when an item was previously migrated from Google Calendar and is now being migrated back.
Recommendations:
Remove the calendar item and create a new one. Then, rerun the migration job.
GM-SubItemsNumLimitExceeded
Issue:
The folder failed in the migration with the following error:
- GM-SubItemsNumLimitExceeded
Details:
The number of files and subfolders in the destination shared drive has exceeded Google’s allowed limit of 500000.
Recommendations:
Create multiple project mappings to migrate item attachments to different shared drives. Then, run an incremental or “Retry error objects” migration to resolve this issue.
GM-TaskNotesExceedsLimit
Issue:
The task failed in the migration with the following error:
- GM-TaskNotesExceedsLimit
Details:
The task notes exceed Google’s limit of 8192 characters.
Recommendations:
Modify the source task notes to no more than 8192 characters. Then, run an incremental or “Retry error objects” migration job to resolve this issue.
GM-TitleExceedsLimit
Issue:
The task failed in the migration with the following error:
- GM-TitleExceedsLimit
Details:
The task title exceeds Google’s limit of 1024 characters.
Recommendations:
Modify the source task title to not more than 1024 characters. Then, run an incremental or “Retry error objects“ migration job to resolve this issue.
GM-UnableToAccessDestinationSharedDrive
Issue:
The migration failed with the following error:
- GM-UnableToAccessDestinationSharedDrive
Details:
There is no available manager to access the destination shared drive.
Recommendations:
Grant the Admin account Manager access to the destination shared drive and rerun the migration job.
GM-UserRateLimited
Issue:
The object failed in the migration with the following error:
- GM-UserRateLimited
Details:
Google has throttled your request due to frequent requests.
Recommendations:
When throttling occurs in Google, it may take minutes or hours to ease up the throttling. We recommend that you wait a bit before you run a “Retry error objects” migration job after a few hours to resolve this issue.