Migrating from HCL Notes to SharePoint
Plan your migration to get an understanding of what's involved.
Identify the Applications to migrate. You probably won't want to migrate everything - unused or old Applications can be left behind or converted to XML, HTML, PDF or PDF/A. The Pipeliner has tools to assist with this.
Group Applications together. Many Notes Applications can be grouped together, for example all Discussion Databases or all Teamrooms. Use a Profile document in the Pipeliner to specify the migration characteristics for these groups of Databases in one place, or provide individual settings for custom Applications.
Create a SharePoint environment. You need to be a Site Owner or Site Collection Administrator to upload files successfully.
Choose SharePoint CSOM (Client Server Object Model) or PnP (PnP PowerShell for SharePoint) for uploading. If using Multi-Factor authentication, use PnP or CSOM with an App password. The Powershell commands for both options are stored in the Defaults document for easy modification, with instructions for installation provided by the Setup Wizard.
Add your Microsoft credentials to the Pipeliner Defaults, Export Settings, 'Microsoft 365 and SharePoint' section. Specify your username/password, SharePoint Base URL, List View Threshold values etc.
Use the Setup Wizard to add Applications to the Pipeliner, which simplifies the setup process. You can also choose to add Databases manually, or use a Profile to add all similar Databases (e.g. all Teamrooms).
SharePoint Site. The Site to create/use, which sits under your SharePoint Base URL.
Document Library. The Library to create/use. We use Document Libraries to provide SharePoint functionality such as attachment indexing and check-in/check-out.
Additional Columns. Any additional columns you want to add to the Document Library, using fields and @formulas to display additional Notes data per document.
ACL Security. Convert Notes ACL security to SharePoint Site Permissions. Individual and Group ACL entries are transferred to SharePoint with the equivalent level of access.
Folder Hierarchy. Use fields and @formulas to define a SharePoint Folder hierachy, e.g. based on Document Category.
Notes View Navigation. Recreate your Notes Application Views as HTML, complete with columns, categories and search, to provide familiar navigation to end users.
Migration happens completely automatically, and the Pipeliner allows you to migrate the same data as many times as you want, so you can change settings to achieve the best result.
Folder Hierarchy.Your defined folder hierarchy is presented in SharePoint, along with optional Navigation. In this case we've exported a Notes Teamroom Database;
Navigation.Notes Views are recreated using the original Database Views, to provide familiar end-user navigation;
Notes Views.In these Views, documents are presented as links. Note the Search and Category expand/collapse functions;
Document Rendering.Documents are rendered using the original forms, with Metadata, Rich Text, Doclinks etc;
Responses and Attachments.Response Hierarchy, Attachments and Embedded Objects are also supported;
