What's new in this release

As we add features, enhancements, and fixes to Google Apps Migration for Microsoft Outlook®, we'll release updates both automatically and from our download page. We'll also continue to update this page with the latest release information. Here's a look at what's new in the latest release, and how you can get it.

Getting the latest release

Getting the latest release

Update Google Apps Migration
  • If you installed Google App Migration yourself: Updates are checked for and downloaded to your computer automatically.
  • If your administrator installed Google Apps Migration: Updates are downloaded to your computer automatically, if your administrator enables automatic updates.
  • You can also download the latest version at any time from this Google Apps Migration download page.

Release 3.1.21.46
December 15, 2014

What's New

What's New

Google Apps Migration for Microsoft Outlook® now uses the latest Email Migration API (version 2).



Release 3.0.19.44
August 5, 2014

What's Fixed

This release fixes the integration with Google Apps Sync for Microsoft Outlook. There was an issue that prevented existing Outlook profiles/PSTs from being imported when creating a new Google Apps Sync profile.



Release 3.0.17.42
July 21, 2014

What's New

What's New

Google Apps Migration for Microsoft Outlook® calendar migrations now uses the latest Google Calendar API (version 3).

Calendar migrations now recognize more time zones.

Google Apps Migration for Microsoft Outlook® can now get the sender's email address from the message's internet headers even if it's missing from the sender field in Outlook.

What's Fixed

This release fixes the following issues:

  • Removed ClientLogin API support, as the API is deprecated. This means that users can now only authenticate using the browser with OAuth.
  • Removed the incorrect request to copy the authorization code during the authorization flow. The prompt now only asks the user to switch back to the application after authorizing access.
  • Fixed an issue where re-migrating secondary calendars would fail if the user had deleted the calendar in Google Apps.
  • Fixed issue where the -noenable_label_prefixes command line option was not respected when using the GUI.
  • The command line option -noenable_label_prefixes was renamed to -noenable_label_prefix to be consistent with Google Apps Migration for Microsoft® Exchange (GAMME).
  • Fixed a crash that would happen if the password dialog was cancelled when performing a PST migration.


Release 2.3.14.36
May 22, 2013

What's New

What's New

Google Apps Migration for Microsoft Outlook now supports Outlook 2013 (32-bit and 64-bit), and runs on Windows 8 in addition to previously-supported operating systems.



Release 2.3
September 15, 2011

What's New

What's New

Google Apps Migration is now available in 26 new languages!

Google Apps Migration is now available in 26 languages (in addition to English). Its documentation is available in many of these languages, too.

Which languages are supported?
Chinese simplified
Chinese traditional
Czech
Danish
Dutch
French
German
Filipino
Finnish
Hindi
Hungarian
Indonesian
Italian
Japanese
Korean
Norwegian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Russian
Spanish
Swedish
Thai
Turkish
Ukrainian
Vietnamese

Google Apps Migration now matches whichever language the user has defined for Microsoft Outlook, if that language is one that we support. If not, it matches the user's Windows default language, if supported. Otherwise it opens in English.

Google Apps Migration documentation is available in these languages, too. To view documentation in your language, visit the following links and choose your language from the pop-up list at the bottom of the page.

Help for users
Help for administrators



Release 2.1.1.234
April 29, 2011

What's New

What's New

Google Apps Migration now supports SSO via 3-legged OAuth

Google Apps Migration now supports using 3-legged OAuth for migrating users' mail, contacts, and calendar data to Google Apps. When running the migration utility, users can now sign in to their Google Apps account via a Single Sign On (SSO) system—using their current service's login credentials, rather than their Google Apps credentials.

3-legged OAuth is also more secure since users can explicitly grant access to their account and then revoke it any time.

The new version also supports a new command-line flag to disable calendar fanouts, creating events only for the user whose data is being migrated—without adding the event to calendars of other attendees. This new flag is useful when performing test migrations.

Read the Blog post
<a data-cke-saved-href=" http:=" "="" mail.google.com="" support="" a="" google.com="" bin="" answer.py?answer="1254189&quot;" target="_blank">Learn more about implementing SSO