Address Replacement Advanced Options
- Replace Usernames
- Address Replacements (.csv)
- Non-Matched Address Replacement Behaviour <
- Replace CSV Addresses Only
Default Value: On
Replace any remapped usernames from the user's page, when migrating the items specified in Domain Replacement Types tab. If this option is disabled and replacements are required, explicit mappings for email addresses and domain names should be provided.
Address Replacements (.csv)
Default Value: None
Specify a path to a CSV file containing replacement values to modify email addresses for appointments and contacts during migration. To perform no replacements, do not specify a file.
- User A owns a file
- User B has access to the file
- User A isn’t being migrated to the destination domain
- User B is being migrated to to the destination domain and will need to be able to access the file
During the course of the migration the ACL for the file is amended adding user B new destination address. Which will allow User B to continue to access the file that’s still in the source platform.
Non-Matched Address Replacement Behaviour
Default Value: Retain Original Address
When Replace Usernames is enabled and a CSV has been provided for address replacement, set the behavior when an address has not been matched. Either replace the domain name of the address, or leave the original address.
Default Value: Off
Perform email addresses and domain replacements from the CSV file specified in Address Replacements and do not attempt to perform replacements using any other method.
Change Conditions: Turn on to only change address of users specified in the CSV under Address Replacements (.csv).
[GoogleDriveImporter] [Error]  [firstname.lastname@example.org]  Unexpected exception processing import. Message is: Following address replacement, new owner email address email@example.com for item [itemID+title] does not exist in the destination domain, or does not have Drive enabled. Please check you have provided the correct address replacements for all email addresses, including aliases. You could use the option 'Allow Alternate Item Ownership', but this will result in a change of ownership. cloud.solutions.Migration.Google.GoogleImporterException
Example Explained :
When migrating Google Drive to Google Drive, unowned items in the migrating users' My Drive may be migrated. As mentioned in the linked article, it is advised that you provision all users prior to migration. If this is not done, it will result in the above error above.
It is literal in nature and means that while migrating firstname.lastname@example.org, it came across an item owned by a user called owner on the source. That user does not exist as email@example.com in the destination - IE has not been provisioned - OR does exist and does not have Drive enabled, so CloudM Migrate now needs to know what to do with the item.
It gives you two options:
Use Address Replacements to replace the owner with a different existing user in the destination or;
Enable 'Allow Alternate Item Ownership'.