If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage. In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API. The scenario I'm going to use is simple - migrate single Document library with single document. The document has one taxonomy column (MyTaxonomy) and three versions: Here are the steps: Step 1: Export the document library Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4 This command will export the document library and will create the initial package. The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the
A blog about software product development, Office 365, SharePoint, Dynamics 365, ReactJS.