Chat now with support
Chat with Support

Binary Tree Migrator for Notes 20.11 - User Guide

Section 1. Introduction Section 2. Pre-migration Activities Section 3. User Provisioning Section 4. Email Repliability Section 5. Migrating Mail Files Section 6. Rooms and Resources Database Migration Section 7. Mail-in Database Migration Section 8. Setting Migration Status Section 9. Access and Delegation Migration Section 10. All Accounts Section 12. Logs Appendix A: Staging Replicas Appendix B: Pre-Migration Troubleshooting Appendix C: Work with Files (Import/Export) Appendix D: Item Processing Results Appendix E: Migration Result Statuses Appendix F: Recovery Process Appendix G: Automatic Migration Restart Appendix H: Folder Processing Order Third Party Components

Section 2. Migration Control Center and Workstation Requirements


  • Pentium IV Class or higher

  • Hard Disk Drive: 80 - 100 GB + free space

Migration Control Center: 2 Cores, 4GB of RAM

Migration Workstations: Single Core, 2 GB of RAM

Operating Systems

  • Migration Control Center    

    • Windows Server 2019

    • Windows Server 2016

    • Windows Server 2012 R2

    • Windows Server 2008 R2 SP1

Note: US English version and US English regional setting must be used.

  • Migration Workstations

    • Windows Server 2019

    • Windows Server 2016

    • Windows Server 2012 R2

    • Windows Server 2008 R2 SP1

    • Windows 10 (64-bit)

    • Windows 7 SP1 (64-bit)

Note: US English version and US English regional setting must be used.

Double byte character set language packs should not be installed.


The operating system time zone must have a valid offset (e.g. UTC +00:00 Dublin, Edinburgh, Lisbon, London). UTC Coordinated Time is not supported.

Outlook Client Requirements

  • Supported versions:

    • Outlook 2016 (32-bit), Outlook Professional Plus 2013 SP1 which is part of Microsoft Office Professional Plus 2013 SP1 (32-bit only) (most recent version of Microsoft Outlook, via Windows Update, is required). Office 365 ProPlus and Click-to-Run 2016 and 2019 versions are also supported.

Note: This must be the 32-bit version of Outlook Professional. Home, Workgroup or any other specialized version is not supported on any migration workstation.

  • All reminders are shut-off (click Tools -> Options -> Other -> Reminder Options)

  • Auto-archiving is disabled (click Tools -> Options -> Other -> Auto Archive)

  • Programmatic warnings disabled (click Tools –> Trust Center –> Programmatic Access –> Never warn me about suspicious activity (not recommended))

  • Cache mode must not be enabled because the migration data will not be written directly to the server store

  • Outlook should be updated to the current patch levels, at the time of this product release


For Office 365 migrations the Outlook client should be activated for best performance.

In testing, there have been performance loss for throughput between Outlook 2016 or Outlook 2019 and Outlook 2013 with 2013 showing better performance.

Lotus Notes Requirements

  • Supported versions:

    • Lotus Notes version 11 is supported for Windows 10, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Lotus Notes version 10 is supported for Windows 10, Windows Server 2008, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Lotus Notes version 9.0.1 FP8 is supported for Windows 7, Windows 10, Windows Server 2008, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Lotus Notes version 8.5.3 Fix Pack 6 is supported for Windows 7, Windows Server 2008, and Windows Server 2012

    • Lotus Notes must be installed as a single user installation (multi-user installations are not supported)

    • Lotus Notes Designer must be installed for Notes links to migrate properly

    • The Lotus Notes Designer client must be installed in the migration workstation for doc links to migrate properly

*Lotus Notes 7.0.4 is NOT supported

*If you are using Notes 8.5.3, Fix Pack 6 is required due to a product defect that could impact data fidelity

*If you are using Notes 9.0.1, Fix Pack 8 is required due to a product defect that could impact data fidelity

  • Ensure that you enable the Notes ID security for the option “Do not prompt for password from other Notes-based programs (Reduces security)”

  • Ensure that you turn off Notes mail reminders in the Notes client preferences mail section

  • Ensure that you enable TCP/IP as the only port in the Notes client install preferences

  • On each migration workstation, Server Connection documents may be required to provide access to some of the Notes/Domino servers; if connection documents are required, it is the customer’s responsibility to provide the appropriate Destination server address

  • A standard HCL Domino mail template is required to be applied to the .nsf email databases for migration; mail templates from R6.5 to R11 are supported; R8.5 or R9 mail templates are recommended

General Requirements

  • For the Migration Control Center only:

    • IIS with web service components (SMTP and FTP components not needed); for more details, refer to the next section

    • English version of SQL Server 2012, SQL Server 2012 Express, SQL Server 2016, or SQL Server 2016 Express*; if SQL Server is not detected during installation, the installer will provide the option to install SQL Server 2012 Express

*Internet access is required for the installer to install SQL Server 2012 Express

*Non-English versions of SQL Server are not supported

*Before installing SQL Server Express, complex password requirements must be disabled on the server

*SQL Server 2016 Express is not compatible for installation with Windows Server 2008 or Windows 7

*TLS 1.0 should be enabled on the controller for the installation process to access the SQL server and create the database

  • For the installation of Migrator for Notes, you will need Microsoft Visual C++ 2013 runtime (both x86 and x64 on Migration Control Center) and .NET 4.5.2; if any of the additional packages are not installed, the Installer will automatically install them

  • You must disable any applications which take over or block the use of port 80 on the Migration Control Center

  • Windows PowerShell 2.0 Engine must be enabled on the Control Center to allow PowerShell matching; to enable PowerShell 2.0, navigate to Add Roles and Features Wizard > Features > Windows PowerShell and check Windows PowerShell 2.0 Engine

  • For the Migration Workstations:

    • For the installation of Migrator for Notes, you will need Microsoft Visual C++ 2013 runtime (only x86 on Workstations) and .NET 4.5.2

The installer will not install these items and they will need to be installed separately

  • For both Migration Control Center and Migration Workstations:

    • To use the import users with Excel feature or export users to Excel feature, Microsoft Excel must be installed and properly registered with the operating system; typically, this is only needed on the Migration Control Center, or where the import is going to be performed from

    • Do not have restrictions in your Group Policies or workstation policies that prevent the automatic creation of MAPI profiles or .pst files on the migration workstations

    • Ensure that any personal firewalls and the Windows firewall are OFF and disabled as a service

    • Ensure that Antivirus software is disabled, specifically, the real time scanning protection; otherwise, migration throughput will be reduced and other issues can occur such as crashes in stressful states of migration workload. If it cannot be disabled, please exclude the following directories from scanning:

      • C:\windows\temp and (%TEMP% if different)

      • C:\Program Files (x86)\Binary Tree\CMT for Exchange

      • C:\Exported PSTs (or the directory specified by the user for storing PSTs)

      • C:\windows\temp and (%TEMP% if different)

      • C:\Program Files (x86)\Binary Tree\CMT for Exchange (Migration Worker)

      • C:\Program Files\Binary Tree\CMT for Exchange (Migration Controller)

      • C:\Exported PSTs (or the directory specified by the user for storing PSTs)

      • %LocalAppData%\Binary Tree (eg C:\Users\Administrator\AppData\Local\Binary Tree)

    • Ensure that WSUS, Intel LanDesk, and other such programs are excluded from running on the migration workstations. These programs can halt migrations as their screens pop up to run tasks, as well as unscheduled re-boots caused by these processes can interrupt migrations.

    • Ensure that User Account Control (UAC) is disabled to allow Migrator for Notes to communicate with other applications and temporary folders

    • The Windows workstation login account should be a Local Administrator

    • Ensure that you turn off Automatic Windows updates



Windows Updates can be processed on migration machines but these should be completed in a planned method without migrations in progress

IIS and ASP.NET in Windows

  • For the Migration Control Center only:

    • Base version (v10.0) within Windows Server 2019

    • Base version (v10.0) within Windows Server 2016

    • Base version (v8.5) within Windows Server 2012 R2

    • Base version (v7.5) within Windows Server 2008 R2 and Windows 7

    • IIS Server installed with the default website, settings and default locations including:

  • Default Weblog Path: C:\WINDOWS\system32\LogFiles

  • ISAPI Objects Enabled (filters must be disabled)

  • Unlimited web site connections

  • No bandwidth throttling

  • Home directory: C:\inetpub\wwwroot

  • Directory Security: SSL Disabled

  • ASP

  • ASP.NET version 4.0

  • .NET 4.5.2 or higher

  • To avoid installation issues, IIS 6 Management Compatibility components should be installed and enabled if using Windows 7, Windows Server 2008 R2, or Windows Server 2012 R2

In Windows 7, enable IIS 6 Management Compatibility and all sub-options under Web Management Tools in Windows Features

In Windows Server 2008 R2 or Windows Server 2012 R2, enable IIS 6 Management Compatibility and all sub-options under Management Tools in Web Server (IIS) server role

  • For both Migration Control Center and Migration Workstations:

    • The machines must be logged into the destination Exchange Domain if migrating to an on-premise Exchange environment (does not apply to O365 migrations)

      • You cannot have restrictions on any workstation policy that can prevent the automatic creation of MAPI profiles or .pst files

      • All workstation names must be excluded from group policies that restrict local account privileges; It is recommended that all workstation names be excluded from Group Policy Objects (GPOs)

    • All migration workstations must be able to talk with each other over Port 80

    • XML calls must make connections between the Migration Control Center and All Migration Workstations using Anonymous Access

Migration Account Permission Requirements

  • There are two accounts used on the migration workstations for the actual migration of data: Exchange migration account and the Lotus Notes ID.

Exchange Migration Account:

  • Must be a mailbox enabled user object

  • Password should be set to never expire

  • Must be used to log into each of the migration worker machines

  • Is set to have Full Access to Exchange mailboxes during the Provisioning process


When multiple migration workstations are configured, several Migration accounts can be used and configured individually for migration workstations. This can be used to minimize the impact of Exchange or Office 365 throttling policies.

Lotus Notes Migration ID:

  • Must have Manager Access to all mail files being migrated

    • Manager Access allows you to migrate unread marks and update source file ACL

  • Must be configured on each of the migration worker machines

  • Must be used to perform the Mail File Audit

  • For the person(s) performing the migration process there are two accounts to consider when performing migrations: The Active Directory account (or Office 365 Administration account) that is logged into the machine being used and the Notes ID that is being used to access the Migrator for Notes Domino application.

Active Directory Migration Operator Requirements:

(PS represents PowerShell and ADO represents direct calls to Active Directory):

  • Ability to run Exchange PowerShell scripts (either remote or local to the workstation), generally the Exchange roles Organization and Recipient Management (PS)

  • Ability to manipulate user objects, specifically modify the targetAddress, proxyaddresses, mail and msExchPoliciesExcluded attributes (ADO)

  • Ability to delete contact objects created by the directory synchronization process (ADO)

  • Ability to update Distribution List member lists (ADO)

  • Ability to create and modify Distribution List objects (ADO/PS)

  • Ability to create and modify Mail Contact objects (PS)

Lotus Notes Migration Operator ID Requirements:

  • Manager with Delete access to the Notes Migrator.nsf Domino application database (EMM).

  • Manager access to all mail files.

  • Editor access to the Domino Directory

  • The Person Modifier Role is required to set the Mail Forwarding in the Domino directory

  • Right to issue console replication commands to Domino Mail and Staging server(s)

  • Right to create new replicas on Domino Staging server(s)

  • Right to create new databases on Domino Staging server(s) (required for Rooms and Resources migration)

  • Domino server security rights to run agents

Delegation Migration Requirements    

The following is required if using Access and Delegation Migration.

  • PowerShell 4.0 or 5.0 must be installed on workstations used for delegation migration, and on the Domino server if access delegation will be run as a scheduled agent on the server (this requirement is only for running scheduled agents in the local notes workspace)

  • When running delegation locally as a scheduled agent, the following conditions must be met:

    • Enable local scheduled agents must be set in the Notes Preferences of the workstation

    • The EMM database must be located under the workstations Notes data directory

    • The workstation and Notes client must be running for a locally scheduled agent to run

    • An Exchange or Office 365 account with the Application Impersonation role for access to the CAS Server and EWS

Ports and Endpoints

General Requirements:

  • DNS (Port 53) for workstation name and autodiscover resolution

  • Windows Active Directory for workstation login processing (Service overview and network port requirements for Windows)

  • Microsoft SQL Server (Ports 1433, 1434) for back end database access (Migration Controller only)

  • IIS Web Server access (Port 80) for Migration Worker communication to the Migration Controller


The IIS server on the Migration Controller is only used for connectivity between Notes and the Migration Workers to the SQL backend server. This does not require direct exposure to the Internet.

HCL Domino Requirements:

  • Domino server access for mail files and the Notes Migrator.nsf (Port 1352)

Microsoft Exchange and Office 365:

  • Port requirements are available in the ‘NM: What ports need to be open for Notes Migrator?’ Knowledgebase article.


Microsoft requirements for port connectivity to Exchange and Office 365 should be followed. This is provided by Microsoft in their online documentation.

Microsoft 365 endpoints

The following service endpoints are required for Exchange and Office 365 connectivity:

  • Autodiscover

  • MAPI

  • OutlookService

  • PowerShell

  • REST

  • EWS

  • RPC


For Office 365 the endpoint connectivity can vary for regional data centers. Microsoft provide details for endpoints in their online documentation which should be verified for the target tenant location.


For Office 365 Multi-Geo tenants the accounts used for Migration workers must be in the same locations as the target mailboxes to be migrated.

Proxy Servers:

Migrator for Notes will utilize the default browser proxy configuration where this is configured on Migration Controllers or Migration Workers.

Proxy auto configuration files are not supported, the proxy has to be directly configured for the default workstation browser.


Based on experience, the use of Proxy Servers does impact on the migration throughput (speed). It is recommended where possible to avoid the use of proxy connections to the target system and to exclude communications between the Migration Controller and Migration Workers from using proxy servers.


Setup and configuration of Proxy Servers is not covered by Product Support

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating