Chapter 2
Using the Migration Wizard
As you export data from your existing system, a set of migration files — a packing list file and primary and secondary files — is created. These files are imported into Microsoft Exchange Server by the Migration Wizard, which is a tool that is available in the Administrator program. The Migration Wizard is also used to create mailboxes and addresses.
When you set up Microsoft Exchange Server and install the Administrator program, the Migration Wizard and necessary files are installed automatically.
To ensure that data is moved efficiently, import when the server is least active, such as during evenings or weekends. Also, back up the Microsoft Exchange Server information store and directory.

Important
Run the Migration Wizard on the destination server for maximum performance.

Importing Migration Files
All migration files are imported the same way, regardless of the existing system they come from. Before you begin, map a drive letter or connect to the server where the migration files are stored.
See Appendix C for information about command-line options and batch use of the Migration Wizard.

Tip
For best performance, move the migration files to the hard disk of the computer running the Migration Wizard.

	To import migration files
	1.	In Program Manager, choose Microsoft Exchange, and then choose Microsoft Exchange Migration Wizard.
		
	2.	Select Import Migration Files, and then choose Next.
	3.	Read the informational screen, and then choose Next.
	4.	In the Pathname for Migration Files box, type the path to the packing list file, or choose Browse to specify the path.
	5.	Choose Next.
	6.	In the Enter a Server Name box, type the name of the destination Microsoft Exchange Server computer that will be receiving the data, and then choose Next.
	7.	If you import shared data to a public folder, select the default access permissions, and then choose Next. (This step is optional.)
	8.	In the Choose a Recipients Container box, select the Recipients container where custom recipients or mailboxes are to be created. If you are importing data for existing mailboxes, select the Recipients container where the mailboxes have been created.
	9.	If you are creating either custom recipients or mailboxes, and you want to use a template recipient, in the Use This Account as a Template box, type the recipient’s directory name, or choose Browse to select the recipient from the Address Book.

Important
Template recipients must be of the same type as all the recipients that are created with this migration file. For more information about using templates, see the Microsoft Exchange Server Administrator’s Guide.

	10.	Choose Next.
	11.	In the For Users That Don’t Have Windows NT Accounts box, select an option for creating Windows NT accounts.
Option	Description	
		
Create Accounts and Generate Random Passwords	Creates Windows NT accounts for each mailbox. The account name will match the common name. The passwords are written to the file ACCOUNT.PASSWORD in the working directory of the Migration Wizard. Users will need these passwords to log on to Windows NT.	
Create Account and Use Alias as Password	Creates Windows NT accounts for each mailbox. The account name will match the common name. The passwords default to the common name of the mailbox. Users who don’t know what their alias is will need these passwords to log on to Windows NT.	
Don’t Create Windows NT Accounts	If a Windows NT account that matches the common name of a mailbox does not exist, create the mailbox without an associated Windows NT account. No one will be able to access this mailbox until a Windows NT account is associated with it.	

	12.	In the Windows NT Security Domain box, select the domain where the user’s Windows NT accounts are located or to be created, and choose Next.
	13.	Choose Next to begin the migration process.

Replacing Custom Recipients with Mailboxes
When the Migration Wizard creates a custom recipient, it adds an e-mail address of type migrate: and an address which uniquely identifies the recipient’s mailbox on the existing system. For example, if Ann Devon is a custom recipient with a target address of PROFS:SYDNEY(AnnDevon), her e-mail addresses would include migrate:PROFS:SYDNEY(AnnDevon).
	
When a message is imported by the Migration Wizard, it checks the global address list for either of the following e-mail addresses:
	A migrate e-mail address that matches the source system mailbox address. 
	A source system e-mail address with the address of the mailbox being migrated.

The Migration Wizard looks at the type of entry that has been found. If it is a mailbox, the message is imported. If it is a custom recipient, the following occurs:
	The directory information for that custom recipient is read.
	The custom recipient is deleted.
	The new mailbox is created.
	The new mailbox is added to all the distribution lists containing the custom recipient in this site.
	The directory information and e-mail information for the custom recipient is added to the mailbox.

See Chapter 3 for a complete list of preserved attributes.
Limitations of Migrating Custom Recipients to Mailboxes
To use the custom recipient-to-mailbox conversion system, you need to determine how you plan to create your custom recipients.
Distribution lists should be created in the same site as the custom recipients if you want their membership to be updated automatically. This may require creating the lowest level distribution lists in individual sites. If you are planning to manage distribution lists from a central site, consider nesting these distribution lists with those managed from the central site and maintaining the lowest-level distribution lists locally until after migration is complete.
You must create the custom recipient in the same Recipients container as the mailbox. You cannot move custom recipients or mailboxes between Recipients containers. Therefore, you must configure directory synchronization to import addresses into the correct Recipients container. 
If there are multiple sites, you need to configure directory synchronization at each site to import only those addresses that will migrate to the local site, as shown in the following figure:
	
Replacing Custom Recipients with Mailboxes Manually
It may be necessary to create custom recipients in a different site or in a different Recipients container. In this case, the Migration Wizard cannot replace the custom recipients with mailboxes. You can select one of the following options:
	Delete the custom recipients before migration.
This allows you to create the mailboxes in the same Recipients container with the same common or directory name. This is the only way you can create the mailbox with the same e-mail addresses.
	Wait for directory synchronization to remove the custom recipient automatically.
The migrated mailboxes must have unique e-mail addresses. This requires users to notify all external correspondents with the change in their SMTP, X.400, and other external addresses. The mailboxes also need different common or directory names from the custom recipients, or they need to be created in a different Recipients container. There will also be duplicate addresses in the Address Book, unless one of the recipients is marked as hidden from the Address Book.

You must also plan how to handle the custom recipient’s directory information.
E-mail addresses, telephone numbers, managers, and distribution list memberships can be handled in one of two ways:
	Preserve the directory information.
You can use the Directory Export command to export all custom recipients to a file with all the attributes you want to transfer specified. This file can then be modified for the obj-class of mailbox instead of remote and imported by selecting the Overwrite option under Multivalued Properties in the Directory Import dialog box.
	Delete the custom recipient and its directory information.
The information can be retrieved from the source files used to create the custom recipients and added to the mailbox creation data. Select this option if custom recipients were not created with any personal information, or distribution list membership either doesn’t exist or is easily reconfigured.

Deleting Custom Recipients While Preserving 
Directory Information
Custom recipients can be deleted only in the site where they were created. You can find out where a custom recipient was created by viewing the home site attribute in the custom recipient’s General property page.
	To export custom recipients’ directory information and delete the custom recipients
	1.	Create a text export file with all the fields you want to preserve.
Obj-class,mode,common-name,display-name,address,assistant-name,given-name,initials,member,surname,proxy-addresses,secondary-proxy-addresses

	2.	In the Administrator program, connect to any server in the site where the custom recipients were created.
	3.	From the Tools menu, choose Directory Export.
		
	4.	Choose Export File, and select the export text file you have created.
	5.	Choose Container, and select this site’s Recipients container where the recipients were created.
	6.	Under Export Objects, select Custom Recipient.
	7.	Choose Export.
	8.	Make a backup of the exported file.
	9.	Edit the exported file as follows. This file becomes the new import file.
	Remove the custom recipients that you are not migrating.
	Change the obj-class from remote to mailbox.
	Change the mode field to modify.
	If the values in the common-name field of the custom recipients do not match the common-names of the mailboxes to be migrated, modify the common name value to reflect the change.
	10.	Edit the backup of the exported file as follows. This file becomes the delete file.
	Remove the custom recipients that you are not migrating.
	Change the mode field to delete.
	11.	From the Tools menu, choose Directory Import.
	
	12.	Choose Container, and select this site’s Recipients container where the recipients were created.
	13.	Choose Import File, and select the delete file.
	14.	Choose the Import button.
	15.	If the recipients were deleted from a different site from where the mailboxes will be migrated, wait for directory replication to occur. When the custom recipients disappear from the global address list, continue the procedure.
	16.	Migrate the mailboxes.
	17.	In the Administrator program, connect to any server in the site where the mailboxes were created.
	18.	Import the edited import file into the Recipients container where the mailboxes were created. This preserves the custom recipient’s directory information and copies it to the migrated mailbox.

Deleting Custom Recipients and the Directory Information
Custom recipients can be deleted only in the site where they were created. You can find out where a custom recipient was created by viewing the home site attribute in the custom recipient’s General property page.
You can delete custom recipients in the Administrator program by selecting them and choosing Delete from the Edit menu. There are several advantages of using the Directory Export and Directory Import commands:
	The directory import file can be archived as a record of the transaction.
	The directory import file can be used to undo the deletion.
	To delete the custom recipients
	1.	In the Administrator program, connect to any server in the site where the custom recipients were created.
	2.	From the Tools menu, choose Directory Export.
		
	3.	Choose Export File, and type the path and name for the new file.
	4.	Choose Container, and select this site’s Recipients container where the recipients were created.
	5.	Under Export Objects, select Custom Recipient.
	6.	Choose Export.
	7.	Edit the backup of the exported file as follows.
	Remove the custom recipients that you are not migrating.
	Change the mode field to delete.
	8.	From the Tools menu, choose Directory Import.
	
	9.	Choose Container, and select this site’s Recipients container where the recipients were created.
	10.	Choose Import File, and select the delete file.
	11.	Choose Import.
	12.	If the recipients were deleted from a different site from where the mailboxes will be migrated, wait for directory replication to occur. When the custom recipients disappear from the global address list, continue the procedure.
	13.	Migrate the mailboxes.