The utility makes a WinHTTP connection to Google Apps.
Using 2-legged OAuth, the utility logs in to the users’ Google Apps accounts, and writes the transformed message-store data to each user’s account.
Email is processed at a maximum rate of one message per second per user, assuming that no latency is introduced by mail server or network performance. For example, if you configure the utility to process 25 users at a time, then the utility will process up to 25 messages per second. However, processing times can often be significantly slower for larger messages, especially those with attachments.
Note: For customers running a hosted Exchange or IMAP solution that is not located on the same LAN as the GAMME client, the rate of migration can be significantly impacted based on the network latency to and from the hosted mail server. If you are planning to migrate, try to run GAMME on your server, and configure your network to minimize latency. Alternatively, ask your hosting provider to provide you with PST files for all users you want to migrate, and then run a PST migration.
The original message headers are preserved. Duplicate messages are filtered out based on subject and body.
Calendar and contact data are processed according to the speed at which your network connects to external networks.
What is migrated
During the migration, contacts and then calendar data are processed first, followed by email.
The following tables outline which aspects of mail, calendar, and contact data are and are not migrated from Microsoft® Exchange to Google Apps. For example, messages with .exe attachments are not migrated.
Any data that fails to migrate is identified in the log files by account name, entry ID, and location. Log files are located on each client machine in the following location:
Windows 7 or Vista: C:\Users\user-name\AppData\Local\Google\Google Apps Migration\Tracing\ExchangeMigration
Windows XP: C:\Documents and Settings\user-name\Local Settings\Application Data\Google\Google Apps Migration\Tracing\ExchangeMigration
user-name in the path identifies the administrator who logged in and ran the utility.