Are you stuck on a legacy version of Exchange? Perhaps 2000 or 2003?
If the answer to that question is yes, then you are probably considering a move to Exchange 2013 in the near future and are starting to evaluate the new functionality that Microsoft has added to this new version. One thing that you need to keep in mind is that direct migration with true coexistence from Exchange 2003 or earlier is not supported by the Exchange 2013 native migration tools. If your migration project with native tools involves Exchange 2003 or earlier, you will need to perform a double-migration – first migrating to Exchange 2007 or 2010, and then to Exchange 2013. This can be difficult because you’re looking at two different Exchange architectures, multiple deployment issues in terms of which servers to configure first and then, just when you get that first transition done, you have to turn around and do it again. Any transition introduces risk, so having to perform two back-to-back migrations can get tricky.
I am hoping that you made it this far in the article because I have some good news. Quest’s Migration Manager for Exchange solution allows you to perform a direct migration from Exchange 2000/2003 to Exchange 2013 with true coexistence throughout the entire migration project. True coexistence is essential if you are going to transition from one version of Exchange up to 2013 or perform an Exchange consolidation to a new Exchange 2013 environment. There are other third-party migration tools on the market, but beware because if they utilize the native functionality in their tools, they will require you to do a two-step migration and that comes with headaches that you just don’t need.
But, don’t take my word for it, check out this brief video from migration expert, Ron Robbins. Ron explains how Quest’s Migration Manager for Exchange solution can help you ensure a successful and direct migration from a legacy version of Exchange to Exchange 2013 and with ZeroIMPACT on your end users.