NMSP Client:
- 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.
- Windows Identity Foundation is required on the NMSP Client for the Office 365 Authentication environment type. Windows Identity Foundation is not supported on Windows XP.
Notes data extraction:
- Windows XP, Windows 2003, Windows Vista, Windows 7 or Windows 2008
- Lotus Notes 5.04 client or higher (may connect to remote Notes 3.0 or higher servers on any platform). Conversion of native embedded images requires Notes 6.x or higher.
- .NET Framework 3.5 and 4.0 installed
SharePoint data load using native web services:
- Any SharePoint 2010 or 2013 server with web services enabled
SharePoint data load using Import Service:
- Windows 2003, Windows 7 or Windows 2008
- Windows SharePoint Services 3.0, Office SharePoint Server 2007, SharePoint 2010 or SharePoint 2013
- .NET Framework 3.5
- Administrator access on the SharePoint server, database and site collection
NMSP Console
- Notes Migrator for SharePoint Console is a MMC Snap-in so Microsoft Management Console (MMC) 3.0 is required to run the Console. This is part of Vista and is now included in recent Windows Service packs, but if need it you can download it here: http://support.microsoft.com/?kbid=907265.
Note: On Windows XP or Windows 2003, it is a Microsoft best practice to run MMCPerf.exe before installing NMSP or other managed MMC snap-ins. After installing MMC 3.0, the MMCPerf.exe tool can be found in the Windows System32 folder. Running this tool can improve the performance of MMC and will prevent certain errors launching the NMSP Migration Console.
- The Notes Migrator for SharePoint Console requires that the free Microsoft Report Viewer 2008 be installed in order to display and export reports. If this component is not installed, the Discovery, Analysis and Migration reporting options will be not enabled. The Report Viewer may be downloaded from: http://www.microsoft.com/downloads/details.aspx?familyid=6AE0AA19-3E6C-474C-9D57-05B2347456B1&displaylang=en
- For creating custom report templates (RDLC files), you need a third-party report designer. Microsoft's Visual Studio Report Designer is currently the only report designer supported as the RDLC editor. The Express versions are not supported however. For more information about this report designer and how to build reports using it, please refer to http://msdn.microsoft.com/en-us/library/ms157166.aspx
- The NMSP Console uses a local Notes database as its Repository in order to store data that is gathered through analysis and user input. The Setup Wizard that is run after the Console is installed will create this database for you.
- For large discovery and analysis projects involving hundreds of databases, we strongly recommend more memory than the minimum described above. Having 4 GB or more of RAM available is desirable for this type of project.
Link Tracking Service
The Link Tracking Service uses a SQL Server 2005 or 2008 database to keep track of documents that have been migrated to SharePoint and intra-document references. If you choose to install the Link Tracking Service you will be prompted to create a new database or upgrade an existing one during the install process. If you plan to migrate Notes documents to multiple front-end SharePoint servers, you may wish to direct each Link Tracking instance to the same shared database so intra-document links will work correctly in as many cases as possible.
If this is your first Notes Migrator for SharePoint Services installation, you should create a new database on the SQL Server instance of your choice. This will require that the account used to run the installation program has sufficient rights to create new databases. After 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).
Import Service
The Import Service is deployed as a stand-alone IIS web site and thus needs to be configured with a unique port number and/or host header on your server. While it is possible to carefully arrange host headers such that the Import Service and various SharePoint sites can coexist on the same machine with the same port number, it is more common to simply assign a unique port number to the Import Service. In either event, it will be important that anyone using remote Notes Migrator for SharePoint or the Desktop clients have access to the Import Service and is not blocked by any firewall software. The Import Service is a Windows Communication Foundation (WCF) and thus allows a variety of transport protocols and security options. In particular you can decide to leverage SSL or use session level encryption.
Note: This list shows only the most basic requirements; it is meant to define the supported versions of the source and target systems, as well as summarize the nature of the required environment. Additional requirements must be satisfied for an actual installation and configuration; these are fully documented in the product installation guide.