Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Puedes trasladar a Compute Engine instancias de VM, imágenes personalizadas o discos que estén disponibles en un entorno existente, como los locales o los de otros proveedores de servicios en la nube.
Hay una variedad de rutas de migración disponibles que admiten diferentes formatos.
La elección de una ruta de migración depende de si mueves una instancia de VM, un disco o una imagen.
En la siguiente tabla, se resumen las rutas de migración disponibles en Compute Engine.
Migrar instancias de VM desde otros proveedores de servicios en la nube como VMware y AWS
Probar tus apps en la nube antes de migrar. Si tus apps no funcionan de forma adecuada, puedes realizar una reversión con facilidad
Con Migrate to Virtual Machines, tienes un conjunto de funciones que te ayudan a automatizar, simplificar y acelerar el proceso de migración.
Migrate to VMs es de uso gratuito para los clientes que migran a Google Cloud. Se aplican tarifas de facturación estándar para todos los demás productos deGoogle Cloud (como Compute Engine o Storage) que se usan o consumen durante la migración o después. Por ejemplo, si usas las VMs de Compute Engine para implementar Migrate to VMs, deberás pagar esas horas de instancia. Para obtener información más detallada sobre los precios, consulta Precios de Migrate to VMs.
Si necesitas realizar personalizaciones avanzadas o tener discos de origen en un formato que no sea compatible con el comando de importación, puedes importar y configurar los discos de forma manual.
Importa imágenes de máquinas. Una imagen de máquina es un recurso de Compute Engine que almacena toda la configuración, los metadatos, los permisos y los datos de uno o más discos necesarios para crear una instancia de VM.
Este método es más adecuado para crear imágenes de máquinas desde dispositivos virtuales.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eCompute Engine allows you to migrate VM instances, custom images, and disks from on-premises environments or other cloud providers.\u003c/p\u003e\n"],["\u003cp\u003eThe migration path you should use depends on whether you're moving a VM instance, disk, or image, and the format of the content.\u003c/p\u003e\n"],["\u003cp\u003eMigrate to Virtual Machines is recommended for migrating multiple VM instances or VM instances from other cloud providers like VMware and AWS, with features to automate and accelerate the migration process.\u003c/p\u003e\n"],["\u003cp\u003eFor importing a small number of prepackaged virtual machines, importing virtual appliances is the most suitable migration path.\u003c/p\u003e\n"],["\u003cp\u003eYou can import virtual disks or template disks using the image import feature, which is being transitioned to Migrate to Virtual Machines, or you can import and configure them manually.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nYou can move VM instances, custom images, or disks that are available in\nan existing environment, such as on-premises or on other cloud providers, to\nCompute Engine.\n\nA variety of migration paths are available that support different formats.\nChoosing a migration path depends on whether you are moving a\nVM instance, disk, or image.\n\nThe following table summarizes the migration paths available on\nCompute Engine.\n\n| **What you want to migrate** | **Tool or procedure** | **Best used for** |\n|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| VM instances | [Migrate to Virtual Machines](/migrate/compute-engine/docs/latest) | - Importing multiple VM instances and their data. - Migrating VM instances from other cloud providers such as VMware and AWS. - Testing your apps in the cloud before you migrate. If your apps do not function properly, you can easily roll back. With Migrate to Virtual Machines, you have a suite of features that help you automate, simplify, and accelerate the migration process. Migrate to VMs is free to use for customers migrating to Google Cloud. Standard billing rates apply for all other Google Cloud products (such as [Compute Engine](/compute/all-pricing) or [Storage](/storage/pricing)) used or consumed during or after the migration. For example, if you use Compute Engine VMs to deploy Migrate to VMs, you'll need to pay for those instance hours. For more detailed pricing information, see [Migrate to VMs pricing](/migrate/compute-engine/pricing). | **Pro Tip:** This method is ideal for | moving a large number of workloads. |\n| VM instances (in OVA or OVF format) | [Importing virtual appliances](/compute/docs/import/import-ovf-files) | Importing virtual appliances. A virtual appliance is a prepackaged virtual machine. | **Pro Tip:** This method is best suited for | importing a small number of virtual machines. |\n| Virtual disks or images | [Import virtual disks](/compute/docs/import/importing-virtual-disks) | Importing virtual disks or template disks from an on-premises or other cloud environment. \u003cbr /\u003e These methods use the [images import](/sdk/gcloud/reference/compute/images/import) command. \u003cbr /\u003e If you need to make advanced customizations or have source disks in a format that is not supported by the import command, you can [manually import and configure disks](/compute/docs/import/import-existing-image). | The image import feature on Compute Engine is being moved to Migrate to Virtual Machines. We recommend that you use the new [image import feature on Migrate to Virtual Machines](/migrate/virtual-machines/docs/5.0/migrate/image_import) to import your virtual disks to Google Cloud. |\n| Machine images | [Importing a machine image from a virtual appliance](/compute/docs/machine-images/import-machine-from-virtual-appliance) | Importing machine images. A machine image is Compute Engine resource that stores all the configuration, metadata, permissions, and data from one or more disks required to create a VM instance. \u003cbr /\u003e This method is best suited for creating machine images from virtual appliances. |"]]
