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:
- **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 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**: 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.
