I recently migrated a production website from Vercel to my own VPS, using Coolify and Cloudflare. I let Codex (GPT-6.1 Terra High) handle pretty much the entire process.
For context, the migration involved:
- Moving the application from Vercel to the VPS using Coolify
- Configuring DNS, domains and Cloudflare
- Setting up backups, rollback procedures and security checks
- Testing deployments, routing and connectivity
- Switching production traffic with zero downtime
- Setting up a fallback to Vercel through Cloudflare Workers in case the VPS goes down
The good news is that everything worked. The site is now running on my VPS, the migration happened without downtime and I'm happy with the result.
What surprised me was the amount of work involved. The whole process consumed roughly 70% of my weekly Codex usage allowance on the Plus plan.
There was a lot of back and forth between testing, debugging, changing configurations and verifying that everything was working correctly across Coolify, Cloudflare and Vercel.
Now, this was my first time handling this kind of migration, so I didn't really know what to expect. I understand that we're talking about production infrastructure and that being careful with backups, rollback options and downtime is important. I'm definitely not expecting something like this to be done in five minutes.
I'm just trying to understand whether this level of resource consumption is normal for a migration of this scope, or if there's something I could have done differently to make the process more efficient.