Forum Discussion
Solved
Groups: Tenant to tenant migration
After a merge we are in the process of moving as much content as possible from one tenant to another.
The process a moving a unified group looks easy.
- Evaluate which groups should be migrated (and which groups should be abandoned)
- Create the corresponding group in the new tenant
- Use a migration tool to copy the content between mailboxes
- Use a migration tool to copy the SharePoint content between tenants.
There are a few things that are not so easy however:
Planner migration (which I suspect will be a manual process)
Connector migration which will absolutely be a manual process
I'm still investigating OneNote migration options.
Any thoughts, tips and pointers will be appriciated.
Groups use special forms of mailboxes that not all migration tools even reveal let alone access... That is my warning.
Just as an example, try using the Get-Mailbox cmdlet to list group mailboxes. They don't exist. You have to use Get-UnifiedGroup. But you can feed a group mailbox id into Get-MailboxStatistics... So it's inconsistent, hence the warning.
Just a quick note: OneNote is part of SharePoint, so it should move with the SharePoint content migration.
Hi.
I just create a q like this, can someone help me?
This is my scenario:
I have 100 mailbox in Office365 (online) and I want to move them to another Office365 (online). I want to keep my current email (Javier@source.com) and my new email (Javier@target.com).How can I do it?. I´m trying do it with Admin Office365 portal like "migratin from Online" but I´m not sure.By other hand, i have to give permission to my admin usr (the user that has permissons to migrate) in the endpoint. How can I do it?Hi Javier,
you can use the best T2T migration tool in the market. Check here for more information: https://help.bittitan.com/hc/en-us/articles/115008258788-Office-365-to-Office-365-Migration-Guide-While-Changing-the-Domain-Name
Look at your inbox I will ping you my contact in case you need any technical help.
Hi Mats,
A few migration tool are able to help you. One of them is the Cloudiway migration platform available online with an audit tool for your evaluation. You can also combine the SharePoint feature to migrate the content between two tenants. You will find more information on the web site https://cloudiway.com/solutions/google-groups-to-office-365-groups-migration
Feel free to reach out if you have any questions.
"the process of moving a unified group looks easy"...
That's some statement, especially because no OOTB tools are available to do the work.
The components you might have to deal with are as you listed, unless you use Teams, in which case you have chats etc. to move too. Planner and Teams share the same characteristics in that they store "their" data (as opposed to Files and plan comments) in data services outside EXO and SPO. You might be able to extract this data with the Microsoft Graph API.
SharePoint is easy enough because you are moving documents and files around - but be aware that metadata might be lost if you use file-level movement utilities. In other words, the devil is in the detail.
Extracting group conversations is, I think, possible with the Graph API too. Perhaps the AvePoint DocAve backup could help here as it now supports backup and restore of group conversations.
So getting at the data is possible. The issue might be stitching everything back together so that users see the same Groups as they had in the source and that all of the data belonging to those groups is in place and available, conversations are composed of the correct items, files are in the right libraries and have the right permissions (both for the group and any specific sharing), and so on.
Because no OOTB tools are available to do all of this, you are on your own. Good luck, fair sailing, and do let us know when you complete the task.
Well, Teams are a big problem right now, Planner is another biggie. I know that there are ways of using Microsoft Graph API to get all that data, I am unsure if I am also able to put that same information into the new tenant. But that is a bit academic since I'm not a developer. Luckily the use of Teams and planner is not wide spread in our old tenant.
Isn't group conversations really just a mailbox? as opposed to Teams conversation which is I-Don't-Know-What?
And Files is just a sharepoint site/DocLib?
We thought we just needed to recreate the target groups, use a mail migration tool like MigWiz or BitTitan to move the contents of the mailboxes.
Use Sharegate or another tool to migrate the sites/doclibs..
The notebook migration should be relativiely easy too, even if manual. Just move the sections between the notebooks using OneNote.
We are a relatively small company with only about 350 users so even if it wont be done in a day it's not an overly complicated process.. Unless I'm missing something?
Planner and teams are, like I said, a different story.
Im not saying that it is a fast process, but not an overly complicated one. Unless
Groups use special forms of mailboxes that not all migration tools even reveal let alone access... That is my warning.
Just as an example, try using the Get-Mailbox cmdlet to list group mailboxes. They don't exist. You have to use Get-UnifiedGroup. But you can feed a group mailbox id into Get-MailboxStatistics... So it's inconsistent, hence the warning.
Regarding Planner migration, please check the below thread.
https://techcommunity.microsoft.com/t5/Planner/Ability-to-migrate-Planner-content/m-p/40070#M474
