How do I configure a migration from Lotus Notes?
This guide is intended to provide an overview of the steps to follow for the administrators responsible for migrations from Lotus Notes 6.5+ using the MigrationWiz platform. However, in order to successfully perform a migration from Lotus Notes, we recommend referring to the migration guide specific to your scenario. These are in the Mailbox Migrations: Migration Guides section.
Note: In the case of clustered Domino servers set up with replication enabled, a single Domino server has to be selected as a source of data for all migration activities using MigrationWiz.
Step 1: Set up an administrative account for the migration:
A single administrative account will be used to migrate all mailboxes. This means there is no need to specify a password for each user's mailbox. In order to set up an administrator account on the Domino server, proceed as follows:
- Open the Domino Administrator.
- Select the server where the mailboxes are located.
- Go to the Files tab:
- Select the folder containing the mailboxes, and right-click on it:
- Go to the menu to manage Access Control:
- Select the user to be used to perform the migration:
- Grant this account sufficient rights to access the mailboxes:
Step 2: Set up the Lotus Extractor(s):
Lotus Notes is the only messaging system supported by MigrationWiz that requires the installation of local client software to perform a migration. The Lotus Extractor is a small console application (available here ) responsible for extracting data from the Domino server and securely streaming this data to the MigrationWiz cloud migration platform.
Note: The Lotus Extractor requires that you have the .NET Framework version 4.6.1 or later installed on the computer on which you install and run the Extractor. To determine the .NET Framework version currently installed, follow instructions provided by Microsoft: How to: Determine Which .NET Framework Versions Are Installed.
Regarding connectivity of Lotus Extractors, there is no need for additional connectivity like external IP addresses. Since the communication is initiated by the Extractor, no external IP address is necessary.
Read this Knowledge Base article for detailed configuration information on Lotus Extractor: KB004286.
We recommend that customers do not work with their mail files during the migration. We also recommend that custom Domino agents, if any, working with mail files are stopped during the migration to avoid document locking.
Lotus Extractor will communicate with two servers:
- The www.migrationwiz.com website (to retrieve connectors and submitted mailboxes).
- One or more migration servers in the cloud (to receive migration commands and push Lotus Notes data).
The diagram below provides an overview of this mechanism.
This method is best suited to large-scale migrations intended for large businesses and distributed environments.
Install one Lotus Extractor per machine (or virtual machine). We can migrate up to 15 mailboxes per Extractor. Each running Lotus Extractor requires a separate endpoint in MSPComplete and a separate machine (or virtual machine).
To set up the Lotus Extractor(s), follow these steps on each machine that will run a Lotus Extractor:
- If you have not opened the Lotus Notes client and logged in with the same administrative account you're performing the extraction with, do so now. Retrieve the ID file for that specific user and copy it to the machine.
- Ensure that the proxy settings are correct by opening Internet Explorer and navigating to Tools -> Internet Options -> Connections and disabling the Automatically Detect Settings option. If unable to connect to the internet with this option disabled, contact the network administrator to allow the Lotus Extractor.
- Close the Lotus Notes client (this will release the lock taken by the Lotus Notes client on the notes.ini file).
- Start the Lotus Extractor.
- Each Lotus Extractor displays a unique identifier, called the Lotus Extractor Identifier (see example in the screenshot below, line 2). Copy this identifier, because it will be needed later, during the migration configuration.
- Enter the MigrationWiz username and password.
- Enter the password of the Lotus administrative account you created in the previous step.
Important information about the Lotus Extractor:
- Each Lotus Extractor can simultaneously migrate up to 15 mailboxes.
- Deploy each Lotus Extractor within the Local Area Network where its target Lotus Domino server is located.
- Do not deploy a Lotus Extractor on a machine on which the Lotus Domino server is deployed.
- Do not deploy more than one Lotus Extractor on the same machine.
- Do not stop a running Lotus Extractor. Leave the console window open; the migration will start automatically after the last step of the configuration.
- After authenticating, the Lotus Extractor will generate a CSV file named "LotusExtractor.csv" to help perform a bulk import if necessary.
- Create the customer in MSPComplete KB005421
- Create the Source and Destination endpoints. KB005427
- Log in to the MigrationWiz account.
- Create the Mailbox Migration project. KB004834
The Project is now ready and will be automatically detected by the associated Lotus Extractor after the mailbox migration has begun.
Perform a full backup of any NSF file that will be migrated.
From the Project Dashboard:
- Select the mailboxes to be migrated.
- Click Start.
- Select the type of licenses to be used, and follow the on-screen instructions to start the migration.
If the configuration is correct, the migration will be launched within five to ten minutes, and data will start being migrated to the Destination.
If there is difficulty connecting to the Internet with Lotus Extractor, ensure that the proxy settings are correct by opening Internet Explorer and navigating to Tools -> Internet Options -> Connections and disabling the Automatically Detect Settings option. If you are unable to connect to the internet with this option disabled, contact the network administrator to allow the Lotus Extractor.
- When running Domino on A/S 400, we recommend first running a proof of concept to validate that your A/S 400 version is supported. Our QA department has not tested all versions of A/S 400, so we cannot guarantee that all are supported.