Migration setup prerequisites

A VaultMe for Admins migration will require:

1. Active and fully licensed source accounts.

• Only online accounts (i.e., accounts accessible in the cloud) can participate in a migration.
• Accounts must not be suspended or deactivated. If accounts are archived (inactive), they must be assigned licenses and passwords before the migration.
• Alternate accounts (email aliases) cannot be used as source accounts. If an account has an alias, the primary email address of that account must be connected to VaultMe for Admins.

2. Active and fully licensed destination accounts.

• Only online accounts (i.e., accounts accessible in the cloud) can participate in a migration.
• All user accounts must be created and configured at least at the basic level before the migration. This includes domain ownership verification, configuring email authentication settings (DKIM and DMARC) and SPF records, and assigning sufficient storage. VaultMe for Admins does not create users, modify accounts' settings, or transfer domains.
• Accounts must not be suspended or deactivated. If accounts are inactive, they must be assigned licenses and passwords before the migration.
• Alternate accounts (email aliases) cannot be used as destination accounts. Content should be migrated to the corresponding primary account, and an alias should be recreated after the migration.

For more information on setting up Google Workspace accounts, refer to Set up Google Workspace for your organization.

3. Fully enabled services for user accounts in the destination.

All services involved in the migration, such as Gmail or Google Drive, must be enabled for each user by an administrator for the migration to complete successfully.

For instructions on enabling services, see Turn a service on or off for Google Workspace users.

The MX records may still point to the source accounts, but the destination accounts must be fully set up for the migration.

4. Admin privileges if planning to use admin authorization. If admin access is unavailable, admins can use users' credentials or send sign-in links to users.

If users have MFA enabled, it should be disabled before the migration, or users must be available to assist with the sign-in process.

5. User credentials for personal Gmail accounts. Admins planning to connect the accounts individually will need to use users' credentials. If that is problematic, sending sign-in links for users and instructing them to connect their accounts themselves will be possible.

If users have MFA enabled, it should be disabled before the migration, or users must be available to assist with the sign-in process.