Requesting a Cell change for an existing Okta Org involves a defined process. This article outlines the steps and considerations.

• Okta cell
• Migration
• Okta Classic Engine
• Okta Identity Engine (OIE)

Currently, Okta does not support migrating an existing organization (org) from one cell (geographical region) to another. For example, from the EU cell to the US cell or vice versa. There is no native functionality for moving or "translating" an org between Okta cells.

If a presence in a different region is required, the only option is to provision a new org in the desired cell. This process involves:

• Decommissioning the existing org (if no longer needed).
• Requesting the creation of a new org in the target cell (for example, via contacting the Customer Success Manager or Okta Support).
• Manually reconfiguring all settings, integrations, policies, and user assignments in the new org from scratch.
• Migrating users and applications manually or via API/scripts, if applicable.

NOTE: Data, configurations, and user identities from the original org cannot be automatically transferred to the new org. This may require detailed planning and testing to ensure a smooth transition, especially in complex environments.

Okta understands that this may present challenges, and it is recommended to contact the Okta account team to discuss the implications and, if needed, get assistance with planning.