diff --git a/pods/troubleshooting/pod-migration.mdx b/pods/troubleshooting/pod-migration.mdx
index 499a86f6..ae0d202b 100644
--- a/pods/troubleshooting/pod-migration.mdx
+++ b/pods/troubleshooting/pod-migration.mdx
@@ -10,6 +10,15 @@ import { MachineTooltip } from "/snippets/tooltips.jsx";
 Pod migration is currently in beta. [Join our Discord](https://discord.gg/runpod) if you'd like to provide feedback.
 </Note>
 
+<iframe
+  className="w-full aspect-video rounded-xl"
+  src="https://www.youtube.com/embed/q7I0uVTOhqg"
+  title="3 Minute Runpod: Migrate your volume to a new Pod automatically"
+  frameBorder="0"
+  allow="fullscreen; accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowFullScreen
+></iframe>
+
 When you start a Pod, it's assigned to a specific physical <MachineTooltip /> with 4-8 GPUs. This creates a link between your Pod and that particular machine. As long as your Pod is running, that GPU is exclusively reserved for you, which ensures stable pricing and prevents your work from being interrupted.
 
 When you stop a Pod, you release that specific GPU, allowing other users to rent it. If another user rents the GPU while your Pod is stopped, the GPU will be occupied when you try to restart. Because your Pod is still tied to that original machine, you'll see message asking you to migrate your Pod. This doesn't mean there are no GPUs of that type available on Runpod, just that none are available on the specific physical machine where your Pod's data is stored.