We have used the Configuration Migration Tool (CMT) in the past, and while it successfully establishes all underlying relationships, it migrates all components (including all profiles, emission calculations, etc.) in a single deployment. This approach does not align with our requirement, as we prefer not to migrate all components each time (iterative movements) between environments.

What we are looking for is the ability to migrate a specific profile created in a lower environment, rather than transferring all profiles along with their underlying relationships.