Chat now with support
Chat with Support

Migrator for Notes to SharePoint 6.15 - User Guide

Migrator for Notes to SharePoint Migrator for Notes to SharePoint Console
Overview Console configuration using the setup wizard Advanced configuration options Database discovery QuickPlace/Quickr discovery Domino.Doc discovery Discover directory entries Import database records Notes databases Applications Classification Rules Classification Rule Properties SharePoint Targets Scheduled tasks Reports Task history Link Analyzer/Updater/Finalizer License
Migrator for Notes to SharePoint Designer Migration jobs Appendix: Reference information

Create technical class

This action will automatically create a Technical Class using the Notes database or template that you have highlighted. The highlighted Notes database or template will be assigned as the Reference Database for the new Technical Class. You can use this to quickly create a Class that uses the database as the Reference Database and is preconfigured for Best Fit testing. If it is a template, the class rule will recognize it that way.

Select Create Technical Class.

Export database records

This action will export all of the database properties to an XML file. This file may be analyzed by or imported into external tools, but cannot be imported back into the Console.

Export data analysis details

Right-click a database and select Export Data Analysis Details to create the following .csv files in a folder named after the database name:

The content of these files is taken from fields displayed in the Data Analysis tab of the Database Properties. See the last four table entries in the Data Analysis tab.

You can select multiple databases. A folder is created for each database.

If no data applies to a file, the file is not created. If no files are created, the folder is not created.

Extract database users

This tool will export database users to an XML file. You can select one or more databases in any database view in the Migration Console and then extract all the user names contained in those databases. This tool is useful for simply gaining an understanding of the users involved in a group of Notes applications, but the primary purpose of the tool is ultimately to generate a user mapping file that Migrator for Notes to SharePoint can use at migration time.

Select Analyze Databases. Click OK, then Close.
Select Export Database Users.

The sources of the user names are listed in the view columns. You can filter this list by using the filter options at the top of the dialog box. Filter by source allows you to filter the sources shown to only list users that came from certain sources. The list will automatically refresh when a filter option is changed.

The type of user name (Person, Group, Unspecified) is also shown and you can filter based type. Note that Unspecified users may become specified as you perform certain operations such as group expansion or imports. Finally, you can manually set the user type by using the combo boxes in the view.

You can also filter by the Notes domain. This is a simple text match against the last part of the abbreviated name, so either "Westford/IBM" or just "IBM" would select "Kevin MacDonald/Westford/IBM". If is common to want to select all the users plus all the groups, which the "No domain" check box allows you to do.

Users may also be added to the list by expanding Domino groups. If a group is listed in a database, it is sometimes useful to be able to find all the members of the group. If you press the Expand Groups button, Migrator for Notes to SharePoint will contact the configured Group Resolution Server (from Advanced configuration options ) and look up every Group and Unspecified entry (in case it really is a group). Any new members will be added to the list and indicated as "ACL via Group".

Users may also be added to the list by importing existing Migrator for Notes to SharePoint User Mapping XML files.

To remove users from the list, you can select one or more rows and click Remove.

The last column in the view is the SharePoint names column. You can set these names automatically using the Import function, using the Set SharePoint Names function, or by typing them in manually.

The Import process loads in users from existing XML User Mapping files and sets the Imported column. Imported data is merged with existing data but if a SharePoint name is specified in the imported file, it will overwrite the existing name every time.

The Set SharePoint Names function gives you several ways to automatically assign your SharePoint names.

Lookup value in Domino Directory - use any field in the user's Person document on the Domino directory as the new SharePoint name
Set Default using format string - Generate a new SharePoint name by substituting the various parts of the Notes name.
Set Default using the Notes common name - Use the simple common name as the SharePoint name
Click Export to generate a User Mapping file (either in an XML or comma delimited format).
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating