Loading
Moving an existing application to Google Cloud — planned against your actual constraints, with a rollback at every step.
The problem
The cron job on the old box. The hardcoded IP. The certificate someone renews manually. A migration plan built from a diagram misses all of it, which is why we start by finding out what is really running.
What we do
Stack we use here
How it runs
We inventory what is actually running, not what the documentation claims.
Sequenced so that any single step can be reversed without a bad night.
Non-critical services first, so the process is proven before the important part moves.
DNS moves last, after the new environment has been serving real traffic in parallel.
Specifics
A cloud engagement is easy to describe vaguely, so here is the concrete list.
Deliverables
FAQ
Where this sits