User and Group mapping is mandatory step, it allows the conversion of User and Group data to something suitable in the target system so that if User “ShelleyP” or Group ‘Senior Leadership’ appears on the source item then replace this with a suitable user or group as specified in the mapping e.g. Percy.Shelley@acme.com.   The result of the mapping will affect the  CreatedBy/ModifiedBy fields in the target.  Any user or groups not mapped will cause the relevant items to fail migration unless the ‘Default’ feature is used, see below for more details.

Permission mapping is an optional step.  It’s the process of mapping a type of access right on the source to a suitable access right on the target. For example, a user may have read access on a folder in the source and this needs to be mapped to the equivalent Read access in the target.  This information is used with the user/group mapping so that User “ShelleyP” who has “Read” access on the source is represented as Percy.Shelley@acme.com with “Read” access for the migrated item.

NOTE: If no permission mapping is specified then no specific permissions are applied to migrated items, and so they would inherit their access permissions from the target.

For each of the entities, there is the option to download the relevant data to .CSV file were it should then be modified (preferably in Excel) to add mapping information and then the updated file can be imported back into PMA.

NOTE: Permission mapping capabilities are limited when migrating to M-Files or File System.  Contact technical support for more information.