Discovery prevents cutover drama

The most expensive migration problems are rarely caused by proxy bundles alone. They come from assets nobody fully owns: company apps used by active partners, app credentials created for emergency releases, API products with outdated approval settings, and developers tied to an Edge portal login that will not exist in Apigee X. Discovery must build a source of truth across runtime, developer ecosystem, and governance data.

What to inventory

At minimum, capture organizations, environments, proxies, shared flows, KVMs, target servers, API products, companies, company developers, company apps, developer apps, credentials, product associations, app status, credential status, and OAuth-related policies. The inventory should include business owner, support owner, last traffic seen, consumer criticality, and migration disposition.

Decision outputs

  • Move as-is for active, governed assets.
  • Move with remediation for assets that are active but non-compliant.
  • Retire stale apps and credentials with no recent traffic.
  • Hold migration when ownership or legal basis is unclear.

A clean migration begins when the inventory becomes a decision register, not just a spreadsheet.