Are you planning a migration from Lotus Notes to Microsoft Exchange? If so, it may seem there are too many moving parts and seemingly competing priorities.
A common challenge (or opportunity) I hear from individuals as they work through this process is properly balancing these priorities to optimize the outcome. They want to provide the best possible experience for the users, while effectively using their organization’s resources.
To help accomplish these goals, I often suggest a complete evaluation of migration options relative to the environment and organizational needs. Specifically, I encourage them to consider self-service migration for aspects of the migration or even the entire process.
Why would I suggest self-service migration? Admittedly, some individuals are initially hesitant, but it is highly effective when implemented using a solution properly designed to support the approach. Self-Service Desktop Migrator (SSDM) – a component of Notes Migrator for Exchange – can provide significant benefit for your migration and here are a few to consider:
- Silent Mode – Configuring Self-Service Desktop Migrator (SSDM) for Silent allows you to set the migration policies in advance. You will have granular control over the content migrated, filters applied, and target location for each data type. In addition, you can determine the level of interaction & screen visibility for the end users. For your migration, this means users can simply enter their Notes password and the migration will run silently as they continue to work.
- Seamless Conversion of Encrypted Content – You can use the central migration option to convert header information along with a custom message body for items encrypted in Notes. The custom message body can include a link to Self-Service Desktop Migrator (SSDM), which will run with the user’s credentials (in Silent Mode) and update the target messages with the encrypted content from Notes. The end result is fully migrated content without forcing your users to decrypt sensitive content in the Notes environment.
- Automated Conversion of Local Data – You may also face a significant challenge as you attempt to efficiently convert valuable Notes content stored in local NSFs. These may be local archives, personal address books, journals, or mail file replicas. You could consider replicating this content to a central location prior to migration, but that requires server storage, bandwidth, and proper timing to ensure a complete migration. As an alternative, you should consider Self-Service Desktop Migrator, which allows direct migration of this local content to PST, the Exchange mailboxes, or even the Personal Archive Mailbox available in Exchange 2010 and hosted platforms.
- Central Management and Control – As you consider this distributed architecture, you may have concerns about management and control. Self-Service Desktop Migrator (SSDM) eliminates these concerns through its architecture, deployment, and features. The solution installs in shard locations, so installation on the users’ computers is not required. You can simply distribute a link – via custom email, login script, or various other methods – to initiate the migration. In addition, SSDM allows you to control migration windows, the number of concurrent migrations, project timing, and the custom communications to each migration group. These features provide granular control over the timing and duration of the migration activity, while leveraging the efficiency of a distributed approach.
- Consolidated Monitoring – To ensure a successful and efficient migration process, Self-Service Desktop Migrator also provides central monitoring of the distributed migration process. You can use the central logging to analyze the results, monitor the migration process, and proactively assist users (if required).
Self-Service Desktop Migrator (SSDM) is a valuable component of Notes Migrator for Exchange that can significantly reduce the cost and complexity of your migration. The approach also reduces the burden placed on your team and provides an exceptional user experience. As you plan your project, I strongly suggest considering self-service migration as a component of your overall migration process.