Migrator for Notes to SharePoint 6.16 - Installation Guide

Clients

Clients

Migrator for Notes to SharePoint (MNSP) supports the following methods to control your migration. For information on choosing a client, see Choosing a client.

Table 1. Clients

Client	Description
MNSP Designer	Allows you to design, edit, test and run migration jobs. The scope of this tool is one migration job, moving data from one Notes database to one SharePoint list or library or SQL Server® database.
MNSP Console	Allows you to look across many databases (potentially all the databases in your organization), and helps you to control the entire migration process from pre-migration assessment to provisioning and content migration.
MNSP Command Line	Allows migration jobs to be run from the command line, from batch scripts, and from scheduling tools. Allows certain job parameters to be overridden for easy automation of large quantities of similar migration job.

Migrator for Notes to SharePoint services

Migrator for Notes to SharePoint services

Migrator for Notes to SharePoint migrates content through the native SharePoint and SharePoint Online web services.

For increased performance and additional functionality on an on-premises SharePoint Server, you may install several of the server-side component described in this section. For information on choosing the Import Service or Web Services, see Choosing between Import Service and web services.

Table 2. Migration services

Service	Description
MNSP Import Service	Allows remote users of Migrator for Notes to SharePoint clients the option of sending exported Notes documents directly to the SharePoint server. The Import Service performs the SharePoint provisioning parts of the migration process and is implemented as a web service that can be accessed seamlessly from remote clients. It can provision new Lists and Document Libraries or populate existing ones, and leverages many capabilities of SharePoint including content types, folders, versioning, enhanced HTML, InfoPath forms, and document level security. The Import Service is architected as a Windows Communication Foundation (WCF) web service and allows for efficient, secure connections between clients and the SharePoint server over a variety of protocols. Administrators can configure the Import Service to run on the network port of their choice, who is allowed to access it, and which SharePoint sites are to be accessible through this service. There are two main deployment options for the Import Service. • Install the Import Service on every front-end server so Migrator for Notes to SharePoint clients can bounce between them. • Dedicate one or two front-end servers to be "Migration Servers" and arrange for all migration traffic to be sent there. This can be done either by using a non-load-balanced URL or by configuring the Load Balancer accordingly. In some cases, it may make sense to keep normal users off the dedicated Migration Servers completely, which again would be a Load Balancer configuration. A dedicated Migration Server can be thought of as a "disposable" server and by using it, you can avoid putting Migrator for Notes to SharePoint code on the "real" production servers. NOTE: The use of this mode of operation requires the Migrator for Notes to SharePoint’s Import Service and Front-End Services components, which are part of Migrator for Notes to SharePoint Services. For more information, see Installing Migrator for Notes to SharePoint services
MNSP Front-End Services	The Front-End Services component allows you to configure the Import Service and Link Tracking Service using the Site Settings page of your SharePoint site collection (site collection administration rights required). The SharePoint Administration Services component allows you to do the same configuration using a SharePoint Central Administration page (central admin access and site collection administration rights required).

Link Tracking

Link Tracking

The method used to track links during migration depends on the migration method used, as described below.

Table 3. Link Tracking

Method	Description
Link Tracking Service (LTS)	The Link Tracking Service (LTS) is part of the Front-End Services component. It ensures that Notes DocLinks continue to work before, during and after the migration process, regardless of the order of document migration. The service maintains a record of every document that is ever migrated and guarantees that users clicking on an intra-document link will always be able to find the current location of the document. Users can view a Link Tracking information page first, or simply be redirected to the desired page in Notes or SharePoint. As each document is migrated to SharePoint, its new location is tracked in a SQL Server database called the LTS database. When migrating Notes rich text fields that contain DocLinks to other Notes documents, these DocLinks are converted to URL links to a Link Tracking service that knows how to resolve them. If a SharePoint user clicks on a link to a document that has not been migrated yet, they will be redirected to the appropriate document in the Notes client. If the user clicks on that same link after the document is migrated, they will be redirected to the new copy of the document in SharePoint (which might be a list item, a document library file, or even an InfoPath form). Documents can be added to the Link Tracking Service whether the migration is accomplished via the Import Service or by using Migrator for Notes to SharePoint products in “local” mode (running the tool directly on the SharePoint server). If, after your migrations, you move your SharePoint site to another server or location, you can update the links in the LTS database using the Link Tracking Finalizer/Updater. If you have relocated the LTS redirector page, the Link Tracking Finalizer/Updater can also update all documents that have links to the LTS redirector page in order to look for that page in the new location. If you would like to remove the Link Tracking Service completely after the migration is done, the Link Tracking Finalizer/Updater can finalize the links to allow for its removal.
MNSP Sandbox-safe Link Redirector	Provides a simple diagnostic page for displaying doc link information. Because the Sandbox-safe Link Redirector page does not connect to an external database, it always offers to redirect user to Notes, even if the document has been migrated to SharePoint (Optional). This solution is a light-weight alternative to the Link Redirector that is part of the Front-End Services component. The Sandbox Link Redirector is intended for cases where you do not have the ability to install custom solutions and/or you cannot establish SQL connections from your server to the shared Link Tracking database. This solution should be used for a Microsoft Office 365 environment and other highly secured hosting environments. This page is packaged as a simple SharePoint solution (Quest.SandboxLinkRedirector.wsp). Because it is a sandbox safe solution, it can actually be installed by any site collection administrator, even on locked down environments such as Office 365, without involving your farm administrators at all. To deploy the Sandbox Redirector Page, see Deploying the Sandbox Redirector page.

Platform support

Platform support

The following platform versions and features are supported.

Table 4. Platform support

Platform	Description
Lotus Notes	• Supports Notes/Domino R5 or greater locally and can connect to any version of Domino server on any platform • Uses built-in Notes/Domino explorer or drag-and-drop Notes databases from Windows Explorer • Selects documents using view/folder lookups, full-text searches, or dynamic @Formula expressions • Reads note items, pre-computed view column values, attachments, embedded images, OLE objects, multi-valued items, rich text, doc links, dynamically computed values, unread marks and more • Converts Notes Rich Text fields to HTML or MIME (MHT) data formats • Accesses data using credentials of assigned Notes ID file • Includes predefined Data Definitions for Document Library, Discussion, Contacts, Calendar, Address Book, Calendar, Team Room and more
QuickPlace/ Quickr	• Accesses any Lotus QuickPlace/Quickr site or sub-room • Selects desired page types or customizes your query by folder, form used, or application of a selection dynamic formula • Extracts standard fields, custom fields, or QuickPlace/Quickr meta-data, including attachments, discussion threads, calendars and user lists • Converts rich text fields to standard HTML or MIME (MHT) data formats, including embedded images and attachments • Preserves folder hierarchy and security settings
Domino.doc	• Accesses any Lotus Domino.Doc library, cabinet or binder • Selects desired cabinet or customizes your query by binder, document type, or application of a selection dynamic formula • Provides the option to extract lastest draft versions, latest major versions or both • Extracts standard fields, custom fields, or Domino.Doc meta-data • Reads attachments, embedded images, OLE objects, multi-valued items, rich text, doc links, dynamically computed values and more • Converts Notes Rich Text fields to HTML or MIME (MHT) data formats • Preserves binder hierarchy • Preserves checkout status • Preserves security settings for the cabinets
SharePoint	• Supports SharePoint 2010, 2013, 2016, and 2019 • Writes List Items using original document creation/modification dates and user identities • Adds new fields to existing Lists • Adds file attachments to standard List Items or Document Libraries • Generates InfoPath forms and other XML documents • Supports InfoPath List Forms (SharePoint Server 2010/2013). • Supports Document Sets and Managed Metadata • Supports PDF and PDF/A document generation • Supports Microsoft® Word® document generation • Preserves Reply-To response hierarchies in Discussion applications • Maps calendar items, including recurrence details • Optionally detects already-migrated documents to prevent duplication • Provides advanced security mapping options • Supports advanced SharePoint features such as document level security, versioning, folder support, duplicate document handling, content types and document approval • Tracks migrated documents and ensures that DocLinks continue to work (regardless of the order of document migration)