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.
Your team is deleted during migration and cannot be restored. Personal resources contributed by members during the merge are folded into the organization permanently and are never returned, even if a member later leaves.
What happens during migration
- A Runpod staff member runs the migration for your team. A single migration can merge multiple teams into one organization or extend an existing one.
- The team is disbanded. Your team owner account becomes an admin of the new organization.
- All org-aware resources previously owned by the team transfer to the organization automatically, including Pods, endpoints, network volumes, Instant Clusters, templates, secrets, registry auth, Flash apps, reservations, and S3 credentials.
- All team members join the organization automatically. Team roles map to org roles using these rules: team owners become admin; members with an unknown or unmapped role default to basic; a member who belongs to multiple teams keeps the highest role across all teams.
- Every participant’s personal resources fold into the organization during the merge and cannot be reclaimed.
- Each team in the merge becomes a group in the organization.
What to do before migration
Tell members about resource transfer
Make sure your team members understand that any personal resources they contribute during migration are folded into the organization permanently before the staff run.
Check for migration blockers
The following conditions block migration and must be resolved before Runpod can run it:
- Any participant with an active savings plan blocks the merge.
- Paying accounts require a billing cutover acknowledgement.
- Secret-name or derived group-name collisions hard-fail.
Resolve cross-team memberships
Every team that any participant belongs to must be included in the same merge. If a participant is in or owns a team outside the merge set, migration is blocked. That participant must leave that team first, or the other team must be added to the merge.
Rotate org S3 credentials
If your team uses Runpod’s S3-compatible storage credentials, rotate them before removing any member post-migration. When a member is removed from an organization, their org S3 credentials are revoked immediately.
Do this in order:
- Create replacement credentials attributed to a remaining admin.
- Update all external service configurations to use the new credentials.
- Then remove the member.
Understand SSH key behavior
For Pods deployed by the organization, Runpod sets PUBLIC_KEY to the union of all current org members’ SSH public keys (see Connect to a Pod via SSH for how key injection works). Shared SSH access works automatically: every member whose key is on file when the Pod is created can connect.
Because the key set is frozen at creation, adding or removing a member’s key affects only Pods deployed after that change. Existing Pods keep the keys they were created with until they are redeployed.
To override the injected keys on a specific Pod, set the PUBLIC_KEY environment variable on that Pod. When PUBLIC_KEY is already set on a Pod, Runpod skips the member-key injection.
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.
- Review your migrated members and their mapped roles in Settings → Members.
- Set up groups to organize your migrated members. See Groups.
