How to use the console views and reporting features in Migrator for Notes to SharePoint

Hi. My name is Randy Rempel. And I'm a senior product manager. Today, I'm going to briefly review the console views and reports in Migrator for Notes to SharePoint. The console has many features and functions available to you. The left pane displays the notes and subnotes available to display the functionality available or the various types of information about the environment that can be displayed. For example, it can display databases by disposition, by server, by technical class, by business class, and by notes templates. All of the views start with the same columns. But you can move the columns to change the order. And you can resize the columns as needed. And you can click on the column header to sort the view. You can also add more columns to views. I just added two columns, moved them, and quickly sorted on one of the columns. Now I can see which databases have the most forms and views. I like to see information about design elements. It helps me when I set the technical class value. Now I added grid lines to the views. Sometimes, this makes it easier to read the data in the views. Not only can you customize existing views, you can also create new custom views. This is useful when you want to create a new view that shows columns that do not appear in one of the existing views. Now you can see that you have options available for creating a new custom view. You can set the views title, view scope, and the filters. The new view appears under Custom Views. It will start with the same columns that appeared in the original view. You can also delete the view. Now let's take a quick look at reporting. I have a blog post that reviews a few reports that you're welcome to read. I want to focus on database usage here. The database usage pie chart will give you a summary of how many databases were last used in specific time periods. This report does filter usernames based on the exclusion list. However, this report does not tell you how much each database was used within any time period. The User Activity by Database Report provides more usage detail on Notes databases. Now you can see when a database was last used and details on the number of users, writes, and uses. This report excludes all users in the exclusion list. Here, I can see that the employee handbook has 104 users, but was last used in 2008. The User Activity by Database All Users Report provides the same details, but does not exclude any users. The Database Class Report by Server shows data in a different way. Here, we can see how many databases have a particular technical class assigned. This particular report shows that about half the databases have the personal mail file, or domino administration technical classes, assigned. Neither of these will likely be migrated using the MNSP tool I recommend that you set the disposition value in databases so that you know which databases will be migrated. For this database, I'm setting the disposition to end of life. This database will not be migrated to SharePoint or any other application platform. Now you can see that the database appears in the end of life disposition view. I recommend that you set the technical class, business class, and disposition on all Notes databases, even if that means using values like Not Applicable.