I’ve used Transend for this. (And yes, I’m a reseller, because I’ve used the product a number of times. But it works well, otherwise I wouldn’t use it.)
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss Sent: Friday, July 7, 2017 2:10 PM To: exchange@lists.myitforum.com Subject: RE: [Exchange] recommendations for Exchange migration from Zimbra Okay. How then do I keep both Zimbra and Exchange running for a while, though? Is that possible? I’m frankly tired of the nuke everything start over option. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael Pope Sent: Friday, July 7, 2017 1:50 PM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: Re: [Exchange] recommendations for Exchange migration from Zimbra We've done one of those migrations. We used everyone's PST files. On Jul 7, 2017 12:03 PM, "Katherine M. Moss" <km...@winterhillsolutions.com<mailto:km...@winterhillsolutions.com>> wrote: Hey all, We’re currently using Zimbra due to resource constraints; that was, until the other day when I was able to get a good deal on a new server. We want to return to our Exchange-based roots. I’m curious what the most graceful method of performing a cutover would be? In other words keep Zimbra running until all of the issues are worked out of the Exchange deployment (we originally dumped it due to only one of us having issues accessing; even though all configurations for all of us were the ssame), aand so I need to know how to do that smoothly without duplicate things happening. Any recommendations? Thanks. Operating systems are Windows 10 builds 1607 and 1703, and Server 2016 for everything.
