Enterprise Vault™ NSF Migration
- Introduction to Enterprise Vault NSF migration
- NSF migration: scripted
- NSF migration: wizard assisted
- About NSF migrator
- Outline of the NSF migration process
- About planning for NSF migration
- How to edit the welcome messages for NSF migration
- NSF file locations for NSF migration
- How to match NSF files to archives for NSF migration
- Standard mail templates for NSF migration
- NSF migration failed and ineligible items
- Item age limit for NSF migration
- Mail file limits and NSF file access control
- Users' execution control lists for NSF migration
- Multiple instances of NSF migrator
- How NSF migration affects users
- Running NSF migrator
- NSF migration audits
How NSF migration affects users
This section contains a summary of the changes users see once their NSF files have been migrated.
Immediately following successful migration of each NSF file, its owner receives an automatic message saying that the file's content has been migrated to Enterprise Vault.
If you chose to create shortcuts to migrated items, it is these shortcuts that the users now see rather than the original items. According to the choices you made, the shortcuts are either in their original NSF files or beneath the view in their mail files.
In the case of shortcuts that are created in user mail files, each user sees one of two folder structures beneath the view:
One combined folder structure that contains the content from all the user's NSF files.
A set of folders, named after each of the NSF files. Each folder contains the content from just one NSF file.
If you chose to delete NSF files after successful migration, these files are no longer available to users.