V&M Home Page


Mail/Calendar/Contacts Migrations using the Cloud
Introduction
When companies decide to move their email from Lotus Notes to Exchange/Office  they need some additional hardware during the mail migration. Once the mail migration is complete, then these computers are no longer needed.

When working with larger companies they typically have a virtual infrastructure available. I can tell them the hardware and software requirements. They will spin up the required computers and I can go ahead and install and configure the Migration Software.

However, for the smaller customers like the James County Water Department with 200 users they don't have a lot of spare hardware. So they scramble around and locate some spare computers . Some are new and others they found under a desk. This mixing of hardware makes it an additional challenge to install and configure.

As an added service I would like to be able to offer the client the option of providing the additional hardware in the cloud. This takes pressure off the client and I get an environment that I prefer with identical workstations.

Background
At it's simplest, we need an additional computer which has Lotus Notes installed and access to the Lotus mail files. We use Notes to read the mail, calendar, contacts and journals from the Domino server.  The migration software reads the emails and transforms the data so that it is in a format that the Exchange/Office 365 will understand. This computer also has Outlook installed so that it can use MAPI to write to the Exchange server. Pretty simple read from one side, massage the data and write to the destination.

I refer to this initial computer as the Migration Control Centre (MCC). While this computer can handle the migrations the throughput is not going to be acceptable. Migrating to Office 365 we might get to speeds of 0.2 GB per hour. In order to gain more throughput we need to get multiple Migration Workstations (MWs) moving the data. So we build some additional MWs to Read/Massage/Write . With the addition of control software on the MCC the MWs request work from the MCC's queue. The MW grabs a job and starts migrating the mail/calendar/contacts and journals from Notes and writes them to Exchange/Office 365. Once the migration is complete, the MW reports back to MCC to say job is complete and to request the next job in the queue.

Ideal Solution
MCC
In the cloud, we build a MCC by installing the software required but we do not configure the software. We have Lotus Notes, Outlook, Migration Software, Excel, IIS, .NET frameworks, etc. installed. When we are engaged to help with a mail migration, we create a copy of this Master Migration Control Centre. On the new MCC, we begin our configuration. We connect to the Notes server(s). We run our mail analysis software to get an assessment of the source data. Next we connect Outlook to our Exchange/Office365 environment. Then we configure the Migration Software. So when we are engaged we are already half way there.

MWs
Over the past seven years of migrating mail, I have had as few as 5 Migration Workstations and up to 75 MWs all running simultaneous migrations. Like the MCC we create a Master Migration Workstation. All the software is installed but not configured. When we begin our engagement, we copy the Master and create a 1st MW. Now we connect to Lotus Domino and Exchange/Office 365. Now we make multiple copies of the 1st MW. Lastly we register all of the MWs with the MCC and we have the machines we need in the cloud.

We have been able to quickly spin up a migration environment.

Comments
That's the idea. All comments are welcome.
Click to send a comment




Author's Background
I am a Notes/Consultant with twenty-seven years of experience (almost exclusively with Lotus Notes / Domino). My experience with Notes began when I worked as a Senior Computer Consultant for Price Waterhouse. In 1993, I went to work for Lotus Development Corporation as a Senior Notes / Domino Instructor. I started teaching Application Development and System Administration with Version 3. Helped to develop the course materials for Version 4.x and Release 5.x When LotusScript, Javascript and Java were added to Notes/Domino I started teaching these programming languages.

In 1995, IBM acquired Lotus. For several years we were left alone and the culture did not change. It was a lot of fun to work for Lotus. In 1999 the handwriting was on the wall and I decided it was time for me to leave. So I established V&M to do Lotus Notes/Domino Application Development, System Administration and Training. I've been at it ever since. The life of the consultant is constantly changing. It has given me the chance to travel across Canada and the United States, Scotland, England, Bermuda, Jamaica, Barbados and Hawaii. No travel to the Far East yet. Anyone?

For the last seven years I have been helping companies move their data from Lotus Notes to the Microsoft platform.

Some thoughts on Notes to Exchange Migrations
Migrating from Lotus Notes to Microsoft - Very easy and very hard
Pre- Migration Report that I use
Encrypted Mail Choices
Export a Notes View to CSV
Mail Migrations Using the Cloud
Mail Migrations - Some Lessons Learned
Speeding Some Migrations
Redirecting Mail Migration Traffic
One post migration story
One Approach to Mail Rules
Remove Encryption Button
Microsoft's "Secret" Mail Migration Tool
NME Migrations from a secondary Domino Directory
How to remove encryption from a Notes database
NME and Secondary Address Book
Multi File Selector for Binary Tree CMTe
Problem Mail Files for NME (Notes Migrator for Exchange)
Using a Staging Server for Notes to Exchange migrations
SmartCloud to Office 365
Notes2SharePoint Part 1
Migrating Private Folders
Different roles in an email migrations
What to do with Profile Docs during a Migration

If you would like to see my resume
Click Here


Email John


Copyright 1999-2017, John Vanderhoff. All rights reserved. This document is NOT in the public domain and remains the property of John Vanderhoff. Distribution or modification of this document without the knowledge, review and express permission of John Vanderhoff is strictly prohibited.