I used the codetwo product when it was released. Couple of issue with it. It was extremely slow, and it didn’t bring over the users contacts.
I ended up using the native 0365 migration tools. Since you can sync the users data at any time without the users knowing. And then at the scheduled time hit the complete button and let the move complete. Once the move is complete the user gets a pop-up in outlook saying their exchange admin has made a change and they need to restart the client. No matter what tool you use you are going to have to restart outlook. Mobile device are a little more picky, and some needed manual intervention, but codetwo won’t solve that either From: [email protected] [mailto:[email protected]] On Behalf Of Todd Lemmiksoo Sent: Tuesday, July 21, 2015 11:29 AM To: [email protected] Subject: Re: [Exchange] Anyone used CodeTwo for Office 365 migration Not easy to schedule as it runs when Microsoft wants it to. And the users desktop/Outlook needs adjustment after the mailbox move completes. On Tue, Jul 21, 2015 at 9:59 AM, Ramatowski, Paul M.. <[email protected]<mailto:[email protected]>> wrote: Why not just use the built in Remote Move Request? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Todd Lemmiksoo Sent: Tuesday, July 21, 2015 10:50 AM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Anyone used CodeTwo for Office 365 migration I have a hybrid Exchange setup with Exchange 2010, Exchange 2013 and Office 365. 99% of the mailboxes are still on 2010 and small pilot group in O365. The 2013 servers are CAS/MB. Has anyone used CodeTwo for their migration to O365. If yes.... what was the benefit for you and any downside. -- T. Todd Lemmiksoo -- T. Todd Lemmiksoo
