Lotus Notes to Microsoft 365 Migration Guide

Overview

This guide explains how to configure a Lotus Notes Connector to use the Cloudiway Platform Mail migration product and migrate to Google Workspace or Microsoft 365.

How It Works

The Lotus Notes migration requires a local agent installed on a dedicated workstation within your network. This workstation acts as the bridge between your Domino server and the Cloudiway cloud platform.

Pre-Migration Configuration

Before starting the migration, you must set up a migration workstation with the following configuration:

Migration Architecture

The migration is performed entirely from the workstation:

Data Flow Process

The agent connects to the Notes mailbox databases and dumps them locally. Then, it zips and uploads the data to the Cloudiway server. All exchanges are performed over a secure channel (TLS 1.2). Once uploaded to the Cloudiway server, the data is pushed to the target (Microsoft 365, Google Workspace, or Exchange). At the end of the migration, the data uploaded to the Cloudiway server is removed.

Prerequisites

To perform the Lotus Notes to Microsoft 365 migration, you need the following:

System Requirements

The migration agent workstation must meet the following minimum requirements:

What is Migrated

When migrating from Lotus Notes, the following mail-related items can be migrated:

Step 1: Create Lotus Notes Connector

First, create a new Lotus Notes connector in the Cloudiway platform:

Step 2: Install Local Agent

After connector creation, click on the Lotus Notes connector to access the download page. You will see both the Agent download and the Configuration file:

Configuration File Parameters

The configuration file contains the following important settings:

Step 3: Configure API Token

The agent needs an API token to authenticate with the Cloudiway platform. You must create a Personal Access Token and add it to the configuration file.

Access the APIs Page

Login to the Cloudiway portal and navigate to Account > Apis in the top-right menu:

Create a New Token

"Security": {
    "Name": "Test_Migration",{'
'}    "Token": "your-token-value-here"{'
'}{'}'}

Step 4: Create Target Connector

Create a target connector for your destination platform. You can migrate to Microsoft 365 or Google Workspace.

Option A: Microsoft 365 Target

Option B: Google Workspace Target

Option C: Exchange On-Premises Target

You can also migrate Lotus Notes to an on-premises Exchange server using EWS (Exchange Web Services).

Step 5: Run Migration

Now you can configure the migration settings, populate the user list, and run the migration.

Configure Global Settings

Navigate to Mails > Global Settings to configure your migration options:

Key settings to configure:

Populate User List

Navigate to Mails > User List to add users for migration. There are three ways to populate the user list:

Option 1: Discovery (Get List)

Under MIGRATION, click on the Get List option:

Specify the following parameters:

Option 2: Import User List

Click on MANAGE > Import to upload a CSV file containing the users to migrate.

Option 3: Create Manual Entry

Click on MANAGE > Create to manually add individual users. Enter the source Lotus Notes email address and the target email address for each user.

Run Audit (Recommended)

Before migrating, run an Audit task to assess mailbox sizes and identify potential issues:

Execute Migration

Once you have reviewed the audit results, you can start the migration:

Other Migration Options

Shared Mailbox Migration

Shared mailboxes can also be migrated in a similar way.

For this, create a file named LotusSharedMailboxes.csv in the same directory than the agent.

Here is the format (header row):

email;servername;sharedmailbox path

Example: [email protected];domino01;mail\sharedmailbox1.nsf

email is the email address of the shared mailbox.
servername is the Domino server name where the shared mailbox is stored.
path is the folder location on the shared mailbox on the Domino server.

Archive Migration

Cloudiway solution allows to migrate Lotus Archives.

First, you need to enable this setting in the configuration.json where you must set MigrateArchives = true.
Lotus Notes archive migration is managed directly from the Notes agent, not from the Cloudiway platform. The Archive view under mail migration is not used by Lotus Notes migration.

Instead, you must create a file named LotusArchives.csv in the same directory than the agent. This is where you will define the location of the archives.
Archives can be stored in a Domino server or in a network path.

Format of LotusArchives.csv

The CSV file must contain a header row with the following data:

email;NetworkFile;servername;archive path

email is the user email address associated with the archive;
NetworkFile is a boolean (true | false) that specifies if the archive is hosted on a network share (true) or on a Domino server (false);
Servername is the Domino server name where the archive is stored.
path is the folder location on the archive.

On a Domino server, it would be the relative path of the nsf archive file, for instance, archive\archivefile.nsf
On a network drive, it would be the path of the archive. For example, if the file is stored in \\NasServer\Archives, you can first map it to a drive (net use h: \\NasServer\Archives)
the path of the archive in the CSV file would then be h:\archivefile.nsf

Example of csv file:

email;NetworkFile;servername;archive path
[email protected];true;;h:\bobarchive.nsf
[email protected];false;domino01;archive\johnarchive.nsf

If a user has multiple archives, you must reference all the archives in the csv file, for instance:

email;NetworkFile;servername;archive path
[email protected];true;;h:\bobarchive1.nsf
[email protected];true;;h:\bobarchive2.nsf
[email protected];true;;h:\bobarchive3.nsf

Running Multiple Agents

If you want to run more migrations in parallel, you need to setup several workstations.
Let's say that you want to run 4 agents simultaneously:

Install 4 Workstations and configure 4 Notes clients.
Create 4 Notes Connector.
On each workstation, download the agent of 1 connector and its associated configuration.json.
Warning Do not use the same configuration.json on multiple agents/computers.

It would have unpredictable results such as automatically stopping migrations running on other agents.

In the cloudiway User List, dispatch your users among the different connectors.
Now, when you will schedule the migration of 1 user, it will start on the associated agent.

Frequently Asked Questions