Guide an AI to move your SaaS between cloud providers

A developer used Claude Code to help shift a product from AWS to DigitalOcean, handling infrastructure, data migration, certificates, and launch-day fixes.

Done with Claude Code· Intermediate

What they did
They brought Claude Code in as a coding partner while setting up the new DigitalOcean environment with GitHub Actions. The agent assembled the droplet, managed Postgres, Spaces, and Docker pieces, then looked through failed job output with the gh CLI to track down problems and update the workflows. It also adjusted the database import for psql SSL, cleaned owner links in the dump, created Cloudflare origin certificates for nginx, and repaired the SPA proxy setup.
How it went
By the developer’s account, the transfer was done in about four hours without downtime. It covered 29 tables and over 3,000 rows, and the monthly bill went from around $120 to about $44. One mismatch between VITE_API_URL and VITE_API_BASE sent the frontend to localhost and took 20 minutes to sort out.
Tips
Double-check that every environment variable name matches the code path that reads it. For any step that could affect live traffic or data, have the agent pause and wait for approval first.

Try it yourself with Claude Code

Help me migrate [app name] from [current host] to [new host] as a hands-on coding partner. Start by scanning the repository and drafting a phased plan for provisioning, database transfer, SSL, DNS switching, and fallback if something breaks. Then carry out the work with me one stage at a time, and before any step that could change production, DNS, delete data, send messages, or take money, stop and show me the exact command, file change, or action for approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on dev.to ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.