Lotus Notes to On-Premises Exchange Migration Guide
- This is the complete onboarding task flow for migrating mailboxes from Lotus Notes, or Lotus Domino, to On-Premises Microsoft Exchange versions 2007, 2010, 2013, or 2016..
- Complete each step in order. Links to corresponding Knowledge Base articles are provided.
- The MSPComplete section includes steps to deploy the Device Management Agent (DMA) to end users. Deploying DMA to end users is a prerequisite if you will be using DeploymentPro.
- DeploymentPro can be used to configure the Outlook profiles. Note: DeploymentPro requires licenses to be purchased before it can be used. Refer to Scenario 2 in KB004875 to read why it is recommended (but not mandatory).
- Lotus Notes is the only messaging system supported by MigrationWiz that requires installation of local software to perform a migration. This is because there are no remote APIs for Lotus Notes. The Lotus Extractor is a small console application (a standalone .exe file) responsible for extracting data from the Domino server and securely streaming this data to MigrationWiz's cloud migration platform. The steps to install this Extractor are included in the Prepare the Source Environment section of this guide. After installing our Lotus Notes Extractor, you can then manage the migration from the MigrationWiz web portal (e.g., to stop/start migrations, view statistics, etc.).
Prepare the Source Environment
- Set up an administrator account for migration on the Source Lotus Notes or Lotus Domino Server. KB005632
- Test administrative access to the mailboxes. KB004211
- Perform mailbox cleanup:
- Mailboxes should be emptied of unneeded/unsupported data:
- Old/unwanted email (this will reduce the time for migration)
- Large attachments (any attachment larger than 150MB will not be migrated)
- Unwanted mailboxes should be archived/deleted according to company compliance policies.
- Lotus Notes contacts are stored locally on the user's hard drive, in a local .nsf file. In order to migrate them, each user must have synchronized their personal address book on the Lotus Domino server before the migration begins.
- We recommend that you send an email to all users with instructions on how to synchronize their personal address books. Provide them the instructions that are in KB004310.
Prepare the Destination Environment
- Set up user accounts
- Create an admin account for migration that has full access permissions to all mailboxes. KB004725
- Set up a remote PowerShell session with Exchange 2010+. KB005111
- To manually grant administrative access for migration, execute the following PowerShell command in the Exchange PowerShell Console:
- Get-Mailbox -ResultSize Unlimited | Add-MailboxPermission -AccessRights FullAccess -Automapping $false -User MigrationWiz
- In the PowerScript script above, change the -User account to match the name of the admin account that was set up for migration.
- Any user account that is a part of the domain administrator, schema administrator, or enterprise administrator groups will not have any administrative rights to mailboxes, no matter how many permissions are granted. A security default of Exchange Server is to explicitly deny any user that is a member of these groups. This is why we recommend creating a new user account specific for migration.
- Increase message size limits. KB004613
- Increase maximum accepted content length. KB004609
- Increase maximum receive message size. KB004532
- Increase maximum accepted request length. This is only valid if your Destination server is running Exchange 2007. KB004610
- For the Source endpoint: Note: Create separate Source endpoints for each Extractor that you have set up. These will be used when setting up your MigrationWiz projects. You will be setting up one MigrationWiz project per Extractor.
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type, select Lotus Notes 6.5+.
- In the Server Name field, enter the Lotus Extractor Identifier. Note: This was generated in Step 8 of KB005633, when setting up your Lotus Extractor(s).
- For the Destination endpoint:
- Click on EndPoints > Add Endpoint > Enter endpoint name > For endpoint type select Exchange Server 2003+.
- Enter the OWA URL KB004392
- Click on the Provide Credentials radio button, and enter the admin account credentials for the account that was set up under the Prepare The Destination Environment of this guide.
- Via Group Policy Object (GPO). Note: This is the recommended methodology, because no end user interaction is required. KB005412 video
- Via email. KB005411
- Launch DeploymentPro.
- Go to All Products > DeploymentPro and follow the prompts to launch.
- Select a customer from the list by clicking on the customer name. Note: The status column will show enabled when a customer account has had DMA deployed.
- Configure the customer DeploymentPro module:
- Enter the Domain.
- Select the Destination endpoint.
- Checkmark the Auto-populate box.
- In the Client Interface Configurations section, upload your company logo and add supporting text. Note: We strongly recommend doing this, because this is the logo and text that end users will see in a desktop pop-up when they are prompted to reconfigure their Outlook profiles. If you do not upload your own logo, the default BitTitan logo will be included instead.
- Save and continue.
- Either select all users (by checkmarking the box to the left of the Primary Email column heading), or select the individual users (by checkmarking the boxes to the left of the user email addresses). Note: You will need to purchase DeploymentPro licenses for each user that will be using DeploymentPro. KB004647
- Click on the Run Module button.
- Set the date and time for the Outlook profile configuration to occur, and click on the Run Module button.
- The DeploymentPro module will install on user devices immediately, and then run silently until this date.
- The profile cutover date should be set to a date and time that is shortly after MX record cutover.
Watch this video to see a walk-through of the steps below.
- Create the Mailbox Migration project. KB004380 Note: You will create one project per Lotus Extractor.
- Create the Mailbox Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint.
The following options are the most valuable for this migration scenario:
- Set Maximum concurrent migrations. This should be set to 25. Each Lotus Extractor can simultaneously migrate up to 25 mailboxes only.
- Note: If Lotus Notes is configured to use rich text formatting (RTF) by default, you shouuld add the following advanced option setting: LotusDisableRetryOnGetMIMEFailure=1. This ensures proper MIME conversion of the formatted text.
- Note: If migrating in batches and coexistence is required, you will not be cutting over the MX records until your final batch of users has been migrated, and you must perform an extra step:
- Set up mail forwarding for Lotus Notes. KB004270
- If contacting Support for a Lotus Notes migration issue, you should provide the log files with your support request. The required log files are: LotusExtractor.log, Coordinator.log, Heartbeat.log. These files are located at C:/Users/UserName/AppData/Local/BitTitan/logs, as detailed in KB004301.
- If error messages state that email addresses cannot be resolved at the Source, refer to KB004285.