Products

NEW VERSION!
CMT for Exchange 3.1 now includes the following significant new features...

Full Native Support for Migrations from Lotus Domino to Exchange 2010
CMT for Exchange now includes support for direct migrations from Domino to Exchange Server 2010 while still maintaining support for Exchange 2007/2003 and hosted Exchange Environments like Microsoft Online/BPOS.

Transitional Calendar Workflow
This feature allows users to schedule/update/reschedule/cancel single occurrence and recurring meetings regardless of the migration status of the principle or invitees. This highly valuable functionality is unique to CMT for Exchange and has been demanded for quite some time by organizations of every size. When combined with CMT for Coexistence, this functionality is further advanced to achieve an unparalleled level of calendar and scheduling workflow between Domino and Exchange.

Full Support for Migration of Domino Rooms, Resources and Online Meeting Places
This feature not only includes Domino Rooms and Resources into full calendar workflow by properly displaying them in the attendee fields, it also displays Room, Resource and Online Meeting Place information in the meeting location field and, optionally, within the body of a meeting to ensure that important information is preserved and presented in the most transparent fashion. This highly valuable functionality is unique to CMT for Exchange and has been demanded for quite some time by organizations that implemented Rooms, Resources and Online Meeting Places in the legacy Domino environments.

Centralization of All Configuration Parameters
All configuration options, some of which were previously defined on individual Migration Workstations, will now be available as part of a centralized configuration, further reducing CMT for Exchange configuration efforts, while preserving the richness of options and the high level of product functionality and flexibility.

Exchange from Notes Data Fidelity
CMT for Exchange migrates Lotus Notes email messages, calendar entries, contacts, to-do’s, journal entries and more to Microsoft Outlook and Exchange while retaining the original text formatting, images, attachments, and links. CMT for Exchange also ensures that even custom recurring meetings are properly migrated so that any subsequent changes, reschedules, or cancellations can be entered once for all instances of the meeting. The data fidelity of CMT for Exchange significantly reduces the risk that your users will experience business process disruptions, or worse – data loss or corruption.

Notes to Exchange Migration Management
CMT for Exchange’s unique Enterprise Migration Manager (EMM) allows you to manage the entire migration project. CMT for Exchange’s EMM enables you to schedule users for migration, automatically or manually provision the users in Exchange, monitor the status of their migration, and to configure pre- and post-processing actions like decrypting encrypted email items, collecting rules and access control lists, and more. EMM also enables you to control which data, and how much data, is migrated by enabling you to filter by data type and to set quotas on the amount of data migrated per mailbox. Acting as a centralized migration management system, CMT for Exchange’s EMM reduces the risk of forgotten tasks and provides an ‘audit trail’ of tasks both completed and pending.

Lotus Notes to Exchange Migration Throughput
CMT for Exchange can scale to meet the migration requirements of any organization. One CMT for Exchange migration workstation when properly configured can migrate more than 8 Gb of data per hour. For smaller organizations, one CMT for Exchange workstation may be appropriate. For larger migrations, multiple CMT for Exchange workstations, whether on virtual machines or individual workstations, will coordinate the work effortlessly. Adding additional workstations is a simple and painless process. These additional workstations use a technology called Automated Workload Distribution (AWD) to ensure that each workstation is kept busy continuously. Other products suffer from non-productive 'idle-time' because each worker waits for the last worker to complete it's job before they are all handed a new batch of mail files to migrate.