Google Cloud Exit Rights: How to Avoid Lock-In at Renewal

The Real Source of Google Cloud Lock-In

Lock-in is a word that gets used loosely in cloud procurement conversations. It often conjures images of technical dependencies — proprietary APIs, data formats, managed services with no open-source equivalent. Those technical factors are real, but they're secondary to the contractual factors that prevent enterprises from credibly threatening to leave at renewal time.

The most powerful tool Google has at renewal is your inability to demonstrate that you could realistically migrate. If your procurement team enters a Google Cloud renewal with no documented migration plan, no contractual data portability rights, and no history of testing alternative providers, Google's account team knows you won't leave regardless of the price it offers. The renewal discount you receive reflects the leverage you've built, not just the volume you spend.

This article is part of the Google Cloud contract terms negotiation guide. For the commercial deal structure that accompanies these legal provisions, see our Google Cloud PPA negotiation guide and our GCP negotiation leverage framework.

Google's Egress Fee Waiver: The Good News

One significant development that has genuinely improved the exit rights landscape for Google Cloud customers is Google's announcement that it will waive all egress fees for customers transferring data out of Google Cloud when exiting to another cloud provider or to on-premises infrastructure. This policy, formalised in 2024, means the data transfer cost that previously made large-scale Google Cloud exits prohibitively expensive has been eliminated for qualifying scenarios.

How the Waiver Works

The egress fee waiver applies to customers who are terminating their Google Cloud relationship and migrating to another provider. The customer must request the waiver from Google, document the migration intent, and execute the transfer within a defined window (typically 60 days). The waiver covers egress costs for data transferred out of Google Cloud infrastructure to external destinations.

What the waiver does not cover: egress fees for ongoing multi-cloud operations (where you're running workloads on both GCP and another provider simultaneously), cross-region data transfers within Google Cloud, or data transfers that occur before a termination notice is issued. The waiver is an exit mechanism, not a blanket elimination of egress charges.

Embedding the Waiver in Your Contract

Google's egress fee waiver policy is published but not automatically embedded in all enterprise contracts. For new agreements and renewals, Redress recommends requiring the following language in your Order Form or Service Schedule: "Upon Customer's notification of intent to terminate this agreement and migrate to an alternative cloud provider, Google shall waive all egress fees for data transferred out of Google Cloud infrastructure within 90 days of such notification, at no additional charge."

By embedding this in the contract rather than relying on Google's policy page, you have a contractual right rather than a published policy that Google could modify. Google's willingness to include this language is generally good because the underlying policy already commits them to it.

Data Portability: Getting Your Data Out in Usable Form

Eliminating egress fees is necessary but not sufficient for genuine exit rights. You also need contractual assurance that you can export your data in standard, portable formats — and that Google will provide the technical assistance required to execute the export.

What Google's Standard Terms Say

Google's standard Master Agreement includes a general provision that you can export your data at any time using the tools provided by Google's services. This sounds adequate but conceals several gaps. For highly managed services (BigQuery, Spanner, AlloyDB for PostgreSQL), the export capability exists but requires significant customer-side engineering. For operational data processed through Vertex AI or managed ML pipelines, the model artefacts and training data may be in formats that are technically exportable but operationally unusable without Google's ecosystem.

Negotiating Specific Portability Rights

Strong data portability provisions specify the format, timeline, and assistance obligations for exit-related exports. The key elements are: (1) open standard export formats (JSON, CSV, Parquet, open SQL formats) for all data categories, not Google-specific proprietary formats; (2) a contractual commitment to maintain export APIs for the duration of your contract term plus a defined post-termination period (typically 90-180 days); (3) Google-assisted migration support, including technical documentation and professional services credits for complex migrations; and (4) staged export capability — the right to export data categories incrementally rather than requiring a single complete export at termination.

Frame this negotiation in the context of business continuity. You're not asking for exit rights because you plan to leave — you're asking for them because your board and regulators require assurance that you're not creating irreversible dependencies on any single vendor. This positions the request as governance compliance rather than a bargaining adversarial move. The Google Cloud CUD negotiation process is a natural point to include these provisions as conditions of committing to multi-year spending.

API Continuity and Feature Deprecation Rights

For organisations building applications on Google Cloud APIs, the risk is not just that Google will change its pricing — it's that Google will deprecate or materially change APIs that your production systems depend on. Google's product strategy includes regular service deprecations, and the standard contract provides limited protection against the operational disruption these cause.

The Deprecation Risk Profile

Google's standard terms allow it to deprecate services or APIs with notice to customers. The notice periods vary: for Generally Available services, Google's deprecation policy commits to 12 months' notice for major deprecations. For Preview/Beta services, no minimum notice period exists. For changes that are characterised as "security patches" or "minor updates," changes can occur with no advance notice at all.

The business impact of an unexpected API deprecation on a production workload can be severe. Enterprises have experienced situations where a Google service deprecation forced an emergency re-architecture that consumed months of engineering resources, at costs that far exceeded the annual GCP spend on that service.

Negotiating API Stability Commitments

For critical APIs that your production systems depend on, negotiate service-specific stability commitments: "Google shall not make backward-incompatible changes to the APIs listed in Exhibit A without providing 12 months' prior written notice to Customer, and shall maintain the prior version of such API concurrently for a minimum of 12 months following release of any breaking change." List the specific APIs — do not rely on generic language about "Generally Available services."

This is particularly important for AI and ML services. The Google Gemini enterprise licensing guide covers model version stability in detail — Google's AI model deprecation cadence is significantly faster than its infrastructure service cadence, and the standard Gemini and Vertex AI terms provide minimal protection against disruptive model changes.

Termination-for-Convenience Rights

Termination-for-convenience provisions are standard in most enterprise cloud contracts, but the terms governing when and how you can terminate — and what happens commercially when you do — vary dramatically. Google's standard terms offer termination rights but attach significant financial consequences to early termination of committed services.

CUD and PPA Termination Consequences

If you've entered a Committed Use Discount (CUD) or Private Pricing Agreement (PPA), terminating early means paying for the remaining commitment. A three-year CUD with 18 months remaining means you owe 18 months of committed spend regardless of whether you continue to use the services. This is the commercial lock-in that accompanies the discount — and it's a rational trade if you're confident in your Google Cloud trajectory.

Where it becomes problematic is when business circumstances change — a merger, an acquisition, a regulatory requirement to repatriate data, or a strategic decision to consolidate on a different cloud platform. Without contractual protections, you face the choice between continuing to pay for services you're not using or paying a termination fee to exit early.

What to Negotiate

The most valuable termination provisions for enterprises are: (1) material change rights — the right to terminate without penalty if Google makes a material adverse change to the services or pricing; (2) change-of-control rights — the right to terminate if your organisation is acquired or undergoes a change of control, without incurring the remaining commitment; (3) regulatory exit rights — the right to terminate if a regulatory change makes it unlawful or commercially impractical to continue using the services; and (4) step-down provisions — the right to reduce commitment levels by up to 20-30% annually if business conditions change, without triggering penalty clauses.

Google will resist broad termination flexibility because it undermines the financial value of the commitment discount. The negotiating position is to frame these provisions as risk management rather than exit planning: "We're making a significant multi-year commitment. In exchange for that commitment, we need contractual protection against scenarios where continuation becomes impractical through no fault of our own." This framing acknowledges Google's commercial interest while asserting legitimate business needs.

Building Real Leverage: The Multi-Cloud Strategy

Contractual exit rights create theoretical leverage. Multi-cloud capability creates real leverage. The most effective Google Cloud renewal negotiations Redress has participated in all share a common characteristic: the customer had already demonstrated credible multi-cloud capability before entering the renewal conversation.

What Credible Multi-Cloud Looks Like

Credible multi-cloud doesn't require running 50% of workloads on AWS and 50% on GCP. It requires having 10-15% of workloads on an alternative provider, documented migration plans for an additional 20-30%, and an engineering team that has demonstrated they can execute cloud migrations. This is enough to change the conversation from "we need a discount because we spend a lot" to "we need competitive terms because we have validated alternatives."

The GCP negotiation leverage framework includes a multi-cloud readiness assessment that enterprise procurement teams can use to evaluate and build their leverage before entering a Google Cloud renewal cycle. The Google Workspace licensing negotiation process involves similar leverage considerations, particularly given the 17-22% price increase applied to Workspace in January 2025 with the Gemini AI bundling.

Using the Exit Rights Conversation as Leverage

Requesting strong exit rights during contract negotiations signals to Google's account team that you have multi-cloud options and are seriously evaluating them. Even if you have no immediate intention of migrating, the act of negotiating data portability terms, API stability commitments, and egress fee waivers demonstrates that you've done the work to understand what migration would require. Google account teams price this credibility signal into their negotiation positions.

The Exit Rights Checklist

Before signing a Google Cloud renewal or new agreement, confirm that these provisions are documented in your contract:

• Egress fee waiver: Contractual right to waive egress fees upon termination and migration, with defined timeframe.
• Data portability: Export rights in open standard formats for all in-scope data categories, with API access maintained for 90+ days post-termination.
• API stability: 12-month advance notice for breaking API changes on listed critical services, with concurrent version maintenance.
• Material change termination: Right to exit without penalty on material adverse changes to services or pricing.
• Change-of-control rights: Right to exit without penalty following qualifying change-of-control events.
• Regulatory exit: Right to exit without penalty if regulatory requirements prohibit continued service use.
• Commitment step-down: Annual right to reduce commitment by 20-30% without penalty trigger.
• Migration assistance: Defined professional services or credits to support exit migration for accounts above a defined spend threshold.

About the Author

Morten Andersen is Co-Founder of Redress Compliance, with 20+ years in enterprise software licensing and 500+ vendor engagements. He is Gartner-recognised for independent advisory on cloud and SaaS procurement. Connect on LinkedIn.