HCL Notes (Lotus Notes / IBM Domino) to Microsoft 365 Migration

Platform prerequisites

CloudM Migrate only supports migrations from HCL / Lotus Notes version 10 and earlier.

The following software should be installed on the migration workstation:

  • HCL Notes client, version 6.0.2 or higher (up to HCL Notes version 10). The client installation should be compatible with the server installation

You will also need:

  • The HCL Notes/Domino server address
  • Administrator username. The username is usually in the format Admin/ORG
  • Administrator password
  • Administrator Notes ID file

Source Platform prerequisites

Service Access to Mapped Drives - If you are using the web version of CloudM Migrate or a multi server setup with secondary servers and want to migrate NSF files that are not on the Notes server and will be accessed directly from the file system then you should make sure that the CloudM Migrate service has access to mapped drives if the files are located there. Please see the article on making mapped drives available for more information.

Logging into the Notes Client - You must log into the Notes client on all servers where the migration will run when logged into the server as the specified Windows User and with the Notes Administrator username and password. Note Client should be closed after logging in. Failure to do this will result in permission issues when opening the Notes ID file.

Source Platform Settings

Choose Lotus Notes as the migration source and enter your HCL Notes (Lotus Notes / IBM Domino) settings into CloudM Migrate and then click Next.

Multi-Server configuration and network access - In a multi-server configuration, it is vitally important that the Master and Secondary servers have full network access. In some scenarios, this may require configuring proxy settings through Internet Explorer by clicking Tools > Internet Options > Connections > Local Area Network (LAN) settings to allow access.

Server Details

  • Server Address – The hostname or IP address of the Lotus Notes server.
  • ID File – The path to the Administrator's Notes ID File.

Client Authorization Settings

  • Admin Username – The abbreviated name of the administrative user that will be used to perform migrations. This should be of the form ‘Administrator/ORG’
  • Admin Password – The administrator’s password. This should be the password that can be used to access Notes using the ID file of the administrative user, who should have previously logged into Notes from the migration workstation.

You must log into the Notes client on all servers where the migration will run when logged into the server as the specified Windows User and with the Notes Administrator username and password. Failure to do this will result in permission issues when opening the Notes ID file.

Windows Authorization Settings

  • Windows Username – The username of the Windows User the Notes migration should run as (normally the same as the currently logged in user).  Specify domain\username if required.
  • Windows Password – The password for the Windows user.

Resource Database Details

These settings can usually be left at the default settings unless special customization is required based on your Notes infrastructure.

  • Resource Database – The name of the server database containing resources. If there are no resources, please leave this setting empty.
  • Resource Views – The views within the resource database containing resources.

User Database Details

These settings can usually be left at the default settings unless special customization is required based on your Notes infrastructure.

  • User Database – The name of the server database containing users.
  • User View – The view within the user database containing users.
  • Import Name Attribute – The name of the attribute used to generate the ‘Import Name’ field in the user list. Only the name part of any email address is used.

Configure Destination Platform Settings - Microsoft 365

Basic Platform Settings

Choose Microsoft Office 365 as the migration source and enter your Microsoft Office 365 settings into CloudM Migrate and then click Next.

  • All Advanced Settings are set to a default value, designed to ensure that your migration will work without additional configuration. You should only edit the Advanced Settings if instructed to by CloudM Support or in a CloudM Knowledge Base article.


Set the following settings:

  • Office / Microsoft 365 Plan - Set to Office 365, Office 365 Germany or Custom, as required.
    • If you want to migrate Shared Calendar Permissions, you will need to set the Plan to Custom, as you need to provide an Autodiscovery Service URL. Direct Exchange EWS URL should not be presented.
  • Authentication Method - Choose the authentication type that will be used with the server. For Microsoft 365, set to Modern.
  • Domain Name - The domain name of the Exchange domain. This should be the internet domain of the Exchange system and not the local domain name.
    • This might be the part after the @ in your administrator email address. 
    • If migrating from several different domains, several migrations will be needed.
  • Admin Username - The email address of a global administrator within your Microsoft 365 environment.
  • Admin Password - The password for the global administrator account specified earlier.
  • Test Username - The email non-admin user who is already present in the system to test connections.
    • Specify a primary SMTP email address (or just the part before the @ symbol and the domain name will be appended). The test user must have an active mailbox.]

Advanced Settings

For Microsoft 365 advanced settings, see here.

Select which items to migrate

It's now time to add which items you'd like to migrate.


To add the items from that you want to migrate from your source platform to your destination platform, select Add items to migrate drop down menu and click on one of the following options:

  • Get Items from source - Get a full list of all items in the source platform.
  • Bulk add / import items - Upload a CSV file to bulk add users.
  • Add User/Resource/ Group/Shared Drive/Team Site/Microsoft Team etc.- Manually add an item of the selected item type.

Selecting a Star next to any specific user or users will prioritize their migration. When a migration starts, threads will be assigned to any starred user first so that their migration can start immediately. 

At this point you can choose what to migrate for each user, you can migrate Mail, Contacts, Calendars, Tasks, Classic Sites, Notes and Channels.

Enter your user's full email address within the Export Name field. If you have already created your Microsoft 365 users, then you will just need to enter their username.

Select how much content to migrate

CloudM Migrate lets you decide how much content to migrate to your domain by specifying required date ranges. 


If you are changing your email address as part of the migration you can verify that the domain names are correct here. You can also specify specific Address Replacements in the respective section of the advanced settings.

Environment Scan

Environment Scan allows you to plan and prepare your migration by performing analysis of your source file and mail environment and reporting important information such as item counts, data volume, permissions, and folder depth.

Reports are produced which can be exported and analysed. Using the information provided you can estimate your migration's duration more accurately, and address any potential issues before your migration even begins.


Selecting Scope of Scan


Depending on your source platform, you can choose to scan files, emails, or both sets of items.


  • Leaving the Report on File Permissions setting unchecked will speed up the Environment Scan process.
  • In order to include Report on File Permissions in the process, you will need to check this setting AND enable Document Sharing (or a setting related to document sharing) in the Source Platform settings. If either is not enabled, the Environment Scan will not scan or report on File Permissions.


Your CloudM Migrate userlist is used to define the scope of the scan. You can choose to scan all accounts from your list, or restrict the scan to users selected for migration.


How to run an Environment Scan

After entering your source and destination server settings, populating your userlist, and configuring your settings, you will be prompted to run an environment scan. It is optional, but recommended for file platforms.

Click Start and then confirm by selecting Start Environment Scan on the pop-up box to begin the scan. CloudM Migrate will connect to your source environment and capture file and / or mail information. This can take up to several hours, depending on the amount of data present.


Once the scan completes, the data is reported on the Environment Scans page and can be exported to file, using the Export Scan Results option.


Start your migration

To begin your migration, select Start.



Review your migration results

During the migration process, CloudM Migrate will report back in real time exactly who is being migrated and the items being processed. All you now need to do is sit back, relax and wait for your migration to complete.

Check the progress of your migration.

Once complete you can download a full report for your migration.

Delta Migrations

CloudM Migrate supports delta migrations of all migration types. To run a delta migration after the first pass, simply start the migration again. Already processed mailbox items will be skipped, and file items will be checked for changes and re-migrated if updated since the previous run. More info:

Was this article helpful?
0 out of 1 found this helpful