Home / Platform Considerations

Notes NSF Considerations

Transend supports the migration from and to NSF files.

Requirements:

Notes email client: A 32-bit Notes email client is recommended and must be installed on all migration machines. For the best calendar data fidelity, we recommend Notes client v9.0.1 FP 8 or higher. The Notes client should be installed as a single user install “only for me” into its default location, or setup as a stand-alone client (if you do not need to use an ID file and password). The Notes client must be closed when using Transend Migration Console or the verification of credentials and migration will fail.

Important:

  • Transend supports migrations with a single-user Notes client installation, and does not support migration with multi-user Notes client installations.

  • If you only have a 64-bit Notes client installed, the following Custom Option enables 64-bit client support.

Notes ID file & password: You can use an Admin ID file and password to migrate your entire user base without requiring end-users’ ID file and password. If the NSF file is protected, the ID file, account name, and password will be required to access the NSF file. If the NSF file is accessed via a live Domino server then you will need the account information in order to access it. If the NSF file is taken from the Domino server and placed onto the local workstation you can bypass the need for an ID file. Normally, the NSF file is only protected when it is accessed through a Domino server or if the user elects to protect the file. Lastly, if messages are encrypted, then the ID file and password is required.

Data File: The data file is identified by the .NSF extension and the mail NSF file is based upon the Mail template.

Local Archive Migrator:

Depending on the size of your migration, Transend provides a customized Local Archive Migrator to support the migration of NSF archives. This utility contains a simplified user interface that allows NSF archives to be migrated with the click of only a few buttons.

This is a recommended option if you are not able to centralize end-users’ ID files and passwords, and require the migration to be performed on end-user machines.

View details of the Local Archive Migrator.