During a migration, some delegate or folder permission entries fail with warnings such as:
WARNING: Unable to migrate the public delegate and/or folder permissions for 'example_account@domain.com'.
The address could not be found in the Global Address List.
or
WARNING: Unable to migrate the public delegate and/or folder permissions for 'example_account@domain.com'.
Only mail-enabled security principals such as mailboxes, mail users, or mail-enabled security groups are supported by Exchange delegates and folder permissions.
In these cases, mailbox data migrates successfully, but delegate/folder permissions associated with certain objects do not.
This issue occurs when the source environment contains objects with formats or attributes that are not recognized as valid, mail-enabled security principals in the target environment. Examples include:
Objects that are not mail-enabled in Domino.
Syntax variations in account names or addresses that do not align with Exchange GAL requirements.
Custom or system accounts that exist in Domino but have no equivalent, valid representation in Exchange.
These cases are environment-specific and usually detected through professional services (PSO) tools or scripts.
Check formatting: Where possible, adjust the source object’s formatting to align with Exchange-supported formats before migration. For example, ensure the account is properly mail-enabled and visible in the GAL.
Exclude unsupported objects: If the object is not required in the target environment (e.g., system or placeholder accounts), consider excluding it from delegate or folder permission migration.
Engage PSO if needed: For complex cases where multiple objects are affected or formatting cannot easily be adjusted, engage Quest Professional Services (PSO) through your Quest Account Manager. PSO has specialized tools and scripts to detect and resolve these scenarios.