Migrating Groups
During the ingestion phase of the migration, groups are migrated if they are required to satisfy the ACLs or CUG policies on the migrated content. See Group Migration for more details.
Migrated groups (those not created by Assets Collection or Private Folder creation — see Collections and Private Folders below) are configured as IMS groups. What this means is that any group of the same name created in IMS (via the Admin Console, for instance) will be linked to the group in AEM, and users which are members of the IMS group will become members of the group in AEM as well. In order for this linking to happen, the group must also be created in IMS first. Use the Admin Console to create groups, individually or in bulk, in your AEM instance, as described in Managing Principals in IMS with the Admin Console.
Use the AEM Security UI to assign IMS groups to local AEM groups. To do this, go to the Tools page in AEM, click on Security, and choose Groups.
IMS Users
Since users are not migrated, they must be created in IMS so that they can be used in AEM. There are several ways to achieve this, but it is important that the users created be assigned to the correct IMS groups in order for the users to have the same access to the content they had in the previous AEM system. One of the tools that can be used for this is the bulk upload functionality in the Admin Console; use the bulk uploader to upload users along with groups they must be members of. Before doing this the groups must first be created in IMS, as described above.
To know which groups each user should belong to, you can make use of the User Report (see Group Migration). This report lists the groups each user should be a member of, and this list will normally be included in the Bulk User input file for use with the Admin Console bulk upload functionality.