Google Apps Migration for Lotus Notes Installation & Administration Guide - Manual (Page 73)

Managing Your Migration 73
To migrate a user or database that was successfully migrated and moved to Completed
status:
1. Open the Administration database and select the Complete view.
2. Double-click the profile that you want to reprocess.
3. Click Migrate Again.
This action sets the migration profile back to Draft status. Once activated all previously
migrated content will be migrated again.
This action is not the same as just setting the profile back to Active, which migrates
previously unprocessed content only. With this process, everything is reset to
unprocessed and migrated again, so use this action with caution.
When using this action, make sure you clear all mail, calendar, and contacts/group
information from the Google Apps account you’re migrating to. If you are migrating content
to a Google Group, you should delete and recreate the group in your Apps domain before
using this action.
Decrypt Mail
Because Gmail does not read encrypted mail, the system does not migrate encrypted mail.
Encrypted messages are visible in each user’s mail database in the Migration Status > Mail
view, and are categorized as Encrypted. To migrate those messages, the mail database
owner must first decrypt them.
Have the user follow these instructions to decrypt messages:
1. Open the Migration Status > Mail view.
2. Select all messages categorized as Encrypted.
3. Click Decrypt Email in the action bar.
Those decrypted messages are migrated the next time the system process the user.
Note: The invitation-to-migrate email includes the Decrypt Email button, and users can
decrypt mail before they initiate the migration process.
Monitor Database Sizes
During the initial phase of migration, email and any documents that are being migrated to a
Google Groups archive are routed through the Feeder databases. This process generates a
large amount of internal email traffic on your network. With this in mind, monitor the following
conditions daily:
• The size of the MAIL.BOX databases. Check whether the server has been able to
compact these databases, and if not, compact them manually.