You can use Migration Wizard to extract the following data.
| Item | Notes |
|---|---|
| Messages | Messages are converted to Exchange Outlook format. Messages retain only the display name. Replies to these messages must resolve the address against the Exchange global address list or an accurate PAB. Mail messages that have senders or recipients with SMTP or X.400 addresses are migrated with the complete address and can be replied to without address resolution. |
| MMFs | If the MMF for a mailbox is on the
postoffice, it is migrated by Migration Wizard to an Exchange
mailbox store. The MMF is not deleted and can be archived as a
backup.
Important If the MMF is copied to the correct directory in the postoffice and has the correct name, Migration Wizard migrates it. If the user has already imported the messages into a personal archive file, this can cause duplicate mail. If the MMF for a mailbox is on the client or stored on a server—meaning not in the Microsoft Mail postoffice—Migration Wizard does not migrate this data. In this case, the user migrates the contents using the import option in Outlook. |
| Personal address book (PAB) entries | Microsoft Mail personal address books
(PABs) are converted to Outlook PAB files during migration. The PAB
file is migrated as an attachment in a message and is put in the
Inbox of the new mailbox, with instructions on how to import it
into the Outlook Address Book. You can change the message by adding
a file named Pabmsg.txt to the Exchange\Bin folder; the text in the
file is substituted for the default instructions. The PAB entries
for users on foreign mail systems, such as SMTP, FAX, and X.400,
are valid. Any message addressed to these entries is delivered
provided Exchange can route the message.
Note You need to modify the PAB entries for PROFS and SNADS users before the entries can be used. In Microsoft Mail for PC Networks, these addresses are stored in the format of gateway\node\user. Exchange expects these addresses to be in the form of node\user with the appropriate type of information. |
| Shared folders | Migration Wizard copies shared and group folders. Folders are copied to the public folder store and appropriate permissions are assigned to them as specified in Migration Wizard. These folders should be migrated no more than once for each postoffice. After a copy is migrated to a public folder on Exchange, there is no way to automatically replicate the differences between the copies that exist on Microsoft Mail and Exchange. If you have a critical shared or group folder, migrate all the folder's users at the same time. |
| Private folders | Private folders created by MS-DOS and Macintosh clients can be stored on the postoffice or moved to local storage on the client. If they are moved outside the postoffice, they must be moved back to the postoffice to be migrated. This can be done only from the client computers and not from the Administrator program. |
| Calendar data | You can use Migration Wizard or Outlook to migrate calendar data. This data is converted to Outlook format the first time the calendar is opened, when Outlook searches for a local copy of the .cal file. |
| Passwords | When mobile users access Outlook offline after migration, they are prompted to enter the passwords they use to access their Schedule+ 1.0 calendar file. Many users will have forgotten this password. For this reason, you should tell users to make a note of their current Schedule+ 1.0 passwords prior to migration. |
| Remote users and offices | Windows remote client users who upgrade to Outlook can migrate their MMFs to a personal folder file. Users of the MS-DOS remote client have no way to migrate their messages to a .pst file. They must forward the messages to themselves and print them to a printer or file if they want to preserve the information. |
| File Format API Applications | If you have applications or gateways
created with the File Format API (FFAPI), they will work with
Exchange. You need to plan what to do with them when all of your
postoffices have been migrated to Exchange. The connector
postoffice is like any Microsoft Mail 3.2 postoffice for the
purposes of FFAPI applications and gateways.
Important You need to use the -md switch on the FFAPI to disable the mailer. If you don't disable the mailer, mail going through the connector postoffice may be returned as undeliverable. After all postoffices are migrated to computers running Exchange, you can continue to use the FFAPI applications with the connector postoffices as long as the Microsoft Mail Connector interchange and MTA services run. Contact the vendor of the application to see if they have native Exchange applications. |
Tip You can control which items you migrate in the Migration Information screen of Migration Wizard.
Migration Wizard does not migrate the following items.
| Item | Notes |
|---|---|
| Rich-text formatting | For example, the MS-DOS client for Microsoft Mail for PC Networks can format messages with different color text and background. This formatting information is not preserved when the messages are migrated. |
| Personal address lists (PAL) | Not migrated. |
| Template information | If you use template information in Microsoft Mail, the postoffice migration tool does not migrate that information to the directory of Exchange mailboxes. If you want to migrate template data, you must use directory synchronization to migrate the templates, and then allow Migration Wizard to convert contacts to users. |
| Groups | The group information in a Microsoft Mail postoffice can be printed in the Administrator program. This produces a file with display names, which may be the same as the real display names if the user is on another postoffice. |