• Status: Solved
  • Priority: High
  • Security: Public
  • Views: 71
  • Last Modified:

Office 365 hyrbid mailbox move Concurrency and best practice

By default 20 mailboxes are concurrent moves to cloud from On-Premises. And we can extend through PowerShell by

Set-MigrationEndPoint <Identity> –MaxConcurrentMigrations <value between 1 and 100>

Using On-Premise Exchange 2013 Enterprise on Physical Hardware.

Question is:

  • How much we can Maximize Concurrent Migrations according to best practice?
  • What would be the best number to stick with also we're using script to move mailboxes to cloud..
  • If we need to extend the limit, Would it be after starting the migration or we need to extend prior to start migration batch?
  • 2
2 Solutions
timgreen7077Exchange EngineerCommented:
I would suggest contacting O365 support for that question because Microsoft cloud servers are coming into play also and you will have no control over that. I would contact their O365 and inquire about best practices for that because MS will still have throttling in place and support can assist with the best setup and number of moves so that moves would be a lot smoother.
the maximum concurrency you can set is 300
but before that u need to contact Microsoft to ask them to turn off throttling for your tenant or adjust it based on your needs and then only increase your concurrency accordigly, say 50
you have to have good internet pipe bandwidth to allow high thruputs (say 100 mb)
the default 20 concurrency works well with 40 Mbps pipe and can migrate data up to overall 14 gb per hour
further it depends on other factors such as individual mailbox size, number of mail items
timgreen7077Exchange EngineerCommented:
Author's question has been answered. Closing ticket and assigning points.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now