Skip Ribbon Commands
Skip to main content

What are some best practices for setting up the Lotus Notes Extractor environments?

Last Update: 7/21/2017 11:33 AM
This article has been moved to our new Help Center. Please update your bookmarks.

What are some best practices for setting up the Lotus Notes Extractor environments?



Multiple Extractors can be set up to support your migration from Lotus Notes, or Lotus Domino, to Destinations, such as Office 365.

The Extractors need to be set up on physical or virtual machines that are part of the customer's Local Area Network.

The Lotus Extractors will communicate directly with the Source Lotus Notes or Domino servers.

The Lotus Extractor will then be used for the communication to BitTitan servers. Communication to BitTitan occurs as follows: 

  • To BitTitan MSPComplete and MigrationWiz platforms to retrieve the endpoints and submitted mailboxes.
  • To one or more migration servers in the cloud (to receive migration commands and push Lotus Notes data).

The diagram below provides an overview of this mechanism.



This method is best suited to large-scale migrations, intended for large businesses and distributed environments.

Read this Knowledge Base article for detailed configuration information on the Lotus Extractor: KB004286.


  • Regarding connectivity of the Lotus Extractors, there is no need for additional connectivity, like external IP addresses, since the communication is initiated by the Extractor.
  • We recommend that customers do not work with their mail files during the migration. We also recommend that custom Domino agents, if any, working with mail files, are stopped during the migration to avoid document locking.
  • Install one Lotus Extractor per machine (or virtual machine). Typically we can migrate 25 mailboxes per Extractor. ​Each running Lotus Extractor requires a separate endpoint in MSPComplete and a separate machine (or virtual machine).​​