Mapping sensitivity labels ensures content retains the appropriate protection and compliance settings during migration.
ShareGate Migrate helps maintain label integrity and compliance across environments.
How-to
Select Copy from the menu.
Select the type of migration you want to perform.
Click Options on the top right.
Select the Sensitivity labels tab.
Activate Map source labels to destination labels for Structure-level or Content-level labeling.
Click Mapping.
Click on the Run auto-mapping icon to automatically match your labels.
This can be undone with the Clear mapping icon.
Use the Search destination labels field to find destination sensitivity labels.
Drag and drop them to map your source labels.
Click Save.
Default mapping behaviors
You can use the Run auto-mapping button to match labels.
Auto-mapping is based only on the label name. ShareGate matches the parent label name (if available) and the label name at the destination. The match must be exact.
You can manually edit these mappings and map unmatched labels.
All available destination labels are listed. They are limited to labels published for the migrating user.
Unmapped source labels are ignored. If no destination label is mapped to a source label, the destination object or file will have no sensitivity label applied unless Microsoft automatically assigns one, like you'd see with a default library label.
For sensitivity labels on files:
If the source label is ignored, the file is migrated with its original sensitivity labels intact.
If a label is applied via mapping, it is added to any existing labels on the file.
In same-tenant migrations, no change occurs if the same label is mapped since the label is already on the file. Otherwise, the new label replaces the existing one, as a file can only have one sensitivity label per tenant.
Considerations
Be aware of the following when configuring or reviewing sensitivity label mappings:
Auto-mapping does not match with label properties other than name. The app does not consider ID, color, description, or priority for the auto-mapping.
Label visibility is user-specific. Labels that are not published to the migrating user will not appear.
Tooltips provide key details. Hovering over a label in the UI reveals the label’s name, encryption status, and scope to assist with validation.
Library default label enforcement. Files without a sensitivity label can automatically inherit the library’s default label at the destination. SharePoint enforces this behavior and cannot be bypassed by ShareGate Migrate.
Document encryption. For files, encryption is only removed when applying another label with encryption. If a label with encryption is mapped to a label without encryption, the new label will not be applied for security reasons; in such cases, the modification must be made manually.