#Exchange Related Codes

#EX-AccessDenied

Issue:

The mailbox failed in the migration with the following error:

Details:

The error may occur when the connection account’s access to EWS in Exchange is denied.

Recommendations:

Check the client access settings and make sure the connection account can access the EWS in Exchange. Refer to the following links for more information on how to control access to EWS for users:

#EX-AccessDeniedToOffice365Group

Issue:

The object failed in the migration with the following error:

Details:

The error indicates that the destination service account or app profile does not have sufficient permissions to create the Microsoft 365 Group in the destination or migrate the object to the destination.

Recommendations:

Make sure the service account or app profile has sufficient permissions, and rerun an incremental migration job or a “Retry error objects” migration job.

#EX-ArchiveMailboxNotFound

Issue:

The mailbox failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

Make sure the archive mailbox is enabled for the destination mailbox. Refer to the for information.

#EX-ArchiveMailboxQuotaIsNotEnough

Issue:

The item failed in the migration with the following error:

Details:

There is no available quota in the destination archive mailbox when migrating the archive mailbox.

Recommendations:

Enable auto-expanding archiving for additional storage space and run several incremental jobs. If the quota of the archive mailbox is not enough, manually delete some data in the destination archive mailbox to release the quota. Make sure the destination Retention policy is disabled during the migration.

#EX-AzureADUnavailable

Issue:

The mailbox failed in the migration with the following error:

Details:

The error may occur when the Active Directory Domain Services (AD DS) of the Exchange server is unavailable.

Recommendations:

Make sure the Active Directory Domain Services (AD DS) of the Exchange server is available, and rerun the migration job later to migrate the failed mailbox.

#EX-CalendarFolderNotFound

Issue:

The calendar permissions failed in the migration with the following error:

Details:

The calendar folder cannot be found in the destination.

Recommendations:

Check if the calendar folder exists in the destination:

#EX-CalendarOccurenceOverlapped

Issue:

The item failed in the Gmail migration job report with the following error:

Details:

The error occurred when the occurrence duration of one recurring calendar item overlapped. For example, the duration of your recurring event is longer than one day, but the recurring frequency is Daily. This event is not supported in the destination Exchange.

Recommendations:

Check the source event, and if possible, shorten the duration for each occurrence to ensure that the duration does not overlap.

#EX-CallsThrottled

Issue:

The item/folder failed in the migration with the following error:

Details:

The error may occur when you migrate many items, which makes the Exchange server busy. In this case, calls to the Exchange server are throttled by Microsoft 365.

Recommendations:

Rerun the incremental migration job later to migrate the failed item/folder.

#EX-CanNotMigrateToHiddenFolder

Issue:

The folder failed in the Gmail migration report with the following error:

Details:

The destination folder with the same name is hidden. In this case, the source folder cannot be migrated to the destination.

Recommendations:

Rename the source folder and run a “Retry error objects” migration job to resolve this issue.

#EX-CanNotReplaceTeamsLink

Issue:

The item failed in the migration with the following error:

Details:

Recommendations:

#EX-CustomAddressHasBeenUsed

Issue:

The email address / mailbox alias failed in the migration with the following error:

Details:

The source email address / mailbox alias is currently being used by another destination mailbox.

Recommendations:

Check if the destination user needs the email address / mailbox alias. If the user needs to use the email address / mailbox alias, ignore the error. If the user does not need to use the email address / mailbox alias, delete it from the user in the Microsoft 365 Exchange admin center and run a “Retry error objects” migration job to resolve the issue.

#EX-DataCorruptionError

Issue:

The item failed in the migration with the following error:

Details:

The error indicates that the source item is corrupted. Fly cannot migrate such items to the destination.

Recommendations:

Here are two options to resolve this issue:

#EX-DeleteItemsFailed

Issue:

The item failed with the following error:

Details:

There is no available quota in the destination Recoverable Items folder, and Fly cannot migrate items in source Deletions folders to the destination mailbox.

Recommendations:

1. Refer to to increase the destination Recoverable Items quota.

2. (Optional) Refer to to execute the Get-MailboxFolderStatistics cmdlet using PowerShell to view the capacity of the Recoverable Items folders.

Sample PowerShell Command for Primary Mailbox:

Get-MailboxFolderStatistics -Identity -FolderScope Recoverable

Sample PowerShell Command for Archive Mailbox:

Get-MailboxFolderStatistics -Identity -FolderScope Recoverable -Archive

#EX-DestinationUserNotFound

Issue:

The item failed in the migration with the following error:

Details:

Recommendations:

#EX-DifferentTenantInAttachmentLabel

Issue:

The email failed in the migration with the following error:

Details:

The email attachment applies a sensitivity label that does not exist in the source tenant. In this case, Fly cannot remove the sensitivity label from the email attachment.

Recommendations:

Here are two options to resolve this issue:

#EX-EmailAddressHasSpecialCharacters

Issue:

The mailbox failed in the migration with the following error:

Details:

The email address of the destination Microsoft 365 Group/distribution list/mail-enabled security group/shared mailbox/dynamic distribution list contains invalid characters or starts with a period. The invalid characters include: ~ ` ! @ $ % ^ & * ( ) + = [ ] {{ }} | \ : ; “ < > ? /. Note that if the destination is a shared mailbox, the email address cannot contain pounds (#) except for the above characters.

Recommendations:

#EX-EmailAddressNotRecognized

Issue:

The rule failed in the migration with the following error:

Details:

The error occurs when Fly cannot retrieve the source users’ email addresses in the rule since the users do not exist in the source.

Recommendations:

#EX-EncryptWithPassword

Issue:

The email failed in the migration with the following error:

Details:

The email contains an attachment encrypted with a password, and you configure the MigrateLabelsForEmailAttachments=1 or MigrateLabelsForEmailAttachments=2 customized feature string in the migration policy to manage the sensitivity label of the attachment. However, Fly cannot manage sensitivity labels of such email attachments due to Microsoft API limitations.

Recommendations:

Remove the MigrateLabelsForEmailAttachments customized feature from the migration policy, or change the customized feature string value to 0 to not manage sensitivity labels of attachments in source emails. Then, run an incremental or “Retry error objects” migration job to resolve this issue.

#EX-ExportItemFailed

Issue:

The item failed in the migration with the following error:

Details:

The error indicates that Fly fails to retrieve the source item.

Recommendations:

You can run an incremental migration job or Retry error objects.

#EX-FailedAddLabel

The email failed in the migration with the following error:

This error indicates that the destination sensitivity label cannot be added to the email. It may occur in the following situations:

1. The destination label does not have the In Outlook, enforce on the following restrictions encryption setting selected.

   

2. The destination label does not have the Encrypt files and emails protection setting selected.

3. The destination connection uses the app profile, and the destination label has the Assign permissions now encryption setting configured, but the label has not been published to all.

   **Recommendations:**

For the above situations 1 and 2, you can edit the label settings, and run an incremental migration job.

For situation 3, publish the destination label to all users/groups, or you can choose to use a service account only for the destination connection.

#EX-FailedSetModerationEnabledOption

Issue:

The setting failed in the migration with the following error:

Details:

Failed to migrate the Group moderators setting of the source object or the Group moderators setting is not configured for the source object. In this case, the Require moderator approval for messages sent to this group setting cannot be enabled for the destination mail-enabled security group.

Recommendations:

Check if the Group moderators setting is configured for the source distribution list.

#EX-FailedSetOwnerApprovalOption

Issue:

The setting failed in the migration with the following error:

Details:

Failed to migrate the owner of the source object or the source object does not have an owner. In this case, the Joining the group setting of the destination mail-enabled security group cannot be configured as Owner approval.

Recommendations:

Check if the source object has an owner.

#EX-FolderNotFound

Issue:

The rule failed in the migration with the following error:

Details:

The error indicates that the folder in this rule cannot be found in the destination. This error may be caused by the following reasons:

Recommendations:

Here are two options to resolve this issue:

#EX-GroupNotDefaultDomain

Issue:

The group failed in the migration with the following error:

Details:

The error appears when you migrate groups in the migration and the destination Microsoft 365 Group does not exist. This error indicates that the destination Group mailbox email domain is not the tenant's default domain and cannot be created.

Recommendations:

#EX-InboxRuleInvalidSourceName

Issue:

The inbox rule failed in the migration with the following error:

Details:

The source rule name only consists of invalid characters. Such rules cannot be migrated to the destination.

Recommendations:

#EX-InboxRulesValidationError

Issue:

The mailbox rule failed in the migration with the following error:

Details:

An error occurred while migrating the mailbox rule.

Recommendations:

Navigate to Projects > Project mappings > View mapping report > Migration error tab in Fly to check the error details of the rule in the comment of the Migration error section. Then, locate the corresponding rule in the source and manually fix the issue based on the error details. For example, in the case of the comment below, the rule failed in the migration because the property value exceeds the maximum allowed length. You need to reduce the property value length in the source.

After fixing, run an incremental or “Retry error objects” migration job to resolve this issue. If this issue persists, contact Support, and provide the migration mapping information and job ID to analyze the error.

#EX-IncorrectDomainName

Issue:

The object failed in the migration with the following error:

Details:

The error indicates that Fly fails to create the shared mailbox/mail-enabled security group/distribution list, or add the mailbox alias using the domain you configured in the migration mapping. The domain does not exist in the destination tenant.

Recommendations:

#EX-IncorrectGroupMember

Issue:

The user/group failed in the migration with the following error:

Details:

The error indicates that the user/group cannot be added to the destination group as a member. This error may occur when the user/group is already a member of the destination group.

Recommendations:

#EX-IncorrectGroupOwner

Issue:

The user/group failed in the migration with the following error:

Details:

The error indicates that the user/group cannot be added to the destination group as an owner. This error may occur when the source user/group is mapped to a distribution list, which cannot be added as the group owner.

Recommendations:

#EX-IncorrectMailboxType

Issue:

The mailbox failed in the migration with the following error:

Details:

The error indicates that the mailbox type you selected for the mailbox in the mapping is incorrect.

Recommendations:

Correct the mapping in the migration project and run the migration again to resolve the error.

#EX-IncorrectPermissionUser

Issue:

The user/group failed in the migration with the following error:

Details:

The error indicates that the user/group cannot be added while migrating object permissions. This error may occur when the user/group is mapped to a contact, which cannot be granted the object permissions.

Recommendations:

Configure a user mapping in the migration policy to map the source user/group to a valid destination user/group, and rerun an incremental migration job or a “Retry error objects” migration job.

#EX-InsufficientPermissionsForGroup

Issue:

The item failed in the migration with the following error:

Details:

The service account or the consent user of the delegated app profile is not the owner of the Microsoft 365 Group. In this case, the item cannot be migrated.

Recommendations:

Add the service account or the consent user of the delegated app profile as the owner of the Microsoft 365 Group. Then, run an incremental or “Retry error objects” migration job to resolve this issue.

#EX-InsufficientPermissionsForImpersonation

Issue:

The item/mailbox failed in the migration with the following error:

Details:

The error indicates that the service account or app profile account does not have the ApplicationImpersonation role to impersonate the mailbox user.

Recommendations:

Make sure the accounts configured in the source and destination connections have the ApplicationImpersonation role. If you do not migrate Microsoft 365 Group mailboxes, distribution groups, or auto-complete lists in the migration, you can grant the Full Access permission to the source connection account without adding the ApplicationImpersonation role.

#EX-InsufficientPrivileges

Issue:

The object failed in the migration with the following error:

Details:

The error indicates that the source/destination service account / custom app profile / custom delegated app profile does not have sufficient permissions.

Recommendations:

Refer to to assign the required permissions to the service account / custom app profile / custom delegated app profile, and rerun an incremental migration job or a “Retry error objects” migration job.

#EX-InternalServerError

Issue:

The item failed in the migration with the following error:

Details:

The error indicates that an internal server error occurs while migrating the item.

Recommendations:

Try accessing the mailbox. Rerun an incremental migration job or a “Retry error objects” migration job when the mailbox can be accessed.

#EX-InvalidCalendarFolderOrInsufficientPrivileges

Issue:

The calendar permissions failed in the migration with the following error:

Details:

The source service account does not have sufficient permissions, or the calendar folder name contains the following invalid characters: / or ****.

Recommendations:

Here are two options to resolve this issue:

#EX-InvalidGroupOwner

Issue:

The item failed in the Gmail or Exchange Online migration report with the following error:

EX-InvalidGroupOwner

Details:

The source group owner is mapped to a destination distribution list/Microsoft 365 Group. Distribution list/Microsoft 365 Group cannot be added as distribution list/Microsoft 365 Group owners.

Recommendations:

Make sure the user mapped for the group owner is not a distribution list/Microsoft 365 Group and run a “Retry error objects” migration job to resolve this issue.

#EX-InvalidLicense

Issue:

The migration failed with the following error:

EX-InvalidLicense

Details:

The user does not have a valid license for this mailbox.

Recommendations:

Assign a valid license to the user and then rerun the migration job.

#EX-InvalidSourceName

Issue:

The folder failed in the Gmail migration report with the following error:

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.

#EX-InvalidToken

Issue:

The folder failed in the incremental migration with the following error:

The Microsoft changelog data used to retrieve the newly created or modified source data is corrupt or invalid. In this case, Fly cannot retrieve the updates in the folder.

Recommendations:

Run a full migration job to try again.

#EX-ItemAlreadyHasAnID

Issue:

The item failed in the migration with the following error:

Details:

At least one item in the same package has already been migrated to the destination and has an ID. In this case, the item cannot be migrated.

Recommendations:

Run an incremental or “Retry error objects” migration job to resolve this issue.

#EX-ItemBatchProcessingStopped

Issue:

The item failed in the migration with the following error:

Details:

The error may occur when you migrate multiple items in a migration job. If some items that are migrated before this item fail to be migrated due to an unknown error, the migration job will fail. In this case, this item cannot be migrated to the destination.

Recommendations:

Contact Support and provide the migration mapping information and job ID to analyze the error.

#EX-LabelNotExist

The email failed in the migration with the following error:

This error indicates that the email cannot be migrated since the source sensitivity label of the item cannot be found. It may occur in the following situations:

Recommendations:

Contact Support and provide the migration mapping information and job ID to get the migration logs. Find the ID of the label in the logs if it has been deleted. Then, configure a label mapping in the migration policy using the label ID to map the source label to another label with the same Assign permissions now or let users decide? setting. Run an incremental migration job with the configured migration policy.

#EX-LabelNotFound

The email failed in the migration with the following error:

This error indicates that the email cannot be migrated since the destination sensitivity label cannot be found. It may occur in the following situations:

1. If you select the Apply same label in the destination option in the migration policy, there is no mapped label in the destination with the same name as the source label. If you select the Apply labels in the destination based on label mappings option in the migration policy, the destination label configured in the label mapping does not exist.

2. The destination label has not been published to the service account.

3. The destination label has the Let users assign permissions when they apply the label encryption setting selected and contains sublabels. This label is not supported.

4. The destination label does not have the File & emails scope configured.

5. If you select the Apply labels in the destination based on label mappings option in the migration policy, but the options selected for the Assign permissions now or let users decide? setting of the source and destination labels in the label mapping are different.

Recommendations:

Refer to the following methods to resolve this issue in different situations, and run an incremental migration job:

1. If you have selected the Apply same label in the destination option in the migration policy, make sure a label with the same name and the same Assign permissions now or let users decide? setting already exists in the destination. If you have selected the Apply labels in the destination based on label mappings option in the migration policy, make sure the destination label configured in the label mapping already exists.

2. Make sure the destination label has been published to the service account of the migrations.

3. Make sure the mapped destination label does not have sublabels.

4. Make sure the mapped destination label has the File & emails scope configured.

5. Make sure the option selected for the Assign permissions now or let users decide? setting of the source and destination labels are the same.

#EX-LabelNotInMapping

The email failed in the migration with the following error:

The error occurs when you select to use a label mapping to manage sensitivity labels for the source email in the migration, but the sensitivity label applied to the source email does not match the source sensitivity label configured in the selected label mapping.

Recommendations:

Configure a label mapping for the source sensitivity label and use the label mapping to run an incremental or “Retry error objects” migration job.

#EX-LackExchangeAdminRole

Issue:

The migration failed with the following error:

Details:

The error indicates that Exchange Online PowerShell is unavailable since the app of the Fly app profile does not have the Exchange administrator role.

Recommendations:

You can refer to the instructions below to assign this role, and run the migration again to try again.

To assign the Exchange administrator role to the app, refer to the following steps:

1. Log in to Microsoft Entra admin center (or Azure portal) and navigate to Microsoft Entra ID.

2. Click Roles & admins (or Roles and administrators) in the left pane, and click Exchange Administrator.

   

3. On the Assignments page, click Add assignments. The Add assignments panel appears.

4. Enter the app name in the search box to search for the app to which you want to assign the role. (The name of the Fly app is AvePoint FLY)

   

5. Select the app, and click Add to assign the role. Note that the assigned role will take effect in about 30 minutes.

#EX-LackManageAsAppRole

Issue:

The object failed in the migration with the following error:

Details:

The error indicates that the custom app you use in the destination app profile does not have the Office 365 Exchange Online API > Exchange.ManageAsApp permission to create the shared mailbox/Microsoft 365 Group/distribution list/mail-enabled security group in the destination or migrate the Send As, Send on Behalf, and Full Access permissions to the destination.

Recommendations:

Assign the Office 365 Exchange Online API > Exchange.ManageAsApp permission to the destination custom app, and rerun an incremental migration job or a “Retry error objects” migration job.

#EX-LegacyExchangeDNHasBeenUsed

Issue:

The mailbox failed in the migration with the following error:

Details:

The source X500 email address is currently being used by another destination user.

Recommendation:

Check which destination user occupies the source X500 email address, remove the occupied X500 email address from the destination user in the Exchange admin center, and rerun the migration job.

#EX-LegacyExchangeDNIsEmpty

Issue:

The mailbox failed in the migration with the following error:

Details:

The source mailbox does not have an X500 email address or the source tenant has expired.

Recommendation:

Make sure the source mailbox has an X500 email address and the source tenant is available. Then rerun the migration job.

#EX-MailboxMoveInProgress

Issue:

The mailbox failed in the migration with the following error:

Details:

The error indicates that the mailbox is being moved to a different mailbox store or server when Fly migrates it. This can also indicate that the mailbox is on another server or mailbox database.

Recommendations:

Run an incremental migration job later to migrate the failed mailbox.

#EX-MailboxNotFound

Issue:

The mailbox/item failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-MailboxQuotaIsNotEnough

Issue:

The item failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-MailboxStoreUnavailable

Issue:

The folder/item failed in the migration with the following error:

Details:

The error indicates that the mailbox is unavailable due to the exception of the mailbox database. For example, the mailbox database is offline or shut down.

Recommendations:

Run an incremental or “Retry error objects” migration job to resolve this issue.

#EX-MailSizeExceedLimit

Issue:

The item failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-MimeContentInvalid

Issue:

The item failed in the Gmail migration report with the following error:

Details:

The error occurs in the following situations:

Recommendations:

For situation 2, manually forward the source mail to the destination.

#EX-MIPAccessDeniedError

Issue:

The email failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-MIPLabelMismatchedWithTenant

Issue:

The item failed in the migration with the following error:

Details:

The error occurs when the email cannot be decrypted by the source tenant since the sensitivity label of the email is applied by a user in another tenant.

Recommendations:

#EX-MIPNoSuperUser

Issue:

The item failed in the migration with the following error:

Details:

This error occurs when the source or destination service account does not have the super user role to manage sensitivity labels.

Recommendations:

Assign the super user role to both source and destination service accounts. Refer to for details.

#EX-NoDestinationCASProcessRequest

Issue:

The item/folder failed in the migration with the following error:

Details:

The error indicates that the item/folder cannot be migrated because there are no Client Access Servers in the destination to process the request.

Recommendations:

Run an incremental migration job later to migrate the failed item/folder.

#EX-PermissionUserOrGroupTypeIsNotSupport

Issue:

The calendar permissions failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-PrimaryMailboxQuotaIsNotEnough

Issue:

The item failed in the migration with the following error:

Details:

There is no available quota in the destination mailbox.

Recommendations:

Increase the storage quota of the destination mailbox and make sure the source mailbox size does not exceed the destination available quota to contain the source data.

#EX-PublishMeetingFailed

Issue:

The item failed in the migration with the following error:

Details:

The meeting item has been migrated to the destination, but if the meeting participants contain external users, when the external user clicks the destination meeting link to attend the meeting, they will wait in the lobby until the meeting organizer allows them to enter the meeting.

This error indicates that the source meeting link failed to be published to everyone.

This error occurs when you do not select the Replace meeting links with the destination information option in the migration policy and you add the ChangeTeamsMeetingScopeAsEveryone=true customized feature string to publish the meeting link to everyone. However, you only use the service account authentication for the source tenant, or the source app profile does not have sufficient permissions, so the source meeting link cannot be published to everyone.

Recommendations:

Make sure you have configured an app profile for the source tenant, and the app has the permissions below to publish the source meeting link:

#EX-RecoverableFolderNotFound

Issue:

The folder failed in the migration with the following error:

Details:

The error may occur in the following situations:

Recommendations:

#EX-RecoverableItemsFolderQuotaIsNotEnough

Issue:

The item failed in the migration with the following error:

Details:

There is no available quota in the destination Recoverable Items folder. For example, after running a full migration job, you run multiple full migration jobs with the Overwrite conflict resolution, and the Single item recovery and/or In-Place Hold, and/or Litigation Hold settings are enabled in the destination. In this situation, the destination conflicting items in each job will be deleted and stored in the Recoverable Items folder, which may result in this issue.

Recommendations:

Refer to the following steps to resolve this issue:

1. Refer to to execute the Start-ManagedFolderAssistant cmdlet using PowerShell to release the quota of the specified folder in this cmdlet.

2. Sample PowerShell Command:

Start-ManagedFolderAssistant -Identity user@contoso.com

3. Check if the capacity of the Recoverable Items folders has been released. If the capacity has been released, you can refer to the following instructions to rerun the migration job to resolve the issue:

   • If you do not need to use Overwrite conflict resolution for the migration, select Skip conflict resolution in the migration policy to avoid deleting the destination item to the Recoverable Items folders.

   • If you need to use Overwrite conflict resolution for the migration, we recommend that you disable both litigation hold and single item recovery on related destination mailboxes.

   • If litigation hold or single item recovery is enabled, when items are deleted or overwritten, Exchange will automatically move those items to the Recoverable Items folder and take up storage there. By default, litigation hold is disenabled while single item recovery is enabled.

   • Refer to and for details.

   • Sample PowerShell Command:

Set-Mailbox -Identity user@contoso.com -SingleItemRecoveryEnabled $false -LitigationHoldEnabled $false

4. (Optional) Refer to to execute the Get-MailboxFolderStatistics cmdlet using PowerShell to view the capacity of the Recoverable Items folders.

5. Sample PowerShell Command for Primary Mailbox:

Get-MailboxFolderStatistics -Identity user@contoso.com -FolderScope Recoverable

6. Sample PowerShell Command for Archive Mailbox:

Get-MailboxFolderStatistics -Identity user@contoso.com -FolderScope Recoverable -Archive

#EX-RequestTimeout

Issue:

The item/folder failed in the migration with the following error:

Details:

The error indicates that the request to the Exchange server is timed out because the Exchange server is busy or due to a bad network.

Recommendations:

#EX-ResourceMailboxUnresolved

Issue:

The item failed in the Gmail migration report with the following error:

Details:

The resource mailbox in the source event has been mapped to a resource mailbox that does not exist in the destination.

Recommendations:

Check the user mapping and make sure the resource mailbox exists in the destination, and run a “Retry error objects” migration job to resolve this issue.

#EX-RuleQuotaNotEnough

Issue:

The inbox rule failed in the migration with the following error:

Details:

There is no available rule quota in the destination mailbox. In this case, the inbox rule cannot be created in the destination.

Recommendations:

Increase the rule quota of the destination mailbox or manually delete some inbox rule in the destination mailbox. Then, run an incremental or “Retry error objects” migration job to resolve this issue.

#EX-SourceUserNotFound

Issue:

The item failed in the migration with the following error:

Details:

Recommendations:

#EX-SubstrateHoldsNotFound

Issue:

The folder failed in the migration with the following error:

Details:

This error indicates that the SubstrateHolds folder cannot be found in the destination. It occurs when the In-Place Hold, Litigation Hold, or a Microsoft 365 or Office 365 Teams Chat retention policy is not enabled for the destination mailbox.

Recommendations:

Make sure that you have enabled the In-Place Hold, Litigation Hold, or a Microsoft 365 or Office 365 Teams Chat retention policy for the destination mailbox, or filter out the SubstrateHolds folder in the migration policy.

#EX-UserNotInMapping

Issue:

The item failed in the migration with the following error:

Details:

Recommendations:

#EX-UserRequestsExceedLimit

Issue:

The item failed in the migration with the following error:

Details:

The error indicates that the number of concurrent requests to the Exchange server from the user exceeds the maximum number allowed for the user.

Recommendations:

#EX-ValidateFailed

Issue:

The migration failed with the following error:

Details:

The mailbox cannot be connected to.

Recommendations:

Please verify that permissions are sufficient and that there are no networking issues. Then, rerun the migration job.

#EX-WarnAbnormalSyncItemsProcess

Issue:

The folder failed in the migration with the following error:

Details:

The folder has been migrated to the destination, but an unknown error occurred while migrating the items in the folder.

Recommendations:

Try running the incremental jobs (it may require multiple runs) and then check the item count in the destination folder to ensure all data in the source folder has been migrated.