This page describes the steps required to qualify for RaMP incentives, how rewards are calculated, and the rules for managing the migration journey and the limitations that apply to RaMP incentives.
Qualify for RaMP incentives
To qualify for RaMP incentives, you need to prepare your environment and tag your workloads. The following sections describe the necessary steps.
Complete a RaMP assessment
To begin the RaMP incentives journey, a customer must undergo a data-driven RaMP assessment to formally qualify for a RaMP Agreement. This assessment identifies eligible RaMP workloads and validates the Projected Annual Run Rate as defined in the RaMP terms. The estimated Projected Annual Run Rate must be at least $60,000 USD per workload to qualify for RaMP.
To start your RaMP assessment, try our free migration assessment or contact your Google Cloud account team.
Sign a RaMP Agreement
Once a RaMP assessment is complete, a RaMP Agreement must be signed and the identified RaMP workloads (which can be one or more workloads) must be tagged to qualify for any RaMP incentives.
RaMP Workload
A RaMP workload is a collection of resources within a Google Cloud project that function together to achieve a business outcome and drive spend on Google Cloud. The following are Workload Types that can earn incentives:
- General
- Database
- Data Analytics
- Oracle
- Windows
- Modern Infra (Google Kubernetes Engine (GKE), Cloud Run, ARM/Axion), and SAP.
These Workload Types are identified as part of the RaMP assessment and receive a unique Workload ID number in the RaMP Agreement.
Tag RaMP Workloads
Tagging is the primary mechanism for identifying and tracking workloads by applying the provided RaMP Agreement ID number and Workload ID number that is bound to the customer's Google Cloud resources.
Workload tagging is required for Google to calculate and disburse RaMP incentives. The customer is responsible for ensuring tags are applied accurately and timely. Google cannot perform retroactive adjustments. Failure to appropriately tag workloads will result in the forfeiture of RaMP incentives for that period.
For more information about tagging RaMP workloads, see
Workload exclusivity
To prevent incentive duplication, RaMP enforces the following strict exclusivity rules across workloads:
- A single, defined workload can reside in exactly one RaMP Agreement.
- A workload cannot be split or shared across multiple RaMP Agreements.
- If a workload is inadvertently included in a second RaMP Agreement, the original RaMP Agreement takes precedence.
Additional RaMP Agreements and billing account best practices
RaMP enables customers to have more than one active RaMP Agreement under the same primary billing account (as the customer plans different workloads and completes different RaMP assessments over time, including entering into a new RaMP Agreement for a different Workload Type).
The primary billing account is where consumption is tracked for incentive eligibility.
Calculate RaMP incentives
RaMP incentives are calculated based on factors including eligible spending and workload type. The following sections explain how incentives are calculated.
Incremental eligible spend for incentives
Google Cloud Services Credits and Partner Services Funds are earned from spend on the RaMP 2026 SKU Group. Offerings that are not eligible for RaMP incentives from incremental spend include Google Cloud Marketplace offerings, Google Cloud Support (including Technical Support Services or TSS), subscriptions, GPUs, Archival Storage, and Google Distributed Cloud.
Funds to support Migrate and Modernize
The following incentive types are available to help support migration and modernization needs: Google Cloud Consulting Services Funds and Training and Implementation Services Funds as well as Partner Services Funds.
For General Workload Types, each workload is eligible for the lesser of 20% of the Projected Annual Run Rate and $2M USD. For specialized Workload Types (for example, VMWare) a higher Projected Annual Run Rate percentage is available. Projected Annual Run Rate only includes eligible incremental spend. For more information, see RaMP Terms.
Funds to support Deployment
Google Cloud Service Credits are available to support Deployments. For General Workload Types, each workload is eligible for 25% of the incremental eligible spend, capped at the lesser of 30% of Projected Annual Run Rate and $3M USD. For specialized Workload Types (for example, Oracle) a higher Projected Annual Run Rate percentage is available.
While the preceding information determines the maximum amount of Google Cloud Service Credits available for each unique Workload ID, additional requirements to earn quarterly Google Cloud Services Credits include:
- Total account growth: Google will provide RaMP incentives only if the incremental eligible spend for all of the Customer's workloads under the primary billing account is equal to or greater than the growth of the specific applicable workload.
- High watermark: The customer must show continuous incremental year-over-year growth as of every quarter for the tagged resources within a RaMP Agreement in order to receive RaMP incentives. I.e. if at any point the customer has a spending dip, they must surpass the previous high watermark spend (calculated as the highest spend of continuous 4 quarters) in order to receive incentives.
Example: Calculating Google Cloud Service Credits
A customer signs a RaMP Agreement for $1,000,000 USD General Workload Type Projected Annual Run Rate on January 1, 2026.
| Q1 | Q2 | Q3 | Q4 | Total per Year | ||
|---|---|---|---|---|---|---|
| 2026 | Google Cloud Eligible Spend | $0 | $100,000 | $150,000 | $200,000 | $450,000 |
| Incremental Eligible Spend | $0 | $100,000 | $150,000 | $200,000 | $450,000 | |
| Google Cloud Service Credits | $0 | $25,000 | $37,500 | $50,000 | $112,500 | |
| 2027 | Google Cloud Eligible Spend | $250,000 | $250,000 | $250,000 | $250,000 | $1,000,000 |
| Incremental Eligible Spend | $250,000 | $150,000 | $100,000 | $50,000 | $550,000 | |
| Google Cloud Service Credits | $62,500 | $37,500 | $25,000 | $12,500 | $137,500 | |
| 2028 | Google Cloud Eligible Spend | $250,000 | $250,000 | $250,000 | $250,000 | $1,000,000 |
| Incremental Eligible Spend | $0 | $0 | $0 | $0 | $0 | |
| Google Cloud Service Credits | $0 | $0 | $0 | $0 | $0 |
Incentive disbursement and restrictions
After incentives are calculated, they are disbursed according to a specific schedule and are subject to certain restrictions. The following sections provide details on the disbursement process and applicable limitations.
Disbursement to Designated Accounts
For each RaMP Agreement, RaMP incentives will be applied towards Fees from tagged workloads on the customer's primary billing account.
Payout Schedule: Google Cloud Services Credits
Disbursement will be within 45 days of each calendar quarter-end beginning with the quarter-end falling on June 30, 2026. For clarity, this means the first set of earned Google Cloud Service Credits for RaMP Agreements executed through June 30, 2026 would be deposited into the primary invoiced billing account (or, as applicable, the primary sub-account associated with the Relevant Customer) by August 15, 2026.
Payout Schedule: Partner Services Funds
Disbursement is tied to both statements of work completion and consumption milestones from incremental eligible spend on the RaMP 2026 SKU group.
Training and Implementation Services Funds; Google Cloud Consulting Services Funds
For Google Cloud Consulting services, RaMP incentives are issued using an Order Form for eligible, registered workloads. These incentives can be applied to partially or fully fund the project, as defined in the Statement of Work (SOW).
Additional RaMP Incentive Information
Expiration: If a workload is not fully migrated before the RaMP Agreement expiration, all future incentives for that workload growth are void.
Rollover: Workloads where migration work has started cannot be rolled over into a new RaMP Agreement