Specify workload and license details Stay organized with collections Save and categorize content based on your preferences.
On theWorkloads and licenses tab, you can select the applicationsthat you run in your infrastructure, such as Oracle, SAP, or MicrosoftSQL Server, and add the details. Also, select which OS platforms you use andprovide the additional details.
Before you begin
- Complete the steps tospecify infrastructure details.
Specify workload and license details
In theOracle and SAP workloads section, select the workloads you wantto include in your cloud estimate calculation:
Oracle. After you select this workload, additional optionsappear for different Oracle workload types. In theOracle vCPUssection, follow these steps:
For each workload type, specify what percentage of the total number ofx86 vCPUs you want to migrate as that workload.
Specify the total storage, in GB, to use for the Oracle database.
Optional: To edit theOracle sizing default assumptionsused for this estimate, clickEdit Oracle sizing details.
SAP. After you select this workload, additional options appear fordifferent SAP workload types. In theSAP vCPUs section, follow thesesteps:
For each workload type, specify what percentage of the total number ofx86 vCPUs you want to migrate as that workload.
Optional: To edit theSAP sizing default assumptionsused for this estimate, clickEdit SAP sizing details.
In theLicenses for all other workloads section, select theoperating systems for your remaining vCPUs after excluding the Oracle andSAP vCPUs. For the additional options that appear in this section, followthese steps:
For all the selected operating systems, specify the percentagedistribution of your remaining vCPUs.
In the related license sections, choose the licensing model for allthe operating systems you selected. For all the operating systems,Pay as you go (PAYG) is the default licensing model.
If you've selected Windows Server, then to determine whichlicensing model you're eligible for, you can do the following:
In theWindows Server licenses section, clickDetermine your license eligibility.
In theWindows Server license eligibility pane thatappears, select the appropriate options about your licenses, and thenclickNext.
The licensing model that you're eligible for is displayed.
To apply the displayed licensing model to your estimate, clickAccept.
For more information about licensing, see the following:
If you've selected Red Hat Enterprise Linux or SUSE Linux EnterpriseServer, then choose a pricing track for these Linux operating systems.The default pricing track is 3-year committed use discount. For moreinformation about the pricing tracks, seeDisk image and pricing.
If you're migrating Microsoft SQL server, then in theMicrosoft SQL serverlicenses section, select theMicrosoft SQL server checkbox. For theadditional options that appear in this section, follow these steps:
To determine which licensing model you're eligible for, do the following:
ClickDetermine your license eligibility.
In theMicrosoft SQL Server license eligibility pane thatappears, select the appropriate options about your licenses, and thenclickNext.
The licensing model you're eligible for is displayed.
To apply the displayed licensing model to your estimate, clickAccept.
Alternatively, you can manually choose the licensing model. The defaultmodel isPay as you go (PAYG).
For each SQL license type, specify the percentage distribution.
Specify what percentages of vCPUs with the operating systems youselected are running Microsoft SQL Server.
To set up the migration timeline, clickNext.
What's next
- To continue with your estimate, see how toset up the migration timeline and apply discounts.
- Optional: To review the default assumptions that are used to calculate yourcloud cost estimate, see how toreview the default assumptions.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.