There are a lucky few organizations in the world how can migrate all their Notes mail and calendar files to Exchange and their all their Notes applications to SharePoint in a relatively short period of time. The rest of us need to think about coexistence.
There are a lot of aspects of coexistence. Making mail and calendar work between your Notes and Exchange users is a pretty well-understood problem. But keeping applications that depend on each other and applications that depend on mail working together through an extended migration (or in a permanently mixed environment) is much harder.
Here are some of the ways in which Quest tools (including mine) try to make that easier.
Make sure your DocLinks keep working - Notes Migrator for Exchange and Notes Migrator for SharePoint work together to ensure that links in migrated documents continue to work before, during, and after the migration process. For example, if a workflow application running on Notes sends a notification that contains a link to an application, that link should work whether it is opened in Notes or Outlook, and should continue to work even after the linked-to document is migrated to SharePoint or InfoPath.
Integrate Notes Clients with SharePoint - Notes Migrator for SharePoint includes new capabilities to connect Lotus Notes clients to SharePoint servers. End users can, for example, select a few Notes documents and “drag and drop” them to SharePoint. Notes developers can also elect to use the tool’s LotusScript API to push Notes content to SharePoint directly from their Notes applications according to the organization’s business rules.
Surface Live Domino Applications in SharePoint - Web Parts for SharePoint includes web parts that allow you to access external data sources via web services. Customers can now use this capability to present and update back-end Notes/Domino applications in a SharePoint user interface. (In addition, Web Parts for SharePoint is a great tool for rebuilding Notes applications on SharePoint - more on that later.)