Migrate from classic Dev Portal (v2) to the new Dev Portal (v3)

Uses: Dev Portal
Related Documentation
Incompatible with
on-prem

With the GA release of the new Dev Portal (v3) in June 2025, you can migrate from classic Dev Portals (v2) to the new Dev Portal.

Dev Portal v3 provides additional features such as a streamlined API creation and publishing process and enhanced Dev Portal customization with Markdown components and snippets.

Migrate to Dev Portal v3

To migrate from Dev Portal classic (v2) to the new Dev Portal (v3), do the following:

  1. For Kong-hosted classic Dev Portals, do the following:
    1. Create a new v3 Dev Portal in Konnect
    2. Republish your API catalog either via the UI or the v3 API
  2. If you are using an IdP for developer credentials, update your IdP with the new Dev Portal domain for the redirect URIs. This will maintain developer logins.
  3. If you are using Konnect developer logins, like basic auth, developers will need to register at the new v3 Dev Portal and regenerate their API credentials.
  4. If you’re using a custom domain for your Dev Portal, do the following:
    1. Decrease your domain TTL in advance to reduce the transition time. Some minimal downtime will be required to move custom domains.
    2. Delete your custom domain from v2 Dev Portal.
    3. Add the custom domain to the v3 Dev Portal.
  5. If you’ve enabled developer RBAC, manually assign developers to teams and roles by navigating to your v3 Dev Portal in Konnect, clicking Access and approvals in the sidebar, and click the Teams tab.

    For self-hosted Dev Portals, contact Kong support for help.

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!