Pre-Requisites
- Enable these HCL settings, before moving to the migration procedure.
- Destination User(s) should be already created at destination Admin account.
- SysTools Customer Management domain should be whitelisted in users network firewall.
- Create Console Project in Office 365. Read more...
- If your NSF file is password protected, then the UserID is required for migration.
- CN Value mapping CSV needs to be there for recipient address mapping.
- If you have Encrypted NSF file, then we are not supporting, in this case user can replicate the existing file with no encryption option.
- If DOAS is enable in that case user should compact NSF from Domino Server before adding to migration.
- Log in service with MachineName/UserName having admin privilege.
- Lotus Notes 12 (64-bit) & above versions should be installed and configured properly.
- Microsoft .NET Framework 4.8.0 or above
Following are the Steps to Perform HCL to Microsoft 365 Migration
Download and install SysTools Migrator on your system. While launching, you will be prompted to provide the Administrator id and password for authentication.
If your tool is not activated, then see the activation steps here. Activation Steps
Now, select “Lotus Notes” as a source platform and “Microsoft 365” as destination platform.
To enable advance settings for Concurrent migration (optional). Read more: Advance Settings
In the same screen, select the categories that you want to migrate from Lotus Notes to Office 365 under the Workload selection.
Use the Date Filter option to perform a date-based selective migration of mailbox data. Then, click Next to continue.
In the Source window, enable the “Connect Domino Server” option for Domino to Office 365 migration. For NSF to Office 365 migration, keep this option disabled.
You will need to put NSF files in the specific pattern as shown below:
Create a folder in disk drive, like:
D:/NSF Files/[email protected]/ (put all NSF files of user1)
D:/NSF Files/[email protected]/ (put all NSF files of user2)
D:/NSF Files/[email protected]/ (put all NSF files of user3)
etc...
And then select the folder "D:/NSF Files/" into our tool as "Source Folder Path".
The “D:/NSF Files/” folder must contain the NSF files of all the respective users with a NSFUserMapping.csv file as shown below:
Important Note: Ensure that the Source ID in the NSFUserMapping.csv file and the Folder Name must be same respectively. And CN Value Address must follow the syntax shown in the image. Users can not be validated if there is any mismatch in both the names.
Once the NSF folder is selected, check the Permissions section and make sure Read User, Read Email, Read Contact, and Read Calendar show green marks. After all required permissions are validated, click Next to continue.
Enter the target admin account details, Admin Email and Application ID, and then click Validate.
Now, map the users automatically by clicking Fetch Users. For more precise mapping, you can use Import Users or Download Template.
Once the process is complete, the tool will display the fetched users. Click OK to continue.
You will now see that all the source users have been successfully fetched. Next, start adding the target users, as shown in the image below.
You can also prioritize a user by marking them with a star. Then, click Validate in the top-right corner of the screen.
Once everything is verified, initate the process by clicking the Start Migration button.
A new window will then appear showing the licenses purchased, consumed, and available. After verifying that all the details are correct, click Start to proceed.
Once the migration process is complete, a new window will appear displaying the message “Migration started successfully.” Click OK to proceed.
In the migration window, three options are available at the top: In Progress, Pending, and Completed.
In the top-right corner, you will find the Download Report option. Click it to access the following two reports:
- Migration Summary Report
- Detailed Report
You can open any of these reports by clicking on it, selecting the destination folder, and then clicking Download. A CSV file will be generated in the chosen location, containing the complete details of the migration process.
If the report shows that some data did not migrate successfully, you can use the Re-run Migration option. Click it to access the following three choices:
- Retry Failed Items: Moves only the items that failed during the previous run.
- Re-run Full Migration: Restarts the entire migration process from the beginning.
- Delta Migration: Transfers only the newly added or changed data since the last migration.
- Open Domino Server and create a new replica of the user’s NSF file. Rename it to
filename1.nsfto differentiate from the previous file. - Move
filename1.nsfto the same folder as the original NSF file. - Open the SysTools Lotus Notes to Office 365 Migrator Tool.
- Ensure Lotus Notes and Office 365 settings are correctly configured. Verify that mapped users are linked to their respective Office 365 accounts.
- Click Start Migration to transfer only new and modified data. The tool will skip previously migrated data and transfer only the latest updates.
Pre-Requisites
- Ensure to enable these HCL settings, before moving to the Domino to Office 365 Migration.
- Lotus Notes 12 (64-bit) & above versions should be installed and configured properly.
- Lotus Notes component should be registered.
- Lotus Note Client should be connected to the Domino Server.
- The user configured to Lotus Notes Client should have minimum Manager level access.
- CN value, Mail file path and Internet address should be there for every user in names.nsf file.
- Project should be created on Azure portal to get the service account credentials.
- Project should be granted with required scopes.
- Destination user should have a valid O365 license.
- UPN should be provided for the user.
- .NET Framework 4.8 should be installed.
- Lotus Notes password should be provided if applicable.
- If DOAS is enable in that case user should compact NSF from Domino Server before adding to migration.
- For application service installation user should provide MachineName/UserName having admin privilege’s.
- User which you want to migrate must have at least Read permission.
Following are the Steps to Perform Domino to Office 365 Migration
Download and install SysTools Migrator on your system. While launching, you will be prompted to provide the Administrator id and password for authentication.
If your tool is not activated, then see the activation steps here. Activation Steps
Now, select “Lotus Notes” as a source platform and “Microsoft 365” as destination platform.
To enable advance settings for Concurrent migration (optional). Read more: Advance Settings
In the same screen, select the categories that you want to migrate from Lotus Notes to Office 365 under the Workload selection.
Use the Date Filter option to perform a date-based selective migration of mailbox data. Then, click Next to continue.
In the Source window, enable “Connect Domino Server.”
Ensure all pre-requisites are complete. You can find the steps here: Domino/Notes Pre-Requisites
Enter the target admin account details, Admin Email and Application ID, and then click Validate.
Now, map the users automatically by clicking Fetch Users. For more precise mapping, you can use Import Users or Download Template.
Once the process is complete, the tool will display the fetched users. Click OK to continue.
You will now see that all the source users have been successfully fetched. Next, start adding the target users, as shown in the image below.
You can also prioritize a user by marking them with a star. Then, click Validate in the top-right corner of the screen.
Once everything is verified, initate the process by clicking the Start Migration button.
A new window will then appear showing the licenses purchased, consumed, and available. After verifying that all the details are correct, click Start to proceed.
Once the migration process is complete, a new window will appear displaying the message “Migration started successfully.” Click OK to proceed.
In the migration window, three options are available at the top: In Progress, Pending, and Completed.
In the top-right corner, you will find the Download Report option. Click it to access the following two reports:
- Migration Summary Report
- Detailed Report
You can open any of these reports by clicking on it, selecting the destination folder, and then clicking Download. A CSV file will be generated in the chosen location, containing the complete details of the migration process.
If the report shows that some data did not migrate successfully, you can use the Re-run Migration option. Click it to access the following three choices:
- Retry Failed Items: Moves only the items that failed during the previous run.
- Re-run Full Migration: Restarts the entire migration process from the beginning.
- Delta Migration: Transfers only the newly added or changed data since the last migration.
- Open Domino Server and create a new replica of the user’s NSF file. Rename it to
filename1.nsfto differentiate from the previous file. - Move
filename1.nsfto the same folder as the original NSF file. - Open the SysTools Lotus Notes to Office 365 Migrator Tool.
- Ensure Lotus Notes and Office 365 settings are correctly configured. Verify that mapped users are linked to their respective Office 365 accounts.
- Click Start Migration to transfer only new and modified data. The tool will skip previously migrated data and transfer only the latest updates.
Free Download SysTools Lotus Notes to Office 365 Migrator Download Now