Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Roles required to select or create a project
Select a project: Selecting a project doesn't require a specific
IAM role—you can select any project that you've been
granted a role on.
Create a project: To create a project, you need the Project Creator
(roles/resourcemanager.projectCreator), which contains the
resourcemanager.projects.create permission. Learn how to grant
roles.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
Roles required to select or create a project
Select a project: Selecting a project doesn't require a specific
IAM role—you can select any project that you've been
granted a role on.
Create a project: To create a project, you need the Project Creator
(roles/resourcemanager.projectCreator), which contains the
resourcemanager.projects.create permission. Learn how to grant
roles.
En la tarjeta Calculadora local, haz clic en Agregar a la estimación.
Haz clic en Iniciar estimación.
En la página Iniciar la estimación, en la tarjeta Local, haz clic en Iniciar.
Especifica los detalles de la infraestructura
En la página Estimate basics, deja la ubicación predeterminada como está
y haz clic en Siguiente.
En la página Infraestructura, en la sección CPU virtuales totales que se migrarán, en el campo Cantidad de CPU virtuales, ingresa 78250.
Según la proporción predeterminada de almacenamiento para procesamiento, que es 4:1, el campo Memoria del centro de datos requerida se actualiza automáticamente a 313000.
Deja en blanco la casilla de verificación Incluye una infraestructura que no sea x86.
En la sección Almacenamiento en uso actualmente en los centros de datos, especifica los siguientes detalles:
En el campo Total storage (TB), ingresa 110.
Deja los valores predeterminados de % Almacenamiento de archivos, % Almacenamiento en bloque y % Almacenamiento de objetos como están.
Para especificar los detalles de la carga de trabajo y la licencia, haz clic en Siguiente.
Especifica los detalles de la carga de trabajo y la licencia
En la página Workloads and licenses, en la sección Oracle and SAP workloads,
selecciona Oracle y SAP.
En los campos adicionales Oracle vCPUs y SAP vCPUs que aparecen, ingresa los siguientes valores:
Porcentaje del total de CPUs virtuales que ejecutan la base de datos de Oracle: 32
Porcentaje de CPU virtuales totales que ejecutan Oracle Exadata: 0
Porcentaje del total de CPUs virtuales que ejecutan la base de datos del almacén de datos de Oracle: 0
Almacenamiento para base de datos de Oracle (GB): 50
Porcentaje del total de CPUs virtuales de aplicación de SAP: 38
Porcentaje de CPU virtuales de base de datos de SAP: 12
En la sección Licenses for all other workloads, selecciona Windows Server.
Selecciona SO Linux y, luego, Opciones gratuitas de SO Linux (Ubuntu, CentOS, Debian, AlmaLinux, openSUSE, etcétera).
En el campo Porcentaje de CPUs virtuales que ejecutan Windows Server, ingresa 30.
En el campo % de CPUs virtuales que ejecutan el SO Linux gratuito, ingresa 70.
Para configurar el cronograma de migración, haz clic en Siguiente.
Configura el cronograma de migración
En la página Migration timeline, pricing, and discounts, deja los
valores predeterminados como están.
Para revisar y exportar los resultados, haz clic en Enviar.
Revisa y exporta los resultados de las estimaciones
En esta página, se muestra lo siguiente:
Rango estimado de inversión en Cloud por 5 años.
Para este ejemplo, el rango es de USD 57.5 millones - USD 70.3 millones.
Precios estimados para el entorno que seleccionaste.
En este ejemplo, para ver el desglose del costo anual por migrar tu
infraestructura local a Google Cloud y el desglose del
costo anual de cada producto, haz clic en Ver detalles en
la tarjeta de resultados Local.
Para ver el desglose del costo anual de cada producto, haz clic en el nombre del producto. Por ejemplo, para ver el desglose de costos anuales de Compute Engine, haz clic en Procesamiento.
El precio de lista anual y el porcentaje de la estimación total se muestra para cada componente de Compute Engine.
Además, para ver los detalles de cómo se calcula este costo para cualquier
componenteGoogle Cloud , haz clic en el nombre del componente. Por ejemplo, haz clic
en Compute para núcleos de Hot (N2).
Se muestran los detalles sobre cómo se calculan el tamaño y el precio. Estos cálculos se basan en tus entradas y en las suposiciones predeterminadas que puedes editar si es necesario.
Para exportar los resultados de la estimación, en la parte superior de la página de resultados,
haz clic en Exportar y selecciona la opción adecuada.
Limpia
Sigue estos pasos para evitar que se apliquen cargos a tu cuenta de Google Cloud por los recursos que usaste en esta página.
Borra el proyecto
La manera más fácil de eliminar la facturación es borrar el proyecto que creaste para el instructivo.
Para borrar el proyecto, sigue estos pasos:
In the Google Cloud console, go to the Manage resources page.
[[["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-11 (UTC)"],[],[],null,["# Quickstart: Generate a rapid cost estimate\n==========================================\n\nLearn how to generate a rapid cost estimate for running your infrastructure on\nGoogle Cloud with Migration Center.\n\nThe estimates are generated based on Google Cloud best practices. Your\nactual cost can be higher or lower than the generated estimate.\n\nIn this example, you will estimate the cost of migrating an on-premises\nenvironment that has the following specifications:\n\n- Contains x86 vCPUs only\n- Includes SAP and Oracle vCPUs\n- Includes both Linux and Windows vCPUs\n- Has a migration timeline of 5 years\n\n*** ** * ** ***\n\nTo follow step-by-step guidance for this task directly in the\nGoogle Cloud console, click **Guide me**:\n\n[Guide me](https://console.cloud.google.com/?walkthrough_id=migration-center--estimate--generate-estimate)\n\n*** ** * ** ***\n\nBefore you begin\n----------------\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\nStart estimation\n----------------\n\n1. In the Google Cloud console, go to the **Migration Center Estimate cost** page.\n\n [Go to Estimate cost](https://console.cloud.google.com/migration/spend)\n2. In the **Estimate name** field, enter `demo_estimate`.\n\n3. In the **On-premises** calculator card, click **Add to estimate**.\n\n4. Click **Start estimate**.\n\n5. On the **Start your estimate** page, in the **On-premises** card, click **Start**.\n\nSpecify infrastructure details\n------------------------------\n\n1. On the **Estimate basics** page, leave the default location as is\n and click **Next**.\n\n2. On the **Infrastructure** page, in the **Total vCPUs to be migrated**\n section, in the **Number of vCPUs** field, enter `78250`.\n\n Based on the default storage to compute ratio, which is `4:1`, the\n **Data center memory required** field is automatically updated to `313000`.\n3. Leave the **Include non-x86 infrastructure** checkbox blank.\n\n4. In the **Storage currently in use in your data center(s)** section, specify\n the following details:\n\n 1. In the **Total storage (TB)** field, enter `110`.\n\n 2. Leave the default values for **% File Storage** , **% Block Storage** ,\n and **% Object Storage** as is.\n\n5. To specify the workload and license details, click **Next**.\n\nSpecify workload and license details\n------------------------------------\n\n1. On the **Workloads and licenses** page, in the **Oracle and SAP workloads**\n section, select **Oracle** and **SAP**.\n\n2. In the additional **Oracle vCPUs** and **SAP vCPUs** fields that appear,\n enter the following values:\n\n - **% of total vCPUs running Oracle Database** : `32`\n - **% of total vCPUs running Oracle Exadata** : `0`\n - **% of total total vCPUs running Oracle Data Warehouse Database** : `0`\n - **Storage for Oracle database (GB)** : `50`\n - **% of total SAP Application vCPUs** : `38`\n - **% of total SAP Database vCPUs** : `12`\n3. In the **Licenses for all other workloads** section, select **Windows Server**.\n\n4. Select **Linux OS**\n and then select **Free Linux OS options (Ubuntu, CentOS, Debian, AlmaLinux, openSUSE, etc)**.\n\n5. In the **% of vCPUs running Windows Server** field, enter `30`.\n\n6. In the **% of vCPUs running free Linux OS** field, enter `70`.\n\n7. To set up the migration timeline, click **Next**.\n\nSet up the migration timeline\n-----------------------------\n\n1. On the **Migration timeline, pricing, and discounts** page, leave the\n default values as is.\n\n2. To review and export the results, click **Submit**.\n\n\u003cbr /\u003e\n\nReview and export estimation results\n------------------------------------\n\nThis page displays the following:\n\n- Your 5-year cloud spend estimate range.\n\n For this example, the range is **$57.5M - $70.3M**.\n- Estimated pricing for your selected environment.\n\n In this example, to view the breakdown of the annual cost for migrating your\n on-premises infrastructure to Google Cloud and the breakdown of\n the annual cost for each product, click **View details** in\n the **On-premises** results card.\n\n To view the breakdown of the annual cost for each product, click the product\n name. For example, to view the annual cost breakdown for Compute Engine,\n click **Compute**.\n The annual list price and percentage of the total estimate is\n displayed for each Compute Engine component.\n\n Further, to see the details of how this cost is calculated for any\n Google Cloud component, click the component name. For example, click\n **Compute for Hot cores (N2)** .\n The details about how the sizing and price is calculated is displayed. These\n calculations are based on your inputs and the [default assumptions](/migration-center/docs/estimate/review-defaults)\n that you can edit if needed.\n\nTo export the estimation results, on the top of the results page,\nclick **Export** and select the appropriate option.\n\nClean up\n--------\n\n\nTo avoid incurring charges to your Google Cloud account for\nthe resources used on this page, follow these steps.\n\n### Delete the project\n\n\nThe easiest way to eliminate billing is to delete the project that you\ncreated for the tutorial.\n\nTo delete the project:\n\n| **Caution** : Deleting a project has the following effects:\n|\n| - **Everything in the project is deleted.** If you used an existing project for the tasks in this document, when you delete it, you also delete any other work you've done in the project.\n| - **Custom project IDs are lost.** When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as an `appspot.com` URL, delete selected resources inside the project instead of deleting the whole project.\n|\n|\n| If you plan to explore multiple architectures, tutorials, or quickstarts, reusing projects\n| can help you avoid exceeding project quota limits.\n1. In the Google Cloud console, go to the **Manage resources** page.\n\n [Go to Manage resources](https://console.cloud.google.com/iam-admin/projects)\n2. In the project list, select the project that you want to delete, and then click **Delete**.\n3. In the dialog, type the project ID, and then click **Shut down** to delete the project.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- Learn more about [cost estimation](/migration-center/docs/estimate/overview)."]]
