Migrate data from Exchange using GAMME

If you've set up your organization to use Google Apps, you can migrate users' mail, calendars and contacts from your Microsoft® Exchange environment to Google Apps using Google Apps Migration for Microsoft Exchange (GAMME).

System requirements

  • Google Apps for Work or Google Apps for Education
  • Microsoft Exchange 2000/2003/2007/2010. Note that GAMME also can migrate mail from PST files and IMAP servers (Novell GroupWise®, Cyrus, Dovecot, Courier, SunMail, Zimbra or Gmail). For more information, see the GAMME Admin Guide.
  • Microsoft Outlook 2003, 2007, 2010, or 2013 (not including Click-to-Run editions). Use the 32-bit version of Outlook, as GAMME currently does not work with the 64-bit versions of Outlook.
  • Administrator access to Exchange and super administrator access to Google Apps.

To learn more about GAMME, see the GAMME Admin Guide, which includes detailed information about how the utility works, getting started, and running your migration.

Don't run GAMME on the server itself, but download the application and run it on a Windows computer.

Before you begin

Before you begin, create a list of the user accounts that you are migrating. When migrating from a Microsoft Exchange server, we recommend you use the same usernames in Google Apps as you do in your current mail server. This streamlines the process and allows you to create user lists with just one name or SMTP address per line. You don't need to enter your users' passwords in the CSV because authentication is through your Exchange server administrator account.

Generic example of CSV:

If the addresses in your mail server are different from the addresses in Google Apps, then you need two addresses per line in the CSV: the mail-server address followed by the Google Apps address.

Generic example:
user1@exchange-domain.com, google_apps_user1@gmail-domain.com
user2@exchange-domain.com, google_apps_user2@gmail-domain.com
user3@exchange-domain.com, google_apps_user3@gmail-domain.com

Business example:
jsabia@solarmora.com, joesabia@solarmora.com
jsciarrillo@solarmora.com, joesciarrillo@solarmora.com
linc@solarmora.com, lincjepson@solarmora.com

Ensure that there are no extra characters in the CSV file. Some software can insert quotation marks around each line, which will cause the tool to fail. Learn more about creating a CSV file for GAMME to migrate users and calendar resources. To migrate only a portion of your users at a time, see "Migrate a subset of users" in the GAMME Admin Guide.

Configure the Admin console

Step 1: Enable Domain Admin API access

  1. Sign in to the Google Admin console.
  2. From the dashboard, go to Security > API reference. Where is it?
  3. Check Enable API access.
  4. Click Save changes.

    Domain Settings, Enable provisioning API

Step 2: Enable your OAuth consumer key

You must configure OAuth Client access to migrate data.

  1. In the Admin console, click Security > Advanced settings > Authentication > Manage OAuth domain key.
  2. Click Enable this consumer key and then write down your OAuth consumer key and your OAuth consumer secret.

    Enable OAuth consumer key in Admin console

Step 3: Specify the API scopes

  1. Click Security > Advanced settings > Authentication section, and click Manage third party OAuth Client access.
  2. In the Client Name field, enter your OAuth consumer key from step 2. This is usually your primary domain: example.com or www.example.com.
  3. In the One or More API Scopes field, enter the following comma-separated list of URLs:


    API scopes public folder migration

  4. Click Authorize. You can now migrate data to your domain(s).

Configure the utility

The instructions below are for Exchange servers in your network. If you're migrating from a hosted Exchange server, you'll need to specify a profile to use for migration and enter the Outlook Admin profile you want to use to log in to your hosted Exchange Server. Learn more in the GAMME Admin Guide.

Step 1 of 3: Server Details

  1. For Server Type, select Exchange.
  2. In the Hostname/IP Address field, enter your domain name or the IP address of the email server from which you want to migrate data. For example: smtp.mydomain.com or 198.102.434.8.
  3. For Admin username, enter the username for the Microsoft Exchange administrator account you want to use to open your users' mail stores.
  4. Click Next.

Step 2 of 3: User and Domain Information

  1. In the Google Apps domain name field, enter the new primary Google Apps domain where the data will be migrated.
  2. In the Google Apps Two-legged OAuth details section, enter the OAuth consumer key and OAuth consumer secret you recorded above into the appropriate fields.
  3. For the File of users to migrate field, select the CSV file that you created before beginning the configuration.
  4. Click Next.

Step 3 of 3: Migration Settings

  1. Select the checkbox for each type of data you want to migrate: email, calendar, or contacts.
  2. Click Next.
  3. The Migration Settings screen appears, showing a summary of the configuration.
  4. Review and optionally make changes to the settings:
    • Migrate all data: Only use this option if you are migrating an account again.
    • Save settings: When checked, the utility will retain the current configuration for future use.
    • Run Diagnostics: When checked, the utility will verify the configuration before running the migration.
    • Estimate: When checked, the utility will estimate the message count for the source users.
    • Migrate: When checked, the utility will perform the migration.
  5. Click Next to begin the migration process.
  6. In the dialog box that appears, enter the username and password for the Microsoft Exchange administrator account you are using to open your users' mail stores. Selecting Remember my password will bypass this step in future migrations.
  7. Click OK to begin the migration process.

For more information on how to monitor the progress of your migration and to troubleshoot any issues, see the GAMME Admin Guide and help center articles.

Notes about folders:

  • Folders will be migrated into labels.
  • Folders must contain messages or the labels won't be migrated.
  • Messages must be present at each level of nested labels or the structure will be broken.
Was this article helpful?