#Customized Features for Exchange On-Premises Migration

Fly provides a customized feature for Exchange On-Premises Migration. Refer to the following information to use the feature:

• UseGraphMode - This defines whether to use the Graph API instead of the EWS for all Exchange On-Premises migrations.

  If you want to use the Graph API for all Exchange On-Premises migrations, you can add the UseGraphMode=true string in the Customized feature section.

  NOTE

  Before switching from EWS to Graph API, refer to the Support List for the limitations.

• InvalidLicenseTypes – For Exchange On-Premises migrations, if the destination mailbox is Exchange Online Kiosk, Microsoft 365 and Office 365 F1, or Microsoft 365 and Office 365 F3, Fly automatically uses the Graph API for migration. If you want to automatically use the Graph API for mailboxes assigned with other licenses, you can add the InvalidLicenseTypes=" " string and enter the subscription ID of a license as the value. For example, InvalidLicenseTypes=SPE_E3. To add multiple license IDs, separate each ID with a semicolon (;). For example, InvalidLicenseTypes=SPE_E3; SPE_E5.

• EnableGraphModeForInvalidLicense – This defines whether to use the Graph API to migrate mailboxes assigned with invalid licenses. By default, Fly automatically uses the Graph API to migrate such mailboxes. If you want to switch to use EWS to migrate these mailboxes, you can add the EnableGraphModeForInvalidLicense=false string in the Customized feature section.

• 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. However, Fly cannot retrieve the type of an Exchange On-Premises resource mailbox. The migration of the resource mailbox will fail.

  To define the resource mailbox type, you can add the CreateResourceMailboxType=number string, and replace number with any of the following:

  • 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 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.

• 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.

• 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 migrate only 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

  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.

• MoveLegalHoldChildFolderItemsToParent – Define whether to migrate subfolders within the Recoverable Items folder, along with their contents, to the parent folder when the corresponding folders do not exist in the destination.

  Due to Microsoft API limitations, subfolders in the Recoverable Items folder and their contents cannot be migrated if the corresponding destination folders do not exist.

  To enable migration of these subfolders and their contents to the parent folder, add MoveLegalHoldChildFolderItemsToParent=true to the Customized features section.