I honestly couldn't tell you. What version of Exchange are you running on-premises now, and how big are your mailboxes? Your internet connection speed and quality will make a huge difference too do you have a metro-E fiber connection that is really fast? A broadband (aka, residential grade) 10 Meg connection simply won't cut it. How good are your desktop support people in dealing with Outlook/credential manager issues? Have you done anything yet (AD Sync, ADFS, etc), or are you literally starting from scratch? Is Exchange fully patched and on the latest CU/rollup? Lots of questions to be answered.
I can tell you that we took it *very* slowly. I started production migrations in June and finished the bulk of them by Thanksgiving. Could we have done it faster? Yes, but the ability to field calls from end users who had not properly patched (even though they said they had) and other miscellaneous desktop issues kept us pretty busy during the day. 99% of the issues you have will be with the client side. Then once you get all of the end users, you have shared mailboxes, room mailboxes, equipment mailboxes.... Also note that if you have forwarding on any mailboxes, you will need to document that and set that back up once the mailbox is migrated. Also permissions on mailboxes will need to be documented and re-configured for anyone who has send-as or full ownership permissions. And depending on what version of Exchange you are migrating off of, calendar free/busy detail may not work the way you hope and expect. I actually got Microsoft to update their KB on how free/busy worked in a coexistence scenario with Exchange 2007 because it was originally misleading. Thanks, [cid:[email protected]] Jonathan L Raper, A+, MCSA, MCSE, FCC Licensed Technician, VCA-DCV, VCA-Cloud Director of Infrastructure Technology [cid:[email protected]]Corporation 336.232.5244 Cisco Single Number Reach 7025 Albert Pick Road, Suite 302, Greensboro, NC 27409 www.NWNIT.com [cid:[email protected]] NWN helps customers solve business problems through technology [cid:[email protected]] <https://www.facebook.com/NWNCorporation> [cid:[email protected]] <https://www.linkedin.com/company/nwn-corporation?trk=company_logo> [cid:[email protected]] <https://twitter.com/nwncorporation> From: [email protected] [mailto:[email protected]] On Behalf Of Jesse Rink Sent: Wednesday, August 24, 2016 1:54 PM To: [email protected] Subject: Re: [NTSysADM] Office 365 migrations Out of curiosity, start to finish, how many service-hours did it take you to do 600 users, start to finish, including project planning, etc.? Thanks for Patching tip with Office. Jesse Rink Website<http://www.sourceonetechnology.com/> | Blog<http://www.sourceonetechnology.com/blog/> | LinkedIn<https://www.linkedin.com/in/jesse-rink> | Twitter<https://twitter.com/SourceOne_WI> ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Jonathan Raper <[email protected]<mailto:[email protected]>> Sent: Wednesday, August 24, 2016 11:39 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Office 365 migrations +1 for O365 for IT Pros: http://exchangeserverpro.com/ebooks/office-365-for-it-pros/ The authors know their stuff. I follow them on Twitter and they've responded to a couple of questions I've thrown at them. I actually completed a hybrid migration from Exchange 2007 to O365 last year. We presently have right at 600 users in O365. Let me know what questions you have and I'll do my best to answer. Basic overview... Get an O365 tenant setup Figure out your certificate Add/federate domain to O365 Setup Azure AD Connect to sync on-premises objects to O365 Setup ADFS for true Single Sign On (not the same as Same Sign On) Spin up one (or more) hybrid server (in our case, two 2013 servers) Setup one or more migration endpoints (in our case, we used the hybrid servers, plus one additional 2013 server - that we decommissioned once the users were migrated) Migrate some test mailboxes back and forth Migrate a batch of test users Perform full migration (maximum batch size is dependent upon speed/quality of internet connection and number of migration end points) Decommission all but the hybrid servers - you'll need the hybrid servers in order to be able to fully manage the users' mailboxes Somewhere along the way you'll need to validate that everyone has a supported version of Outlook, and that all systems are FULLY patched with windows and Office updates. This WILL bite you in the rear if you don't make certain that Office is fully patched. Jonathan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Todd Lemmiksoo Sent: Wednesday, August 24, 2016 10:18 AM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] Office 365 migrations Office 365 for IT Pros over at ExchangeServer Pro On Wed, Aug 24, 2016 at 8:17 AM, Jesse Rink <[email protected]<mailto:[email protected]>> wrote: Does anyone know of any really good documentation or planning guide for mid-sized scale Office 365 migrations (roughly 300-600 users)? I know Microsoft has some guides available (https://support.office.com/en-us/article/Deployment-planning-checklist-for-Office-365-5fa4f6ef-35ad-4840-91c1-4834df3df5a0?ui=en-US&rs=en-US&ad=US ) but I'm curious if anyone knows of other guides or EXAMPLES that are worthwhile.... Do we have anyone on the list who has gone through and performed any migrations of that size that can provide input? I have one upcoming and it's going to be very important that the entire migration is Planned, Staged, Tested, Piloted, Documented, etc. Jesse Rink Website<http://www.sourceonetechnology.com/> | Blog<http://www.sourceonetechnology.com/blog/> | LinkedIn<https://www.linkedin.com/in/jesse-rink> | Twitter<https://twitter.com/SourceOne_WI> -- T. Todd Lemmiksoo NOTE: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately. NOTE: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.
