Migration
Methodology:
 |
|
Regardless of reasons for a migration or the
migration platforms, the essence of migration projects is to move a group of
users from an environment with which they are familiar, to an environment which
is new for most of them. The main goal is usually to accomplish the move as
quickly as possible with minimal disruption to users’ normal working routine.
Achieving such a goal requires a great deal of expertise and experience.
Unfortunately, the messaging migration process is often simplified
and reduced to e-mail, calendar, and directory data migration, which
greatly underestimates the complexity of the effort and causes such
projects to fail in the eyes of user communities.
Mail migration is not easy, however, with proper planning and
preparation it can be performed successfully and meet its goal.
Organizational commitment, expertise and experience of migration
team members are keys to the success of the project. As decisions
are made regarding the time and resources required for various
aspects of a mail migration project, careful consideration should be
taken regarding the capability and availability of the internal
staff. Also, the amount of time and effort required for internal
staff to attain desired levels of expertise in performing migration
activities as well as whether such expertise has a long-range use
within the organization should be measured.
Migration projects frequently require and greatly benefit from
external assistance provided by organizations with substantial
migration expertise and experience. Sometimes such assistance is
limited to the migration pilot activities only and sometimes it
includes supporting or completely staffing entire production
migrations. While there is no single “right” answer to the mix of
internal and external resources involved in a migration project, one
conclusion is obvious: right resources ensure the ultimate project
success.
|
 |
 |
 |
|
|
|