Pre-Requisites
- Destination User(s) should be already created at destination Admin account.
- Microsoft Visual C++ Redistributable Latest (Visual Studio 2015, 2017, 2019, and 2022) Should Be Installed. Download
- 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 9.0 or greater installed and configured.
- Microsoft .NET Framework 4.8.0 or above
Following are the Steps to Perform Lotus Notes to Microsoft 365 Migration
Download and install SysTools Migrator on your system. While launching, you will be prompt to provide the Administrator id and password for authentication.
If your tool is not activated, then see the activation steps here. Activation Steps
Tool provides the help section for the details about each migration mode. Click on "Help" button to view this section.
Then, you will get this screen where you can select Source & Destination Account to export data from Lotus Notes to Office 365.
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.
Using the Date Filter option you can perform the date based selective migration of the mailbox data. Click on Next.
Move to the Source Screen now. Provide the Admin Email and Lotus Notes Client Password details carefully.
After this, browse the NSF files using Source Folder Path option.
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.
Now click on Destination. Provide Admin Email and Application ID. Click on Validate for permission validation. Hit the Next button.
See how to create project for Office 365. Office 365 Project Settings
On the Users screen, there are several ways in which you can add users from the source account that needs to be processed.
Fetch Users: This option will fetch all the NSF files available in the selected location in Source tab.
The list of users is now, displayed on the screen.
You can select users by setting Priority wherein the prioritized mailboxes will be migrated first. One can set the priority by marking the desired source email.
Enter the Destination Email of the respective Source Email and Click on Validate to authorize selected user source and Destination Permission.
After the validation is successfully completed it will show against the Source and Destination permissions. Click on Start Migration after that.
Users can also Stop Migration if required while the migration is In Progress.
Pre-Requisites
- Lotus Notes client 9.0 should be installed on the machine.
- Lotus Notes component should be registered.
- Lotus Note Client should be connected to the Domino Server.
- Domino server should be on premise and it should be ON.
- 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.
- VC++ redistributors should be installed.
- .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 Launch the migration tool.
If your tool is not activated, then see the activation steps here. Activation Steps
Tool provides the help section for the details about each migration mode. Click on "Help" button to view this section.
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.
Date Filter: This option allows you to perform the date based selective migration on the mailbox data.
After making required changes, click on Next button.
Now under the Source screen, enable the Online toggle bar to perform Domino migration.
Provide the Admin Email, Lotus Notes Client Password, and Domino Server IP.
After filling all the required details, click on Validate button.
Now click on Destination. Provide Admin Email and Application ID. Click on Validate for permission validation. Hit the Next button.
See how to create project for Office 365. Office 365 Project Settings
Fetch Users: This option will fetch all the mailboxes available in the Domino Server.
Important Note: Please make sure that all the mailboxes are assigned with the Internet email address. If any mailbox is not assigned with the Internet email address, then that mailbox will not appear in this fetched user's list.
Import Users: You can use this option to import a CSV file containing Source and Destination mailboxes along with the CN Value.
Enter the destination email address adjacent to the source email address and click on Validate button to authorize Destination Permissions.
Once the permissions are validated, you will see the green icons under Source and Destination Permissions columns.
You can use the dropdown window to filter only the users with successful and failed permissions.
You can use this toggle bar to display only selected users in the dashboard. You can select the users by enabling the checkbox adjacent to the user mailbox.
You also get the option to set priority for users to migrate them prior to others.
After successful validation, click on the Start Migration button.
The software will start mailbox scanning.
Users can also Stop Migration if required while the migration is In Progress.
After completion of migration, click on the Download Report button to generate the detailed migration report.
The tool provides two options for downloading the reports:
Summary Report: The summary report will be a single .csv file containing migration reports of all the selected users for migration.
Detailed Report: Here, you get the option to save the detailed migration report of the mailboxes you want to. Select the mailbox and click on Download button.
Choose the destination location where you want to save the Detailed Report.
Re-Run Migration option is also provided in order to perform the migration again.
- Retry Failed Items: To migrated the data which didn't get migrated.
- Re-Run Full Migration: To perform the entire migration process again.
- Delta Migration: To migrate the newly arrived data in between the migration process
