Stay organized with collections Save and categorize content based on your preferences.

Quickstart: Generate a rapid cost estimate

Learn how to estimate the costs of running your infrastructure on Google Cloud with Migration Center.

In this example you will estimate the cost of migrating an environment that has the following specifications:

  • Contains x86 vCPUs only
  • Includes SAP and Oracle vCPUs
  • Includes both Linux and Windows vCPUs
  • Has a migration timeline of 5 years

To follow step-by-step guidance for this task directly in the Google Cloud console, click Guide me:

Guide me


Before you begin

  1. 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.
  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Cloud project. Learn how to check if billing is enabled on a project.

  4. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  5. Make sure that billing is enabled for your Cloud project. Learn how to check if billing is enabled on a project.

Start estimation

  1. In the Google Cloud console, go to the Estimate cost page.

    Go to Estimate cost

  1. In the Estimate name field, enter demo_estimate.
  2. To specify the infrastructure details, click Next.

Specify infrastructure details

  1. On the Infrastructure page, in the Total vCPUs to be migrated section, in the Number of vCPUs field, enter 78250.

    Based on the default compute to storage ratio, which is 1:4, the Data center memory required field is automatically updated to 313000.

  2. Leave the Include non-x86 infrastructure checkbox blank.

  3. In the Storage currently in use in your data center(s) section, specify the following details:

    1. In the Total storage (TB) field, enter 110.

    2. Leave the default values for % File Storage, % Block Storage, and % Object Storage as is.

    3. In the Storage location section, leave the default value, North America, selected.

  4. To specify the workload and license details, click Next.

Specify workload and license details

  1. On the Workloads and licenses page, in the Enterprise workloads section, select the checkboxes for Oracle and SAP.

  2. In the additional Oracle vCPUs and SAP vCPUs fields that appear, enter the following values:

    • Oracle Database: 25500
    • Oracle Database running on Exadata:0
    • Oracle Data Warehouse Database:0
    • For your Oracle workloads, leave the default location, North America, selected
    • SAP Application vCPUs: 30000
    • SAP Database vCPUs: 10000
    • For your SAP workloads, leave the default location, North America, selected
  3. In the Microsoft SQL and OS vCPUs and licenses section, select the checkboxes for Windows and Linux.

  4. In the additional Windows vCPUs and licenses and Linux vCPUs fields that appear, enter the following values:

    • Windows vCPUs: 3825
    • Windows bring-your own-licenses: Leave the default value, 100, as is
    • Linux vCPUs: 8925
  5. To set up the migration timeline, click Next.

Set up the migration timeline

  1. On the Migration timeline page, leave the default values as is.
  2. To review and export the results, click Submit.

Review and export estimation results

This page displays the following graphs:

  • Your 5-year cloud spend estimate range.

    For this example, the range is $55.8M - $68.2M.

  • The graph for year-over-year spending based on your migration timeline.

  • Estimated pricing by product area.

    To view the breakdown of the annual cost for each product, click the product name. For example, to view the annual Compute Engine cost breakdown, click Compute. The annual list price and percentage of the total estimate is displayed for each Compute Engine component.

    Further, to see the details of how this cost is calculated for any Google Cloud component, click the component name. For example, click Compute for Hot cores (N2). The details about how the sizing and price is calculated is displayed. These calculations are based on your inputs and the default assumptions that you can edit if needed.

To export the estimation results in a PDF, on the top of the results page, click Export > Export summary to PDF.

Clean up

To avoid incurring charges to your Google Cloud account for the resources used on this page, follow these steps.

Delete the project

The easiest way to eliminate billing is to delete the project that you created for the tutorial.

To delete the project:

  1. In the Google Cloud console, go to the Manage resources page.

    Go to Manage resources

  2. In the project list, select the project that you want to delete, and then click Delete.
  3. In the dialog, type the project ID, and then click Shut down to delete the project.

What's next