Today's enterprises are having to manage more and more APIs, Services, Events, Messages all in different developer environments, pipelines, and runtimes. Without one view of all your assets, you have no way of understanding what's good and well governed, what's not, what's being used and by who, what's not being used or not used effectively, and where you have duplication. The solution is creating a catalog where you can import and harvest integration environments from pipelines and runtimes to create one unified view of everything you have. In this paper we detail the current challenges, the criteria for a catalog that provides a reportable baseline, and 5 proven steps on how to get there.