Enable Lotus Notes migration to SharePoint and Office 365 with no data loss

Migrate your Lotus Notes, QuickPlace/Quickr and Domino.Doc applications to SharePoint on-premises, online and hybrid environments, with high data fidelity and minimal downtime, using Migrator for Notes to SharePoint

Reduce the risk of data loss and failed projects with Migrator for Notes to SharePoint’s detailed pre-migration analysis. Stay in command of your transition with an intuitive management console, while your complex applications migrate quickly and seamlessly.

Features

Scan & plan - Discover, classify and analyze the design and data complexity of Notes, QuickPlace/Quickr or Domino.Doc databases. Quickly identify unused applications that don’t need to be migrated, as well as those needing development resources. Data collected during analysis can help you automate and manage the project.

Rules-based automation - Assign new migration jobs and target locations using a customizable rules-based engine for data collected during analysis. Use predefined rules for standard Notes applications, or define your own for custom applications. Automate hundreds of individual migration jobs, and reuse design work, to speed migration and reduce errors.

Easy provisioning - Reducing IT burden by automatically provisioning new SharePoint sites, sub-sites, libraries and lists based on your source infrastructure. Reproduce custom Notes applications schema in SharePoint lists and libraries, for example. Provision new targets for your migrated content from scratch or reuse the custom SharePoint site and list templates you have already developed internally.

Extreme data fidelity - Migrate Notes rich text and complex application data with no fidelity loss, giving users a smooth transition experience. Preserve all essential data, including keyword fields, embedded objects, multi-valued items, nested tables, document metadata and security attributes. Throughout the migration, you can maintain document links and HTTP links between documents by redirecting users to the current location of each document, whether or not it has been migrated to SharePoint.

Dynamic document destinations - To best achieve business objectives, you can choose from multiple options for application migration, beyond just lists and libraries. For example:

Complex app accelerator - By detecting which Notes forms are being used as content types and which applications include complex data features, Notes Migrator accurately determines migration requirements. Now you can:

Make use of native SharePoint features to migrate application content.

Move Notes form designs to InfoPath list forms or form libraries, and Notes views to SharePoint views.

Reduce complexity by migrating Notes data to SQL Server tables.

Specifications

Before installing Migrator for Notes to SharePoint 6.4, ensure that your system meets the following minimum hardware and software requirements.

Migrator for Notes to SharePoint 6.4 Clients

Before installing Migrator for Notes to SharePoint clients, ensure the system requirements are met.

At least 1 GB of RAM is recommended for running migration jobs and doing
small analysis projects. For large analysis projects or bulk migrations
involving over hundreds of databases, we recommend at least 4 GB of RAM.

Administrator access on the SharePoint server, content database, and site
collection (if you are installing on a 32-bit SharePoint server and plan to
migrate directly without using the Migrator for Notes to SharePoint Import
Service)

Lotus Notes or Domino

Some form of the Notes "engine" be installed on the same computer.

NOTE: Some functionality, such as conversion of native embedded images, requires Notes 6.x or higher. Rendering forms works better with later versions of Notes. We recommend using a Notes client version 7.0.3 or later for best results.

NOTE: Notes/Domino does not need to be running

NOTE: The Notes version requirements do not limit backwards compatibility of database formats. As long as you install a 5.x client locally (6.x or higher, if you want to convert native embedded images) you can access databases formatted for Notes 4.x (ODS 20) or even 3.x (ODS 17) and migrate them to SharePoint. You can connect to remote Notes 3.x and 4.x servers (even on non-Windows platforms) to
extract data.

Install and configure your Notes client (or Domino server). Run the product at least once to make sure that you can connect to other Domino servers in your organization.

Any user accounts that runs the Migrator for Notes to SharePoint clients should have Full Control access to the Notes program and data folders.
NOTE: On Windows Vista or Windows 7 environments employing User Access Control, the operating system virtualizes the Program Files folder that interfere with Migrator for Notes to SharePoint's access to Notes configuration and data files. Therefore, install Notes in a different location outside the Program Files folder, such as C:\Lotus\Notes.

Microsoft's Visual Studio Report Designer to create custom report templates (RDLC files). The Express versions are not supported however. For more information about this report designer and how to build reports using it, go to http://msdn.microsoft.com/en-us/library/ms157166.aspx.

Database

SQL Server® 2005, 2008, 2012, 2014

SharePoint Data Load
using web services

Any SharePoint 2010 or 2013 server with web services enabled

SharePoint Data Load
using Import Service

Windows 7, Windows 2008, Windows 2008 R2, or Windows 2012

SharePoint 2010 or SharePoint 2013

.NET Framework 3.5

Administrator access on the SharePoint server, database and site collection

System path

The program directory must be included in your system’s path environment variable to locate the Notes DLL. Set the system environment variable
NOTESNTSERVICE equal to 1 to make sure that Notes background processes are not terminated unexpectedly. Reboot the system after making these changes.

NOTE: You can access the environment variables through the Control Panel.

Content migration

Ensure that SharePoint Workflows or SharePoint Event Receivers are disabled/removed before you begin a migration.

Migrator for Notes to SharePoint 6.4 Services

Before beginning installation of Migrator for Notes to SharePoint, ensure the following system requirements are met.

Notes ID that can access Domino servers and read content from source databases

SharePoint Privileges

db_owner role in the Link Tracking database (if configured)

Full control access on Shared Files folder (if configured)

Import Services

a unique port number and/or host header on your server.

NOTE: You can have host headers so that the Import Service and various SharePoint site can coexist on the same computer with the same port number.

If you are using remote Migrator for Notes to SharePoint, you must have access to the Import Service and not be blocked by any firewall
software.

a new application pool with the desired service account or select an existing one. The service account must have administrative rights on the
local computer and any target SharePoint site to which you plan to migrate. The application pool will also need read, write, and execute
privileges for the Link Tracking database:

access on front-end server where Import Service is running:
Administrator access,
Member of WSS_WPG group
Member of IIS_WPG (Windows 2003 only)
Full control access on Shared Files folder (if configured)

SharePoint access
Member of the Farm Administrator's group
Site Administrator on site collections being migrated to

Database access
db_owner role in the SharePoint content databases being migrated to db_owner role in the Link Tracking database (if configured)

Configuration Privileges

Site Administrator access on the site collections being configured.

Link Tracking Service

account used to run the installation program has sufficient rights to create new databases

when the database is created, SQL Server administrators can adjust the security settings of the database to control who can write to it (anyone
migrating documents, as well as the Central Administration service account) and who can read it (anyone who might want to traverse an intra-document link).

Content migration

Ensure that SharePoint Workflows or SharePoint Event Receivers are disabled/removed before you begin a migration.

Upgrade and compatibility

For upgrading Migrator for Notes to SharePoint Client from a version previous to 6.3.x to version 6.4, uninstall your current version of Migrator for Notes to SharePoint. Then follow the installation instructions in the Installation and Administration.chm document included with this release.

If you are upgrading from a 5.0 Repository database and you need the new Quickr classification rules, you may open both your Repository database and the QuestRepository.ntf template in Notes and copy the documents containing the Quickr classification rules from the template to your Repository database.

NOTE: If you are currently using an older version of Migrator for Notes to SharePoint, obtain a new license from your sales representative to upgrade to version 6.4.

NOTE: If you were using a Link Tracking database that contains information about documents migrated using version 5.1 or earlier, you will need to run a conversion procedure on your database before finalizing the older links. Contact Support for further instructions.

For upgrading Migrator for Notes to SharePoint Client from version 6.3.x to version 6.4, you can do an in-place upgrade.

NOTE: The Job Files Path, Default Definitions Path, and Log Files Path are kept when you upgrade from 6.3.x to 6.4.

For upgrading Migrator for Notes to SharePoint Services from a previous version to 6.4, uninstall your current version first.