Chat now with support
Chat with Support

Migrator for Notes to SharePoint 7.2 - 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

Site Columns tab

This tab allows you to define the columns for the Content Type. Any site columns that do not already exist in the target site will be created during the provisioning of the Content Type. Then the new or existing site columns will be added to the target content type.

If a Content Type column already exists with the same name and has the same properties, Migrator for Notes to SharePoint will use it rather than creating a new one.

If a Content Type column already exists with the same name and has minor differences in properties, Migrator for Notes to SharePoint will use it and a warning will be issued.

If a Content Type column already exists with the same name but the Type is different, an exception will be issued.

If a Content Type column does not exist, but a Site column with the same name, type and properties already exists, Migrator for Notes to SharePoint will add it to the Content Type definition.

If the column has Is Title Field set to true, the current Title column will be renamed in the Content Type definition.

If a Site column already exists on the target site that has the same name but the Type is different, Migrator for Notes to SharePoint will create a new Site column and add it to the Content Type definition.

Otherwise a new Site column will be created and it will be added to the Content Type definition as well.

Migration Jobs

This tab contains the list of all the migration jobs defined for this database. From here you can edit or delete an existing job, create a new job, import a job from a file or export a job to a file. You can run one or all of the listed jobs.

To edit an existing job
1
Select the job in the list.
2
Click Edit.
This will open the job definition in the Job Designer dialog box.
To create a job
•
Click New.
An empty Job Designer dialog box opens.
To give your job an easily identifiable name, select the Properties button on the Job Designer. You can define a Job Name and Description which will then be displayed in the Migration Jobs tab.

For detailed information on defining a migration job using the Job Designer, see “Migrator for Notes to SharePoint Designer” on page 92.

For detailed information on running a migration job, see “Migration Jobs” on page 63.

Migration History

This tab contains the history of all of the migration jobs run for this database. It lists out each job with Date and Time the job was run, the status of the job and the description of the job. Double Clicking a job will open the log file for the job. This information is also viewable in the Task history node.

To migrate the failed items for a job, right click on the job entry, and select Migrated Failed Items. For more information, see Migrating failed items.

Applications

There are cases where one or more Notes databases can be grouped together as a single "application". This is particularly useful when treating multiple databases as a single application is important: namely QuickPlace, Quickr, and Domino.Doc. With these environments, recognizing the patterns of application organization can drive automatic assignment of migration jobs or automation of actual migration jobs.

Applications are "discovered" by running the Discover Quickr Applications, Discover QuickPlace Applications, and Discover Domino.Doc Applications actions. Once these applications are discovered, you can expand the Applications node and drill-down into the Quickr and QuickPlace server/place/room or Domino.Doc server/library/cabinet application hierarchies.

* 
NOTE: This hierarchy of application nodes can be used to automatically generate a similar hierarchy of SharePoint sites. To accomplish this, see the “Create subsite for every child application” option in the Auto Target tab of the Classification Rules.

The nodes and sub-nodes displayed here are really just database nodes (the same ones shown in the databases views) except that they are displayed according to the rules of the application abstraction rather than as "plain" databases. To view information about the underlying databases, select the Properties action.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating