When migrating local files, source properties can be mapped with destination fields.
- To set up those mappings, click on Map properties (the Property mappings window can also be opened from the property template).
- In the Property mappings window, the list of source properties is displayed on the left and mapped properties are displayed on the right.
The source properties are all the values pulled from the file system 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.
By default, all properties with the same name are automatically mapped. 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 accordingly next to the desired destination properties.
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 that 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 Enable Document Properties Extraction is selected.
- You can click on "Add from PDF or Office file". Office must be installed for extracting properties from an Office file.
- You will be prompted to select a sample PDF or Office file.
- Once you select the file, all the properties will be extracted from the file and will be added to the list of source properties. For example, if your sample PDF file contains properties called Category, Company and Keywords, these three properties will be added to the list of source properties. You will then be able to map some or all of them to destination properties.
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).
From the Property Template
The Property mappings window can also be opened from the template selection window or from the property template window.