I found this via one of my news alerts over the weekend; the slideshow on ITBusinessEdge apparently is the visual companion to a Quest Software whitepaper of the same title.  In an attempt to demonstrate that SharePoint 2010 is a more-suitable target for migrating Notes applications than previous Microsoft attempts, the 10+ page paper throws just enough jargon that it could be placed on an IT executive's desk and seem credible in answering the question of "can we migrate these Notes apps?"

Unsurprisingly, the paper and slideshow don't hold up under scrutiny.  As with so many of the magic black boxes proposed in the past, the subhead on every page should be "no one said it would be easy or cheap, but there are at least new methods to try".  It isn't clear how half of the supposed improvements mentioned here will actually help a Notes application make the transition to a SharePoint one, other than to try to match capabilities.  Migrating data?  Sure.  Migrating application logic?  Nothing in the paper addresses the actual conversion process or how it will be simpler or more cost-effective than past approaches.

There's also the challenge that many of the referenced "game changers" aren't actually part of the picture.  For example, #3 on the list talks about Office integration.  Now we've had Office integration in Notes for many years, and partners like Integra, Mainsoft, PSC, Swing Software, and even Microsoft's own tools have provided ways to use Office and Notes together effectively.  The described collaborative editing feature of Office 2010 + SharePoint sounds pretty cool.  I guess that's why I'm surprised that months after release, nobody is talking about this capability.  I did several Google searches (and even tried Bing!) to find the breathtaking first-person accounts of how useful the not-quite-synchronous editing model in SharePoint 2010 is...and can't find any.  Another example, #5 on the list, talks about how SharePoint 2010 is optimized for SharePoint Online deployment.  Sounds great, except that Microsoft hasn't deployed SharePoint 2010 to SharePoint Online standard customers yet.  They say they'll get around to it when they roll out Office 365 next year.  Further down the list, #8 covers InfoPath List Forms -- which might be interesting, except that few corporate customers deploy InfoPath as part of their Office usage (and some, of course, use tools like Lotus Symphony or OpenOffice).  Quickly, we've been able to eliminate three of the ten points of SharePoint 2010 from consideration.

Other SharePoint 2010 updates seem to be in the category of catch-up or, in one case, addressing problems you didn't know you had.  SharePoint 2010 apparently has some better taxonomy-generation tools and ways to manage lists, but I'm surprised at the boasting here about scalability (emphasis mine):

Organizations attempting to move ... content to SharePoint 2007 ran into some pretty severe size limitations on SharePoint lists and libraries. The most painful one was that only 2,000 documents could be displayed in any one view or folder; if you had 10,000 documents, you had to split them into multiple folders or find another way to balance the load. These workarounds not only slowed down the migration process, but sometimes resulted in a structure that was unusable. ...

With SharePoint 2010, however, the recommended maximums for many items have more than doubled. Even better, the penalty for exceeding the limits is far less severe: Performance does not drop off dramatically once you exceed the recommended limits, and SharePoint will now automatically throttle certain operations that previously would have brought your servers to their knees.
So some major problems have now been turned into "just" bottlenecks and others have more headroom before they are major problems.

Reason #6 on the list talks about improvements in SharePoint content pages.  There are plenty of customers who have used similar techniques in Notes/Domino for years for content creation and editing, and tools like the DominoWiki available on OpenNTF.org make for great content systems, such as we have deployed on IBM developerWorks.  Reasons #7 and #9 focus on application development and workflow, two hallmarks of Notes/Domino applications.  While it is true that SharePoint takes a different approach to app dev and workflow, there are clearly many situations where Domino developers are not "building from scratch" as is asserted in the paper/presentation.  And there are now thousands of code examples and complete applications available on OpenNTF.org for developers to get started with Domino Designer -- which, of course, is now free and can be utilized with the Amazon EC2 cloud for development and testing without needing to buy Domino licenses.

In short, as with any Microsoft product, SharePoint has had several improvements and come a long way from the Office server extensions and FrontPage tools of ten years ago.  However, I see little in this paper/slideshow that says to me, OK, now SharePoint is a Notes replacement, or that application migration suddenly has some massive ROI that commands customers to think about moving successful investments in Notes/Domino through the meat grinder with unclear results.  Are there a host of existing Notes/Domino applications that could benefit from modernization?  Sure.  Many of our customers have been taking advantage of Domino 8.5's XPages model to do just that.  Partner tools are coming that will accelerate such modernization in the Domino world.  The best destination for Notes/Domino apps continues to be Notes/Domino, and will be regardless of what the flavor of the week coming out of Redmond may be.  Judge for yourself.

Link: ITBusinessEdge: 10 Ways SharePoint 2010 Will Affect Your Notes Migration >

Post a Comment