Developers are identities, not rows

Edge estates often include company developers who were created through built-in portals, manual onboarding, or historical partner programs. In Apigee X, the target identity approach should be deliberate. Some users may belong in an external identity provider, some should be archived, and some should be re-invited through a governed onboarding workflow.

Migration decisions

Do not migrate every developer automatically. Review last login, app ownership, company association, email validity, role, and support relevance. Where a user maps to an external identity provider, establish federation and lifecycle ownership before go-live.

Governance checklist

  • Validate email domains and partner ownership.
  • Map users to companies and apps before target creation.
  • Move authentication to the external provider where possible.
  • Keep an exception register for users requiring manual handling.

Identity cleanup during migration reduces operational ambiguity for years after cutover.