Map Property on a Site Object Migration
- Content types
- Metadata: ex. set mapped value or default to fill in empty fields
- Page layouts
- Etc.
Stephanie Pelland
shared this idea
3 comments
-
Victor
commented
Some users would like to have more flexibility with their content types when doing full site migrations. In a lot of cases, have an option to replace content types at the destination on a site level would be very useful for those using migration as an excuse to clean up their sites
-
Fred Larssen
commented
The lack of this possibility is what prevented us from using Sharegate as the only tool for migration. With custom content types containing custom columns of custom field types it was impossible to copy site objects including content. A possibility to specify a global property template with content type mapping and metadata settings would have solved this. Objects related to the source content types could then be skipped as they are not needed at the destination. The workaround is to clean up document libraries after the copy of sites, and then copy the content once more with mapping. A time consuming process when there are many document libraries.
-
It would be great if you could use some form of data mapping in site-level migrations to correct data quality issues that might crop up – eg. where required cells contain no data - > map a value, or where lookups are broken -> copy a blank cell.
