You can modify the source properties to map the value of that property to the defined destination properties.
- Click Copy.
- Select the action you want to perform from the Copy menu and connect to a source, and a destination.
- Click from the top right corner.
- Select the Properties tab.
- Search for the Properties in the source.
- Drag and drop them in the appropriate spot.
- Click Save
By default, all properties with the same name are automatically mapped together. To change a mapping or to create a new one, simply drag and drop properties from the list of source properties to the right pane. Make sure to place them next to the desired source property.
The source properties are all the values pulled from Google Drive and from the files themselves, while the destination properties are all the fields that are available in the destination library. The system properties are not displayed in the list of destination properties since they are not writable, they will automatically be handled depending on the options you choose for the copy.
Once saved, these mappings will be applied during the copy. The value in the source property will be copied to the destination property. A colored indicator will display whether a property is mapped or not. Red means it isn't mapped while green means it is.
Note: You can't add fields to your library from this window. It simply displays what is available in SharePoint. If you want more properties to appear in this window, you will need to add columns to your SharePoint library.
If a destination column allows for multiple values, you will be able to merge multiple columns into one during the migration. For example, two metadata values from the source file can be merged to a managed metadata column that allows multiple values in the destination library (considering the values exist in the term set used by the managed metadata column).
Key Properties appear for list item property mappings only, and can only be modified in Copy Content.
When ShareGate Desktop copies list items, there is no implicit way to know if the item that is being copied already exists in the destination of your migration, so it uses the Key Properties feature to avoid overwriting items.
As an example, take a migration where you are copying the item "Meeting 1" that was created on January 15th. If the destination also has an item called "Meeting 1" that was created on February 7th, ShareGate Desktop will not know they are different items unless "Created" was set as Key Property. By default, ShareGate Desktop determines the best key properties for your list to prevent overwrites from occurring. It is always recommended you set key properties yourself to ensure that they are defined to your preference.