Do not migrate names blindly

Edge organizations and environments often reflect historical delivery boundaries. Apigee X introduces different design choices around environment groups, projects, networking, regions, and runtime access. A direct name-for-name migration can preserve complexity that the migration should remove.

Architecture questions

Before mapping assets, decide how many runtime environments are actually needed, which teams own them, how ingress should be exposed, which regions matter for resilience, and how non-production promotion should work. Environment groups should align to routing and exposure patterns, not departmental preferences.

Recommended approach

  • Group APIs by exposure model and operational criticality.
  • Map environments to lifecycle stages with clear promotion rules.
  • Use naming standards that expose business context and risk tier.
  • Define who can deploy, approve, and operate each environment.

The best Apigee X topology is the one that makes daily operations clearer after migration.