Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - Pre-Migration Planning Guide

About this guide Introduction Critical considerations Other strategic and tactical issues Known limitations of the migration process Summary of features and capabilities

Critical considerations

Develop a written migration plan

The migration of any enterprise is typically a complex process that requires careful planning and project management. Even a high-level summary checklist of necessary tasks can be quite long, and will expose a good number of details that must be addressed for a successful migration. The "choreography" in the sequence, timing, and coordination of tasks is also important.

The complexity of most migration projects makes planning and communications critical to a favorable outcome. Halfway through the process is no time to discover that a neglected detail or invalid assumption will cost your organization dozens or hundreds of hours of productivity, or cause unnecessary aggravation for end users. Quest therefore recommends that you develop a comprehensive written migration plan before you begin any migration process.

Developing a migration plan is a valuable exercise that will lead you to consider and accommodate all of the factors likely to affect your organization's migration. At a minimum your migration plan should address all of the topics (and topic categories) discussed in this chapter, and whatever topics in the next chapter may apply to your local circumstances.

Your migration scenario

Virtually all migrations follow a similar basic process, with variations to accommodate each organization's circumstances and needs—what we collectively call a scenario. Your migration scenario determines much of the migration process and your necessary pre-migration preparations, so it is critical to define your scenario at or near the top of your written Migration Plan.

Most variations to the basic migration process are determined by:

Migration Destination (the Exchange "target" type):
Proprietary local Exchange network: A proprietary Exchange environment is one whose hardware and software are wholly under the control of the migrating organization. Ordinarily this is a local Exchange network—on the same premises as the GroupWise source, or at least near enough to use high-performance network cables for data transfer. But a proprietary Exchange server may be distant from the source—geographically and/or from a network perspective.
Office 365 ("the cloud"): Microsoft’s Office 365 is a hosted Exchange platform (also known as "the cloud"). Cloud computing is a service model in which the hardware and software are owned and controlled by a third party (Microsoft). Microsoft then sells, as a service, access to disk space and the Exchange/Outlook software features.
Pre-Migration State of Local Active Directory (if any): Your organization may already have an Active Directory running for login and security purposes. Part of the migration process will depend on whether you do have an existing AD and, if so, on the state of any objects already provisioned in the local AD.
If migrating to proprietary Exchange: Do you already have Active Directory configured and, if so, in what state are any previously provisioned objects? (If the objects exist, are they already mail-enabled, mailbox-enabled, or neither?)
If migrating to Office 365: Will you maintain a local Active Directory— either temporarily to provision Office 365, or permanently? (One popular option is to provision first to a local AD, which can then be synchronized to Office 365.) Or will O365 be provisioned directly from GroupWise?

Different combinations of target types and states of an existing local AD (if any) produce an array of migration scenarios. The scenarios listed below cover almost all variations to a GroupWise-to-Exchange migration, and the Migrator for GroupWise Scenarios Guide describes them all, with suggested process instructions:

The Migrator for GroupWise Scenarios Guide provides step-by-step process instructions for the most common migration scenarios. Migration by any scenario is still, basically, a GroupWise-to-Exchange migration, and the processes for all scenarios share certain steps in common. Since all migrations follow the same basic process, with just a few variations for different scenarios, we can generalize to present just two linear procedures that are suitable for virtually all scenarios. Of course each scenario has its own particular needs and procedural variations, and these are noted in the process instructions in the Scenarios Guide.

The Scenarios Guide also describes three special-case scenarios, any of which would occur in combination with one of the above-listed scenarios:

Offline Migration: A proprietary Exchange server may reside at a physical location distant from the source environment (geographically and/or from a network perspective). An offline migration is a two-phase migration strategy in which the GroupWise source data is migrated first to a nearby intermediate storage medium, which can be physically transported to another location where you have a more favorable bandwidth connection to the Exchange server. The data is then migrated from the intermediate medium into Exchange.
Phase (Staged) Migration: A phased-migration is a strategy by which users remain on the GroupWise server(s) throughout most of the transition period, receiving and sending mail and managing their calendars in GroupWise just as they always have, while their oldest data (90-95% or even more of the total) is migrated to the new Exchange environment. After the older data has been migrated, the proportionately smaller volume of data remaining can be migrated relatively quickly, so that more users can be migrated together within a shorter window, typically in one final cutover weekend.
SSDM Silent Mode Migration: The Migrator for GroupWise Self Service Desktop Migrator (SSDM) offers a Silent Mode configuration, commonly used to minimize end user involvement when SSDM is deployed, but while maintaining the flexibility and other benefits of a distributed migration.

Chapter 1 of the Migrator for GroupWise Scenarios Guide provides more information about these special-case scenarios.

Quest strongly recommends that all migration admins and others associated with a migration project read the entire first chapter of the Migrator for GroupWise Scenarios Guide to fully understand all of the basic migration scenarios. It is critical to identify and characterize your migration scenario at the outset of your planning, and to identify your scenario near the top of your written Migration Plan.

Before-and-after site configurations

Characterize the configuration of the organization’s servers, both as they are now and how they will be after the migration.

Draw a network map of the pre-migration GroupWise environment, showing:

The network map should be a graphical illustration, to help migration planners visualize the relationships between the data volumes of the various servers and the inter-node bandwidths that connect them.

For each server, note also (but not necessarily on the same network map):

If you are migrating to an on-premises proprietary Exchange environment, draw another network map to show your post-migration world: the locations and domain names of all Exchange servers, and the data capacity of each server. Then view the pre-migration and post-migration configuration maps side-by- side, and determine which users from which GroupWise servers will migrate to which Exchange servers. Your Migration Plan should include your before-and- after diagrams, and a table to document the before-and-after server assignments for each group of users to be migrated.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating