My team is adopting the Universal Migration Tool (https://github.com/Kentico/xperience-by-kentico-universal-migration-tool) for the first time as part of a new project migrating from a non‑Kentico platform.
The source system has an established concept similar to reusable schemas, and we are aiming to preserve this structural approach in the new Xperience by Kentico solution.
Our initial plan was to fully configure the migration to transform content types while maintaining their relationships with reusable schemas. However, after reviewing the Universal Migration Tool, I haven’t been able to find any references to built‑in support for reusable schemas. This led me to wonder whether others have encountered this scenario and, if so, how they have approached defining reusable schemas as part of the import process.
While our preference would be to define these automatically during migration, we do have a fallback option: omitting content type definitions from the automated migration, creating and configuring the reusable schemas manually upfront, and then limiting the migration tool to handling content only.
So, in short: has anyone successfully automated reusable schema migration using the Universal Migration Tool without extending the toolkit itself or introducing custom code to create and assign schemas?