What is your goal for running a successful Exchange migration? My goal is the successful migration of the users' e-mail data into a new Exchange environment with as little disruption to the users as possible. I'm guessing your goal will be similar.
I can't say that I have ever been involved in any migration that could be considered a failure. In the end, every migration has resulted in the successful relocation of users' e-mail data from one mail system to another. This does not mean that they have all gone as smoothly as possible. I have also been called into the middle of a few migrations that were going poorly, but we ended up rescuing them and achieving the goal.
What went wrong in the migrations that did not go as smoothly? What glitches caused the migration process to be too slow or to put more of a burden on the end user? In my experience, migrations are less than perfect for a few reasons:
Organizations fail to consider all of the necessary prerequisites.
Some hardware or software does not meet the minimum version requirements.
Someone plans poorly or does not anticipate the necessary process or tools.
There is insufficient communication with the user community and/or management.
Organizational support is inadequate or management support is lacking.
User expectations are not set.
A test or pilot project is not planned or performed.
In this chapter, I'll review the factors that will help you plan and execute a successful migration ...