6. Improved Content Pages: In the SharePoint world, content doesn’t live only in list items and document library Office files, it also lives in pages. SharePoint 2007 included several different types of pages - basic pages, wiki pages, web part pages and publishing pages - but their capabilities were limited and end users’ editing experiences were mediocre. Content pages have been greatly improved in SharePoint 2010, and the new rich text editor sizzles.  End users now can upload images and files, and even embed Web parts. These improvements make content pages a great target format for migrating certain types of Notes applications.

7. Code-Free Development Capabilities: There are good tools on the market today for migrating the content of Notes applications to SharePoint, but what about the design?  A big barrier to moving large numbers of Notes applications to SharePoint is the cost of rebuilding complex applications.  

Some organizations mistakenly assume a Notes application that took a certain number of hours to develop in Notes, with a certain number of lines of code, will require the same effort to rebuild on SharePoint. This is far from the truth. SharePoint is designed as a modern collaborative platform and allows you to do many things out-of-the-box or via the simple configuration that Notes developers had to build from scratch.

This list was fairly large in SharePoint 2007, but it’s expanded even more in SharePoint 2010.  In addition to new “big ticket” items like the Managed Metadata feature, a number of smaller features helpful to developers will reduce the cost of building applications.  

Many new capabilities are available to administrators who configure lists and libraries in a browser, including the ability to use simple input validation formulas. Now, you can specify validation for individual fields, or for the document as a whole, including messages that should be displayed if the tests fail. You also can add multi-level column indexes, specify which columns require unique values, and enforce “relational” constraints between lists.