MAIL AND DIRECTORY MIGRATION

Specifying where to migrate archives
When migrating archives, users can specify where the upgrade wizard will store the resulting Notes archive database. By default, the upgrade wizard migrates all archives into a single Notes mail file database. That is, if a user migrates cc:Mail archives and Microsoft Mail archives, all of the archives are placed in a single Notes archive database. Unless otherwise specified, the database is created in the MAIL subdirectory of the user's Notes Data directory, as specified in the NOTES.INI file. Users are prompted to provide a Notes password when they create the archive database.

The resulting Notes archive automatically derives an eight-character name from the Notes name of the migrated user, to which it adds the prefix A_ . For example, if the Notes name of the user migrating an archive is Robin Rutherford, the resulting Notes archive database would have the name A_RRUTHE.NSF.

For Microsoft Mail and Microsoft Exchange, if an archive file contains multiple files, these files become folder views in the resulting Notes archive database. To distinguish among duplicate archive filenames (from multiple source directories) the wizard appends a numeral to the archive name. For example, if the upgrade wizard moves the two files archive\1996\meetings and archive\1997\meetings they appear as folders with the names meetings1 and meetings2 within a single Notes database.

The default settings are maintained when users select Express as the upgrade method. To specify a different destination, cc:Mail users must select the Custom upgrade method and edit the Folder field on the Archive Conversion Options dialog box. Users converting from Microsoft Mail or Microsoft Exchange can change the destination regardless of the upgrade method selected.

Running the wizard again to migrate additional archives

Users can run the upgrade wizard more than once to migrate archives. By default, archives migrated after the initial session are added to the existing Notes archive database. User can place archives that they migrate later in a different archive database as follows: