SharePoint is a robust collaborative platform that is an ideal destination for many Lotus Notes Application Databases. Rivit’s successful migration program is based upon extensive experience and knowledge in both SharePoint and Lotus Notes. Rivit understands what Lotus Notes applications will migrate to SharePoint well, and how to modify those that will require it.

Applications that are created from standard IBM templates including Team Rooms, Discussion databases, and Quickr, can be migrated to equivalent SharePoint applications with relative ease. The effort to move these databases can be estimated with great accuracy, allowing your organization to better mange the migration. There are a lot of companies that say they can migrate Lotus Notes to SharePoint, but few do it well.

Migrating simple Lotus Notes Applications to SharePoint will provide an immediate boost to the migration by establishing the new go forward collaborative platform. In a relatively short period of time, end users will have access to the important information and applications they once depended on in Lotus Notes.

Would you like to speak with one of our migration experts?

Contact us today!

Rivit’s migration process is a four step process

  • Step 1. – Design Migration

    Although most migration utilities claim to migrate Domino databases with relative ease, the reality is that only few database designs migrate perfectly.  Most will require design work by highly skilled developers to ensure the fidelity of the new application and data.

  • Step 2 – Data Migration

    If design analysis indicates that the elements of a Domino database can be rendered on the new platform with acceptable fidelity, the data migration should be accomplished with little issue.  One important factor to consider during early stages of the migration is the size of a Domino database.  Data thresholds can be an issue in target platforms.  If a database has been heavily used and contains a considerable amount of data, the application data should be largely archived using Dcom, with only a subset of recent data moved forward onto the new platform.

  • Step 3 – Conversion Result Analysis

    Once the data migration has occurred, it’s important to perform a one to one comparison of Domino data with the new application.  Not all application data replicates well, and concessions may have to be made with respect to the final fidelity of the data on the target platform.

  • Step 4 – Testing

    The final step in in the migration of a Domino database is User Acceptance testing by the business unit.  It’s important to remember that your users will need time to learn how to leverage the new platform for their specific needs.