What is IMAP Migration | How IMAP Migration works | Migrate Emails from Outlook.com to Office 365

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
hi guys i hope you all are doing well and welcome to office 365 concepts in this particular video we will be talking about imap migration we will be discussing what is imap migration and in what scenarios imap migration is performed we will be discussing what are limitations of imap migration what are the prerequisites or the steps those are involved in imap migration and then i will demonstrate you how to create imap migration endpoint and we will migrate emails from outlook.com account to office 365 account also i will be showing you how to troubleshoot the migration process using powershell commands so first let's understand what is imap migration imap migration is used to migrate emails from the source email system to office 365. let's assume you use outlook.com to manage your emails the users of your organization use outlook.com to send and receive emails so that means outlook.com is the email provider for your organization now let's say you decided to move to office 365. you want to use office 365 services and you want exchange online to host your mailboxes and the contents of the mailboxes so first option that you have in this scenario is to export the contents of the mailboxes into a psd file and export that pst file to the office 365 mailbox but this option is not feasible if you have multiple mailboxes or users in your organization if you have more than 1 000 users or 10 000 users in your organization you can't just export the psd file for each and every user and import those psd files to office 365. so in this scenario you can use imap migration but there are few limitations to imap migration that you should be aware of before you start migrating mailboxes using imap migration imap migration is not supported between two office 365 organizations once you have migrated your mailboxes from source email system to office 365 you cannot off-board them that means you cannot move those mailboxes back to the source email system imap migration is not supported in on-premise exchange servers if you want to migrate mailboxes from on-premise exchange server you can use cut over migration staged migration or exchange hybrid migration imap migration doesn't support messaging records management or archive policies if you have applied archive policies in your source email system and if emails are moved to archive imap migration will not migrate those emails imap migration migrates only emails of the mailbox it does not migrate calendar items contacts or tasks and this is very important to know that imap migration does not migrate calendar context and task of the mailbox by using imap migration we can migrate only the emails you can migrate a maximum of 500 000 emails from a user's mailbox and the maximum size of the email that can be migrated using imap migration is 35 mb so now let's understand how imap migration works or what are the steps those are involved in imap migration if you have recently signed up for office 365 tenant then you need to verify your domain that you will be using for the email addresses after that you will create users in office 365 and you need to assign licenses to these users then you will create a csv file and you will add all the users that you want to migrate from the source email system to office 365 once you have the csv file you will create a migration endpoint so that office 365 can connect with the source email system then you will create a migration batch and you will start the migration once migration batch is synced you will point mx record to office 365 so that emails start routing to office 365. once you verify that the emails are getting routed to office 365 you will complete the migration batch and once migration batch is completed you can let your users know that now they are using office 365 as a service so this is the flow of imap migration now let me show you practically how to perform imap migration in this particular demo we are going to migrate emails for this particular user who is using outlook.com services as of now this user's emails are hosted on outlook.com that is outlook.live.com we are going to migrate all his emails from outlook.com to office 365 using imap migration so first let's create a user i will not be adding the domain because i already have that verified in this particular tenant and mx record is already pointing to this particular office 365 tenant so let's create a user and i will create it as target user and let's give it a password next let's assign a license to this particular user click next finish adding so we have created the user now let's check if the mailbox is provisioned for this particular user or not so let's login with this particular user here target user at and the password so looks like the mailbox is provisioned for this user that's it so now what we are going to do we will migrate these emails to this particular user who is currently hosted on office 365. so the next step is we will create a csv file csv file that we need to create for imap migration requires certain attributes of both the users source account and the target account so first we are going to mention email address column under email address we will use the email address of the office 365 account and that is target user at o365 techlabs.com the next column is user name under username we will use the email address of the source mailbox and the source mailbox is source user1 at outlook.com let me just verify it is source user one at outlook.com and the third column will be password and the password will be this user's password is source mailbox password which is this one now let's save this file and let's save it on desktop so let's say imap dot we will save it as csv file and we will select this one csv click save the file is saved now the next step is we will create a migration endpoint to create migration endpoint we will go to recipients then migration click on these three dots and then click migration endpoints here we will click on plus and here it will ask you what type of migration you are going to perform so as of now we are going to perform imap migration so we will select imap and then click next here you need to type you need to specify the server details these server details are for the source email system so in this demo we are going to migrate emails from outlook.com so here we will mention the server details for outlook.com and for outlook it is outlook.office365.com authentication will remain basic encryption will remain ssl and port number will be 993 click next and here you need to mention a name for this particular endpoint for example imap migration endpoint click next that's it the migration endpoint is created and once the migration endpoint is created the next step is to test the migration endpoint and for that we will run test hyphen migration server availability hyphen imap because this is imap endpoint and then we will use switch remote server under remote server we will specify the server name of the source email system that is outlook.office365.com and then we will mention the port number which is 993 for imap and press enter it should say success or pass if it is failing that means your endpoint is not created properly so here it says result success so that means the endpoint is created properly and we can create the migration batch and we can start the migration and the next step is to create a migration batch so under migration we will click on this plus sign here it will ask you what type of migration you are going to perform you are going to migrate to exchange online or you are doing off-boarding that means migrate from exchange online so as of now we are going to migrate emails from a different source email system to exchange online so we will select migrate to exchange online again it will ask you what type of migration you are going to perform you are going to perform hybrid migration staged cut over imap or google so we are going to perform imap we will select imap migration and then click next here we will select the csv file that we just created select this and click next this is the endpoint details no changes are required here click next and you can give it a name let's say test batch this is the name for the migration batch click next and no changes required here now here you can select if you want to start the batch later or as soon as you click next the batch will start automatically if you want to schedule this batch for later for a different time so as for the timing you will specify here this batch will automatically start so i want to run this batch now so i'll select this option automatically start the batch and click next so let's wait for a few seconds now it says saving completed successfully click ok now here you can see the batch is running and right now it is in syncing state now let's check from powershell if you want to check the migration batch from powershell for that you can run get hyphen migration batch press enter this command will tell you if batch is running what is the status and what is the type of the migration that you are performing and this is the name of the batch if you want to check more details you can simply add pipe fl next to this command and here you can see all the details of the migration batch as of now it is syncing this is the name test batch state is active next you can see what time it was created what time it was started the batch what time batch was started and you can also check as of now it is still running but here you can also check if how many items are moved how many items are skipped and you can check all those details as well if you want to check the details for a particular user for that you can run get hyphen migration user and hyphen identity and here you need to mention the name of the user who is within the batch so let's say you want to check the status of migration for a particular user within the batch so let's type the name so here you can see the batch for this particular user is still syncing so let's say within the csv file we have added let's say 50 users in the same format like i have added target user email address same way you can add multiple email addresses here here source email addresses and the password of these users so same way if you want to check let's say a different user status you can run this command you can change the email address and it will show you what is the status for that particular user migration if you want to check more details you can add piper and it will give you more details related to the migration let's go back to the batch it is still syncing and here we can see the target user that we just created few emails are moved and this particular email was sent to source user one at outlook.com which is the source mailbox this one here we can see test nine and this email is now showing under target user so that means the migration is working properly and emails are moving we can see test eight as well test seven test six test five so the migration is still running and emails are moving so the state of this migration batch has been changed from syncing to synced and here we can see synced mailboxes one out of one we have only one user in this particular csv file so that is the reason it is saying one out of one is synced apart from that if you go to view details now we should see some more details about this migration under skipped items we do not see any item because there is no item that is skipped data migrated will show you how much data is migrated from the source email system to the target email system that is office 365 migration rate will show you the rate of the migration that is being performed last successful sync date this is the date and time and here you can see in progress duration for how long this particular batch is running and if we click on here download the report for this user we should see few more details so now it is giving us the details related to the patch so here you can see the date and time when this particular request was created when the migration batch was created after that this particular request connected to the target mailbox this is your office 365 tenant initial domain after that you can check the stage or the state of this particular migration how much percent is completed if it is under incremental sync incremental sync is basically uh let's say you are running migration and in this source mailbox there are still few emails those are being delivered so those emails will be transferred from or the migrated from the source email system to the target email system during incremental sync and after that you can check if number of items those are migrated here you can see nine items are migrated there are only nine emails in this particular mailbox this is the welcome email that was sent so apart from that there are only nine emails those are within the source mailbox so these nine emails are being migrated to target mailbox so this is how you can analyze the entire logs and you can check if it is failing or if it is running properly so if you have learned something new from this particular video please write in comments and please subscribe to the channel thank you guys thank you for your time take care
Info
Channel: Office365Concepts
Views: 21,167
Rating: undefined out of 5
Keywords: what is imap migration, imap migration, imap migration step by step, office 365 migration, migrate emails to office 365, how imap migration works, imap migration working, migrate emails to m365, hybrid migration process, cutover migration, what is migration endpoint, create migration endpoint, staged migration, migration, migration videos, migration videos in hindi, migration tutorials, imap migration videos, exchange migration, office365concepts, office 365 concepts
Id: rPyyHpMz5Pw
Channel Id: undefined
Length: 19min 38sec (1178 seconds)
Published: Tue Jan 18 2022
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.