Clear the created applications, validate the domain in new tenant and change the MX records. Test the email flow inside and outside working fine. We have not seen any issues after this migration.
Thank you very much for this, worked like a charm! I know that the Microsoft documentation mentions that the ExchangeGUID and LegacyExchangeDN need to be present, but didn't realise in this way and was stumped as to why this kept failing. Thanks again, you're amazing!
A quick question , did you guys applied any additional license like cross tenant user data migration .. in the article it is mentioned - Cross Tenant User Data Migration licenses are also applied to all the users that will be migrated to the target side... your feedback is appreciated as i have project in hand to complete.
@@9920528461 There is no additional license applied for this migration apart from the basic M365 licenses. Soon there will be additional license for migration.
@@manyal2103 Thanks for confirmation. I read about applying cross tenant user data migration .. thus wanted to double check.. I'll be testing this out asap and can confirm whether cross tenant user data migration is an optional thing... Thanks for prompt reply bro!
A very useful and informative set of videos. I'm in the starting phase of planning for a migration of users however from our on-prem Exchange environment into M365. Great knowledge though.
Most helpful video I have ever found! Thanks a lot. I have questions: 1. How can I reduce the amount of work where for each user has to add the X500 value? Maybe there are some scripts for this? 2. Does cross-tenant migration migrate only mailboxes? does it leave files from Sharepoint, Onedrive, chats, channels from Teams and Outlook, calendar? how can i migrate them?
Thanks for the positive feedback. 1. I don’t see any fast process, may be we need to write PS but I think this will also take time since the command has to run for all the users. 2. Migration will include mailbox, including contacts and calendar. Sharepoint and onedrive has to be done manually at the moment. I might find a way and I will make a video on that.
First off, great videos. Extremely helpful! Curious if this process can be done with Shared Mailboxes. Also reaching out to Microsoft on their new Cross Tenant Identity Mapping tool.
Perfect Sir. Thanks for all your knowledge and efforts, I have no words to admire. Just need to know one thing, after the migration is completed what are the steps to clean both the environments (Source & Target ) to make as it was before Migration ? I can delete the Application and Endpoint but what would be the best practice/steps to delete everything related to this Migration ? I have no urgency but please respond at your time. Once again Thank you very much.
Very good tutorial, thank you! What if you have a user in the Source and Destination Tenant with existing mailbox in both. Will the Migration merge the mailboxes?
Thanks Wayne. This can happen if you have same username in different domains under the same tenant. The only choice is to change the name during the migration. Keep a record and once complete. Create the Alias with existing name and make it primary address. Sorted 😀
@@manyal2103 Wouldn't that create a new mailbox? Now there would be two mailboxes for said user. So it is not possible for it to merge the migrated mailbox into the already existing mailbox in the destination tenant? Again, thanks for you thoughts!
Great work on this video. 1 question, i have a user that has a mailbox size as 102GB, the user have a office 365 business standard and Exchange Plan (Plan 2) license. both on the old and new tenant. When i try a test migration, the result failed. Mailbox size 102.1 GB (109,625,155,681 bytes) exceeds target quota 100 GB (107,374,182,400 bytes) any idea what wrong? or what can be done?
Thanks for the great Video... I have couple of questions here... 1. Does the permissions are migrating properly like SendAs, Sendonbehalf, Full access and Calendar permissions... ? Do we need to manually apply permissions after Migrations? 2. If we have 3000 mailboxes in source tenant, what is the best approach to automatically sync those users to target tenant a mail user... ?
Hi @mayilragavan, don’t go for this migration type if you are more than 3000 users. I will prefer to go for a 3rd party tool like Quest or Bittitan or something else. These tools will help you to migrate easily. Which country are you in?
@@manyal2103 Thanks... I am based out of India.... Yes, we are using bittitan only... Our intention to avoid 3rd party and to explore how to use this native method.... I am preparing a guide such as advantage and disadvantage of this native method... So that I asked that
And Also please make a short video on Post migration Clean up activities on the DNS level how we can decommission the old O365 tenant on a DNS level and on O365 Old tenant level
Thank you for the great video. I am going to use this cross tenant migration to move mailboxes from old tenant to a new tenant. My aim is to keep the same custom domain name when I move from the old tenant to the new tenant. I know the email cutover will happen when I add the custom domain under the new Tenant and make it the default domain. Could you advise when would be best to remove the custom domain from the Source Tenant? I am thinking will it be after migration batch is completed? So users don't have interruption in their incoming email.
If you have sufficient downtime. You can remove the domain earlier also. But usually, you change the users custom domain before you start the migration and remove as soon as your migration is completed
The video is very well explained, but I would like to understand one thing. If the source account had not only email, but also data in OneDrive, Teams and SharePoint, after these resources mentioned, could I delete the enterprise application and the endpoint migration?
Hi there. Thank you so much for the hands-on-lab demo. Let me ask a small question. In case, the manually completing batch will be chosen, the source users won't be conveeted until I press finalize? In case I have 500 mailboxes to migrate I can sync all mailboxes in advance w/o any interption for the users and finalize the batch during the weekend aftwerwards.
The mail enabled security group doesn’t support more than 100 users. You can add selecting 5 users in bundles to reach 100 +. But consider that you will be able to migrate 100 users in 1 batch or you will have to create multiple end points and mail enabled security groups to perform them all. Once the mailbox is synced, but the batch is not completed for others, it won’t create the mailbox and it will keep a sync in 24 hrs (as per my test).
@@manyal2103 Thank you again. Even though, we can add more than one Security Group in the attribute MailboxMovePublishedScopes @{Add="Value1","Value2"...; Remove="Value3","Value4"...} of cmdlet Set-OrganizationRelationship. I suppose (or I guess), that we can add as many groups as we need with less than 100 users in each of them. Wait untill the migration will be in synced state, then in black Friday evening press finalize and beg the Cloud forces than finalization will over during the 24 hours
Great video, let me just ask: In a scenario we would want to migrate from one tenant to another and keep the email accounts running on the source tenant and just transfer the mailbox data to the destination tenant is this possible ? I have come a long way to realise Bititan might be the better option because of this reason and you can also do a migration to transfer the big bulk of the data and then later on just do another small migration to transfer the rest of the data which has accumulated.
It was possible earlier when we were dependent on IMAP migration. With the current setup, we create an environment where O365 understands the identities on the source tenant also. One the migration is completed, it changes to mailuser. The objective of sharing this video is to show the No cost way with Microsoft. Your opinion is right, you can go for Quest or Bit-titan.
Thanks Much for the video ,,,I have one Question.... on a hybrid we usually have directory sync / azure ad connect for the object to sync to O365 instead creating objects manually , On a tenant to tenant Migration do we have this option(Syncing ) on tenant to tenant on O365 side to over come this manual work for the larger origination .
Hi, First of all thankyou for the great lesson. I had to migrate with archive mailbox too. It got migrated, I can see the archive mailbox under Manage mailbox archive in Exchange admin center. But, when I go to outlook archive mailbox not shown. Any idea what I am missing?
I hope you the ID’s were mapped correctly along with the archive ID’s. If yes then it should work fine since the archive mailbox is mapped to the same user. Else take support form Microsoft
Thank you so much for your efforts, i have a question. I need to transfer one domain listed in my organization from many domains to be a separate domain. is there a solution for that?
I'm planning migration of exchange mailboxes from one tenant to another and i saw a lot of articles on this but non of them mentions about the Cross Tenant Migration addon. The Microsoft documentation however says you need an addon . Did you use any Add-on for in addition to your MS license for the source tenant users? Please reply.
I am seeing a skipped item in the migration batch which says "MrsLicenseMissing". Pretty sure this is because I don't have the "Cross Tenant User Data Migration", and we are NOT an EA customer so I'm not sure how to get it. Everything SEEMS to be working without it, but I also have not completed the process so I'm not sure.
After Comple the batch if the source email ID becomes mail user insted mailbox, that user will not be able to accessmail? What will be the process in Source ?
@@mohamedberawy6875 Did you find a solution to this? I have ran into this error as well at the Exchange Migration step. I am chatting with MS support, they seem to be confused as well with both the error and not having the option to purchase the Migration license on either our source or destination tenants.
No, this is for mailbox migration only. If you want to do a consolidated migration for mailbox, onedrive, sharepoint and teams. Suggest to use 3rd party tools.
Hello, after the migration, you will assign the license to the mailbox in the destination tenant. The mailbox from the source tenant will be changed to mail user. You should not have the primary user as a mailbox after the migration.
@@manyal2103 Migration completed, my new tenant has changed to mailbox and old tenant has changed to usermail. Now I want the mail in the old tenant to be converted into a mailbox, what should I do?
I was able to perform the migration without problems but the destination email when I tried to send an email I got a message Remote server returned '550 5.7.501 Service unavailable😱
Hello Mandi, this was a great video series, look forward to what you do next!
Clear the created applications, validate the domain in new tenant and change the MX records. Test the email flow inside and outside working fine. We have not seen any issues after this migration.
Thank you very much for this, worked like a charm! I know that the Microsoft documentation mentions that the ExchangeGUID and LegacyExchangeDN need to be present, but didn't realise in this way and was stumped as to why this kept failing.
Thanks again, you're amazing!
Glad that it helped you. Please like the video
A quick question , did you guys applied any additional license like cross tenant user data migration .. in the article it is mentioned - Cross Tenant User Data Migration licenses are also applied to all the users that will be migrated to the target side... your feedback is appreciated as i have project in hand to complete.
@@9920528461 There is no additional license applied for this migration apart from the basic M365 licenses. Soon there will be additional license for migration.
@@manyal2103 Thanks for confirmation. I read about applying cross tenant user data migration .. thus wanted to double check.. I'll be testing this out asap and can confirm whether cross tenant user data migration is an optional thing... Thanks for prompt reply bro!
@@9920528461 waiting for your like on the videos.
A very useful and informative set of videos. I'm in the starting phase of planning for a migration of users however from our on-prem Exchange environment into M365. Great knowledge though.
Thanks for the feedback Justin. All the best for your migration. Let us know if you have any questions. Happy to help.
Amazing video. Obrigado por compartilhar!
Most helpful video I have ever found!
Thanks a lot.
I have questions:
1. How can I reduce the amount of work where for each user has to add the X500 value? Maybe there are some scripts for this?
2. Does cross-tenant migration migrate only mailboxes? does it leave files from Sharepoint, Onedrive, chats, channels from Teams and Outlook, calendar? how can i migrate them?
Thanks for the positive feedback.
1. I don’t see any fast process, may be we need to write PS but I think this will also take time since the command has to run for all the users.
2. Migration will include mailbox, including contacts and calendar. Sharepoint and onedrive has to be done manually at the moment. I might find a way and I will make a video on that.
Great video! Thank you!
Thank you for your feedback
First off, great videos. Extremely helpful!
Curious if this process can be done with Shared Mailboxes.
Also reaching out to Microsoft on their new Cross Tenant Identity Mapping tool.
Yes, absolutely. They are coming up with new license for mergers and acquisitions. I will explore that meanwhile.
Perfect Sir. Thanks for all your knowledge and efforts, I have no words to admire. Just need to know one thing, after the migration is completed what are the steps to clean both the environments (Source & Target ) to make as it was before Migration ? I can delete the Application and Endpoint but what would be the best practice/steps to delete everything related to this Migration ? I have no urgency but please respond at your time. Once again Thank you very much.
Very good tutorial, thank you! What if you have a user in the Source and Destination Tenant with existing mailbox in both. Will the Migration merge the mailboxes?
Thanks Wayne. This can happen if you have same username in different domains under the same tenant. The only choice is to change the name during the migration. Keep a record and once complete. Create the Alias with existing name and make it primary address. Sorted 😀
@@manyal2103 Wouldn't that create a new mailbox? Now there would be two mailboxes for said user. So it is not possible for it to merge the migrated mailbox into the already existing mailbox in the destination tenant?
Again, thanks for you thoughts!
Great work on this video.
1 question, i have a user that has a mailbox size as 102GB, the user have a office 365 business standard and Exchange Plan (Plan 2) license. both on the old and new tenant.
When i try a test migration, the result failed. Mailbox size 102.1 GB (109,625,155,681 bytes) exceeds target quota 100 GB (107,374,182,400 bytes)
any idea what wrong? or what can be done?
Thanks for the great Video...
I have couple of questions here...
1. Does the permissions are migrating properly like SendAs, Sendonbehalf, Full access and Calendar permissions... ? Do we need to manually apply permissions after Migrations?
2. If we have 3000 mailboxes in source tenant, what is the best approach to automatically sync those users to target tenant a mail user... ?
Hi @mayilragavan, don’t go for this migration type if you are more than 3000 users.
I will prefer to go for a 3rd party tool like Quest or Bittitan or something else. These tools will help you to migrate easily. Which country are you in?
@@manyal2103 Thanks... I am based out of India.... Yes, we are using bittitan only... Our intention to avoid 3rd party and to explore how to use this native method.... I am preparing a guide such as advantage and disadvantage of this native method... So that I asked that
All the best for your project. I will be easy.
@@manyal2103 Thank you so much for your response and video
And Also please make a short video on Post migration Clean up activities on the DNS level how we can decommission the old O365 tenant on a DNS level and on O365 Old tenant level
Thank you for the great video.
I am going to use this cross tenant migration to move mailboxes from old tenant to a new tenant. My aim is to keep the same custom domain name when I move from the old tenant to the new tenant. I know the email cutover will happen when I add the custom domain under the new Tenant and make it the default domain.
Could you advise when would be best to remove the custom domain from the Source Tenant? I am thinking will it be after migration batch is completed? So users don't have interruption in their incoming email.
If you have sufficient downtime. You can remove the domain earlier also. But usually, you change the users custom domain before you start the migration and remove as soon as your migration is completed
The video is very well explained, but I would like to understand one thing. If the source account had not only email, but also data in OneDrive, Teams and SharePoint, after these resources mentioned, could I delete the enterprise application and the endpoint migration?
Yes you can delete. But one drive data will stay there and has to be done manually or use the 3rd party tools for migration for smooth transition
Hi there. Thank you so much for the hands-on-lab demo. Let me ask a small question. In case, the manually completing batch will be chosen, the source users won't be conveeted until I press finalize? In case I have 500 mailboxes to migrate I can sync all mailboxes in advance w/o any interption for the users and finalize the batch during the weekend aftwerwards.
The mail enabled security group doesn’t support more than 100 users. You can add selecting 5 users in bundles to reach 100 +. But consider that you will be able to migrate 100 users in 1 batch or you will have to create multiple end points and mail enabled security groups to perform them all. Once the mailbox is synced, but the batch is not completed for others, it won’t create the mailbox and it will keep a sync in 24 hrs (as per my test).
@@manyal2103 Thank you again. Even though, we can add more than one Security Group in the attribute MailboxMovePublishedScopes @{Add="Value1","Value2"...; Remove="Value3","Value4"...} of cmdlet Set-OrganizationRelationship. I suppose (or I guess), that we can add as many groups as we need with less than 100 users in each of them. Wait untill the migration will be in synced state, then in black Friday evening press finalize and beg the Cloud forces than finalization will over during the 24 hours
Good, I have not tried this. Try and update. It will be helpful for lot of people.
Great video, let me just ask: In a scenario we would want to migrate from one tenant to another and keep the email accounts running on the source tenant and just transfer the mailbox data to the destination tenant is this possible ?
I have come a long way to realise Bititan might be the better option because of this reason and you can also do a migration to transfer the big bulk of the data and then later on just do another small migration to transfer the rest of the data which has accumulated.
It was possible earlier when we were dependent on IMAP migration. With the current setup, we create an environment where O365 understands the identities on the source tenant also. One the migration is completed, it changes to mailuser.
The objective of sharing this video is to show the No cost way with Microsoft.
Your opinion is right, you can go for Quest or Bit-titan.
Can you post the video for Domain migration and user migration
Thanks Much for the video ,,,I have one Question.... on a hybrid we usually have directory sync / azure ad connect for the object to sync to O365 instead creating objects manually , On a tenant to tenant Migration do we have this option(Syncing ) on tenant to tenant on O365 side to over come this manual work for the larger origination
.
Microsoft is will be releasing the paid license very soon to achieve such cases
Hi, First of all thankyou for the great lesson.
I had to migrate with archive mailbox too. It got migrated, I can see the archive mailbox under Manage mailbox archive in Exchange admin center.
But, when I go to outlook archive mailbox not shown.
Any idea what I am missing?
I hope you the ID’s were mapped correctly along with the archive ID’s. If yes then it should work fine since the archive mailbox is mapped to the same user. Else take support form Microsoft
Thank you so much for your efforts, i have a question. I need to transfer one domain listed in my organization from many domains to be a separate domain. is there a solution for that?
Yes, you can. Process is same.
Thank you
You're welcome
How did you get Addon license, it is for enterprise customers only right?
Yes. I feel so. Didn’t see any clear instructions. I would prefer to migrate using 3rd party than Microsoft tool bcs of manual tasks and cost.
I'm planning migration of exchange mailboxes from one tenant to another and i saw a lot of articles on this but non of them mentions about the Cross Tenant Migration addon. The Microsoft documentation however says you need an addon . Did you use any Add-on for in addition to your MS license for the source tenant users? Please reply.
No. No addon is used here at the moment.
I am seeing a skipped item in the migration batch which says "MrsLicenseMissing". Pretty sure this is because I don't have the "Cross Tenant User Data Migration", and we are NOT an EA customer so I'm not sure how to get it. Everything SEEMS to be working without it, but I also have not completed the process so I'm not sure.
@Mandeep I have to do a migration from Google Drive to GCC office 365 Tenant. Can you guide me how I can proceed with it.
Now you should use 3rd party tools like bittitan
After Comple the batch if the source email ID becomes mail user insted mailbox, that user will not be able to accessmail?
What will be the process in Source ?
That’s how it should be. The mailbox become active in the destination.
Extemly great video.. but i dont know why you were hurrying up in the last 10 mins. you could have paused and continued.. Hope it works
Hi it asking for licenses of cross tenant migration is that needed..
not yet
but where my onedrive data, pls tel me about it?
Hi, I am working on that video. You will see it soon. 😊
Do we need add-on license for user Data cross tenant migration when we have basic license
Not at the moment.
@@manyal2103 When I tried I got error about missing license
@@mohamedberawy6875 Did you find a solution to this? I have ran into this error as well at the Exchange Migration step. I am chatting with MS support, they seem to be confused as well with both the error and not having the option to purchase the Migration license on either our source or destination tenants.
is there any other option to create batch and enter target delivery domain Manually
Suggest to follow the mentioned process. I have tried other ways but it didn’t work and I had some issues.
what about the calendar events?
It will be migrated along with contacts since it is a mailbox migration
Hello Sir, Target delivery domain not showing in destination migration batch.. plz help me where i mistaken
Hi Manish, I need to take a look on a session. Is it a production environment?
Hi, will this migrate OneDrive, Sharepoint, Teams data as well.
Thanks in advance
Hi Ali, this will only move the mailbox data.
cross tenant migration for SPO/ODfB like this is still in Private Preview
Does this include OneDrive data as well?
No, this is for mailbox migration only. If you want to do a consolidated migration for mailbox, onedrive, sharepoint and teams. Suggest to use 3rd party tools.
@@manyal2103 Thanks
hi,when the migration is done how do i get the mailuser back to the mailbox. Thanks
Hello, after the migration, you will assign the license to the mailbox in the destination tenant. The mailbox from the source tenant will be changed to mail user. You should not have the primary user as a mailbox after the migration.
@@manyal2103 Thanks, I asked how to change usermail to mailbox in tenant cloudedteam.onmicrosoft.com
hi Concept Works, can my case be handled? Thank you
Sure, we can work on this. I would need some more details about the farm.
@@manyal2103 Migration completed, my new tenant has changed to mailbox and old tenant has changed to usermail. Now I want the mail in the old tenant to be converted into a mailbox, what should I do?
I was able to perform the migration without problems but the destination email when I tried to send an email I got a message Remote server returned '550 5.7.501 Service unavailable😱
I hope your domains are proper