Customized Features for Exchange Online Migration
Fly provides multiple customized features for Exchange Online Migration. Refer to the following sections to use the features.
Migration to Gmail
Refer to the following instructions to use the feature for Exchange Online to Gmail migrations.
- **EmailFolderAddSuffix** – This defines whether to add a suffix (-migrated) to the migrated folder in the destination if the folder name is the same as a destination reserved system label name. By default, Fly will not add the suffix to the folder and the migration of the folder will fail.
- > ***Note**: This customized feature is used when the source custom folder name is **non-English** and same to a reserved label in the destination.
- If you want to migrate the folder, you can add the **EmailFolderAddSuffix=”** **”** string to the **Customized features** section and enter the folder name as the string value. For example, **EmailFolderAddSuffix=FolderA**. If you want to configure multiple folder names, separate names with a semicolon (;\). For example, **EmailFolderAddSuffix=FolderA;FolderB**.
- **MigrateLabelsForEmailAttachments** – This defines whether to migrate sensitivity labels of attachments in source emails. By default, Fly will not migrate sensitivity labels of attachments in source emails.
You can define the migration scope by adding the **MigrateLabelsForEmailAttachments=number** string, and replacing **number** with any of the following:
- **0** – Do not migrate sensitivity labels of attachments in source emails.
- **1** – Migrate sensitivity labels of email attachments that meet one of the following conditions:
- Source emails are applied with encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are applied with non-encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- **2** – Migrate sensitivity labels of email attachments when source emails meet one of the following conditions:
- Source emails are applied with encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are applied with non-encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are not applied with sensitivity labels, but the attachments are applied with sensitivity labels.
For the detailed migration results of sensitivity labels in different situations with this feature enabled, refer to [Migration Results of Sensitivity Labels](#missing-link).
- **MigrateSpecialEmailsAsNonAIPEmails** – Define whether to migrate emails meet any of the following conditions when you select to remove sensitivity labels from source emails or apply sensitivity labels to the destination migrated emails, and configure the **MigrateLabelsForEmailAttachments=2** customized feature string in the migration policy to migrate source emails:
- Emails with sensitivity labels from other tenants applied.
- Emails with S/MIME signatures configured.
- Emails with S/MIME signatures configured and encrypted sensitivity labels applied.
By default, emails that meet above conditions cannot be migrated.
If you want to migrate these emails, you can add the **MigrateSpecialEmailsAsNonAIPEmails=true** string to the **Customized features** section to enable this feature.
- > ***Note**: Emails that are encrypted in other tenants but without sensitivity labels applied still cannot be migrated.
- **DisableMailLock** – Define whether to disable the lock for email conversations.
- If you want to disable the lock for email conversations, you can add the **DisableMailLock=true** string to the **Customized features** section.
Migration to Exchange Online
Refer to the following instructions to use the features for Exchange Online to Exchange Online migrations.
- **MigrateLabelsForEmailAttachments** – This defines whether to migrate sensitivity labels of attachments in source emails. By default, Fly will not migrate sensitivity labels of attachments in source emails.
You can define the migration scope by adding the **MigrateLabelsForEmailAttachments=number** string, and replacing **number** with any of the following:
- **0** – Do not migrate sensitivity labels of attachments in source emails.
- **1** – Migrate sensitivity labels of email attachments that meet one of the following conditions:
- Source emails are applied with encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are applied with non-encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- **2** – Migrate sensitivity labels of email attachments when source emails meet one of the following conditions:
- Source emails are applied with encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are applied with non-encrypted sensitivity labels, and the attachments are also applied with sensitivity labels. This also applies when source emails contain emails as attachments and attached emails also contain attachments.
- Source emails are not applied with sensitivity labels, but the attachments are applied with sensitivity labels.
For the detailed migration results of sensitivity labels in different situations with this feature enabled, refer to [Migration Results of Sensitivity Labels](#missing-link).
- **MigrateLabelsForNonEncryptedEmails** – Define whether to migrate sensitivity labels of source emails that meet any of the following conditions:
- Emails in the **Sent Items** folder that are encrypted with sensitivity labels and sent via Outlook Web Access or Outlook mobile app. These emails will be regarded as non-encrypted emails.
- Emails in the mailboxes of the Microsoft 365 tenant with the **Remove encryption if the file or email option is encrypted** option selected in **Microsoft Purview**.
- Emails in the mailboxes of the Microsoft 365 tenant with the **Apply content marking** setting enabled in **Microsoft Purview**.
> ***Note**: With this setting enabled, source headers and footers will be migrated to the destination.
By default, this feature is disabled. Sensitivity labels of these emails will not be migrated.
If you want to migrate sensitivity labels of the source emails. You can add the **MigrateLabelsForNonEncryptedEmails=true** string to the **Customized features** section to enable this feature. Also make sure you select one of the following options in the **Select how to manage sensitivity labels of emails** section of migration policy:
- If a label exists, remove it during the migration (source label remains, it is removed from the email in the destination)
- Apply same label in the destination (same label must exist in the destination)
- Apply labels in the destination based on label mappings (labels must exist in both source and destination)
> ***Note**: Before running the migration job, make sure there are no labels with the same display name in the source or destination. Otherwise, the migration job will fail.
- **MigrateSpecialEmailsAsNonAIPEmails** – Define whether to migrate emails meet any of the following conditions when you select to remove sensitivity labels from source emails or apply sensitivity labels to the destination migrated emails, and configure the **MigrateLabelsForEmailAttachments=2** customized feature string in the migration policy to migrate source emails:
- Emails with sensitivity labels from other tenants applied.
- Emails with S/MIME signatures configured.
- Emails with S/MIME signatures configured and encrypted sensitivity labels applied.
By default, emails that meet above conditions cannot be migrated.
If you want to migrate these emails, you can add the **MigrateSpecialEmailsAsNonAIPEmails=true** string to the **Customized features** section to enable this feature.
- > ***Note**: Emails that are encrypted in other tenants but without sensitivity labels applied still cannot be migrated.
- **ChangeTeamsMeetingScopeAsEveryone** – Define whether to publish the meeting links in source emails to everyone. Then, all meeting participants, including authenticated users, users from trusted organizations, guests, and anonymous users, can enter the meetings directly by clicking the meeting links in emails.
- > ***Note**: This feature is unsupported when the source is a 21Vianet.
By default, this feature is disabled. If the meeting contains destination/external users, when they click the meeting link to enter the meeting, they may wait in the lobby until the meeting organizer allows them to enter the meeting.
If you want to publish the meeting links in source emails to everyone, you can add the ChangeTeamsMeetingScopeAsEveryone=true string to the Customized features section to enable this feature. Make sure you do not select the Replace meeting links with the destination information checkbox in the migration policy. Also, 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:
- Make sure you have assigned the access policy for the **AvePoint Fly** app or custom Azure app. Refer to for details
- If you use a custom Azure app, make sure you have assigned the Microsoft Graph API > **OnlineMeetings.ReadWrite.All** permission to the app.
For more details, refer to the **Notes when Replacing Meeting Links** section in .
- **CreateResourceMailboxAutomatically** – Define whether to create a resource mailbox in the destination if the destination resource mailbox configured in the project mapping does not exist.
By default, this feature is enabled. If the destination resource mailbox configured in the project mapping does not exist, Fly will create the destination resource mailbox as a new one.
If you do not want to create a resource mailbox in the destination when the destination resource mailbox configured in the project mapping does not exist, you can add the CreateResourceMailboxAutomatically=false string to the Customized features section to disable this feature. In this case, the migration of the source mailbox will fail.
- **CreateResourceMailboxType** – Define the type of the resource mailbox to be created in the destination. By default, Fly will create a resource mailbox with the same type as the source resource mailbox in the destination.
- You can define the resource mailbox type by adding the **CreateResourceMailboxType=number** string, and replacing **number** with any of the following:
- **0** – Create a resource mailbox with the same type as the source resource mailbox in the destination.
- **1** – Create a resource mailbox of the **Equipment** type.
- **2** – Create a resource mailbox of the **Room** type.
CreateSharedMailboxAutomatically – Define whether to create a shared mailbox in the destination if the destination shared mailbox configured in the project mapping does not exist.
By default, this feature is enabled. If the destination shared mailbox configured in the project mapping does not exist, Fly will create the destination shared mailbox as a new one.
If you do not want to create a shared mailbox in the destination when the destination shared mailbox configured in the project mapping does not exist, you can add the **CreateSharedMailboxAutomatically=false** string to the **Customized features** section to disable this feature. In this case, the migration of the source mailbox or mailbox aliases will fail.
- **DisableOOFMigration** – Define whether to migrate the Automatic Replies (Out of Office) setting in the migration job. By default, the Automatic Replies (Out of Office) setting will be migrated.
- If you do not want to migrate the setting, you can add the **DisableOOFMigration=true** string to the **Customized features** section to enable this feature.
- **IsReplaceWholeSafeLink** – Define whether to replace the safe link of the source meeting with a normal Teams meeting link in the destination. Then, destination users can enter the meeting via clicking the Teams meeting link.
By default, this feature is disabled. The safe link of the source meeting will be retained in the destination and destination users cannot enter the meeting via clicking the safe link.
If you want to replace the source safe link with a normal Teams meeting link in the destination, you can add the IsReplaceWholeSafeLink=true string to the Customized features section to enable this feature. Make sure you select the Replace meeting links with the destination information checkbox in the migration policy.
IsTrimLabelNameSpace – Define whether to remove the space at the beginning and end of sensitivity labels in the source and destination during the migration. By default, the space will not be removed.
If you want to remove the space at the beginning and end of sensitivity labels during the migration, you can add the IsTrimLabelNameSpace=true string in the Customized feature section.
- **MigrateDistributionListSettings** – Define whether to migrate **Settings** configured for distribution lists / mail-enabled security groups / dynamic distribution group in Exchange admin center. By default, this feature is enabled. Fly will migrate the **Settings** configured for distribution lists /mail-enabled security groups / dynamic distribution group.
If you don’t want to migrate the Settings configured for distribution lists / mail-enabled security groups / dynamic distribution group, you can add the MigrateDistributionListSettings=false string to the Customized features section to disable this feature.
When migrating the Settings configured for distribution lists / mail-enabled security groups / dynamic distribution group, note the following:
- **General** **settings**
- **Hidden this group from the global address list** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Delivery management**
- **Sender options** – Fly will process sender options based on the conflict resolution configured in the migration policy.
- **Specified senders** – To migrate specified senders, make sure you have configured user mappings or a domain mapping for senders in the migration policy.
- **Message approval**
- **Require moderator approval for messages sent to this group** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Group moderators** – To migrate group moderators, make sure you have configured user mappings or a domain mapping for moderators in the migration policy.
- **Add senders who don't require message approval** – To migrate senders in this setting, make sure you have configured user mappings or a domain mapping for senders in the migration policy.
- **Notify a sender if their message isn't approved** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Edit membership approvals**
- **Joining the group** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Leaving the group** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Mail tips**
- **Default mail tip** – Fly will process this setting based on the conflict resolution configured in the migration policy.
- **Mail tip translations** – Only translations for custom mail tips can be migrated.
MigrateLegalHoldFolders – Define whether to only migrate the data in SubstrateHolds, Versions, Purges, and DiscoveryHolds folders when the source mailbox is on the legal (litigation) hold.
By default, this feature is disabled. The data in SubstrateHolds, Versions, Purges, and DiscoveryHolds folders will not be migrated.
If you want to only migrate the data in SubstrateHolds, Versions, Purges, and DiscoveryHolds folders, you can add the MigrateLegalHoldFolders=true string to the Customized features section to enable this feature.
*Note: This feature is unavailable for Group mailboxes.
> ***Note**: The data in the SubstrateHolds, Versions, Purges, and DiscoveryHolds folders cannot be deleted or updated. Therefore, we recommend that you migrate the data in the four folders after the final migration is finished.
- **IllegalCharacterReplace** – Define whether to replace the invalid characters in folder names with specified valid characters. By default, Fly will not replace the invalid characters in folder names. The migration of the folder may fail.
- If you want to replace the invalid characters in folder names with specified valid characters, you can add the **IllegalCharacterReplace=**” ” string to the **Customized features** section and enter the desired characters as the string value. For example, **IllegalCharacterReplace=AA**.
- **IsMigrateMIPProtectionTemplateAsLabel** – Define whether to migrate the protection template applied to emails as sensitivity labels. By default, this feature is disabled. The protection template applied to emails will not be migrated.
If you want to migrate the protection template applied to emails based on the option you selected in the **Select how to manage sensitivity labels of emails** section of migration policy, you can add the **IsMigrateMIPProtectionTemplateAsLabel=true** string to the **Customized features** section to enable this feature.
- **MigrateCustomAddressType** – Define whether to migrate custom email addresses of user/resource/shared mailboxes. By default, this feature is disabled. The custom email addresses of these mailboxes will not be migrated.
> ***Note**: Custom email addresses of the SMTP and EUM types are not supported.
If you want to migrate the custom email addresses of these mailboxes, you can add the **MigrateCustomAddressType=**” ” string to the **Customized features** section and enter the email address types as the string value. For example, **MigrateCustomAddressType=X400**. If you configure multiple custom email address types, separate types with a semicolon (;\). For example, **MigrateCustomAddressType=X400;CcMail**.
> ***Note**: When you enable this feature, only domain mapping in the **User mapping** is supported.
- **DisableArchiveXAnchorMailboxHeader** – Define whether to disable the use of X-AnchorMailbox header for archive mailboxes. By default, Fly will use special headers for archive mailboxes.
- If you want to use SMTP email address instead of special header for archive mailbox, you can add the **DisableArchiveXAnchorMailboxHeader=true** string to the **Customized features** section to enable this feature.
