Changes Are Coming to the Okta Developer Edition Organizations

As part of Okta’s Secure Identity Commitment (OSIC) to lead the industry in the fight against identity attacks, we are making changes to improve our architecture related to developer organizations.

On May 22, 2025, our new Integrator Free Plan will become the default organization type when you sign up on developer.okta.com. If you are actively using an Okta Developer Edition org, please create an Integrator organization and migrate to it. The Okta Developer Edition terms of service will also be updated to clarify: neither your old Developer Edition organization nor your new Integrator organization is meant for production use cases.

New Okta developer organization types tailored for you

We’ve redesigned our developer orgs to better fit how you build. Whether you’re testing app integrations, validating identity flows, or preparing for OIN submission, the new Integrator Free Plan is purpose-built for iterative development—not production deployment.

This new structure reflects real-world developer needs:

• A clean, focused environment optimized for building and validating integrations
• Terms that match typical pre-production use cases
• Streamlined signup and org management aligned with how developers work today

By moving to an Integrator organization, you’ll get an environment that’s aligned with modern dev workflows—simpler, more relevant, and built to support how you build.

Integrator organization benefits

This new organization structure will come with a number of benefits, such as improving integrator access to Okta support resources and expanding developer access to Okta product offerings for testing purposes.

Deprecating Okta Developer Edition organizations

In July 2025, existing Okta Developer Edition organization will be deactivated. At this time, you will lose access to your old Okta Developer Edition organization and all resources in it..

How to migrate your resources from Okta Developer Edition to Integrator Free Plan

Creating an Integrator Free Plan organization will give you a clean slate to test and develop in. However, you might want to replicate setup steps that you’ve performed in your Okta Developer Edition organization to continue work in progress. Several options are available for migrating your configuration from your Okta Developer Edition organization to your Integrator Free Plan organization.

Migrating data is optional

If you want to discard the configuration and data from your Okta Developer Edition organization and start fresh in a new Integrator Free Plan organization, create a new Integrator Free Plan organization and begin using it. Your Developer Edition resources and configuration will be deleted when old organization are deactivated in July..

Re-create resources by re-running automation

If you automated the creation of resources in your Okta Developer Edition organization that you’d like to continue using in your Integrator Free Plan organization, your environment setup will be simple. Create an Integrator Free Plan organization, provide credentials to your setup tooling, and re-run that tooling.

Add automation for long-term management

If you created resources in your Okta Developer Edition organization by hand and you want to automate management of those resources going forward, this is a great time to build the tooling you want using Terraform or PowerShell. Terraformer can help you generate Terraform configurations based on existing resources in your old organization.

Use our migration tool for one-off organization backup

If you’d like to capture a snapshot of your current Okta Developer Edition configuration, try our migration tool. It wraps the Okta CLI Client to create files representing all supported objects in your Developer Edition organization, and can use these backup files to automatically re-create many of the objects in your new Integrator Free Plan organization.

Migrate your public OIN Integration

If you have an integration in the Okta Integration Network associated with your Okta Developer Edition organization, sign up for a new Integrator Free Plan organization and contact Developer Support to request that your integration be migrated to your new organization. Developer Support will link your new organization to your integration so that you can easily update it as needed.

If you have been working on an integration for the Okta Integration Network but it has not yet been accepted, you are responsible for migrating your work in progress from your Developer Edition organization to an Integrator Free plan organization.

Cutoff dates for OIN submissions

As of May 22, 2025, no new OIN integration submissions will be accepted from developer orgs. After May 22, you must use an Integrator Free Plan organization to submit OIN integrations.

If you have submitted an OIN integration from an Okta Developer Edition organization, it must be approved by June 9. Any submissions coming from Okta Developer Edition organizations that are still in Draft or In Review status on June 9 will be automatically rejected, and you will need to re-submit the same integration from an Integrator Free Plan organization.

Key dates

Plan your migration now!

If you’ve used Okta Developer Edition organizations in the past, check now to see if any contain configurations that you’d like to keep. You can check whether you have an organization by checking your password manager for credentials saved on the login page, or searching your email for a welcome message from <noreply@test-account.dev>.

If you have any questions, don’t hesitate to contact us in the comments below.