Lotus notes systems migeration to Sharepoint

HCL Domino Domino Forum
1

Hi All,

Organisation is planning to move lotus system to sharepoint , any idea how to action on this. Whjat steps will be required.

Truly appreciate any ideas and requirements for this. As I don’t have any idea from sharepoint perspective.

Thanks.

2

Subject: Lotus notes systems migeration to Sharepoint

You might want to start with the slide deck from Thomas “Duffbert” Duff’s presentation “Life After IBM Lotus Notes: How to Successfully Transition to a SharePoint World”.

In real terms, it’s a lot more about “transition” than it is about “migration”. Not everything about Notes translates well to the Microsoft stack, so for a lot of things you’re going to find yourself building new tools that work in a very different way. In any case, there are no “magic bullets”; there will be considerable work ahead if your organisation is exploiting more than the most basic of Notes’ capabilities.

3

Subject: Lotus notes systems migeration to Sharepoint

Contrary to what some may say, many companies have successfully migrated their mail and applications from Lotus Notes to SharePoint. There is a proven process to do so. Your management will have to decide on the exact steps to take. Time and budget will help define the level of effort required. I have been involved with Notes migrations in several different roles for 10 years now. I am now the Product Manager for what I consider to be the best Notes application migration tool on the market: Notes Migrator for SharePoint. I will gladly put you in touch with one of our migration experts. Then you can decide for yourself what will work the best for you.

http://software.dell.com/company/contact-us.aspx

You can also look at some of my blog posts on this topic.

4

Subject: Multi-value fields, parent/child designs, and workflows…how’s that work?

So I’m curious. I’ve played around a little with SP and from what I see, moving simple raw document data from Notes to SP is likely to be relatively simple.

Multi-value fields will be more interesting since SQL dbs don’t have that concept. I presume your system somehow normalizes multi-value fields into linked tables (at the SQL level anyway).

It seems to me that workflows would need to be totally rewritten. I see this as the hard part of a migration. Apps have real-time workflows that are user driven and may depend on the user’s role, and/or the state of one to many records. Apps also have scheduled agents that drive docs through the workflow, generate notifications, and manage any escalation process. Worflows can be managed by code written in @Function, LS, JS, or even Java.

I also see complexity in moving from a doc/response doc/response to response doc heirarchy to a SQL design especially if the parent and child docs update each other based on program logic. As a ferinstance, I have a parent with 5 child ‘action’ docs. When the last action is completed, the parent is updated to a ‘done’ status.

Any information you can publically share about howyour product handles these issues would be appreciated.

Thanks for sharing!

5

Subject: Lotus notes systems migeration to Sharepoint

Here is a good slideshare presentation about how a typical migration away from Notes would work:Replacing Lotus Notes? Here's How It Really Goes Down | PPT