Exchange to O365 migration planning

Been assigned to help plan a Migration from Exchange 2010 to Exchange Online.  We have several thousand mailboxes, approx 20K, wtih a limit of 1.5GB per box, so it will be a hybrid migration. I get how to set up the configurations and most of the pain points, but not I have not done a migration of this size and wondering about the length of time and effort to move?  Is 1,000 users a week reasonable? Not sure of how hard it is to test and validate afterwards.  I am just trying to get a general idea of what other have experience and how they have staffed project, so I can begin setting proper expectations.
Craig JahnkeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jose Gabriel Ortega CastroCEO Faru Bonon IT - EE Solution ExpertCommented:
I think that the best way is to move by departments and schedule depending of the number of users.
You need to get a general estimation of the upload broadband to internet.
1000 users x 1.5 gb are => 1500Gb.

I think that would be something like 3 weeks or a month.

Since you're planning it as a hybrid movement, it's totally transparent for the departments and people involved.
Just need to enable MRSproxy point  on exchange 2010.

So the general process would be.
  1. Deploy AD in a domain controller,
  2. Configure all domains or domain into the o365 subs
  3. On-prem Enable MRSproxy
  4. Make initial synchronization of users with the o365 subscription (enable the hybrid configuration option on ad sync)
  5. go to exchange online management console and select hybrid to deploy hybrid, (download and install)
  6. move a test user into o365, and make sure the emails are going back and forth.
  7. After that, you just need to make sure that autodiscover is set to the on-prem environment ALWAYS (because it redirects to o365 when it's required, and o365 doesn't know how to fall back into your on-prem, that's the main reason).
  8. Do the movements.
  9. when finished remove the hybrid environment
  10. clean up.
  11. done.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
you need to do hybrid migration
with hybrid your mailboxes would remain onpremise and cloud at both places

the normal speed of hybrid migration is 14 GB / hour per 20 mailboxes, this is assuming you have at least 40+ MBPS dedicated internet pipe

you can put batch of 50 to 100 users and overnight it should complete the batch, but obvious it depends upon mailbox size how much time it will require to complete, if mailbox size is limited like 1 GB or 2 GB, you may put more than 100 mailboxes for single migration batch.
Jose Gabriel Ortega CastroCEO Faru Bonon IT - EE Solution ExpertCommented:
Also, this can help you with documentation:
technical details and procedures.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Craig JahnkeAuthor Commented:
Thanks guys! @Jose that is the method I was planning on doing, so that helps validate my planning. @Malesh that helps, I just wanted to have a reasonable expectation of what could be moved and how long it would take.  Once you get to running the jobs, would you only need 1 administrator to do that and monitor that?  I talked with someone that said it would take 3-4 "migration resources" and I thought that was excessive.

Thanks again,
ideally with hybrid migrations, exchange outlook profile does not change, users most probably get warning message that outlook has made changes in profile and need to restart outlook once, that's all, this is the benefit of hybrid setup
so if you already inform users to be migrated about consequences regarding what to do, you would need single or two engineers to handle end users IMHO.
Craig JahnkeAuthor Commented:
Thanks Mahesh!!!
Marshal HubsEmail ConsultantCommented:
Check following articles, which will help you out in setting up Hybrid Deployments with Exchange 2010:

Also check Exchange Server Deployment Assistant Tool.

Alternatively, you can also use Stellar EDB to PST Converter to migrate mailboxes from Exchange Server 2010 to Office 365. For more information about the software, please check following link:
Aaron GuilmetteTechnology Solutions ProfessionalCommented:
Once you have completed the initial hybrid configuration, it's down to the core questions:
  • What type of connectivity (bandwidth) do you have?  Migrations are driven on speeds and feeds.
  • How up to date are your workstations?  Failure to be up-to-date with Windows and Office updates is the cause for most failed user experiences.
  • How clean is your identity? Making sure users have parity between SMTP and UPN is the biggest challenge from an identity perspective, and failure to do so will result in elevated service desk calls.
  • In my experience, we typically see a migration failure/problem rate (resulting in a call to the helpdesk) of approximately 1-2%.  Most of the time, the solutions revolve around using the correct credentials or recreating an Outlook profile

If autodiscover resolves correctly and workstations can get to the internet successfully, you should be able to cut over 500-1000 mailboxes per migration event and expect 5-10 calls for those mailboxes cutover.  You can stage users in batches (as previously pointed out, typically, migrating groups of people and their shared mailboxes together in a group) and, if you've used either the Batch Migration configuration in the Office 365 UI or the New-MigrationBatch powershell cmdlet, you can let those groups incrementally update forever, so it's more a matter of making sure your service desk can support the call volume should things arise.
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- Jose Gabriel Ortega C (https:#a42508535)
-- Mahesh (https:#a42508536)
-- Jose Gabriel Ortega C (https:#a42508538)
-- Mahesh (https:#a42508583)
-- Marshal Hubs (https:#a42509122)
-- Aaron Guilmette (https:#a42509905)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.