Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Compute Cloud
    • All guides
      • Stopping and starting a VM
      • Resetting a Windows Server VM user password
      • Attaching a disk to a VM
      • Detaching a disk from a VM
      • Moving a VM to a different availability zone
      • Moving a VM to a different folder
      • Moving a VM to a different cloud
      • Adding another network interface to a VM
      • Deleting a network interface from a VM
      • Assigning a public IP address to a VM
      • Unassigning a public IP address from a VM
      • Making a VM public IP address static
      • Reassigning a public IP address from one VM to another
      • Updating the VM internal IP address
      • Updating a VM
      • Changing VM computing resources
      • Changing VM security groups
      • VM maintenance policy management
      • Configuring VM access permissions
      • Linking a service account to a VM
      • Deleting a VM
    • Viewing service resource operations
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. Managing a VM
  3. Moving a VM to a different cloud

Moving a VM to a different cloud

Written by
Yandex Cloud
Updated at July 29, 2025

While directly moving a VM to a different cloud is not supported, you can create an image from its boot disk and then create a VM from this image in a different cloud.

  1. Use the boot disk of your VM to create an image.

  2. Get the boot disk image ID:

    Management console
    CLI
    Terraform
    API
    1. In the management console, select the folder the disk image is in.
    2. Select Compute Cloud.
    3. In the left-hand panel, select Images.
    4. Copy the value from the ID column for the image in question.

    If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

    By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

    Get a list of disk images in the default folder:

    yc compute image list
    

    Result:

    +----------------------+----------------+--------+-------------+--------+
    |          ID          |    NAME        | FAMILY | PRODUCT IDS | STATUS |
    +----------------------+----------------+--------+-------------+--------+
    | xc8n3spmksqm******** | original-image |        |             | READY  |
    +----------------------+----------------+--------+-------------+--------+
    

    With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

    Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

    For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

    If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

    1. In the configuration file, prepare the output variable with the output data:

      resource "yandex_compute_snapshot" "snapshot-1" {
        name           = "<image_name>"
        source_disk_id = "<disk_ID>"
      }
      ...
      output "snapshot_id" {
        value = yandex_compute_snapshot.snapshot-1.id
      }
      

      Where value is the boot disk image ID. In the example above, the boot disk image is described in the yandex_compute_snapshot resource named snapshot-1.

    2. Apply the changes:

      1. In the terminal, go to the directory where you edited the configuration file.

      2. Make sure the configuration file is correct using this command:

        terraform validate
        

        If the configuration is correct, you will get this message:

        Success! The configuration is valid.
        
      3. Run this command:

        terraform plan
        

        You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.

      4. Apply the changes:

        terraform apply
        
      5. Type yes and press Enter to confirm the changes.

    3. Save the boot disk image ID to the snapshot_id.txt file using this console command:

      terraform output snapshot_id > snapshot_id.txt
      

    Use the list REST API method for the Image resource or the ImageService/List gRPC API call.

  3. Get the ID of the target cloud you plan to move your VM to (next: <target_cloud_ID>):

    Management console
    CLI
    Terraform
    API
    1. In the management console, click the cloud in the list on the left.
    2. On the Overview tab, copy the ID value.

    Get a list of clouds with their IDs:

    yc resource-manager cloud list
    

    Result:

    +----------------------+------------+--------------------------+
    |          ID          |    NAME    |      ORGANIZATION ID     |
    +----------------------+------------+--------------------------+
    | b1g66mft1vop******** | my-cloud-1 |                          |
    | b1gd129pp9ha******** | my-cloud-2 |                          |
    +----------------------+------------+--------------------------+
    
    1. In the configuration file, prepare the output variable with the output data:

      resource "yandex_resourcemanager_cloud" "cloud-1" {
        name            = "<cloud_name>"
        organization_id = "<organization_ID>"
      }
      
      output "destination_cloud_id" {
        value = yandex_resourcemanager_cloud.cloud-1.id
      }
      

      Where destination_cloud_id is the target cloud ID. In the example above, the cloud is described in the yandex_resourcemanager_cloud resource named cloud-1.

    2. Apply the changes:

      1. In the terminal, go to the directory where you edited the configuration file.

      2. Make sure the configuration file is correct using this command:

        terraform validate
        

        If the configuration is correct, you will get this message:

        Success! The configuration is valid.
        
      3. Run this command:

        terraform plan
        

        You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.

      4. Apply the changes:

        terraform apply
        
      5. Type yes and press Enter to confirm the changes.

    3. Save the target cloud ID named destination_cloud_id.txt using this console command:

      terraform output destination_cloud_id > destination_cloud_id.txt
      

    To get a list of clouds with their IDs, use the list REST API method for the Cloud resource or the CloudService/List gRPC API call.

  4. Add a user from the target cloud (where you want to move your VM) to the cloud hosting the folder with the source image.

  5. Assign the target cloud user the resource-manager.clouds.member and compute.images.user roles for the cloud hosting the folder with the source image.

  6. Create a new image in the target cloud:

    CLI
    API
    yc compute image create \
      --name <new_image_name> \
      --source-image-id <source_image_ID> \
      --cloud-id <target_cloud_ID> \
      --folder-id <destination_folder_ID>
    

    Use the create REST API method for the Image resource or the ImageService/Create gRPC API call. Specify the image ID in your request.

  7. In the target cloud, create a VM from the image you created.

Was the article helpful?

Previous
Moving a VM to a different folder
Next
Adding another network interface to a VM
© 2025 Direct Cursus Technology L.L.C.