In this example use case, there is no domain local groups and therefore the migration option for local groups was not enabled. If there were domain local groups as well, you would have to enable the migration of local groups as well.
You could as well use additional "User & Group Migration" type of jobs, if you would like to separate the account from the resource migration. In this case you would not need to enable the account migration options in the "User and Group Filter" page of the data migration job.
If migrating from a regular file server running on a member-server to a cluster and there are local groups (or local users) on the member server, please make sure to enable the "Create users & groups in destination domain" option to convert those to domain groups and users, because Windows clusters do not support those.
It is important that the clusters file server resource name is specified in the copy job and not the clusters node names. The CopyRight2 licenses on the other hand, have to be assigned to the cluster nodes NetBIOS names though. It is recommended that you assign a license to each cluster node, but it works with a single licensed node as well, as long as you ensure that this node owns the file server resource you want to migrate from or to.
The settings used assume that no users are working while the migration takes place. If you want to use an approach with multiple passes (pre-copy/final copy) you additionally have to enable either the "Ignore errors resulting from locked files" ("Error Processing" page) option for the pre-copy pass(es) to prevent errors from occuring because of locked files.