As we add features, enhancements, and fixes to Google Apps Migration for Microsoft® Exchange (GAMME), we'll regularly update this page. Download the latest version of GAMME from the download page. To learn more about the migration tool, see Overview: Google Apps Migration for Microsoft Exchange.
February 14, 2013
New command supported --exclude_message_classes
The command --exclude_message_classes="<string1>,<string2>" allows IT administrators to exclude messages from being migrated from Exchange to Google Apps based on their message class. For more about message classes, see Microsoft's support site. For more details about using commands with GAMME, see Run GAMME from the command line.
This release comes with minor technical fixes and improvements to the GAMME migration tool in the following areas:
- Improvements to the migration reports GAMME generates.
- Fixes to estimating the number of calendar events to migrate.
- Fixes to migrating recurring calendar events when date ranges are given.
December 11, 2012
Calendar migration for resources
Migrate calendar resources (like meeting rooms) from Exchange to Google Apps. During migration, you can also change event attendees from email addresses in Exchange to email addresses in Google Apps.
Public folder migration
Migrate public folders in Exchange to Google Groups using the command line.
Support for Admin-mode migration with Cyrus/Mirapoint IMAP servers
For more information, see p.24 of the GAMME Admin Guide (PDF).
Support for IMAP servers with varying capabilities
For more information, see p. 45 of the GAMME Admin Guide (PDF).
Improved in-product help and error reporting
Click on a question mark in the product to get helpful tips on using the tool. Error reporting is more descriptive in the final step of the tool after you run a migration.
Improved user interface design
Updated look to GAMME 3.0 tool.
Minor technical fixes to the GAMME migration tool.
February 22, 2012
Minor technical fixes and minor updates to the GAMME migration tool.
November 4, 2011
Check for configuration errors in connectivity and authentication; and errors in your user list before you run a migration.
Detailed migration reports
Quickly determine if any message errors occurred during a migration, why those errors occurred, and which users were affected by them.
IMAP server list
Allows you to choose the specific type of IMAP server from which you are migrating data, which improves performance.
Improved data estimation feature
Feature now uses multi-threading for significantly faster overall data migration estimations.
New command line options:
|Command||What it does|
||Specifies the interval between two EMAPI requests to throttle the upload|
||Runs pre-migration diagnostics|
||Specifies the type of IMAP server from which you are migrating data|
||Prevents the utility from generating migration reports, which improves performance|
Migration fails for users with device name
- Issue: If user names were the same as special device names (such as com0...com9, lpt0...lpt9), their migration would fail.
- Resolution: Migrations no longer fail is user names are the same as special device names.
Unread messages in Google Apps Sync for Microsoft Outlook (GASMO)
- Issue: After GAMME migrated data, GASMO would synchronize all messages as unread.
- Resolution: Synchronized messages in GASMO no longer appear as unread.
Contacts in two groups in Google Apps Sync for Microsoft Outlook (GASMO)
- Issue: After GAMME migrated data, users who synchronized personal contacts with GASMO would see their contacts in two separate groups.
- Resolution: Synchronized personal contacts in GASMO no longer appear in two separate groups.
IMAP migration failures
- Issue: IMAP migration would fail if a user's password in the CSV file contained a semicolon.
- Resolution: IMAP migrations no longer fail if a user's password contains a semicolon.
Duplicate folders migrated
- Issue: GAMME would sometimes migrate folders twice from IMAP servers.
- Resolution: GAMME no longer migrates some folders twice from IMAP servers.
Infinite loop with error "stream error - socket could not be read or written"
- Issue: If GAMME's connection to the migration server was dropped and this error occurred, GAMME would appear to be in an infinite loop.
- Resolution: If GAMME loses its connection to a migration server, the utility now stops instead of appearing to be in an infinite loop.
Support for Exchange 2010