Short answer: start a pod on the volume while the workflow still renders, pack that run into a nest, then restore the nest on any Linux GPU machine you rent — another region, or another cloud. The volume stays where it is until you decide what to do with it.
Why not just copy the volume?
You can, with rsync or rclone through a running pod. But that copies files, not a working environment: a Python environment built on the old pods may not work on new ones, and the system libraries your custom nodes need were never on the volume. More on that in Network volume, new pod, still broken.
A nest records the run that worked: the model files, the custom nodes pinned to their commits, the workflow, the exact package versions, and which system libraries the run loaded.
1. Pack on the volume, while it still works
Start a pod in the volume's region with the volume attached, and check that your workflow still renders. Then install the tool:
uv tool install --upgrade renest
export PATH="$HOME/.local/bin:$PATH"
In ComfyUI, export the workflow in API format (Export (API)), and pack:
renest pack --dir /workspace --workflow workflow-api.json \
--out /workspace/nests --dest hosted
--dir is the folder that holds ComfyUI/. --dest hosted uploads the nest to your Renest drive as it packs; that needs an access key from the web console (Settings → Access) and a paid plan (Plus or above — see Pricing). Your nests can also live in your own bucket.
2. Restore where the GPUs are
Rent a Linux machine with an NVIDIA GPU wherever there is stock: another RunPod region, or vast.ai. In the web console, open the nest, choose Restore, and paste the command it gives you. It writes your restore code to grant.json and runs:
cd /workspace 2>/dev/null || cd ~
renest restore --grant grant.json --dir ./run
renest start --dir ./run --listen 0.0.0.0
Before the big download, the restore checks the machine and refuses one the nest can't run on — a GPU generation the packed PyTorch has no code for, a driver too old, a CPU without avx2. Then it downloads every file and checks it against its checksum, installs the locked packages, starts ComfyUI and runs your workflow once, and tells you what passed and what didn't. If the first machine is a dud, the same restore command works on the next one.
3. Then decide about the volume
Once the nest is in your drive and you have restored it somewhere else, you can decide whether to keep paying for the volume. That is your call; Renest never touches it.
Step-by-step pages: Renest on RunPod, Restore a nest, After the restore.