Process for Migrating an Okta Cell Between Regions
Last Updated:
Overview
Okta does not support migrating an existing organization from one geographical region to another. Administrators requiring a presence in a different region must provision a new organization in the desired cell and manually migrate all configurations and users.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta cell
- Migration
Solution
What is the process for migrating an Okta organization to a different region?
Currently, Okta does not support migrating an existing organization from one cell to another, such as from the EU cell to the US cell. Okta lacks native functionality to move or translate an organization between cells.
Administrators requiring a presence in a different region must provision a new organization in the desired cell. Decommission the existing organization, request a new organization in the target cell, and manually reconfigure all settings and user assignments.
- Decommission the existing organization if no longer necessary.
- Request the creation of a new organization in the target cell by contacting Okta Support.
- Manually reconfigure all settings, integrations, policies, and user assignments in the new organization from scratch.
- Migrate users and applications manually or via an Application Programming Interface (API) or scripts.
NOTE: Okta does not automatically transfer data, configurations, and user identities from the original organization to the new organization. This transition requires detailed planning and testing to ensure a smooth transition, especially in complex environments. Contact the Okta account team to discuss the implications and obtain assistance with planning.
