Games  

Migrate Hipchat to Microsoft Teams

Trying to migrate Teams resources from one tenant to some other? We explicate ii means to tackle your Microsoft Teams migration—ensuring users accept everything they need to succeed in their new Teams surround.

Microsoft Teams has become key to the Microsoft 365 user experience—with new and improved features, an like shooting fish in a barrel-to-use interface, and seamless integration with other Microsoft tools.

With the content created in Teams now more than valuable than ever, the ability to migrate this data as needed is no longer a nice-to-have; in the context of a merger or conquering, it’s a critical procedure to ensure our workflows as well transition with united states of america seamlessly.

Hither at ShareGate, we’re well-known for our SharePoint migration tool. And since Teams lives in the same Microsoft 365 ecosystem, we’ve gotten a lot of questions from our customers almost how to migrate their Teams environment to a new tenant, also.

Ensure your Teams Migration is a success
by checking out our complete

Guide to Teams Migration
ebook , we encompass everything before, during and after the migration procedure in a simple, easy-to-read guide plan.


Microsoft Teams migration: Why it’s a claiming

The crux of the problem stems from the fact that most Teams data isn’t stored in Teams; information technology’s actually stored in the post-obit locations:

  • SharePoint team site:
    Files and folders stored in the team document library or shared in a channel, external emails sent to the team, the squad’s wiki page, and each channel’s OneNote assets.
  • Commutation team mailbox:
    Grouping chat and channel chat conversation history, team mail, and contacts.
  • Exchange mailboxes of individual users:
    Private (1:1) conversation conversation history, voicemails, and agenda meetings.
  • OneDrive for Business of individual users:
    Files fastened to private chat sessions, or a conversation during a meeting or call, are uploaded and stored in the OneDrive account of the user who shared the files.
  • OneDrive organizational document library:
    Users’ personal OneNotes.
  • Azure (using Blob storage):
    Images and media (except for GIFs) shared in chats.
  • Stream:
    Meeting recordings.
  • Third-political party storage provider:
    If your organization allows users to store files with a third-party storage provider, either through tabs or other partner apps, that information is stored directly in the organisation used past the partner.

This data sprawl, paired with a lack of publicly available APIs from Microsoft, make it incommunicable to migrate Teams automatically using Microsoft’s out-of-the-box solutions.

Related reading:
What is data sprawl, and how does it relate to role 365 Groups?


Option #1: Drift Microsoft Teams from i tenant to another manually

Migrating Microsoft Teams data to another tenant manually involves multiple steps and a ton of heavy lifting on the part of It.

Technically, there’s no piece of cake, out-of-the-box style to migrate Microsoft Teams betwixt Microsoft 365 tenants.
But yous
tin
motion some of the underlying components, such as the files stored on the associated squad SharePoint site and grouping chat and aqueduct conversation history stored in the team’s Exchange mailbox.

While there are a few unlike ways you can go almost doing this, we’re going to walk you through ane of the nigh straightforward methods that
doesn’t
involve whatsoever third-party tools.

To migrate your Microsoft Teams to another tenant manually, yous need to:

  1. Re-create the teams you want to migrate at the destination
  2. Add all of the right users and permissions to each team
  3. Download the contents of the associated SharePoint squad sites and upload at the destination
  4. Export conversations from the team’s Exchange mailbox, so import them at the destination every bit a document

Step #1: Re-create the teams you lot want to migrate at the destination

Earlier you lot copy any Teams content, y’all need to create teams in your new Teams environment and so that content has a destination.

Essentially, this means re-creating the structure of your source Teams—including the channels and tabs inside each squad. Sound time consuming? That’s because it is. But you’re simply getting started.

Step #2: Add all of the correct users and permissions to each team

Once y’all accept the scaffolding gear up in your new Teams surroundings, yous need to populate information technology properly. That means adding all of the correct users and permissions to each team.

Assuming you lot followed migration best practice, you should already take all your users added at the destination Azure Active Directory. So what you lot’re really doing in this step is inviting users to join the same teams they were members of in the erstwhile Teams surround.

Popular:   Wasd Movement League of Legends

To invite bulk users to a Microsoft Teams team, you need to:

  1. Excerpt users/permissions to a CSV file
  2. Modify the domains associated with each user
  3. Add together users to the destination teams from the CSV file
  4. Alter permissions inside each squad

Excerpt users/permissions to a CSV file

The first thing y’all demand to exercise is generate a listing of details about your existing Microsoft Teams. There’southward no mode to do this using Microsoft tools, so hopefully yous’re comfortable with scripting!

To export details about all of the teams in your source tenant, you can run a slightly modified version of
this PowerShell script.


Notation:
Y’all need to have the
SharePoint Online PnP PowerShell module
installed in order to run this script.

When we ran the script as is, it didn’t render any of the channel information. But we institute that information technology worked perfectly if you lot simply change “Groups” to “teams” in line 22 (between “beta/” and “/$id):

        $team = Invoke-RestMethod -Headers @{Authorization = "Bearer $accesstoken"} -Uri https://graph.microsoft.com/beta/teams/$id/channels -Method Get
      

When prompted, be sure to sign in with your source tenant credentials.


Run the modified script in PowerShell.

The resulting CSV file includes the following information for each squad:

  • Squad name
  • Team type
  • Number of channels
  • Channel names
  • Squad owner
  • Squad fellow member count
  • Team members
Resulting CSV file.

The resulting CSV file should wait something like this.

Change the domains associated with each user

Now it’due south fourth dimension to go creative! In club to map your existing squad membership at the destination tenant, we need to modify the old domain name to the new domain name in the CSV file.


Note:
This method will just work if the usernames are unchanged at the destination.

Using the Find and Replace features in Excel (or whatsoever app you’re using to view the CSV file), alter the onetime domain proper noun that appears after each username to the destination domain name.

Find and replace feature in Excel.

Replace the domain name in all of the user email addresses.

Add together users to the destination Teams from the CSV file

Now that you have your modified CSV file, yous’re going to employ PowerShell (again) to upload/invite those users to your newly created teams.

Running
the PowerShell script outlined in this weblog post
will let you to add multiple users from a CSV file to a Microsoft Teams team.


Note:
You need to have the
Microsoft Teams PowerShell module
installed in order to run this script.

If you go a response when installing saying that the “Get-Team” command is already bachelor (similar I did), you might need to use the “-AllowClobber” parameter to proceed.

I should also signal out that you lot need to be running PowerShell in administrator mode to install the Teams PowerShell module and while running the following scripts.

Outset you need to connect to your destination Microsoft Teams so that you can run the commands to add together users. You can do and then past running the post-obit control:

        Connect-MicrosoftTeams
      

Sign in with your credentials (electronic mail and password) associated with your new Microsoft Teams environment.

Once connected, run the following control to generate a list of all your teams and their associated grouping IDs:

        Get-Team
      
Get-Team PowerShell command.

Note the GroupID next to the proper name of each squad.

This method simply allows you to add users in bulk to one team at a fourth dimension. And so now y’all need to go dorsum to your modified CSV file and:

  1. Copy the user emails from the “Members” column for an individual team.
  2. Create a new CSV file and input the user emails in i electronic mail column, with i user e-mail per line. Save equally a CSV file.
  3. Repeat for every team.
New CSV file for individual team.

New CSV file with members of the HR team.

Back in PowerShell, run the following control to invite all of the users in a CSV file to the new team. (Input the team’s group ID where it says YOUR_TEAM_ID in the script, and supercede YOUR_FILE_PATH with the file path to the CSV file with that team’southward listing of users.)

        Import-Csv -Path "YOUR_FILE_PATH" | foreach{Add-TeamUser -GroupId YOUR_TEAM_ID -user $_.e-mail}
      

If all goes well and the users are added correctly, you lot shouldn’t run into any messaging after running the script. Go along with running the script again for each of your new teams.

Popular:   The Realist Hero Rebuilt the Kingdom Wiki

When you’re finished, you lot should run into all of the users you added in the corresponding teams in the Teams app and the Microsoft Teams admin middle:

Teams in destination Teams admin center.

Members added to teams at the destination Teams admin center.

Change permissions within each squad

If everything has gone smoothly upwards until this bespeak, congratulations! You can move onto the last stride (of this footstep): manually promoting the correct members to owners within each squad.

Your modified CSV file—that 1 that includes the details of all your teams and has multiple columns—has an “Owners” column. Use the user emails in that column to manually place and add the same owners to all of your new teams.

Modify permissions for each team.

Restored permissions visible in Microsoft Teams app.


Step #3: Download the contents of the associated SharePoint squad sites and upload at the destination

With the structure and membership of your teams successfully copied, the next step is to copy the contents of those teams—all of the content mentioned in a higher place that’due south actually stored in a team’south associated SharePoint site.

Because nosotros’re performing a tenant to tenant migration, you can’t just
reorganize that content with SharePoint’due south congenital-in “Copy” and “Motion” features—that would only work if y’all were trying to movement content to some other team site within the same tenant.

To move SharePoint content from one tenant to some other manually, you’re going to take to download information technology from the source tenant and upload it at the destination.

At the very least, you should do this with the contents of each team’s “General” folder in SharePoint. This folder stores the contents of the “Files” tab visible in Microsoft Teams—in order to go users up and running in their new Teams surround as speedily as possible, you definitely desire to move this content as function of your initial Teams migration.

But navigate to each team’s SharePoint site, select the contents of the “Full general” folder, and click the
Download
button at the peak of the user interface.

Download the contents of the General folder.

Download the files from the source team site…

When you lot created your new teams at the destination Teams, an associated SharePoint squad site was automatically provisioned for each squad. Once you’ve downloaded the documents from the source tenant, navigate to the respective team site at the destination tenant and upload that content to the “Full general” binder at that place.

Upload files at destination.

…and upload at the corresponding destination site.

Non only is this method time-consuming, but it will just work for the files and folders within a SharePoint team site’s document library; you won’t be able to download/upload entire SharePoint pages or lists.

It’southward besides worth noting that you’ll likewise lose all of the metadata associated with those files forth the way. And if your library uses versioning, you’ll only get the latest version—none of your previous versions will exist moved over.

Step #iv: Consign/import Teams chat history

As mentioned above, group chat and channel conversation conversation history alive in each team’s Exchange mailbox. To access this information yous’re going to accept to turn to PowerShell (again!).


Annotation:
You need to
connect to Exchange Online PowerShell
in guild to run the following script. Microsoft recommends using the Exchange Online PowerShell V2 module in order to do so.

Verify the GroupMailbox and TeamChat contents with PowerShell

In PowerShell, connect to your source Teams tenant and run the following control to generate a listing of all the grouping mailboxes:

        Get-mailbox -GroupMailbox | select Displayname, WindowsEmailAddress
      

To view the details of the mailbox folders for a specific team, use the corresponding WindowsEmailAddress and run this command:

        Become-mailbox -groupmailbox Team@mycompany.com | Get- MailboxFolderStatistics | select Foldertype,ItemsInFolder
      

You lot should exist able to view the item size of the TeamChat folder from the output. Echo this step for every squad you want to migrate to verify each squad’s contents.

Consign each squad’southward TeamChat information

Now head over to your source tenant’s Security and Compliance centre and run a search for the contents of 1 of the teams you want to migrate.

  • Navigate to the
    Content search
    page and create a
    Guided search. Input a name for your search, something like “Hr chat history”.
Enter a name for your serach.
  • Choose the related Teams grouping as the location and add a condition of
    Blazon
    >
    Equals any of
    and select
    Email messages
    and
    Instant messages, then save and run your query.
Popular:   Outbreak Unknown Signal Cold War
Add a query that equals any of E-mail messages and Instant messages.
  • When your query has finished running, in the
    More
    drop-down menu click on
    Export report.
  • Cull one of the
    All items
    export options, then click on
    Download written report.
screenshot of export report screen

  • Once the written report has been exported, open it in a compatible client to view and relieve the team’s chat history. To brand the conversation history viewable for team members, save it every bit a document and upload it to the “General” binder in the squad’s associated SharePoint site (that style information technology will be visible in the team’s “File” tab in Microsoft Teams).
  • Repeat for every squad you want to drift.

While this manual migration method lets you majority-add members to the destination teams and move over a team’s group chat and channel conversation history, it’s
extremely
fourth dimension-consuming—involving multiple steps, some of which need to be repeated for each squad.

Obviously, trying to migrate Microsoft Teams manually is not an ideal situation for an organization’s IT team.


Option #2: ShareGate’s migration tool for Teams and SharePoint

Migrating existing Teams resources and data is more than crucial than ever, especially in the context of a merger or conquering. Simply all of that scripting and all of those steps brand manual Teams migration a painful and deadening process!

Instead of jumping through all those hoops to get users upwardly and running in their new Teams environment, why not use a third-party tool to simplify the process?

Migrate Microsoft Teams to another tenant—the ShareGate style

Equally you can see past now, with no easy option available to efficiently migrate Microsoft Teams to a new tenant, our engineers put a lot of idea and endeavour into creating an easier, faster fashion to ensure users take everything they need to succeed in their new Teams environment.

ShareGate introduced a dedicated Microsoft Teams migration feature to
our popular migration tool. In just a few clicks,
migrate teams to another tenant—or copy teams within the same tenant—without the need to script.

We as well automatically map users at the destination. That way, you lot’re sure the right people have admission to the right teams with the right set of permissions.

With ShareGate’south migration tool, you lot can bring along:

  • Team settings and clarification
  • Membership (owners and members)
  • Permissions
  • Conversation history (including sender, threaded messages, links, and timestamps)
  • Public channels
  • Lists
  • Files (along with their history and metadata)
  • Tabs
  • Apps and bots (those that are available in the App Store)
  • SharePoint site customizations
  • Default wiki pages
  • OneNotes

Here’due south how information technology works:

1. First at the Copy screen.
Navigate to the reimagined
Copy
screen and select the
Copy teams
option.

Osg Public Migration 3

2. Cull which teams (and channels) to migrate.
Just connect to the tenant you want to migrate from and ShareGate generates a list of all your existing teams along with information most each team’s ownership and privacy settings. Select the teams y’all want to move, then click on
Go on to destination.

Sgm Public Teams Migration 1

Select individual channels within each team
that yous want to bring. That way, y’all but drift the channels you need to.

3. Configure custom copy options.
Side by side, select the destination you’d like to copy to…

Sgm Public Teams Migration 2 1

…and then, cull whether you want to copy to a new team at your destination or copy into an existing squad.

ShareGate’s migration tool also flags potential issues, like duplicate team and aqueduct names, and prompts you lot to modify names past adding a prefix or suffix—or irresolute the name completely—before your migration takes place.

Sgm Public Duplicate Channel Rename Prefix Suffix

Finally, select
Schedule copy
to choose a time for the migration to take place that’s user-friendly for you. When you’re ready, click on
First copy. That’s it!

4. Find and fix bug faster with our robust migration report.
In one case your migration is complete, ShareGate provides you with a summary and then you can run into how it went. If anything unexpected did pop up, nosotros’ll provide you with the information you need to set up information technology fast.

Sgm Public Teams Migration Report

And if you e’er need additional assist, our world-class support team is always bachelor to help.

Ready to offset your Microsoft Teams migration?
Here’s a walk-through of how to get started with copying Teams and their channels
to easily reorganize and restructure your organization.

What did you think of this article?

Source: https://sharegate.com/blog/2-ways-migrate-microsoft-teams-from-one-tenant-to-another