Skip to content

Update pod-migration.mdx #700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lavanya-gunreddi wants to merge 2 commits into
base: main
Choose a base branch
from
+25 −1
Open

Update pod-migration.mdx #700

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c5d0f0
Update pod-migration.mdx
lavanya-gunreddi Jul 9, 2026
d1b33f1
Update pod-migration.mdx
lavanya-gunreddi Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 25 additions & 1 deletion pods/troubleshooting/pod-migration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,31 @@ When prompted to migrate your Pod, you have three options:

2. **Start Pod with CPUs**: If you don't need GPU access immediately, you can start your Pod with CPUs only. This lets you access your data and manually migrate files if needed, but the Pod will have limited CPU resources and is not suitable for compute-intensive tasks.

3. **Automatically migrate Pod data**: This option spins up a new Pod with the same specifications as your current one and automatically migrates your data to a machine with available GPUs. The migration process finds a new machine with your requested GPU type, provisions the instance, and transfers your network volume data from the old Pod to the new one.
3. **Automatically migrate Pod data**: This option spins up a new Pod with the same specifications as your current one and automatically migrates your data to a machine with available GPUs. The migration process finds a new machine with your requested GPU type, provisions the instance, and transfers your network volume data from the old Pod to the new one. See [what happens during automatic migration](#what-happens-during-automatic-migration) below.


## What happens during automatic migration

When you trigger an automatic Pod migration:

1. Runpod provisions a new target Pod with the same GPU specifications as your original. The target Pod may temporarily show 0 GPUs in your pod list until the migration completes — this is expected.
2. A temporary **CPU mover pod** is deployed to handle the data transfer. This pod appears in your pod list during the migration with a billing-exempt status — you are not charged for it. Once the migration completes, it is removed automatically.
3. Your data is transferred from the old Pod to the new one.
4. The migration completes and the new Pod becomes available.
You'll receive an **email and inbox notification** when the migration starts, including the reason for migration and your source and target Pod IDs. You'll receive another notification when the migration is complete.

<Note>
If you see an unfamiliar pod appear in your pod list during this process, it is the CPU mover pod. It will disappear once the migration is complete and you will not be charged for it.
</Note>

If a migration stalls because the source host went offline or becomes unreachable, Runpod will automatically mark it as failed after a timeout. You'll be able to initiate a new migration once the failed migration is resolved.

## During an active migration

While a migration is in progress, the following restrictions apply:

- **You cannot stop or terminate the source Pod.** If you attempt to do so, you'll see the error: *"This pod has a migration in progress. Cancel the migration before terminating."*
- To stop or terminate the Pod, you must first cancel the migration from the Pod's options menu.

## Important considerations for migration

Expand Down
Loading