It seemed like such a good idea at the time, designing and building all those Lotus Notes applications. The platform was robust, it was a good environment for users and you could find plenty of developers. But now that you’ve embarked on a Lotus Notes to SharePoint migration, those applications feel like a parade of dinosaurs lurching and stumbling across your desk.
Management has told you they want you to migrate the apps from Notes to SharePoint. They didn’t tell you how to migrate them or what they want them to look like once you’ve finished. They’ve left that up to you.
The planning phase of your migration from Lotus Notes to SharePoint
In the planning phase of the migration project, you’ll need to address a few big issues:
- Remediation — How will you migrate your existing apps off of Lotus Notes? How will your organization perform the same functions in SharePoint that it has performed in Notes for so long?
- Future state — What will the new environment look like? How will users navigate it? Where will the applications reside in it?
- Budget — How much is it going to cost to remediate these applications?
Up to this point in your migration project, conversations have ended on the note of “Well, we’ll have to see how much this is all going to cost.” In this planning phase, you start filling in the variables with reasonable estimates of the costs in time, budget and productivity that your organization will incur.
Frankly, it’s not unusual for a migration project from Notes to SharePoint to become stranded in this phase. Some companies look at the costs involved in migrating large numbers of simple or custom applications and decide to go no further, either with the entire project or with parts of it.
We’ve put together an eBook, “Overcoming the Top 8 Challenges during Notes to SharePoint Migrations,” about the most common challenges. On page 8 you’ll find compelling arguments for including third-party web parts, forms and workflow tools in your migration project.
Refreshed 27 April 2019 to keep the topic and content relevant. Published 8 June 2015.