Install OutLook on the client that will run the tool
Define a profile in OutLook, it must be configured
Define OutLook as the default messaging client
Run in full Admin mode
We’ve used a dedicated computer to do the migration. We were not allowed to connected from server to server. The dedicated computer must have a lot of disk space. In our case, we have used a test server. In our case, the users were already registered in our NAB.
All the new user's mail files were locally replicated to our test server.
To facilitate this step, a view should ideally be created in the public address book. This view contains only the files to migrate users using a search criteria, such CompanyName = "ABC". If this is not possible, do all the same to the next step. It is based on the hypothesis that the Notes users are already created.
To quickly create replicas of local databases, you could add temporarly to the public address book a new action button.
Dim dbCheck1 As NotesDatabase
Dim replica As NotesDatabase
For i = 1 To coll.Count
Set doc=coll.getnthdocument(i)
Set dbCheck1= session.GetDatabase(doc.MailServer(0),doc.mailfile(0)+".nsf")
If Not(dbCheck1 Is Nothing) Then
If dbCheck1.isopen Then
Call workspace.AddDatabase( dbCheck1.server,doc.mailfile(0)+".nsf")
Directory = Localpath +doc.mailfile(0)+".nsf"
'* http://www-1.ibm.com/support/docview.wss?rs=475&context=SSKTWP&context=SSKTMJ&dc=DB520&dc=DB560&q1=4005&uid=swg21155739&loc=en_US&cs=utf-8&lang=en
On Error 4005 Resume Next
Set replica = dbCheck1.CreateReplica( "", directory )
On Error 4005 Goto 0 'This causes the error handling to revert to normal error handling
'On Error 4005 Goto Error_Handling 'If the application has a error handling section then revert to it instead
Call workspace.AddDatabase( "",repertoire)
End If
End If
Next
Etc.etc.
End Sub
The first goal is a huge gain of performance and processing time. Although the tool can run from server to server, this approach was more appropriate for our scenario.
Following the creation of local replicas, it is possible to start the creation of profiles in the database from BinaryTree knowing that we already know the destination PST files to be converted.
The last preparatory step is to adjust the user's profile into the bineryTree's CMT database
How to Create Profiles in "BinaryTree"
Open the binary db, click the 
button to launch the "Wizard"
Follow the steps below in red which will select the names of the persons to be converted
This step may be carried out before the day of migration based on the location of files (PST) provided
Once completed these steps, go to the "End User Migration" menu
For each user, we must specify the location of the PST file. Each person will have their own.
In edit mode, in "Server Migration Info (1)
A-Select Microsoft Exchange (Point 2).
B-Enter the location of the PST file from this user. We need a format with double \ \ in the beginning.
C-select this option (Item 4)
To have better performance when running CMT, here's a few prerequists to look at:
A replica of the Binary db must also be created on the test server, to avoid transfers over the network.
In the preferences of the user’s client Lotus Notes in the Mail tab, disable the reception of new emails prevent transfers over the network.
In the location document of the Personal Address Book (names.nsf) of the client that will make the conversion, under the Server tab, you must blank the value Server \ Host messaging to avoid transfers over the network
In the Mail Setup tab, specify the local server instead of to avoid transfers over the network
Launch of the conversion
Once the prerequisites of BinaryTree is completed for all users, you can click on "Server Migration".
The system will then propose a list of all users for which you have chosen Microsoft Exchange.
Select the users you want, one or several.
You wait until the conversion is completed. When you're done, you can go and see if errors occurred during conversion. Event logs are located in each file of the database users BinaryTree CMT.
By default, the databases will be deposited in the Data folder of local Lotus Notes client under UnRepertoire \ MAIL \ xxx.nsf where xxx is the file name correspondance.
At the end of the conversion, you must close the Lotus Notes client
Once the migration is completed, you will have many local mail dbs that will need to be copy to your Domino Server. You could initiate a replication but it would be too long. So , you just need to do an OS copy of the local db to your destination server. Be careful of Technote 156522 from 1997, Duplictes of databases created at OS level do not replicate Link
How to Copy of local databases to the Domino server
- Close the Domino server which was started the initial replication (The mail server of the users).
By making a copy using the operating system, it does not change the replica ID of the bases.
- Restart the Domino server to the end of the copy.
The next 2 points are optional if there is a difference in the number of documents in the cluster following the launch of replications.
- Clear the history of replicates on these bases because of potential problems can arise when databases are copied via the operating system (See IBM Technote)
- Compare the number of documents from the 2 sides of the cluster if the history of replication is emptied.
