Mailbox migration to Cloud

%3CLINGO-SUB%20id%3D%22lingo-sub-283161%22%20slang%3D%22en-US%22%3EMailbox%20migration%20to%20Cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283161%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20have%20a%20general%20question%2C%20why%20does%20it%20take%20hours%20before%20our%20%22local%22%20mailbox%20migrates%20to%20office365%3F%3C%2FP%3E%3CP%3EIt%20makes%20sense%20if%20mailbox%20have%20a%20lot%20of%20emails%20inside%2C%20and%20it%20takes%20time%20to%20transfer%20all%20the%20data.%20But%20we%20just%20made%20few%20new%20mailboxes%2C%20and%20migrated%20them%20to%20office365%20about%2030%20min%20later.%3C%2FP%3E%3CP%3EIn%20that%20time%2C%20there%20wasn't%20a%20single%20email%20in%20those%20mailboxes%2C%20yet%20it%20took%205%20hours%20before%20it%20was%20successfully%20migrated%20to%20cloud.%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20any%20information%20why%20does%20it%20take%20that%20long%20even%20for%20empty%20mailboxes%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-283161%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283391%22%20slang%3D%22en-US%22%3ERe%3A%20Mailbox%20migration%20to%20Cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283391%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20add%20on%20to%20this%20from%20Vasil%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20we%20were%20doing%20migrations%20from%20clients%2C%20we%20did%20single%20moves%20on%20ALL%20mailboxes%2C%20and%20%22batched%22%20them%20by%20setting%20their%20powershell%20command%20New-MoveRequest%20with%20the%20variable%20-CompleteAfter%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fmove-and-migration%2Fnew-moverequest%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fmove-and-migration%2Fnew-moverequest%3Fview%3Dexchange-ps%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20if%20we%20wanted%20a%20batch%20to%20complete%20around%208%20am%20one%20day%2C%20we%20would%20just%20Start%20all%20the%20move%20requests%2C%20with%20the%20flag%20of%208%20am%20that%20day%2C%20and%20then%20they%20would%20be%20handled%20as%20individual%20moves%20instead%20of%20a%20batch%2C%20which%20like%20Vasil%20said%2C%20seems%20to%20take%20longer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283281%22%20slang%3D%22en-US%22%3ERe%3A%20Mailbox%20migration%20to%20Cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283281%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20general%2C%20batches%20take%20a%20lot%20longer%20complete%20compared%20to%20individual%20moves%2C%20so%20if%20you%20are%20doing%20tests%20just%20use%20single%20moves%20instead.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-283187%22%20slang%3D%22en-US%22%3ERe%3A%20Mailbox%20migration%20to%20Cloud%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283187%22%20slang%3D%22en-US%22%3ECan%20you%20share%20the%20kind%20of%20migration%20you%20are%20doing%3F%20By%20the%20way%2C%20you%20are%20right...migration%20performance%20is%20given%20by%20the%20size%20of%20the%20mailbox%20that%20needs%20to%20be%20migrated...in%20my%20experience%2C%20around%201%20GB%20%2F%20Mailbox%20%2F%20Hour%20is%20a%20normal%20performance%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

I just have a general question, why does it take hours before our "local" mailbox migrates to office365?

It makes sense if mailbox have a lot of emails inside, and it takes time to transfer all the data. But we just made few new mailboxes, and migrated them to office365 about 30 min later.

In that time, there wasn't a single email in those mailboxes, yet it took 5 hours before it was successfully migrated to cloud.

Does anyone have any information why does it take that long even for empty mailboxes?

3 Replies
Highlighted
Can you share the kind of migration you are doing? By the way, you are right...migration performance is given by the size of the mailbox that needs to be migrated...in my experience, around 1 GB / Mailbox / Hour is a normal performance
Highlighted

In general, batches take a lot longer complete compared to individual moves, so if you are doing tests just use single moves instead.

Highlighted

To add on to this from Vasil,

 

When we were doing migrations from clients, we did single moves on ALL mailboxes, and "batched" them by setting their powershell command New-MoveRequest with the variable -CompleteAfter

 

https://docs.microsoft.com/en-us/powershell/module/exchange/move-and-migration/new-moverequest?view=...

 

So if we wanted a batch to complete around 8 am one day, we would just Start all the move requests, with the flag of 8 am that day, and then they would be handled as individual moves instead of a batch, which like Vasil said, seems to take longer.

 

Adam