A software platform migration can be a painful and expensive undertaking. Oftentimes, it's helpful to first take...
a look at what others have done to get an idea about what works -- and what doesn't. Following are glimpses of how some organizations have approached a migration to Microsoft Exchange Server:
While some caution that a "brand new" approach is the way to go in an e-mail migration, the "upgrade" choice worked out well for a New Jersey school district during its move to Exchange 2003 from 2000.
While migrating 4,500 users to Exchange, a division of Mexican oil giant Pemex had to make a pit stop for an Active Directory implementation.
An Ohio technology training center discovered that mailboxes without size limits can really slow down a migration to Exchange Server 2003. It fully expected some complications with a simultaneous RAID deployment, however.
Feeling that it had little control over its Sendmail-based messaging system, Utah's Private Mentoring Group decided to bring e-mail in-house. But it found there's no easy path from other e-mail servers to Exchange.
This Content Component encountered an error