Google folds cloud migration agents into a single Cloud Modernize push

Google is folding its migration and modernization tools into a new Cloud Modernize umbrella, adding AI agents that can move EKS workloads to GKE.

In 30 seconds Google has grouped its cloud migration and modernization services under Google Cloud Modernize. The package adds an EKS-to-GKE Migration Agent and a Quick Estimator Agent, and puts application and mainframe tools into a console-based Modernization Hub.

What happened

Google is overhauling its cloud modernization portfolio by putting existing migration and modernization tools together with new agentic migration tools and a Modernization Hub under the Google Cloud Modernize umbrella. The first new agent, an EKS-to-GKE Migration Agent, is designed to move Kubernetes workloads from Amazon EKS to Google Kubernetes Engine. According to Google, it can analyze an existing EKS environment, translate Kubernetes manifests, map storage and networking requirements, and prepare workloads for GKE deployment, with human approval points built in.

The Migration Center is also being rolled into Cloud Modernize. Its Quick Estimator Agent gains capabilities to generate total cost of ownership estimates from infrastructure data, including VMware inventory exports, and to test migration scenarios and cost assumptions in natural language. Google is consolidating application modernization tools as well: the App Modernization CLI, Java and .NET modernization capabilities, and mainframe tools including the Mainframe Assessment Tool, Dual Run and Mainframe Connector will live under a new Modernization Hub, accessible through the Google Cloud Console.

With the broader offering, CIOs require fewer handoffs, faster decisions and better visibility across a large modernization program.

Pareekh Jain, principal analyst at Pareekh Consulting

Google is grouping its migration and modernization services under Cloud Modernize.

Why it matters

Analysts argue that consolidation can simplify operations. Pareekh Jain points out that an enterprise may run VMware workloads, Java applications, mainframes, Oracle databases and Kubernetes applications across different clouds. Previously, those domains needed separate tools, assessments and migration teams. A broader offering gives CIOs fewer handoffs, faster decisions and better visibility across a large modernization program.

Viet-Anh Nguyen, machine learning lead at Scopic Software, says the EKS-to-GKE agent can reduce repetitive engineering because it can discover and translate AWS-specific infrastructure and Kubernetes configurations, validate the outputs and create pull requests for human review. Jain cautions that the agent does not remove testing, architectural decisions, data migration or production cutover. Teams still own those steps.

What we don’t know yet

The announcement does not answer pricing, general availability dates or supported EKS versions for the new agents. It also does not spell out how the Modernization Hub will handle workloads that span several clouds or how much manual validation remains before a pull request can be merged. For now, the useful question is not whether the agents can translate manifests, but where your team will still need a human owner.

Opinion · The number that worries me

The number that worries me: Google's EKS-to-GKE Migration Agent can create pull requests for human review, yet it still leaves testing, architectural decisions, data migration and production cutover to the team. That is the part vendors rarely put in the headline. The agent reduces repetitive engineering, but ownership of the risky cutover does not move. If your cloud migration is already understaffed, automation on the discovery and translation layer may only accelerate the arrival of the hard decisions.

Related articles from LaRebelión

AI agents create fresh cybersecurity risks and liability dilemmasGoogle pauses its open-source bug bounty as AI slop floods maintainersOpenAI Under Fire: California Subpoenas Rogue Hacking Agents

Original source: Network World

Produced with AI support and reviewed by the newsroom

Byline · Chief editor · English edition · London

“The agent writes the pull request; your team still owns the production cutover.”