V&M Home Page


NME Migrations from a secondary Domino Directory
On my last project I wanted to migrate the mail for people listed in a secondary Domino Directory. I had installed Notes Migrtor for Exchange (NME) version 4.7 from Dell Software.

We want to peel off a subset of an organisation and migrate only that group to Exchange. In this example, the parent company is 10,000 and they want to sever 500 users to Exchange. I did not want to import the 10,000 users, the groups, the mail-in databases and all the extra baggage that comes with 10,000 users. This became especially important to me because I was going to manage all of the collections.

We only have reader access to the Domino Directory. The client was gracious enough provide a database based on the Domino Directory template and provide Manager access. We copied and pasted the 500 users that we wanted to be migrated, to this new directory.

Since we didn't want 10,000 people in NME. On the Find NAB's choice we added the Migrate Directory and selected it. We deselected the parent company's NAMES.NSF


During our trial migrations the emails from the 500 people to migrated came across fine. Carolyn for example. However Curt and Heath are part of the 9,500 who are not going to be migrated.

When we ran the Directory Export the process includes the creation of Address Translation Table for the people to be migrated. However, when we had mail from one of the 9,500 users, they displayed the canonical name (CN=.....). This was unsatisfactory to the client. I didn't want to create my own AddressTransate.TSV. So I was going to have to add the 10,000 people from the Domino Directory in order to get an Address Translation Table that works.

The working solution was to run an agent against the Migrate Directory to flag these users to be migrated. The agent runs against Selected Documents - it is simply FIELD Migrate := "Yes" Now we are able to add a view to the Migration Directory to only display users selected to be migrated Form = "People" & Migrate = "Yes" When you add new users into NME - you run this agent against the new user. That way they end up in the People to be Migrated View. This view has the formula @Name([ABBREVIATE]; FullName) in the first column and make sure that this column is sorted.

Now we had 500 users and we only wanted to add the user from the Domino Directory if the user was not already in the Migration Directory. I wrote a simple LotusScript Agent to perform this task. I run this every couple of days to pick up the new users created in the Domino Directory.
Now we have everyone in the Migration Directory - the next step is to run a Directory Exportwhich builds the Address Translation for all 10,000 users.

Migrating from a secondary address book has an added benefit. When building the Address Translation table from the Domino Directory, when a user is deleted from the Domino Directory they are no longer listed in the Address Translation Table. Now when we have email from the deleted user the they are displayed with CN=. Since we never delete anyone from the Migration Directory the deleted user still remains in the Address Translation Table.no one ends up reverting to canonical.

I prefer to run these steps manually, but you could schedule both the Agent and the Directory Export.

Summary
We managed to keep the Migration Directory limited as to the content, but we had to have all users in the organisation listed so their emails addresses would display correctly. We also provided a way of updating the Migration Directory with changes in the Domino Directory.


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.