10 ways SharePoint 2010 will impact your Lotus Notes migration

By Steve Walch, Quest Software, Inc., Network World |  Software, collaboration, knowledge management

Over the past five years, many organizations have abandoned their legacy Lotus Notes/Domino environments and transitioned to a platform based on Microsoft Exchange Server, SharePoint and Office. However, some of these companies have hesitated to tackle the most difficult part of the transition: migrating their applications from Notes to SharePoint. Their concerns range from the cost of rebuilding applications on SharePoint to uncertainty about whether SharePoint has the capabilities needed.

The release of Microsoft SharePoint Server 2010 and SharePoint Foundation 2010 offers new features to make a Lotus Notes migration simpler and easier. Here are 10 SharePoint 2010 features that will change the game for any sized enterprise interested in adopting SharePoint to replace or enhance Notes environments.  

1. Scalability: It's not unusual for Notes databases in large enterprises to contain tens of thousands of documents. Organizations attempting to move this content to SharePoint 2007 ran into some severe size limitations on SharePoint lists and libraries. With SharePoint 2010, however, the recommended maximums for many criteria have more than doubled.  Even better, the penalty for exceeding them is less severe, and SharePoint will now automatically throttle certain operations that previously would have brought your servers to their knees.

2. Managed Metadata: Keyword fields are central to most custom Notes applications. These range from simple pop-up or drop-down lists of terms all the way to lookups in other views and databases.  While SharePoint 2007 already had ways to achieve this functionality, SharePoint 2010 adds a powerful new feature called Managed Metadata.  Think of this as the next level beyond Choice and Lookup fields. SharePoint now will allow you to keep all your terms in a managed term store, which includes a complete interface for allowing administrators to maintain them.

The Managed Metadata feature scales well from simple needs to enterprise knowledge management solutions. You can create a simple Managed keyword field and term set scoped to just one SharePoint site. The same term set can be referenced by multiple lists and libraries within that site, and, when needed, it can scale out to "Enterprise" term sets spanning many site collections and even be replicated between multiple SharePoint farms.


Originally published on Network World |  Click here to read the original story.
Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Answers - Powered by ITworld

Join us:
Facebook

Twitter

Pinterest

Tumblr

LinkedIn

Google+

Ask a Question