NM: Need explanation of the migration log category called "Other" and "Skipped" (4316740)

Questions regarding the "Other" and "Skipped" categories in the migration log file.  Responses are in blue.

1.      Is it correct to state that only duplicates, canceled meetings, and missing/corrupt data are not migrated and fall within the "skipped" category. If not, what else would fall into this category?

Skipped items are logged with the reason the document it being skipped.  Duplicates, Canceled Meetings, Documents in a Skipped folder, and Documents missing key fields may all be skipped. 

2.      Is it correct that Calendar related items such as acknowledgements, reschedules, declines, etc. are migrated as a single calendar entry? If not, please explain.

Yes, calendar related items are processed during the migration and applied to the single actual calendar message. For example, a repeating meeting is received, accepted, and an update arrives changing the location of all occurrences.  Then the invitee is migrated.  The response (accept) and the location update are “rolled up” to the calendar event when the “main” event is migrated.  

3.      Is it correct that the "Other" documents are duplicates, canceled meetings, acknowledgements, declines, reoccurring meetings, canceled meetings, and conversion errors? If not, please elaborate.

In the Per Folder Count Summary, the “Other” field is a calculated value of the total items in the folder minus the migrated and skipped items.  All documents in the folder may not be “valid” items to be migrated – calendar updates, or responses are examples of items that may be present in a folder but not be migrated nor skipped, so would be counted as “other”.

4.      Can you please provide additional information on what conversion errors are? Why do some items fail to migrate? What, besides corrupt data, can cause an item to not migrate? 

Certain key fields must present in order to properly migrate an item. The data may not really be “corrupt” in that Notes may be able to display them, but missing fields would cause the migration to not be able to process the items.  Examples may be missing parent IDs, missing repeat fields on events marked as repeating, etc.  Often field problems occur when the Notes database has been upgraded thru several revisions of Notes/Domino or in mail items processed thru or from non-Notes systems.

5.      Specifically, what categories of items are counted as “Other” and therefore not migrated?

See 3A – the other count is calculated, not accumulated during processing.

6.      Why are the "other" items essentially counted twice in the case of duplicates, canceled meetings, acknowledgements, declines, and canceled meetings, when these are already counted as skipped items?

Since message can appear in multiple folders, they are included in the total document count for the folder, so any item not migrated nor skipped for a documented reason is accounted for in the other (calculated) count.  This shows that all items in the folder were evaluated. The total of all documents in all folders will not match the total documents in the database.

7.      Why are the “Other” counts so much higher for the Unfiled folder? What is being skipped and why?

The unfiled folder is actually scanning All Documents in the database to pick up any documents not part of another folder or have not been processed. Based on if the message was migrated, the message type, flags within the message, or other key data (such as parent ID, existence of repeat fields, etc) we still may not be able to process these items or they do not need further evaluation/processing. 

8.      Why do I consistently see all of the items in the Junk Email folder not being migrated? While not all users have items in Junk mail, those that do have them not migrate? Is there a known limitation regarding this? We are not filtering the migrations in any way, except by excluding the “Trash” folder.

The Junk Mail folder should be migrated.  Folders named "($JunkMail)" or "Junk Mail” are included in the processed folders.  If the Notes mailbox was created in an older versions (pre R6), the junk folder name may be different or non-existent.  Verbose log files and/or sample data may identify the cause.