Both the source and destination environment administrators need to decide on how the transfer executes. These transfer options are then communicated to the Google Workspace Domain Transfer team:
- Placeholder domain—The domain name replacing the existing primary domain in the source environment. It’s the only domain left in the source environment after the transfer process completes.
- Transfer root organizational unit—The full path to the transfer root organizational unit in the destination environment.
- Google Drive link sharing—Whether Drive and shared drive files should have link sharing:
- Stripped—All link sharing is removed. If direct sharing is not applied, users will lose access to documents when selecting this option.
- Expanded—All link sharing with the source environment is converted into link sharing with the destination environment.
- Learn more about Sharing files from Google Drive.
- Recreate the organizational unit structure in advance—Whether the destination admin will recreate the organizational unit structure of the source environment in advance, under the transfer root organizational unit in the destination environment. Learn more
- No—The domain transfer product recreates the organizational unit structure under the transfer root organizational unit in the destination during the transfer process.
- Yes—The destination environment admin recreates the entire organizational unit structure under the transfer root organizational unit in the destination in advance.
- Google Vault retention in the source environment—Whether indefinite retention rules are added automatically or manually to the source environment.
- Automatic—The domain transfer product adds the rules. When using this option, Google needs to be told if the work should be scheduled, or if it can be executed on demand.
- Manual—The source’s Vault administrator adds the rules. When using this option, you need to provide a screenshot of your Vault interface, including the account information, to verify the indefinite retention rules are set.
- Feature names—Whether a feature for a calendar resource in the source environment conflicts with a feature in the destination environment. To resolve the conflict, you must either rename one of the features or use the version in the destination. Learn more
- Rename—You can rename one of the features in either the source or destination environment. For example, if the source has a feature named “Comm Unit” with type VISUAL, and the destination has "Comm Unit" with type AUDIO, you can rename one of them to "Comm Unit (1)"
- Destination version—Use the version in the destination environment. For example, if the source has a feature named “Comm Unit” with type VISUAL, and the destination has "Comm Unit" with type AUDIO, you can let all resources associated with "Comm Unit" VISUAL convert to "Comm Unit" AUDIO.
