Understanding the Notes single user to multi-user migration assistant tool
You can use the supplied single user to multi user tool to migrate a Notes® single user install to a Notes multi-user install for an existing Notes release prior to upgrading to a new release. This enables you to convert an existing Notes single user install to a multi-user install for both Notes basic and Notes standard configuration deployments. It also enables you to convert a simulated multi-user install (where the user's data directory is on a mapped drive) to a true multi-user install. This tool is available for Notes 6.5.x, 7.x, 8.x and 9.0 installations on supported Windows™ platforms only.

The Notes multi-user migration assistant tool runs a supplied Visual Basic script (MUMigrationAssistant.vbs), which in turns is driven by a customized configuration file (MUMigrationAssistant.ini). The configuration file enables you to customize the migration for your unique deployment environment. The tool files are supplied in the Utility folder of the Notes install kit.

There are two use cases for this migration tool:

Once you have migrated from single user or simulated multi-user to multi-user within the same release, you can then upgrade from that release to a new release Notes multi-user installation.

Note: While the MUMigrationAssistant.vbs script can be edited, it is designed to be used as supplied with a customized configuration file MUMigrationAssistant.ini. The editable configuration file is supplied in the install kit's Utility subdirectory. However, the MUMigrationAssistant.vbs script is documented internally, so opening the script and reviewing the embedded comments is helpful. The tool provides basic functionality and you can modify the script for your own environment. Most installations can be addressed by just editing the configuration file. However, for uniquely customized installations, you can edit the MUMigrationAssistant.vbs script as needed.

As an administrator, you'll edit fields in the supplied configuration file with user-specific details such as location of the old and new data directories.

Note: Be sure to have enabled permission for needed read/write/delete operations in those directories.

When you start the MUMigrationAssistant.vbs tool, it reads the configuration file and performs the necessary migration operations, including modification of user-specific NOTES.INI values and needed registry setting changes, and migrates the single user install to a multi-user install.

Understanding a simulated multi-user Notes installation

Notes 8.5.1 introduced install options to configure MULTIUSERBASEDIR and MULTIUSERCOMMONDIR directory paths. In Notes 8.5.1 we introduced install options to configure MULTIUSERBASEDIR and MULTIUSERCOMMONDIR directory paths. A simulated multi-user Notes installation was sometimes used prior to the support of a configurable data directory. A simulated multi-user installation is a single user Notes client installation where the user's data directory is mapped to a shared drive. Each user who logs in to the system will have their own data directory on their shared drive, thereby simulating a multi-user environment. The MUMigrationAssistant tool migrates user data and registry entries properly to move from the simulated multi-user Notes installation to a true Notes multi-user installation.

1. An administrator runs the MUMigrationAssistant for the admin user on the system where they have access to the mapped data drive for a specific user.

2. The MUMigrationAssistant tool runs and does the following:

3. The administrator configures the Windows login script for each user to run the tool when they log in to the computer (OS login).

4. As each user logs in, the MUMigrationAssistant tool runs again and migrates that user's data as per the configuration ini file.

Run the tool initially to migrate the common files shared between all users, and also modify the registry settings entries for the whole machine. As each user logs in, a login script is run, with different parameters, which moves only that user's data from his mapped drive and also modifies that user's registry settings.


The following considerations exist:


Before the tool performs the migration it verifies the following checkpoints. If the NOTESPATH or CURRENTINIPATH are not valid, migration will stop. If the other settings are not specified or are incorrect, migration will continue.

Note: The MULTIUSERBASEDIR and MULTIUSERCOMMONDIR settings must either both be specified or not be specified at all.

If an Allclient kit (single user allclient installation) is detected on the system the tool exits with a message indicating that the source installation is not supported for multi-user migration.

If a multi-user kit (multi-user source installation) is detected on the system the tool exits with a message indicating that the installation is already multi-user.

Related tasks
Using the Notes single user to multi-user migration assistant tool