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.

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

IMAP must be enabled in the destination for the migration to work. For free accounts, IMAP is usually enabled by default.

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

5. User credentials for the IMAP-enabled accounts. 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.