Rename or reorganize 'Catalog' the app with 'Catalog' within Migrate
Having ‘Catalog’ in two places has been difficult for my customer users to comprehend. Catalog the tile/app at ADMM > Home versus Catalog the drop down item within Migrate. Can this be renamed somehow?
It’s also been challenging to explain the process of ingesting a new table to be used in Migrate - having to ingest the metadata into Catalog, and then having to import the metadata manually again in Dataset Design isn’t intuitive. I’m sure there was a reason for this but it does seem redundant?
Log in to comment and vote
Comments1
John Munkberg
Oct 21, 2025
This is an artifact related to the Origin of SKP. We are still on our “Journey to the Cloud” where we continue to integrate all of the modules into a single, seamless, multi-tenant cloud application.
Today - Migrate is still a separate code base, and it’s catalog objects “Should” exist in the SKT Catalog. But until we complete the integration, they will co-exist.
Datastores, for example, were changed to close the gap between Systems and Datasources. Eventually the migrate datasources will go away - but there is still a LOT of migrate specific code which requires we keep the migrate datasources where it is.
Rest assured, we will continue to absorb and merge and eventually unify the whole SKP. But that is a multi-year journey.