Lotus Notes to SharePoint Migration : Key Guiding Principles

There is a definitive wave of application migration happening from Lotus notes to SharePoint Platform. These initiatives are usually cost and time consuming. Clearly formulated strategy implementation from day one is needed for long running benefits.

I have put together some key guiding principles thru by experience, Please have a look and provide your feedback,

  • Please note that SharePoint Platform journey for end users should start well before LN apps start appearing there.
  • SharePoint institutionalization is the key to success, even before first app is migrated.
  • Don’t try to build LN look alike apps in SharePoint, since these platforms are entirely different, you will end up spending lot in this desire. Always think from SharePoint perspective than an existing Notes apps.
  • LN will be around for some more time, it takes time, it’s not overnight job, so please be prepared to support both the platform for sometime.
  • Think cohesively for all business stakeholders including Partners, vendors, remote users, global users, multilingual users – so that all can participate, maintain and share information effectively.
  • Understand the pain areas and try to address them effectively even by changing business process to improve productivity.
  • Also Please note that every Notes app need not be migrated to SharePoint, always check feasibility. Some apps may remain there or some may be developed using ASP.NET/Java frameworks or even SaaS route.
  • Take a chance to improve and standardize application portfolio using Industry best practices. It is your golden chance to reorganize.
  • Which App to take first –
    • Application which can easily be migrated to OOB feature of target platform.
    • Sometimes Business critical apps are taken first for taking first come advantage, this can help set credibility of the platform.
    • However, judicious decision can only be taken after detailed assessment and listening point of views of different stakeholders.
  • Meeting with stakeholders and understanding their expectations should ensure success of migration exercise.
  • Effective Governance practice to control performance degradation because of content growth. Generally, the larger the number of people who get information from a particular type of site, the more tightly it is governed, and vice versa.
  • Focus on Reuse and standardization by leveraging consistent Framework, Tools, products.
  • Proper Migration Assessment paves the road to success, allow sufficient time to accomplish this activity.
  • Work closely with ERP, this can give enormous power to users where information is available in SharePoint which is controlled and secure.
  • Devise a strategy on maintaining and sharing Master data between applications and portals.
  • Future-proof organization with Mobility, build some apps to be usable on mobile devices.
  • What areas of the business offer the most opportunity for growth? – Act in that direction, from both Migration and SharePoint Platform adoption perspective.
  • As far as possible, target using Out-of-the-box feature of SharePoint, this may lead to cost saving and ease of maintenance in future. Achieve more and more things using SharePoint Client side object model, this will keep your SharePoint upgrades lighter(low cost).
  • Please note that, Not everything to be achieved in SharePoint, consider cost-benefit analysis and don’t hesitate to look for some third party product on Microsoft technology which can replace some Lotus Notes applications, even some times some business processes can be moved to ERP.

Hope this will help anybody going migration route.

Happy reading !!


Laxmikant Patil


Lotus Notes to SharePoint Migration Scenarios – White Paper

One of my white paper written a couple of years ago which was published on KPIT Technologies company web site is now moved to Birlsasoft’s corporate website since Birlasoft has acquired KPIT. This is about migration scenarios while migrating Lotus Notes applications to the SharePoint platform.

The new location of my paper is – https://www.birlasoft.com/sites/default/files/resources/downloads/whitepapers/microsoft/lotus-notes-sharepoint-data.pdf

It is so nice to see my work getting accommodated thru company acquisitions.

Happy reading !!


Laxmikant Patil

Quality Management Systems(QMS) in SharePoint

How will you map typical QMS (generic instead of specific industry type) with SharePoint Product features? Here I have given a try, please have a look –

QMS Specific Core Features*

  • KPI’s, Interactive Reports
  • Powerful Workflow engine
  • External partner Access
  • Document Management & Control
  • Document conversions
  • Records Management
  • Electronic and digital signatures
  • Metadata control
  • PDF rendering
  • Controlled Printing
  • Governance
  • Communities of Practice

Security & Compliance

  • Segregation of duties
  • Tasks configuration and management
  • Notifications
  • Escalations, Delegations
  • With its integrated security features, Platform supports Security and identity Management sufficient for non-repudiation
  • Microsoft Cloud services and GXP compliance. Office 365 services are SAS70 Type II, ISO 27001, Safe Harbor, HIPPA w/BAA available

Platform Development features

  • Widely used .Net based Platform
  • Build around collaborative features
  • Rapid development features and frameworks
  • Ability to integrate with ERPs, CRMs, SCMs
  • Integrated nature of Microsoft office
  • Data migration possible from existing Systems
  • Cloud as well as On-Premise availability
  • Works closely with Exchange, Lync

User Experience

  • MS Office like UI
  • Entire platform can be used on various mobile devices, PC and tablets
  • Sortable, filterable views of information, ability to control information for set of users,
  • Ability to create ad-hoc views and data exports

* Some of the features may need custom development

Below is pictorial representation of above information, I hope this information will be useful to you.

QMS in SharePoint

Happy reading !


Laxmikant Patil