Solutions:
 |
|
Any Microsoft migration project regardless of size and duration should consist of three major phases:
Analyze
This phase begins with a detailed assessment of the existing messaging and application environment using our state of the art CMT Inspector for Lotus Notes software. During this phase customers will:
· Gain a better understanding of the existing legacy environment
· Understand mail file and application usage, and eliminate unused databases
· Minimize end-user impact associated with a migration
· Identify potential hidden costs and obstacles associated with the migration effort
· Put together a detailed migration plan the outlines the most effective approach to migrate both the messaging and the application environment |
 |
Coexist
Before embarking on the migration effort, Binary Tree recommends deploying CMT for Coexistence to help ease the user transition and compensate for inherent discrepancies between the Microsoft and Domino platforms. A good messaging coexistence solution will ensure high data fidelity, even for challenging embedded or rich text items. It will also provide accurate calendar data integration, taking into account the complex nature of recurring meetings.
It is important to not overlook Domino applications, even when planning to migrate only the messaging environment. Many Domino applications are mail-enabled and are coded to assume the mail client being used is Lotus Notes. If Domino applications will not be migrated at the same time as the messaging environment, Binary Tree recommends installing the CMT ZApp Module as an add on to your CMT for Coexistence implementation. Deployment of the CMT ZApp Module will minimize disruption for application users and remediate issues with mail-enabled applications without having to change a single line of code!
Deployment of both of these products in a pilot or lab environment prior to production deployment is highly recommend.
Migrate
Most migration efforts begin with the messaging environment. During this phase the migration process is designed, tested, refined, and documented. Using CMT for Exchange (formerly CMT Universal), customers can begin the messaging migration process by piloting the proposed approach and verifying it on a small representative group of users. During the messaging pilot, customer environment-specific issues are addressed and the fidelity of the migrated data is confirmed. After successful execution of the pilot, customers can proceed to migrate the mail files of all of their users with the comfort that the process will be seamless and result in high fidelity migration of data.
Application migrations generally follow a messaging migration. Using CMT for SharePoint, customers can begin piloting the migration of applications that are similar in design to standard Notes templates. These applications often have similar templates in the target migration platform. The most common templates include Discussion, Document Library, TeamRoom, and QuickPlace. After a successful pilot of the application migration process, customers can proceed to migrate all of their applications that match the defined standard Notes templates. For applications that do not match a standard Notes template, the application migration process involves using the information gathered about the design of the application from the analysis phase and recoding the application on a new platform.
|
Learn more about Solutions: Migrate to Microsoft | Migrate to Google Apps | Migrate to Lotus | Migrate to the Cloud | Weekend Express |
|
|