Agents cut each service migration from 3 months to 2 weeks
Sportswear brand On says it used a multi-agent approach to migrate 24 core services to Google Cloud, cutting each from three months to two weeks. Its engineers ran 15 of the migrations in-house, with under five minutes of planned downtime per service.
- Agent or tool
- Multi-agent migration (Google Cloud)
- Topic
- DevOps & Infra
- Reported on
- News (Google Cloud)
- Added
- 2026-10-29
Why it matters
Keeping servers and pipelines healthy is constant, detail-heavy work. Agents that can read logs and run routine fixes are a big help, as long as a person keeps an eye on what changes. It is one of 45 sightings filed under DevOps & Infra on Agent Sightings (number 1 by interest), and one of 1 involving Multi-agent migration (Google Cloud).
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Multi-agent migration (Google Cloud) or any similar agent and adjust the details to your situation.
Help me migrate this service to a new cloud. Map how it is deployed across our repositories, write the configuration scripts, replicate the data, and validate the new environment before we cut over.
Tip: Try it first on a staging system or with read-only credentials, and require approval for anything that changes production.
Source
Read the original first-hand account on News (Google Cloud): https://www.googlecloudpresscorner.com/2026-10-08-On-Establishes-Google-Cloud-a…. Our summary is a paraphrase; details are in the source.
Featured in these guides
Built an AI agent? Feature your agent on Agent Sightings, free submission or a featured spot.