Use advanced migration for Exchange Online (beta)

Supported editions for this feature: Business Starter, Business Standard, and Business Plus; Enterprise Standard and Enterprise Plus; Education Fundamentals, Education Standard, and Education Plus; Essentials Starter, Essentials, Enterprise Essentials, and Enterprise Essentials Plus; Nonprofits; G Suite Basic and G Suite Business. Compare your edition

The advanced migration service uses your own dedicated API quota to streamline large-scale data migration from Exchange Online data to Google Workspace. Once you set up a Microsoft Azure application through the Azure portal, you can migrate your data to Workspace in batches.

You can copy:

  • Calendar data
  • Contact data
  • Email data

The migration doesn’t delete or modify a user’s data in Exchange Online but copies it to the user’s account in Workspace. Except where indicated, you complete these steps in the Google Admin console for the Workspace account you’re migrating to.

Note: If you want to migrate data with Google's shared API quota, go to Use default migration for Exchange Online.

Requirements

  • A super administrator must manage the migration on the Workspace side. A global administrator or other qualified user must approve the migration in Exchange Online.
  • You need to verify your Workspace domain. If you have an Essentials edition, you need to verify before starting a migration. For details, go to Verify your domain for Google Workspace.
  • The data migration service migrates only users with existing Exchange Online and Workspace accounts. The service doesn't create new user accounts for migrated data.
  • You need an email address for every Exchange Online user that you want to migrate. For details, go to Plan for where and how you will manage your user accounts.
  • You need a Workspace user account for each user you're migrating to Workspace. For details, go to Options for adding users.
  • Each user needs a license to use Google services. For details, go to How licensing works.
  • Turn on the Gmail and Google Calendar services for the users you're migrating. For details, go to Turn a service on or off for Google Workspace users.
  • You can migrate data for up to 2,000 Exchange Online users in one batch. Advanced migration allows you to migrate 5 batches at one time. Additional users require a separate migration.

Run a migration

You must be signed in as a super administrator for this task. Resellers cannot migrate data for their customer accounts.

Before you begin: To ensure secure data migration from Exchange Online to your Workspace account, you must first create a Microsoft Entra application within the Microsoft Azure portal. For details, go to Set up Microsoft Azure for advanced migration.

Step 1: Connect to your Microsoft Exchange Online account

  1. In the Google Admin console, go to Menu and then Data and then Data import & export and then Data Migration (New).

    You must be signed in as a super administrator for this task.

  2. For Advanced (Beta), click New batch.
  3. For Wave name, enter a name for this batch of users and then click Continue.
  4. For Client ID, enter the unique ID number for your Exchange Online account.
  5. For Client Secret, enter the client secret value for your Microsoft Entra tenant.
  6. For Tenant ID, enter the unique ID number for your Microsoft Entra tenant.
  7. Click Connect.

Step 2: Select users to migrate

Create a comma-separated values (CSV) file that lists the Exchange Online users that you want to migrate in this batch. You can create a new CSV file. Or, download a sample file and add information. The completed CSV file must be smaller than 10 MB and contain no more than 2,000 users.

To get details about users in your Exchange Online tenant, go to Create a group in your organization.

To create the CSV file:

  1. Using your Workspace administrator account, open a spreadsheet program. Or, in the Admin console, select Download a sample CSV file.
  2. Add the header Source Exchange Email and add an email address for each Exchange Online user that you want to migrate. Use a separate row for each email address.

    Example:

    Source Exchange Email
    kim@example.com
    alex@example.com
  3. Save the spreadsheet as a CSV file.
  4. Upload the file to the Admin console:
    1. In your Admin console, click Upload CSV.
    2. Select the fileand thenclick Open.
    3. Click Tasks to confirm that the file is successfully uploaded.
  5. If the CSV file doesn't successfully upload:
    1. Select the file and click Deleteand thenYes to confirm.
    2. Create a new file and try to upload it again.

    If you encounter this issue more than once, Contact Google Workspace support.

(Optional) Step 3: Create & upload an identity map

If necessary, create a second CSV file (separate from the file of Exchange Online users) to map Exchange Online users to Workspace users. You can create a new CSV file. Or, download a sample file and add rows. You don’t need to add external users. Their permissions migrate by default. The completed CSV file must be smaller than 10 MB.

A single Exchange Online user can’t be mapped to multiple users or groups in Workspace. You need to provide a one-to-one or many-to-one mapping.

An identity map is not always required. You don't need an identity map if:

  • The user's email address in Exchange Online is the same as their address in Google Workspace. For example, the user's email address is raha@example.com for their Microsoft account and their Google Workspace account.
  • All users keep the same username in Workspace and are mapped to another domain name. For example, all users have the domain name @example.com and are moving to the domain name @altostrat.com. Users have the same username in Exchange Online and Workspace, and only the domain name changes.

If you have some users that don't need to be mapped and some that do, you can create an identity map for only the users that require mapping. If you’re creating an identity map for only some users or not creating one at all, make sure you check the Copy accounts that aren't included in the map that are discovered during the migration box in (Optional) Step 4: Configure migration settings.

Create an identity map

  1. Using your Workspace administrator account, open a spreadsheet program. Or, in the Admin console, select Download a sample CSV file.
  2. In the first column, add the header Source Email and add an email address for each Exchange Online user that you want to migrate. Use a separate row for each user.
  3. In the second column, add the header Destination Email and enter a Workspace email address for each user in the first column. Use a separate row for each user.

    Example:

    Source Exchange Email Destination Email
    charliecruz@example.com ccruz@other-company.com
    kailee@example.com klee@other-company.com
  4. Save the spreadsheet as a CSV file.
  5. Upload the file to the Admin console:
    1. In your Admin console, click Upload CSV.
    2. Select the fileand thenclick Open.
    3. Click Tasks to confirm that the file is successfully uploaded.
  6. If the CSV file doesn't successfully upload:
    1. Select the file and click Deleteand thenYes to confirm.
    2. Create a new file and try to upload it again.

    If you encounter this issue more than once, Contact Google Workspace support.

Step 4: Configure migration settings

Adjust the following settings to choose which data to copy from Exchange Online.

  1. Click Edit settings.
  2. Check one or more of the following boxes to choose which data to migrate for all your selected users:
    • Email
    • Calendar events
    • Contacts—A new migration duplicates any contacts you already migrated. Contact labels are not duplicated.
  3. For Date range, enter a date to start migrating data from the source you selected. All calendar events and email messages sent or received after this date are copied to Workspace and all contacts are copied, regardless of creation date.
  4. (Optional) For Email options, check any of the following boxes to specify what kind of email information is migrated:
    • Include deleted emails—Migrate deleted email messages.
    • Include junk emails—Migrate email messages in spam folders.
    • Exclude specific folders—Enter the excluded folder names, separated by commas. For details, go to Exclude folders from migration.
  5. (Optional) To migrate the Exchange Online users' calendars and events, including calendars for personal appointments, check the Copy additional calendars box. The calendars migrate to Other calendars in Google Calendar.
  6. (Optional) To migrate all Exchange Online users, including those not found in the identity map, check the Copy accounts that aren't included in the map that are discovered during the migration box and choose an option:
    • If the user's email address in Exchange Online is the same as their address in Workspace, check the Keep their original address box.
    • If the domain name for all migrated users is changing, check the Use a different email address domain for these accounts box and then select a domain from the list.
  7. Click Save changes.

Exclude folders from migration

  • Separately add each Exchange Online folder or subfolder name.
  • If you exclude a folder, the migration doesn’t include its subfolders and any email messages in them.
  • To exclude a subfolder, use the full path and separate the parent folder from the subfolder with a forward slash (/). For example:
    • If you want to exclude the subfolder Asia in the folder Travel, enter Travel/Asia.
    • If you also add Travel in the list, such as Travel, Travel/Asia, then all the subfolders are automatically excluded.
  • To exclude a folder with a forward slash (/) in its name, replace each slash with an underscore (_). For example, to exclude Folder/with/slash, add it as Folder_with_slash.
  • You can also exclude default Microsoft folders, such as Deleted Items, Inbox, or Junk email, and user-created folders.

Step 5: Start a migration and check its progress

Start migrating the current batch of users. You can migrate 5 batches at one time.

  1. Click Run full migration.

    The status changes to In progress and the following information is updated in real time:

    • Users processed—Number of users whose migration is complete for all selected data types.
    • Emails discovered—Number of email messages in the Exchange Online users’ accounts.
    • Emails migrated—Number of email messages that were migrated.
    • Emails skipped—Number of email messages that were skipped. For example, an email is marked as skipped if it was already migrated in a full migration and then you run a delta migration.
    • Emails failed—Number of email messages that failed to migrate.
    • Calendars processed—Number of calendars that were migrated.
    • Calendar events discovered—Number of events in the Exchange Online users’ accounts.
    • Calendar events migrated—Number of events that were migrated.
    • Calendar events skipped—Number of events that were skipped. For example, an event is marked as skipped if it was already migrated in a full migration and then you run a delta migration.
    • Calendar events failed—Number of events that failed to migrate.
  2. You can navigate away from the migration page without interrupting the migration. Your migration continues unless you cancel it.

    When the migration is complete, you get an email with migration statistics. Any reports are attached.

  3. (Optional) To export a report for a migration in progress:
    1. Click Export migration report or Export user report.
    2. If the Tasks list doesn't automatically open with the exported report, click Tasks and then the report link.
    3. Click Open in Google Sheets to open the report in Sheets.
    4. To export and interpret the reports, go to Understand Exchange Online data migration reports.

Step 6: Stop a migration in progress

To stop a migration that’s in progress, click Stop migration. It might take a few minutes for the migration to stop, and the migration process does not roll back.

Email messages, calendars, calendar events, and contacts migrated before you stopped the migration are not deleted from Gmail, Calendar, or Google Contacts.

Step 7: Run a delta migration

After you successfully migrate a batch of data, you can still run a delta migration to copy any newly added or updated data to Workspace. You can also retry migrating data that failed in the initial migration. For details, go to Run a delta migration.

If you migrated the same data in two separate batches, a delta migration won’t create duplicate items as long as you haven’t clicked Exit migration to remove one of the batches.

Exit a completed migration

Once you exit migration for a batch, you can no longer access its configuration data or reports. Don't exit a migration until it's fully complete and no delta migrations are needed.

You can run delta migrations and review information for a completed migration in the Admin console until you exit the migration. To exit a completed migration:

  1. (Optional) If you want to save logs form a completed migration, click Export migration report and Export user report. For details, go to Understand email migration reports
  2. Click Exit migrationand thenExit and delete migration.

When you exit, the system deletes the client ID and removes Data Migration (New) as a client in the domain-wide delegation setting.

Avoid duplicate data

If you exit a migration for one batch and then start a new migration for the same batch of data, the second migration might create duplicates in Workspace. To prevent duplication, avoid creating 2 separate migrations for the same batch of data.

Exchange Online data migration is intended as a productivity feature and isn't designed to assist with legal compliance matters. You and your organization are responsible for assessing and meeting your organization's legal compliance needs.


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.