List Migration
Lotus Notes forms are migrated to SharePoint List using Quest tool and the procedure is explained here.
Step 1
Select the Lotus Notes Database from the server or Local Computer.
Step 2
After clicking the Select Tab, the following popup window will open and here can select the Notes DB based on the location. If it is in the Local Machine, expand the local section or if it is in the server select the server section, or select the button and enter the server path.
Source Data Definition
In this source data definition section, the user can select the Notes data record selection based on:
- Form, View/Folder.
- Records selecting based on Full text search.
- Formula language (this section is especially used to migrate the specific Notes record so the user can use this formula type).
DATA Fields Tab
The data fields tab is very important for migration, here only the user should decide the Notes (source) fields to migrate to SharePoint (the target).
And in this section the user can select the Notes fields from the sample items or database items using the data query option.
If the user needs a new column then you can add the new Notes column here. And the user can change the column type in this section.
After the record selection tab preview tab is there, here check the selected field's value.
Using the The Preview tab we can filter the view and can view the records in Rich Text and Plain Text mode.
We have the following three important sections available:
- Column type: In this section we can decide the column type, like item, rich text, number, embedded object, attachment, render and so on.
- Option Type: in this section is Alias name, an option and main type
- Return type: here we can change the return type like:
• string
• date
• Binary
• Html
• string
• User
Preview tab
SharePoint Target selection
Step 1
Under the SharePoint tab, the Site URL select button is available and the user can select the previous URL that one ca use or can enter the SharePoint URL and list name.
Target data migration
Under the target data migration section click the create button. The following tab sections are available:
- List Definition
- Data Fields
- Advanced
List Definition: Under the List Definition section List Template is available. Here you can change the list type.
Other List
Calendar
Documents
Discussion Board
And Content type migration
Target Data Fields
Here the user should decide the SharePoint field names, we have three methods to create SharePoint fields.
- Load From SharePoint List: some case application is already created in SharePoint and fields are avaible in SharePoint so the user can use those fields to map here, if you click the load from the SharePoint list then the available fields are created in the left section.
- Load from source fields: some cases if you want to reuse the Notes fields then the user clicks the button and the source fields will be populated here.
- Add: Some case the user wants to create a new field in SharePoint the this can be used.
And if created or loaded of the target fields in the left section then user can change the field behavior as in the following:
- Target Type
- Mandatory Fields
- Lookup
- Default value mention
- Add to views
- Auto map section
Advanced Tab
MAP Data
This section is the main one for the migration, here we need to map the fields Lotus Notes to SharePoint. In other words:
Here, the auto map button is available and this section will do the mapping from Notes to SharePoint.
The user does not satisfy those auto map concepts manually to do the mapping, for that purpose the add button is available and can map the field's user expectations.
Advanced
The Advanced tab consists of the following sections:
- user mapping
- security mapping
- Doc Links
User Mapping
User mapping is a very important chapter when migrating Lotus Notes applications to SharePoint.
Before you can configure the User Mapping in NMSP, you need to generate a user Mapping file. You can choose to generate the user Mapping file manually or use the new NMSP UserMappingUtility.
How to configure User Mapping
To configure the User / Group Mapping in Quest, start the Quest tool and open the "Advanced Configuration Options" and go to the Tab "User Mapping".
Threat input as login name:
- This option will use the Notes Username and use it as the login name for SharePoint the for Domino Directory lookup
- The Notes Migrator will look up the User / Group Name in the Domino Directory and pass the lookup value as the login credentials to SharePoint
Notes Database lookup
- The Notes Migrator will lookup User / Group values in a Notes database (like "Names.nsf") and pass the lookup value as login credentials to SharePoint.
ADSI/LDAP lookup
- Notes Migrator will run an ADSI/LDAP query against your LDAP directory. You can specify which values should be looked up in your LDAP directory and where.
Text File lookup
- The Notes Migrator will lookup User / Group information based on a text file. The text file includes a mapping of the Lotus Notes user / group with the corresponding SharePoint value.
Configure User/Group Mapping in questThe "Text File" option is easy to configure and easy to use. Select XML as the format for the mapping file.
To configure the Group mapping function, you need to go to the "Group Mapping" tab in the Quest tool and do the same configuration as for the User Mapping.
After clicking on the "Test User Mapping" link, a new window will open where you can enter a Lotus Notes Username for testing.
By clicking on "Lookup", Quest will look up the name "" in the User Mapping XML file and display the lookup result.
Validate User / Group Name in SharePoint
You can validate the User / Group name in SharePoint by clicking on "Validate in SharePoint".
A new window will open and you can select some settings for the validation in SharePoint.
You can choose the SharePoint environment / site where you want to validate the User / Group name. By clicking on "Test", the User / Group name will be passed to the SharePoint site, SharePoint will look up the User details using the "After Lookup Value".
Once the user has completed the preceding, all the procedure next one is run the migration job.
Link Tracking
Link Tracking can be turned on and configured from this tab. If this is turned on, the document link tracking will be done by the Quest tool during a migration.
To enable client-side document link tracking, select the Enable the Quest Link Tracking Service checkbox.
The following Link Tracking Settings is available in the quest:
- Database Server: The SQL Server instance that contains the Link Tracking database. Leave this value blank to use the default instance for the server.
- Database Name: The SQL Server name for the Link Tracking database.
- Authentication: The credentials that the client should use when accessing the Link Tracking database. This can be your Window's account, a different user's Window's account, or your SQL Server login.
- Test Connection: Click on this button to verify your settings.
- Use default Redirector URL: Link Tracking for SharePoint migrations will use the default redirector page.
- User Defined Redirection URL: This option will allow you to define your own user defined redirection URLs if you want the redirection to be handled in some other way.
Lotus Notes To Sharepoint Migration
Be sure to use the same values for the Link Tracking database since those that were entered for Link Tracking in the NMSP Services configuration page. These values were initially set by the Notes Migrator for SharePoint Services installer but may have been overridden in the Services configuration page.
Log File
The General tab of the Event Log window displays the basic migration job information. To display more information, click the arrows on the upper right side of the tab. Click the arrows again.
To export the log to an XML file, click Export Log.
To open the target SharePoint list, click Go to List.