10 ways SharePoint 2010 will impact your Lotus Notes migration

21.12.2010

Declarative workflow capabilities have improved significantly in SharePoint 2010, and include a much richer set of out-of-the-box workflows to use in your applications, depending on what edition of SharePoint you install, and which SharePoint template you’re using. SharePoint Designer can address the majority of workflows in Notes applications without having to write code, eliminating the need to use Visual Studio.  

Users have a much larger vocabulary of workflow “conditions” and “actions” to choose from, including such Notes-like items as changing permissions on a document after it is submitted for approval, sending mail notifications, and moving content to another location.  You can now design workflows that operate at the site or list levels, reuse workflows across an entire site collection and even export them for use on a completely different SharePoint farm.  

10. Business Connectivity Services and External Lists: Because Notes has many capabilities for connecting to external systems like relational databases and enterprise applications, some of the Notes applications may simply be front-ends for some backend system.

SharePoint 2010 replaces SharePoint 2007’s limited Business Data Catalog with a much more powerful external data connector called Business Connectivity Services (BCS).  With this new facility, you can search, read and write content in your back-end systems and allows you to expose this content as an External List, which looks and feels like a native SharePoint list that you can easily include as part of any SharePoint page.  

This opens up the very interesting possibility of migrating your Notes content to SQL Server and still keeping the main user interface in SharePoint.  Many of the new capabilities mentioned above, such as InfoPath list forms, are still available when your data resides external to SharePoint.