The migration process is designed to support both full application modernisation and selective transformation of Notes data into SharePoint.
Typical migration scenarios include:
- Migration of complete Notes applications to SharePoint sites and libraries.
- Archival of legacy applications into read-only formats (HTML, PDF, XML).
- Consolidation of multiple Notes databases into SharePoint site structures.
- Phased migration using staged data extraction and validation.
Organisations can define precisely what is migrated, archived, or retired as part of a structured transition strategy.
Successful migration begins with structured planning and assessment. Key activities include:
- Application discovery and assessment. Identify active, inactive, and redundant Notes applications across the environment, including distributed and local data sources.
- Migration scope definition. Determine which applications should be migrated to SharePoint and which should be retained in archival formats.
- Application grouping and profiling. Group similar applications (e.g., Teamrooms, Discussion Databases, Document Libraries) and define reusable migration profiles for consistent processing.
- Phased migration strategy. Prioritise low-risk or legacy applications first to validate migration patterns and performance before moving critical systems.
The platform supports detailed configuration of SharePoint target structures, including:
- Site and subsite creation.
- Document library mapping.
- Folder hierarchy generation based on Notes data.
- Metadata mapping using Notes fields and formulas.
- Security and ACL translation into SharePoint permissions.
- Navigation structures derived from Notes views.
This ensures migrated applications are not only transferred, but meaningfully integrated into the SharePoint information architecture.
The Pipeliner supports delta-based migration, enabling organisations to:
- Perform initial bulk migration of existing data.
- Synchronise only changed or new records prior to cutover.
- Reduce downtime during final migration windows.
- Re-run migration processes safely as configurations are refined.
This approach significantly reduces migration risk and supports controlled, repeatable deployment cycles.
Rather than performing a simple file export, the platform reconstructs key Notes application structures within SharePoint, including:
- Views and categorised navigation.
- Embedded views and hierarchical structures.
- Forms and layout elements.
- Rich text content and attachments.
- Response hierarchies and document relationships.
- Cross-application links.
- Security models and access controls.
This enables end users to continue working with familiar business data structures in a modern SharePoint environment.
The migration platform is designed for large-scale enterprise environments and supports:
- Parallel migration of multiple databases.
- High-volume data processing.
- Automated batch execution.
- Centralised configuration management.
- Repeatable migration profiles across application groups.
- Comprehensive logging and audit trails.
This ensures predictable performance even in complex, multi-application environments.
- Migration of Lotus Notes applications to Microsoft SharePoint.
- Support for complex and custom Notes application designs.
- Automated creation of SharePoint sites, libraries, and metadata structures.
- Preservation of View and
Form layouts.
- Mapping of Notes security (ACLs) to SharePoint permissions.
- Delta migration for staged deployment.
- Flexible filtering using dates, forms, folders, and @Formulas.
- Support for embedded objects, attachments, and rich text.
- Scalable processing for enterprise environments.
- Centralised administration and configuration control.
- Reduce dependency on Lotus Notes/Domino infrastructure.
- Improve information accessibility through SharePoint search and metadata.
- Reduce operational and licensing costs.
- Support compliance and long-term records retention strategies.
- Enable phased, low-risk migration approaches.
- Maintain continuity for end users during transition.
The solution is well suited for organisations that need to:
- Retire Lotus Notes/Domino environments.
- Migrate business-critical applications to SharePoint Online or on-premises.
- Consolidate multiple legacy applications into a unified platform.
- Improve governance and document management.
- Preserve historical business systems in a modern format.
- Support enterprise digital transformation initiatives.
Folder Hierarchy.Your preferred folder hierarchy is presented in SharePoint, along with optional Navigation. Shown in this example is a migrated Notes Teamroom;
Navigation.Notes Views are recreated from the original Database Views, to provide familiar end-user navigation;
Notes Views.In these Views, documents - exported as Pages - are presented as links. Note the Search and Category expand/collapse functions;
Metadata.You can also use standard SharePoint navigation. Note the highlighted metadata, added using data from Notes fields and @functions;
Document Rendering.Documents are rendered using the original forms, with Metadata, Rich Text, Doclinks etc;
Responses and Attachments.Response Hierarchy, Attachments, Embedded Objects and Embedded Views are also supported;
