Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 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
        • Updating a VM
        • Changing VM computing resources
        • VM maintenance policy management
        • Configuring VM access permissions
        • Linking a service account to a VM
        • Deleting a VM
    • Viewing operations with resources
    • Viewing metrics Monitoring
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Audit Trails events
  • Release notes
  1. Step-by-step guides
  2. VMs
  3. Management
  4. Moving a VM to a different cloud

Moving a VM to a different cloud

Written by
Yandex Cloud
Updated at July 31, 2026
View in Markdown

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. Navigate to 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 yet, install and initialize it.

    The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

    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 guides on the Terraform website or its mirror.

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

    To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

    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, navigate to the configuration file directory.

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

        terraform validate
        

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

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

        terraform plan
        

        You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

      4. Apply the configuration 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, navigate to the configuration file directory.

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

        terraform validate
        

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

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

        terraform plan
        

        You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

      4. Apply the configuration 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
Updating a VM
© 2026 Direct Cursus Technology L.L.C.