Too bad about all those dinosaurs, isn’t it?
They couldn’t overcome their obstacles to migration — the asteroids, volcanic activity, sun-blocking dust or just plain bad luck that made them obsolete — so they’re not around anymore. Sure, they had a good run of things over 65 million years ago, but unless they were lucky enough to land a role in a Steven Spielberg movie, eventually they had to move on.
Speaking of that, how are you dealing with your Lotus Notes to SharePoint migration challenges?
Although Lotus Notes hasn't been around for millions of years, it has had a pretty long life. Most organizations have accumulated hundreds of Notes applications and databases of varying size and importance.
One of the earliest steps in your migration project is assessment: discovering and analyzing Notes applications and databases, deciding which ones are worth migrating, and making sure that the project includes them. Your goal in this phase is to assess the cost, time and effort of moving apps, and to ensure you can maintain full fidelity of application content after the migration. That’s not easy when, for instance, usage history is not recorded or there are so many custom applications that you can’t categorize them properly.
Assessment is also the phase of the project when you start having conversations with application owners, making decisions about what will and won’t be migrated and discussing how those decisions will affect the business. But you won’t get very far down that path if you cannot identify or find the owners.
We’ve put together an E-Book, “Overcoming the Top 8 Challenges during Notes to SharePoint Migrations,” about the most common Lotus Notes migration challenges. It details the most common sticking points in each of the eight phases of a migration project — Page 5 covers the Assessment step I’ve described here — with ways you can avoid them on your project.