1. Map the deployment path
Write down how code, database changes, environment variables, domains, and rollback are handled. A plan that is easy to deploy but hard to recover can be expensive.
Hosting decision guide
Compare hosting by the work you will actually operate.
The cheapest first-year price can hide the decisions that matter later: recovery, support, renewal, and how easily you can leave. Use this checklist before moving a personal site or small business project.
Disclosure: this is an independent checklist. No paid affiliate link is active on this page. Confirm current pricing, renewal terms, limits, and cancellation rules on the provider’s official site.
2. Price the second year
Record introductory pricing, renewal pricing, add-ons, domain fees, backups, email, and support. Compare the total for the exact stack you will run.
3. Test the exit path
Check whether you can export files and data in a usable format, change DNS without a support ticket, and keep your domain independent of the host.
4. Verify recovery and support
Look for backup frequency, restore scope, support hours, escalation, and a documented incident path. Treat “backup” and “tested restore” as different claims.
5. Match the plan to real demand
Estimate traffic, storage, background jobs, team access, and compliance needs. Avoid paying for scale you cannot yet measure, but leave room for a safe upgrade.