Can EdbMails migrate Lotus Notes NSF files directly to Exchange Server?

Yes. EdbMails supports selecting accessible NSF mailbox data and migrating supported email, contacts, calendars and other items directly to a Live Exchange destination without first converting the data to PST. Prepare the target mailbox and test the connection first. See the NSF migration guide .

What are the prerequisites for NSF to Exchange migration?

Install IBM Lotus Notes for source file access, prepare a reachable Exchange target, and ensure that the connection account has the necessary mailbox permissions. The destination account and storage quota should be ready before migration. Review the prerequisites .

How do I perform NSF to Live Exchange migration?

Launch EdbMails, select NSF Export and Migration and the NSF to Exchange option, then add the source NSF files. Preview available mailbox data, connect to Exchange with an authorized account, confirm source-to-target mapping, apply any required filters and start migration. Finally check logs and destination folders. Follow the migration steps .

Does NSF to Exchange migration require Outlook?

No. EdbMails migrates NSF data directly to supported Live Exchange destinations without a PST export stage. IBM Lotus Notes remains a prerequisite for the documented source workflow. The 32-bit Outlook requirement belongs to NSF-to-PST conversion, not direct Exchange migration. See the Exchange guide .

Can EdbMails automatically create target Exchange mailboxes for NSF migration?

You can choose the automatic creation feature when the application is installed on the destination Exchange Server and that environment supports the operation. Otherwise create the target accounts in Exchange and map the NSF sources to them. Validate Active Directory and mailbox provisioning before starting. See the NSF-to-Exchange steps .

Are impersonation rights needed to migrate NSF files to Exchange?

It depends on the destination connection method. If you use the on-premises Global Admin connection with impersonation, the Exchange administrator must manually configure the required ApplicationImpersonation rights and scope; EdbMails does not assign them automatically. Other individual mailbox access methods may not need impersonation. See the impersonation guide .

Can I migrate multiple NSF files to different Exchange users?

Yes. EdbMails allows multiple source NSF files in its migration workflow and supports mapping them to their corresponding destination Exchange mailboxes. Review every mapping to avoid sending one user’s messages to another mailbox. See the migration walkthrough .

Can EdbMails filter Lotus Notes emails during Exchange migration?

Yes. Use the supported folder and item selections and available date, sender or subject criteria to target only the data you need. Confirm selected filters before migration and reconcile the destination counts against the filtered source. See NSF migration filters .

Which Exchange Server version should I select as the destination?

Select a currently supported Exchange environment and verify the exact EdbMails target compatibility before migration. Exchange Server 2016 and 2019 reached Microsoft end of standard support on October 14, 2025; Exchange Server Subscription Edition is Microsoft’s current on-premises release. Existing legacy environments may be migration sources or historical targets, but they should not be recommended as new deployments. See Microsoft support guidance .

Does EdbMails preserve NSF folders and message attachments?

EdbMails is designed to migrate supported Notes mailbox folders, emails, attachments and item properties that can be read from the NSF source. Lotus Notes application-specific forms or workflows do not necessarily have Exchange equivalents. Check a sample user mailbox after migration. See NSF to Exchange features .

Can I repeat an NSF to Exchange migration incrementally?

Yes. EdbMails supports repeat incremental runs for eligible content using the corresponding saved job and mappings. If the source NSF files have not changed, a repeated pass cannot create messages that were never present. Read EdbMails incremental migration guidance .

How do I verify NSF mailbox migration to Exchange?

Review the EdbMails migration log and compare target mailbox folders, emails, attachments, contacts and calendar entries with the source preview. Investigate mismatched mappings, permissions, size limits or source filtering before rerunning. See the NSF migration steps .

Download Buy Now

Lotus Notes NSF to Exchange Migration Guide

This guide explains how to migrate Lotus Notes, IBM Notes, or HCL Notes NSF mailbox data to a supported Exchange Server target with EdbMails. It covers source preparation, Exchange prerequisites, NSF selection, target connection, mailbox mapping, migration, and post-migration verification.

For the commercial migration workflow, use the EdbMails Lotus Notes to Exchange Migration Tool. The application can migrate supported mailbox content such as emails, contacts, calendars, tasks, attachments, and folders to documented Exchange Server targets. Its incremental migration workflow is designed to process new or modified items on subsequent runs from the same migration environment, reducing unnecessary repeat transfer.

Migrate Lotus Notes to Exchange

EdbMails does not require Outlook for the NSF-to-Exchange migration workflow. The software can create target Exchange mailboxes in supported configurations, and its filter settings let administrators narrow the migration by criteria such as date, sender, recipient, subject, and message state where supported. Use mailbox mapping and migration logs to verify the target after each batch.

The sections below cover the migration prerequisites, step-by-step procedure, and the benefits of using EdbMails for NSF to Exchange migration.

Prerequisites to migrate Lotus Notes to Exchange server
- Step 1 : Install IBM Lotus Notes Application on your computer
- Step 2 : Check that your system meets the Exchange server setup requirements
  Current Microsoft lifecycle note: Exchange Server 2016 and Exchange Server 2019 reached end of support on October 14, 2025. Microsoft now directs supported deployments toward Microsoft 365 or Exchange Server Subscription Edition (SE). The EdbMails workflow on this page documents the Exchange Server targets currently listed by EdbMails; if you plan to use Exchange Server SE, confirm current EdbMails target compatibility before a production migration.
  The following links help you to set up your target Exchange server. Learn more about the network, hardware, coexistence scenarios, and operating system requirements for installing Exchange.
  For current Exchange planning, review Microsoft's Exchange Server supportability matrix and Exchange Server Subscription Edition information. The legacy-version links below remain useful only when you are maintaining or migrating to an older Exchange environment that EdbMails supports.
- Step 3: Prepare your system with the following prerequisites for Exchange server
  Complete the following prerequisites for Active Directory, Windows Mailbox server, and Windows Edge Transport servers before installing the target Exchange server.
- Step 4: Set up the target Exchange server for migration
  Given below is a list of key points for installing and preparing the Exchange server for migration.
  1. Prepare the AD and domains
  - Before installing Exchange Server, you need to prepare your Active Directory forest and its domains for the new version of Exchange.
  - If you have a separate team to manage the Active Directory schema, you need to first extend the active directory schema, else proceed to the next step to prepare the Active Directory.
  - If you have multiple domains you need to additionally prepare the Active Directory domains.
  2. Install Exchange server on your computer
  Ensure that you meet the server system requirements and prerequisites as outlined previously. Next, follow the link to install Exchange 2016 or install Exchange 2019 from the setup wizard based on which server you want to migrate to.
  3. Prepare a clean Exchange target environment
  Configuring Exchange Server for Mail Flow and Connectivity
  - Create and configure a Send connector to send mail outside the Exchange organization.
  - By default, Exchange automatically creates receive connectors for inbound mail flow when the mailbox server is installed. If you need to configure receive connectors manually, follow the steps in the link.
  - Add accepted domains to allow recipients to send and receive email from another domain.
  - Configure the default email address policy to add the accepted domain to every recipient in the organization.
  - Configure external URLs (domains) on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internet (outside the organization’s network).
  - Configure internal URLs on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internal network.
  - Configure SSL certificates from a third-party certificate authority for services such as Outlook Anywhere and Exchange ActiveSync.
  - Verify the Exchange server installation by running the command Get-ExchangeServer on the Exchange Management Shell (EMS).
  4. Create mailboxes and Public folders on the Exchange server
  Before you migrate your mail data, ensure that you create mailboxes on the target server and assign suitable licenses to them. For the Public folder migration, create mail-enabled Public folders.
  See how to create mailboxes in Exchange server
  Steps to create Public folder in Exchange server
  5. Assign management roles to the admin account
  - Application Impersonation
  - View-Only Recipients
  - View-Only Configuration
  Also assign the Organization Management role group to the admin user. It is an elevated permission that is required for mailbox and Public folder migration.
  6. Verify the mailbox of the admin account
  Check to see if the admin account that has been assigned management roles has a valid and non-hidden mailbox on the Exchange server.
  7. Configure the throttling and message-size limits
  Change the EWS throttling and message size limits manually on the Exchange server by following the steps in the link.
  - Change the EWS throttling settings on Exchange server
  - Change message size limits on Exchange
Steps to Migrate Lotus Notes to Exchange server using EdbMails
1. Step 1: Download and Install the EdbMails application
  - Download and install EdbMails on your computer.
  - Follow the on-screen steps to complete the installation process.
  - Open the EdbMails software.
  - Log in using your email address and password, or select the 'Start Your Free Trial’ option.
  - Choose ‘NSF Export and Migration’
  - Select 'NSF to Live Exchange’
  - You can either keep the default job name or click the ‘New Job’ button to rename it. Then, click ‘Next’ to continue.
2. Step 2: Add NSF files
  - Click the ‘Add file(s)’ button.
  - Choose the NSF files from your computer drive and click ‘Next’ to continue.
  - You can also share the offline NSF files on your network, assign read and write permissions to the file, and then proceed with the migration.
  - Select the NSF files you want to migrate, then click ‘Next’ to continue.
3. Step 3: Connect to target Exchange server
  - Click the ‘Add New Connection’ button to establish a new connection to the target Exchange Server. To use the previous connection, select it from the connection list and click the ‘Connect to Existing’ button to proceed.
  - Select the required connection options and click ‘Next’ to proceed. If you're using a Global Admin account to connect to the Exchange server, make sure impersonation rights are assigned.
    Steps to set impersonation rights on Exchange server.
  - Provide the target Exchange server details and click the ‘Login’ button.
  - Select one of the methods to load the mailboxes. Because of Microsoft API limits, the application can load only up to 100 mailboxes automatically. If you need to load more, simply use a CSV file to add the extra mailboxes, then click 'Next' to continue.
4. Step 4: Map source and target mailboxes
  - Choose the required mailbox mapping option. If you have installed EdbMails on an Exchange server, you can option to let EdbMails automatically create mailboxes on your target Exchange server.
    Learn how to automatically create mailboxes on the target Exchange server using EdbMails.
  - EdbMails software automatically maps mailboxes and folders between the source and target servers, which is especially useful for large-scale migrations. Alternatively, you can manually map source folders and subfolders to specific target locations if needed.
5. Step 5: Start NSF to live Exchange migration
  - Verify the NSF files you have selected for migration
  - Click the 'Start Migration’ button to start the migration process.
  - You can now monitor the migration progress. Once the migration is complete, a confirmation message will appear to review the migration status. Click ‘View Logs’ to check the list of migrated folders and mailbox items, along with their item counts.

Benefits of using EdbMails for NSF to Live Exchange server migration

EdbMails lets you directly migrate offline NSF files to Exchange server without Outlook dependency
EdbMails provides filter options to select mail items based on date range, sender address, recipient address, subject, read and unread status of the messages.
EdbMails is compatible with the Exchange Server targets documented by EdbMails, including Exchange 2007 through Exchange 2019 legacy environments
Automatically creates target Exchange server mailboxes
Free trial option to test NSF to Exchange migration features before purchasing
EdbMails offers 24/7 Free tech support

Frequently Asked Questions

Can EdbMails migrate Lotus Notes NSF files directly to Exchange Server?
Yes. EdbMails supports selecting accessible NSF mailbox data and migrating supported email, contacts, calendars and other items directly to a Live Exchange destination without first converting the data to PST. Prepare the target mailbox and test the connection first. See the NSF migration guide.
What are the prerequisites for NSF to Exchange migration?
Install IBM Lotus Notes for source file access, prepare a reachable Exchange target, and ensure that the connection account has the necessary mailbox permissions. The destination account and storage quota should be ready before migration. Review the prerequisites.
How do I perform NSF to Live Exchange migration?
Launch EdbMails, select NSF Export and Migration and the NSF to Exchange option, then add the source NSF files. Preview available mailbox data, connect to Exchange with an authorized account, confirm source-to-target mapping, apply any required filters and start migration. Finally check logs and destination folders. Follow the migration steps.
Does NSF to Exchange migration require Outlook?
No. EdbMails migrates NSF data directly to supported Live Exchange destinations without a PST export stage. IBM Lotus Notes remains a prerequisite for the documented source workflow. The 32-bit Outlook requirement belongs to NSF-to-PST conversion, not direct Exchange migration. See the Exchange guide.
Can EdbMails automatically create target Exchange mailboxes for NSF migration?
You can choose the automatic creation feature when the application is installed on the destination Exchange Server and that environment supports the operation. Otherwise create the target accounts in Exchange and map the NSF sources to them. Validate Active Directory and mailbox provisioning before starting. See the NSF-to-Exchange steps.
Are impersonation rights needed to migrate NSF files to Exchange?
It depends on the destination connection method. If you use the on-premises Global Admin connection with impersonation, the Exchange administrator must manually configure the required ApplicationImpersonation rights and scope; EdbMails does not assign them automatically. Other individual mailbox access methods may not need impersonation. See the impersonation guide.
Can I migrate multiple NSF files to different Exchange users?
Yes. EdbMails allows multiple source NSF files in its migration workflow and supports mapping them to their corresponding destination Exchange mailboxes. Review every mapping to avoid sending one user’s messages to another mailbox. See the migration walkthrough.
Can EdbMails filter Lotus Notes emails during Exchange migration?
Yes. Use the supported folder and item selections and available date, sender or subject criteria to target only the data you need. Confirm selected filters before migration and reconcile the destination counts against the filtered source. See NSF migration filters.
Which Exchange Server version should I select as the destination?
Select a currently supported Exchange environment and verify the exact EdbMails target compatibility before migration. Exchange Server 2016 and 2019 reached Microsoft end of standard support on October 14, 2025; Exchange Server Subscription Edition is Microsoft’s current on-premises release. Existing legacy environments may be migration sources or historical targets, but they should not be recommended as new deployments. See Microsoft support guidance.
Does EdbMails preserve NSF folders and message attachments?
EdbMails is designed to migrate supported Notes mailbox folders, emails, attachments and item properties that can be read from the NSF source. Lotus Notes application-specific forms or workflows do not necessarily have Exchange equivalents. Check a sample user mailbox after migration. See NSF to Exchange features.
Can I repeat an NSF to Exchange migration incrementally?
Yes. EdbMails supports repeat incremental runs for eligible content using the corresponding saved job and mappings. If the source NSF files have not changed, a repeated pass cannot create messages that were never present. Read EdbMails incremental migration guidance.
How do I verify NSF mailbox migration to Exchange?
Review the EdbMails migration log and compare target mailbox folders, emails, attachments, contacts and calendar entries with the source preview. Investigate mismatched mappings, permissions, size limits or source filtering before rerunning. See the NSF migration steps.