Google overhauls cloud modernization portfolio with new AI agents
Google is overhauling its cloud modernization portfolio by bringing its existing migration and modernization tools along with new agentic migration tools and a new Modernization Hub under a new Google Cloud Modernize umbrella to accelerate infrastructure and application transformation at enterprises.
Google is overhauling its cloud modernization portfolio by bringing its existing migration and modernization tools along with new agentic migration tools and a new Modernization Hub under a new Google Cloud Modernize umbrella to accelerate infrastructure and application transformation at enterprises.
The new agentic tools include an EKS-to-GKE Migration Agent, designed to help enterprises move Kubernetes workloads from Amazon EKS to Google Kubernetes Engine (GKE).
The agent can analyze existing EKS environments, translate Kubernetes manifests, map storage and networking requirements, and help prepare workloads for deployment on GKE, with human approval points built into the process, the company wrote in a blog post.
Alongside that agent, Google is also adding new capabilities to its Migration Center’s Quick Estimator Agent. These new capabilities will allow enterprise users to generate total cost of ownership estimates from infrastructure data, including VMware inventory exports, and test different migration scenarios and cost assumptions in natural language.
The Migration Center itself is being rolled into Cloud Modernize and will continue to offer tools around migration planning and assessment.
Beyond the agentic capabilities and the Migration Center, the hyperscaler is consolidating its application modernization tools, such as the App Modernization CLI, Java and .NET modernization capabilities, and mainframe tools including the Mainframe Assessment Tool, Dual Run and Mainframe Connector, under a new Modernization Hub.
In context
- Topic: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Source: CIO
- Published: 06/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
IT governance rarely fails for lack of technology. It fails for lack of clarity about who decides what. A story like this one is usually the visible symptom of an operating model that no longer fits the size of the organisation, and those models get changed before the pressure arrives, not after.
When I look at a move like this, the question is not which tool they bought but which capability was left installed: an architecture function that holds the line on criteria, a prioritised portfolio with real business owners, and metrics somebody actually reviews every week. Without that, any announcement dissolves within twelve months.
What usually goes wrong
What usually goes wrong is the part never discussed with the areas that will carry the work. It gets decided at the top, communicated downward, and the resistance shows up not as opposition but as slowness. Nobody says no; everything simply takes twice as long and nobody can explain why.
What to watch
- How the relationship with current vendors is left, which is usually where the dependency nobody measured is sitting.
- Who ends up owning the decision, and with what budget of their own rather than borrowed.
- Whether business metrics appear or only delivery metrics — cost per transaction beats percentage complete.
How I read this entry
If this landed on my desk, the first thing I would ask for is not a plan. It is an honest inventory of what is already running and what it costs to keep it alive. It almost always turns out that the budget for the new thing comes from switching off something old that nobody wants to name, and that conversation decides whether the project lives.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
