Companies carry business context

In Apigee Edge, companies often represent partner organizations, internal business units, or commercial groupings. Their apps and developers form a consumer identity graph that operations teams depend on during incident response, onboarding, audits, and contract reviews. Losing that context during migration creates long-term support risk.

Migration concerns

Company records should be reconciled before migration. Duplicate companies, inactive partners, inconsistent naming, missing contacts, and orphaned apps should be addressed through business decisions. Company developers should be checked for active association and mapped to the intended identity model in Apigee X.

Best practices

  • Create a company-to-owner register before migration.
  • Preserve company app relationships and consumer metadata.
  • Retire inactive company records only after business confirmation.
  • Use migration logs that can be audited after go-live.

Strong company migration preserves accountability, not just records.