Known issues

Known issues

The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.

Table 2. General known issues

Known issue	Issue ID
Notes Rich Text -> HTML Conversion - In the case where you are converting a Notes document that is stored in a Lotus' native rich text (CD) format to HTML for storing in SharePoint, there are currently some limitations in the HTML that is generated. Certain features are not supported in SharePoint HTML. In particular: • Images work, but image borders and ALT text do not • Tables work, but some table styles do not The following features are not yet supported at all: • Hide-when formulas • Sections (headers are extracted, but sections are no longer collapsible) • CSS Styles • Tabbed tables (extracted as normal tables with headers)	N/A
Extracting Embedded OLE Objects - If you migrate object types that are not listed below, a default conversion behavior is applied and the migrated files will have the .obj extension. Object Extension Acrobat.Document pdf PowerPoint.Show.8 pptx PowerPoint.Slide.12 pptx Excel.Sheet.12 xlsx Excel.Chart.12 xlsx Word.Document.8 doc Word.Document docx PowerPoint.Slide.8 ppt Excel.Sheet.8 xls Paint.Picture bmp SoundRec wav Outlook.FileAttach (calculated by name) WordPad.Document.1 rtf Visio.Drawing.4 vsd	N/A
All data are conducted in the time zone of the local machine. All Notes date/time values in Notes documents will be correctly converted to "local" time and saved as such in SharePoint, but the time zones used in the original Notes documents are lost. A workaround for this would be to use @formulas to retrieve time zone information separately.	N/A

Table 3. Console known issues

Known issue

Issue ID

When using a class rule to automatically assign SharePoint Target Sites, it is possible to end up with multiple databases targeting the same site URL, and thus the same SharePoint site. This is perfectly legal as far as our tool is concerned and is sometimes very useful, but it may or may not be what you intended. In the most extreme case, you could have several entire QuickPlaces/Quickrs (each with multiple lists and sub-rooms) all being merged into a single SharePoint site. In particular, the default Class Rule for QuickPlace/Quickr sites uses Application Name to generate Relative URLs for the corresponding Site Creation plans. Thus, if two QuickPlaces/Quickrs have the same name (or names that differ only by the case of the characters) this could result in the above condition. Possible workarounds are: • Manually override the Target Site URLs for the conflicting QuickPlaces/Quickrs and all of their descendants • Change the class rule to use something other than Application Name to generate Relative URLs (for example, ReplicaId or File Name are more likely to yield unique values) • Create an alternate Class Rule and carefully apply the alternate one to the conflicting QuickPlace/Quickrs

N/A

Table 4. Document sets known issues

Known issue

Issue ID

When migrating to document sets, the uniqueness of document sets is completely determined by the data that is mapped to the document set Name property. For example, if you map the Notes “Subject” to the document set Name property, two documents with the exact same Subject will get merged into the same document set! In future releases, we will detect such name collisions and append a sequence number when needed, as we currently do with generated documents, etc. For now, the user is responsible for mapping a value that will uniquely identify the document (for example a document ID number or a value that is computed with a formula) to the Name property.

N/A

 

Table 5. Link Tracking known issue

Known issue

Issue ID

The Front-End Services solution (part of the full Services installation) contains a SharePoint Feature called the “Migrator for Notes to SharePoint Link Redirector”. The installation program attempts to automatically activate this Feature on all existing site collections, there some environments where this does not work. Also, the feature is not automatically activated when new site collections are created. In both cases, you may need to go to Site Settings -> Site Collection Features and manually activate the “Migrator for Notes to SharePoint Link Redirector” feature.

N/A

 

Table 6. PDF or PDF/A documents known issues

Known issue	Issue ID
When generating PDF documents, the font specified in Notes will be used to render rich text in the PDF documents. When we detect that the installed font does not support all the characters required by the content being migrated, we substitute the “Arial Unicode MS” font instead. This allows us to handle most extended character sets you are likely to encounter, it may not be the highest fidelity choice for a given situation. Also this font (which is part of Microsoft Office), may not be installed on all migration workstations without a copy of MS Office installed.	N/A
If a table cell contains content too lengthy to fit on a single page, it is not split and continued on the next page. In these cases, the page height is extended to accommodate the content of this cell.	N/A

 

Table 7. Installation known issues

Known issue	Issue ID
The installation program prompts the user for the Notes program and data directories using values derived from registry settings on the local computer. Because the registry settings on the local machine may not be set correctly, please double check them and correct them manually if needed. There is no directory browser available to assist the user in locating these directories.	N/A
If SharePoint is removed from the machine before removing Migrator for Notes to SharePoint, the Migrator for Notes to SharePoint Services will not uninstall properly. Uninstall Migrator for Notes to SharePoint before uninstalling SharePoint.	CR57655
When running Lotus Notes on Vista, you may receive the following error in the Setup Wizard when the Console is launched for the first time: 'Can't initialize Notes session' Below are the links to the IBM documents describing the support for Notes on Vista: http://www-01.ibm.com/support/docview.wss?uid=swg21252343 http://www-01.ibm.com/support/docview.wss?uid=swg21269041 To workaround: 1 Turn off UAC on Vista. 2 Install Migrator for Notes to SharePoint. 3 Turn on UAC.	CR61026

 

Table 8. Claims based authentication known issues

Known issue	Issue ID
When connecting to SharePoint servers using Claims-based authentication, the authentication cookies that the tool stores may expire in the middle of a migration job.	N/A

 

Table 9. Migration known issues

Known issue	Issue ID
After Quickr 8.5 forums migration, SharePoint 2013 Community Categories tile shows 0 replies when replies are actually migrated.	Git# 8
You cannot migrate documents 500 MB or greater using Web Services. Workaround: Use the Import Service Mode.	Git# 9
MS-Word 97 documents cannot be embedded to a word document by Aspose.	Git# 282
When documents are migrated to SharePoint by Web Services of SharePoint 2010, the count of the documents shown in a list view cannot exceed a threshold limit set by SharePoint, even if views are set in SharePoint to allow this. Migrator for Notes to SharePoint must query the entire list/library to check for duplicates. There are two workarounds to this limitation: 1) Use the Import Service Mode. 2) Index the NotesUNID column using the SharePoint Server API.	Git# 337
When migrating a multi-user field in a Notes attachment to a multi-user field in SharePoint, users are not added if the attachment has Office 2007 format files. Workaround: Use the PowerShell script to disable document parsing in the SharePoint web site during Notes document migration, as follows: $web = Get-SPWeb “SharePoint_Web_URL” $web.ParserEnabled - $false $web.Update() Enable parsing after migration.	Git# 352

 

 

Table 10. Word online known issues

Known issue	Issue ID
You cannot edit a document that contains a table in Word Online.	Git# 114

 

Table 11. Link Finalization known issues

Known issue	Issue ID
Link Finalization service does not support several migrations of the same content. Only links in documents from the latest migration will be finalized.	Git# 63

 

Table 12. Import Service known issues

Known issue	Issue ID
Migration will fail when using Import Service with the target template is "Page Library 2010/2013" and the template of the Site Collection is "Publishing Portal”. Workaround: Use Web Services.	Git# 138

 

Table 13. Azure Turbo known issues

Known issue	Issue ID
A time out exception is occasionally reported when migrating using Azure Turbo mode. Workaround: None. All documents are migrated successfully.	Git# 424

Limitations

Limitations

The following are limitations to Quest® Migrator for Notes to SharePoint:

•

Migrator for Notes to SharePoint does not support migration into the SharePoint 2013 app list. SharePoint 2013 Apps are isolated. Apps cannot talk to each other. You can access an app only within the context of a SharePoint page.No external tool can access an app's artifacts. You can develop your apps to work with regular SharePoint lists.

•	If you are migrating to SharePoint Online, Migrator for Notes to SharePoint supports Office 365™ authentication and Active Directory Federation Service (ADFS) through Office 365.

•	If you are migrating document sets to SharePoint 2010, use the Quest Import Service. If you are migrating document sets to SharePoint 2013, you can use either SharePoint Web Services or Quest Import Service.

•	The Anchor Link feature in Lotus Notes is not supported.

System requirements

System requirements

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

Migrator for Notes to SharePoint 6.16 clients

Table 14. System requirements

Requirement	Details
Client Hardware and Software	• Windows Vista® Service Pack 2, Windows® 7 Service Pack 1, Windows 8, Windows 2008, Windows 2008 R2, Windows 10, Windows 2012, Windows 2012 R2, Windows 2016, or Windows 2019 • .NET® Framework 3.5 • Windows Identity Foundation is required for the Office 365 Authentication environment type • 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.
Notes Data Extraction	• Windows Vista Service Pack 2, Windows 7 Service Pack 1, Windows 8, Windows 2008, Windows 2008 R2, Windows 10, Windows 2012, Windows 2012 R2, Windows 2016, or Windows 2019 • Lotus Notes 8.5.3 to 10.0.1 • Both .NET Framework 3.5 and 4.0 are required
Privileges	• Administrator access to your local computer. • 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: Notes/Domino does not need to be running • 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. NOTE: Domino servers installed on Windows 2003 are supported.
Migrator for Notes to SharePoint Console	• Microsoft Management Console (MMC) 3.0 NOTE: You can download the MMC Console from http://support.microsoft.com/?kbid=907265. • a local Notes database 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. • Microsoft Report Viewer 2008 or 2012 to display and export reports. If this component is not installed, the Discovery, Analysis and Migration reporting options are not enabled. The Report Viewer 2008 can be downloaded from: http://www.microsoft.com/downloads/details.aspx?familyid=6AE0AA19-3E6C-474C-9D57-05B2347456B1&displaylang=en. The Report Viewer 2012 can be downloaded from: http://www.microsoft.com/en-us/download/confirmation.aspx?id=35747 • 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, 2016
SharePoint Data Load using web services	• Any SharePoint 2010, 2013, 2016 or 2019 server with web services enabled
SharePoint Data Load using Import Service	• Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2, Windows 2016, or Windows 2019 • SharePoint 2010, 2013, 2016 or 2019 • .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.16 services

Table 15. System requirements

Requirement	Details
Server Hardware and Software/SharePoint	Same prerequisites as those required by SharePoint. For a list of requirements for SharePoint 2010, see http://technet.microsoft.com/en-us/library/cc288751(v=office.14).aspx. For a list of requirements for SharePoint 2013, see http://technet.microsoft.com/en-us/library/cc262485.aspx. For a list of requirements for SharePoint 2016, see https://technet.microsoft.com/en-us/library/cc262485(v=office.16).aspx. For a list of requirements for SharePoint 2019, see https://docs.microsoft.com/en-us/SharePoint/install/hardware-and-software-requirements-2019
Database	• SQL Server 2005, 2008, 2012, 2014, 2016
Installation Privileges	• Administrator access on the SharePoint front-end server • Member of the Farm Administrators group • db_owner access to the SharePoint config database • dbcreator server role in SQL Server instance (if creating a Link Tracking database)
Privileges to run Migrator for Notes to SharePoint	• Access to SharePoint targets sufficient to perform desired migration tasks (provisioning sites, adding users, provisioning lists, updating list schema, writing records) • Full control access on Shared Files folder (if configured) • 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). NOTE: The Migrator for Notes to SharePoint Services installer can create a database for you, if desired, or you can create this database yourself by using the SQL scripts that are supplied with the product (installed in the ProgramData folder, for example, C:\ProgramData\Quest\Migrator for Notes to SharePoint\SQL Scripts).
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.16, uninstall your current version of Migrator for Notes to SharePoint. Then follow the Installation instructions in this document.

If you are upgrading from Migrator for Notes to SharePoint 6.9.1, you need to run the license upgrade tool after installing the new version to make your license consumption data available in the License Status dialog box. The tool is located at <MNSP_Home>\bin\UpgradeLicenseData.exe, you can run it by double clicking or from a command prompt window.

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: Versions prior to 6.6 need a new license from your sales representative to upgrade to 6.16.

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.16, 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.16.

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

Product licensing

Product licensing

Migrator for Notes to SharePoint supports standard Quest license validation. The trial version of the product permits you to discover all Notes databases, but limits deep scans to ten databases.

Additional licenses of the following editions can be purchased later: Starter, Standard, or Premier. The difference between the editions is in the number of databases to which you can migrate.

To import a license, see the Installation Guide.