> ## Documentation Index
> Fetch the complete documentation index at: https://runpod-b18f5ded-lg-org-setup-team-mig.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Teams

> What to expect when your Team account is migrated to an Organization.

Migration from Teams to Organizations is performed by Runpod staff. You cannot self-migrate. If you're an enterprise customer and want to migrate, contact your Runpod account representative.

<Warning>
  Migration is permanent and irreversible. Once your Team is migrated to an Organization, there is no path back to the Team model.
</Warning>

## What happens during migration

1. A Runpod staff member runs a migration script for your Team.
2. The Team is disbanded. Your team owner email account becomes an **admin** of a new Organization.
3. All resources previously owned by the Team — Pods, endpoints, volumes, clusters, templates, secrets, registry auth — transfer to the Organization automatically.
4. Former team members are **not** automatically added to the Organization. As the new org admin, you must re-invite them manually.
5. You receive an email notification when migration is complete.
6. When invited former members accept, their personal resources (Pods, templates, secrets, etc.) fold into the Organization permanently and cannot be reclaimed.

## What to do before migration

### Resolve cross-team memberships

If any team member belongs to multiple teams owned by different customers, that cross-team membership must be resolved before migration. The affected user must leave one of the teams before migration can proceed.

### Rotate SharedApiKey credentials

If your team uses SharedApiKey (Runpod's S3-compatible storage credentials), rotate credentials before removing any member post-migration. When a member is removed from an org, their storage credentials are revoked immediately.

Do this in order:

1. Create replacement credentials attributed to a remaining admin.
2. Update all external service configurations to use the new credentials.
3. Then remove the member.

### Understand SSH key behavior

SSH key behavior does not change at migration. Each Pod's `PUBLIC_KEY` remains the deploying user's key only — not a shared org key.

Workarounds if you need shared SSH access:

* Set a `RUNPOD_SSH_PUBLIC_KEY` environment variable per Pod to override the default key.
* Use the web terminal in the console.
* Share a private key across team members (not recommended for security reasons).

Org-level SSH key management is a planned feature for a future release.

## After migration

Once migration is complete:

* The `console.runpod.io/team` page is no longer accessible.
* Your Organization dashboard is available at `console.runpod.io`.
* Invite your former team members from **Settings → Members**.
* Set up SSO, domain allowlists, and groups as needed. See [Access and SSO](/organizations/access) and [Groups](/organizations/groups).

## Membership warning for invited members

When a former team member accepts your invitation, they will see a warning before accepting:

> Joining this Organization will transfer your personal resources to the Organization permanently. These resources cannot be reclaimed if you leave or are removed.

Members must acknowledge this before their invitation is accepted.