Migrating from Lotus Notes to SharePoint

The IONET Notes Pipeliner provides export and migration services for Lotus Notes Applications to Microsoft SharePoint.

The following is a step-by-step guide to the SharePoint migration process.
Migrating from Lotus Notes to SharePoint

1. Planning

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, again using the Pipeliner.
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.
2. Set up your SharePoint Environment

Set up your SharePoint environment. You need to be a Site Owner or Site Collection Administrator to upload files successfully.
3. Install PnP PowerShell

We use PnP PowerShell for uploading, batching requests for greater efficiency, with the PowerShell commands stored in plain text to allow modification. You can also use third-party upload tools.
4. Add your Microsoft credentials to the Pipeliner

Add your Microsoft credentials to the Pipeliner Defaults, Export Settings, 'Microsoft 365 and SharePoint' section. Specify your Username/Password, Client ID/Secret, PFX certificate, Tenant URL, Site Types, List View Threshold values etc.
5. Add your Applications to the Pipeliner

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 easily add all similar Databases (e.g. all Teamrooms).
6. Define specific SharePoint settings in the Pipeliner

SharePoint Site/Subsites. The SharePoint Site or Subsites to create and use.
Document Library. The Document Library to use. We use Document Libraries to provide SharePoint functionality such as attachment indexing and check-in/check-out.
Folder Hierarchy. Use fields and @formulas to define the SharePoint Folder hierachy based on Notes Document data, e.g. a 'Categories' field.
Metadata. Any Fields/Columns/Metadata you want to add, using Notes fields and @formulas, to display and use data from each migrated Notes 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.
Notes View Navigation. Recreate your Notes Views as SharePoint Pages, complete with columns, categories and search, to provide familiar navigation to end users.
7. Start Exporting

Migration takes place automatically, and the Pipeliner allows you to migrate the same data as many times as you want, so you can repeatedly modify your settings to achieve the best result.
8. Results

Folder Hierarchy.
Your defined folder hierarchy is presented in SharePoint, along with optional Navigation. In this case we've exported a Notes Teamroom Database;
Folder Hierarchy Navigation.
Notes Views are recreated from the original Database Views, to provide familiar end-user navigation;
Navigation Notes Views.
In these Views, documents are presented as links. Note the Search and Category expand/collapse functions;
Notes Views Document Rendering.
Documents are rendered using the original forms, with Metadata, Rich Text, Doclinks etc;
Document Rendering Responses and Attachments.
Response Hierarchy, Attachments, Embedded Objects and Embedded Views are also supported;
Responses and Attachments

IONET SoftwarePO Box 77, Paekakariki
Wellington 5034
New Zealand
Tel: +64 4212 5656
info @ ionetsoftware.com
ProductsMigrating
Archiving
Search
Change
Workflow
CompanyContact
Support
Downloads
Partners