You can use the advanced import method to streamline large-scale data imports from Microsoft Teams to Google Workspace.
About the advanced data import method
- Uses your own dedicated API quota.
- You set up a Microsoft Azure application through the Azure portal and import your data to Workspace in batches.
- The import doesn't delete or modify data in Teams 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 importing to.
- Not all Exchange Online features are supported. For details, go to What's imported in an Exchange Online import?.
If you want to instead import data with Google's shared API quota, go to Use the default data import method for Teams.
Workspace Requirements
- Make sure a super administrator sets up and runs the data import. Resellers can't import data for their customer accounts.
- You need a Workspace user account for each user you're importing to Workspace. For details, go to Options for adding users.
- Turn on Google Chat for all the users that you're importing to Workspace. For details, go to Turn a service on or off for Google Workspace users.
- In the Google Admin console, turn on auto-deletion and automatically accept chat invitations.
- You can import data for up to 1,000 teams in one batch. You can import 10 batches at one time. Additional users require a separate data import.
Teams requirements
- The data import must be run by a Global Administrator.
- A good comprehension of your Teams setup. You need the Teams ID for each team that you want to import. For details go to Manage teams in the Microsoft Teams admin center.
Before you begin
- Create an Azure application—To ensure a secure data import from Exchange Online to your Workspace account, you must first create a Microsoft Azure application in the Azure portal. For details, go to Set up an Azure application for Teams.
- Avoid duplicate spaces—If you roll out spaces for one batch of data and then start a new import for the same batch of data, the second import might create duplicate spaces in Workspace. To prevent duplication, avoid creating 2 separate imports for the same batch of data.
Run a data import
Step 1: Create a new import batch
In the Google Admin console, go to Menu
Data
Data import & export
Data import
Advanced.
You must be signed in as a super administrator for this task.
- For Advanced, click Create batch.
- For Batch name, enter a name for this batch of users and then click Continue.
- For Data type, click Microsoft Teams and then click Continue.
- For Client ID, enter the unique ID number for your Exchange Online account.
- For Client Secret, enter the client secret value for your Azure tenant.
- For Tenant ID, enter the unique ID number for your Azure tenant.
- Click Connect.
Step 2: Select teams to import
Create a comma-separated values (CSV) file that lists the teams that you want to import 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 5,000 users.
To create the CSV file:
- Using your Workspace administrator account, open a spreadsheet program. Or, in the Admin console, select Download a sample CSV file.
- Add the header Source MicrosoftTeamsID and enter a Teams ID for each team that you want to import. Use a separate row for each email team.
Example:
Source MicrosoftTeamsID 8f445146-9d80-b020-d50d5589ab bd4685f0-61f2-4789-4c1cda85d93 d0bef58c-9a55-4d8d-976c89n006 - Save the spreadsheet as a CSV file.
- Upload the file to the Admin console:
- In your Admin console, click Upload CSV.
- Select the file
click Open.
- Click Tasks
to confirm that the file is successfully uploaded.
- If the CSV file doesn't successfully upload:
- Select the file and click Delete
Yes to confirm.
- Create a new file and try to upload it again.
If you encounter this issue more than once, contact Google Workspace support.
- Select the file and click Delete
(Optional) Step 3: Create & upload an identity map
If necessary, create a second CSV file (separate from the file of Teams IDs) to map Teams 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 import by default. The completed CSV file must be smaller than 10 MB.
An identity map is not always required. You don't need an identity map if:
- The user's email address in Microsoft is the same as their address in Workspace. For example, the user's email address is raha@example.com for their Microsoft account and their 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. The users keep their username 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.
Create an identity map
- Using your Workspace administrator account, open a spreadsheet program. Or, in the Admin console, select Download a sample CSV file.
- In the first column, add the header Source Email and add an email address for each Teams user that you want to import. Use a separate row for each user.
- 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 group@example.com group@other-company.com - Save the spreadsheet as a CSV file.
- Upload the file to the Admin console:
- In your Admin console, click Upload CSV.
- Select the file
click Open.
- Click Tasks
to confirm that the file is successfully uploaded.
- If the CSV file doesn't successfully upload:
- Select the file and click Delete
Yes to confirm.
- Create a new file and try to upload it again.
If you encounter this issue more than once, contact Google Workspace support.
- Select the file and click Delete
Step 4: Select data import settings
Adjust the following settings to choose which data to copy from Teams.
- Click Edit settings.
- For Date range, select a date. The data import tool will copy all Teams events or messages that were sent or received after this date.
- To import all Teams users, including those not found in the identity map, ensure that the Copy accounts that aren't included in the map that are discovered during the data import box is checked and choose an option:
- If the user's email address in Teams is the same as their address in Workspace, check the Keep their original address box.
- If the domain name for all imported users is changing, check the Use a different email address domain for these accounts box and then select a domain from the list.
- Click Save changes.
Step 5: Start a data import
Starting a data import grants domain-wide delegation and creates a client ID for data import in Workspace. For more information, go to Control API access with domain-wide delegation.
- Click Run full import.
You can see updates on the following information in real time while the data import is in process:
- Discovered tasks—Number of tasks that were successfully completed
- Warning—Number of tasks that were completed but failed to complete as expected
- Failed—Number of tasks that failed to import due to an error
- Skipped—Number of tasks that were skipped because of certain data import settings, or because they were completed in a previous import
- Successful—Number of tasks that were successfully completed
- Channels discovered—Number of channels that were imported, skipped, or failed
- Spaces created—Number of channels that were imported to spaces
- Spaces skipped—Number of spaces that weren't created
- Discovery issues—Number of items that were unable to be read from Microsoft
You can navigate away from the import page without interrupting the import. Your import continues unless you cancel it.
When the import is complete, you get an email with import statistics. Any reports are attached.
- (Optional) To export a report for an import in progress:
- Click View data import logs or Export user report.
- If the Tasks list doesn't automatically open with the exported report, click Tasks
the report link.
- Click Open in Google Sheets to open the report in Sheets.
- For details about the reports, go to Understand Exchange Online data import reports.
Step 6: Stop an import in progress
To stop an import that's in progress, click Stop import. It might take a few minutes for the import to stop, and the import process does not roll back. If you're running other batches at the same time, those batches will continue to import.
Any Teams data that was imported before the stop isn't deleted from Workspace.
Step 7: Run a delta import
After you successfully import a batch of data, you can run a delta import to copy any newly added or updated data to Workspace. You can also use a delta import to copy data that failed in the initial import. If you imported the same data in 2 separate batches, a delta import won't create duplicate items as long as you haven't clicked Exit import to remove one of the batches.
For details, go to Run a delta import for chat data.
Step 8: Make spaces & messages available to users
After you complete the data import, make the imported spaces and messages available to Workspace users. You must complete this process within 90 days of the start of the import, or the imported spaces are deleted.
Important: Don't complete these steps if you still need to run a delta import.
- In your Google Admin console, click Roll out spaces.
In real time, you can review the number of spaces and messages that were successfully imported.
- When the process is complete, click Download logs to view information about which spaces and members were successfully added to users' Google Workspace accounts.
Note: If any spaces fail to import, click Roll out spaces again to retry the process on all the spaces that failed to import.
Retention & legal holds
Data import is intended as a productivity feature and is not designed to assist with legal compliance matters. You and your organization are responsible for assessing and meeting your organization's legal compliance needs. If you require files and folders for legal compliance purposes, consider backing up the files in Teams prior to importing data to Google Workspace.
Related topics
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.