Migrator for Notes to SharePoint 6.16 - User Guide

Migration Status tab

Migration Status tab

The Migration Status tab provides a number of fields useful for planning the migration project and the decisions the users make along the way. In particular, it tracks the high level decisions of whether or not to migrate a particular database and where it should migrate to. The assignments and priorities of certain migration steps may be tracked here as will as which steps have been completed.

The data collected here is primarily used for high level viewing and reporting; it does not drive actual processing. It may be set manually or, in some cases, may be set automatically based on the Class Rules of the database.

Table 32. Migration Status tab

Property	Description
Database Owner	From the dropdown list, select the user that is the database owner. If the user is not in the list, select the edit names entry to add the user.
Business Owner	From the dropdown list, select the user that is the business owner of the database. If the user is not in the list, select the edit names entry to add the user.
Analysis Priority	Enter a number that represents the analysis priority.
Responsible	From the dropdown list, select the user that is the responsible for conducting the analysis of the database. If the user is not in the list, select the edit names entry to add the user.
Locked	Select this check box to keep the manual selections from being over-ridden every time a scan is run.
Migration Priority	Enter a number that represents the migration priority.
Responsible	From the dropdown list, select the user that is the responsible for conducting the migration of the database. If the user is not in the list, select the edit names entry to add the user.
Locked	Select this check box to keep the manual selections from being over-ridden every time a scan is run.
Disposition	Dropdown list of predefined actions that you want to do with this database (for example, ‘Migrate to customized SharePoint targets’, and ‘End of life’). This list can be customized using the Console tab of the Global Options. This value can be automatically set using Classification Rules. For details, see Auto Triage tab of the Classification Rules.
Locked	Select this check box to keep the manual selection from being over-ridden every time a scan is run.
Comments	Text box
Status	These check boxes allow you to keep track of what has been finished for this database in the migration process workflow. As each task is completed, check the task’s check box. Many of these check boxes can be automatically checked as the actions are completed by the console. The Console tab of the Global Options dialog box is where you can turn on the automatic management of these statuses. • Design Analyzed • Data Analyzed • Targets Identified • Targets Provisioned • Targets Finalized • Migration Jobs Assigned • Migration Jobs Finalized • Content Migrated • Migration Verified

Migration Targets tab

Migration Targets tab

This tab collects information about where in SharePoint you plan to migrate the current Notes database. This information may be set manually or, in some cases, may be set automatically based on Classification rules. This tab allows you to have one place for specifying the target for all the migration jobs defined for this Notes database. If the Target Site is set here, it overrides any target defined in a migration job.b

NOTE: The default migration jobs for QuickPlace/Quickr in the Classification Rules in the Migration Console perform a basic quality migration of all pages within a Room to a custom list in the target SharePoint site. If you wish to migrate to SharePoint pages or have special handling blogs or wikis, you will need to customize these jobs.

Table 33. Migration Targets tab

Property	Description
Target Site	Enter the Url of the SharePoint site you intend to migrate to. This target site will override the site that may be specified in the individual migration jobs. By clicking the Select button, the site sector dialog box opens. The site selector shows existing and planned SharePoint sites and subsites in a tree. The planned sites are indicated using a green plus sign icon. To be sure this is the site you want to target, you can open the site by select the site on the tree and selecting the Go To button. To indicate new sites that you plan to provision in the future, select the parent site in the tree and then select the New Sub-Site button. This will bring up the Site Creation Options dialog box. For information on this dialog box, see Plan a new SharePoint subsite.
Target Site Information	This section shows information about the SharePoint site (if it exists) or information about the planned site if it has been defined.

ACL entry mapping and SharePoint group provisioning

Migrator for Notes to SharePoint 's security mapping options will map various access control properties of the source Notes database, QuickPlace/Quickr, or Domino.Doc cabinet to the equivalent constructs in SharePoint. An extensive set of options are available for mapping various access control properties of the source Notes database and individual Notes documents to the equivalent security constructs in SharePoint.

To enable security mapping at the Site level, check one or more of the four available Security Mapping check boxes of your Job Definition.

Table 34. ACL entry mapping

Security Mapping check boxes	Description
Map Notes Users to Domain Users	causes any Notes users listed in the source database's Access Control List to be added to the target SharePoint list or library. The Notes user names are mapped to Site Collection identities based on the rules configured in the tool's User Mapping tab options and those Users are granted access to the target SharePoint site.
Map Notes Groups to Domain Groups	causes any Notes groups listed in the source database's Access Control List to be added to the target SharePoint site. The Notes group names are added to the Site Collection as external groups and are granted access to the target SharePoint list or library. Each group name must correspond to an actual Domain group.
Expand Notes Roles to SharePoint Groups	causes a new SharePoint Site Collection Group to be created for each Role defined in the Notes database ACL
Expand Notes Groups to SharePoint Groups	allows you to take what was once a Domino Directory group (scoped to the entire Notes Domain) and convert it to a SharePoint group (scoped to just one Site Collection). As part of this conversion, the tool will query the Domino Directory for any groups listed in the ACL, extract all its members (expanding any sub-groups as needed), and add those members to the new SharePoint group.

To fine-tune you mapping options, click the Advanced Security Settings link.

Advanced security settings

The options are:

•	Advanced Options tab

•	Permission Mapping tab

•	Group Assignment tab

•

Advanced Options tab

Advanced Options tab

a	From the Advanced Options tab, provision ACL members by:

▫

adding members to an existing SharePoint group (Migrator for Notes to SharePoint will provision security by adding people to one of the predefined SharePoint groups rather than setting permission on the site members. You must fill out the mappings for various ACL levels to SharePoint Groups on the Group Assignment tab.)

▫	setting explicit SharePoint permissions directly on site members. When "Add to existing SharePoint groups" is selected (the mappings on the Permission Mapping tab will apply)

b	Provision SharePoint Groups. This is only active if the Expand Notes Roles to SharePoint Groups or Expand Notes Groups to SharePoint Groups options have been selected in the Migration Targets tab.Group name mappings:

a	To override the new SharePoint group name, click the Group name mappings button. The Security Group Mapping dialog box opens to map Notes Roles or Groups to new or existing SharePoint groups. To disable expanding a Notes Role or Group to a SharePoint group, select False for the Expand Group field.

b	Click Add to add a Notes role or group to an existing SharePoint Group. If you are mapping to a SharePoint group that is not in this mapping table, a new SharePoint Group with the old Notes role or group name is created.

c	To allow only standard SharePoint groups, select the Only allows standard SharePoint Groups check box.

d

Select Prevent creation of new SharePoint Groups check box if you want to limit the number of new groups that are created as a side effect of the user mapping process. If you leave this clear, the "Expand Notes Roles to SharePoint Groups" and "Expand Notes Groups to SharePoint Groups" functions will create groups with the same name that was used in Notes (with the optional prefix). But if you check this option, only the names listed in the mapping table will be used.

e

Enter a value for Prefix the names of groups created for roles with: the Expand Notes Roles to SharePoint Groups option causes a new SharePoint Site Collection Group to be created for each Role defined in the Notes database ACL. To avoid possible collisions with existing SharePoint Group names, you can enter a prefix that will automatically be appended to the beginning of each group name.

c	Provision document level security. The Provision Document Level Security section is only active if the Map Reader/Author fields option is selected in the migration job’s Advanced tab.

▫	Select the Add new site collection members if needed to access documents radio button is selected by default. This ensures that a reader/author that has no access to the site is still given “Limited Access” permissions at the list and site level so that they have access to the document.

▫	Select the Only grant access to documents if member already has access to site collection radio button so the readers/authors with no permissions at the site level will not be given “Limited Access”. They will not be able to access the document.

 

NOTE: All of the security options have the possible side effect that SharePoint permission inheritance links may be broken. This means that future changes to site level permissions would not "trickle down" to the list or library and future changes to list or library level permissions would not "trickle down" to all the individual documents.

The Provision Document Level Security section is only applicable to job specific security settings. This dialog is inactive if opened from the Migration Targets tab of the Database Properties sheet.

Permission Mapping tab

Permission Mapping tab

If either the Map Notes Users to Domain Users or Map Notes Groups to Domain Groups options are checked in the Migration Targets tab, the Permission Mapping options will determine how the Notes database access levels (and related flags) are translated into SharePoint permission levels. The Map ACL Levels to SharePoint Permissions section allows you to assign a SharePoint permission level to each of the possible Notes access levels (Manager, Designer, Editor, Author and Reader). Similarly, the ACL Flag Mapping section allows you to assign a SharePoint permission level to certain access flags (Can Create, Can Delete) in each Notes ACL entry.

While the default mappings provided by Migrator for Notes to SharePoint are good choices in most cases, there is not a one-to-one mapping between Notes access levels and SharePoint permission levels so you may need to adjust the mappings as appropriate to your application. If your SharePoint site defines custom permission levels, you can uncheck the Only allow standard permission levels option and select the custom permission levels that are available in your site.

NOTE: You should be aware that Notes defines an access level called "Author" which implies that a user should only be able to access his or her own documents. A similar concept is available in SharePoint, but it is expressed as a global setting for an entire list or library. Migrator for Notes to SharePoint does not attempt to set this, but you should consider doing this manually for certain applications.

The SharePoint permission level that is selected in the Advanced Security Mapping dialog must match the name of a permission level on the target SharePoint site. This is true even for the standard SharePoint permission levels such as "Full Control". In order for the ACL Level mapping to succeed, there must be a SharePoint permission level on the target site named "Full Control".

This can present a problem when trying to map ACL Levels to a SharePoint site that is not using English. For example, in a French SharePoint site, the name of the "Full Control" permission level is "Contrôle total".

Unchecking the Only allow standard permission levels option will also retrieve the names of the permission levels from the target SharePoint site. In this case, however, the selections will not be restricted to "Full Control" and "Design". The names will be in the language of the target SharePoint site. When this check box is unchecked, the text in the combo boxes can be edited. This allows you to fill in permission levels in case you cannot access the SharePoint site.

Checking the Only allow standard permission levels option again will restore the standard permission level selections to the combo boxes, and they will no longer be editable. If you had entered a non-standard name in the combo box, it will be replaced with the appropriate default for that combo box.

Clicking the Load from SharePoint Site/Refresh link in the dialog retrieves the names of the permission levels from the target SharePoint site thus bringing in the appropriate permission level name. When this dialog box is first opened, a target SharePoint site has not been specified, so Migrator for Notes to SharePoint won't know where to retrieve the permission level values from. The Refresh link will initially be replaced with a Load from SharePoint site link. Clicking on this link will bring up a site picker that will allow you to choose a SharePoint site from which to load the permission level values. Once you have loaded the permission levels from a site, the link will change to Refresh.