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.
In the planning phase of the migration project, you’ll need to address a few big issues:
Up to this point in your Lotus Notes migration, 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.
In our new eBook, “Overcoming the Top 8 Challenges during Notes to SharePoint Migrations,” we cover the most common Lotus Notes migration challenges. Look on page 7 for more details on the planning phase I’ve described here, including the kinds of questions about productivity, financial cost and time that your migration team will need to answer as it makes plans for moving custom Lotus Notes applications to SharePoint.