Unless the scale of your migration is limited to only a handful of users, we strongly recommend that you plan to migrate incrementally, in groups, and prepare a comprehensive Deployment Plan to articulate your migration strategy.
Even a seamless transition will generate calls to your corporate help desk from some percentage of users, and your help staff would much prefer handling just a handful of these calls per day, distributed over several days. Migrating your universe of users incrementally, by subset groups, should substantially distribute your help desk's load.
Moreover, your organization may have good business reasons to avoid scheduling all users in a single migration event. For example, finance and accounting staff cannot tolerate an interruption at the beginning of a month when they are trying to close the books. Likewise, sales staff should not be interrupted near the end of the quarter when they are striving to meet their quotas, and marketing people need to avoid interruptions near key trade shows or other programs. Migrating users in batches provides flexibility in accommodating these legitimate business needs.
Many organizations designate information-services staff as the first group to migrate, since they typically are the most sophisticated users and therefore provide a solid test of the migration methodology and new system.
Finally, remember that the Deployment Configuration Program lets you configure your users' installation processes differently for different groups of users. Presumably you will want to monitor your users' installations, at least passively, and this will be much easier to do by groups of users who share certain qualities and configuration parameters.
The process of developing a comprehensive Deployment Plan is a valuable exercise that will lead you to consider and accommodate all of the factors likely to influence your organization's migration. Halfway through your deployment is no time to discover that a neglected detail has cost your organization several hundred hours of user productivity, or unnecessary aggravation for your users.
Your Deployment Plan will be an internal document, and as such may be as full of undefined jargon and acronyms as you like. But at a minimum your Plan should accommodate all of the issues identified in this Guide, in Chapter 3, Issues to Address in Planning for a New Mail Server Engaging professional services experienced in messaging migration may prove very beneficial.