VPS Migration Planning Guide

List domains, DNS zones, application paths, databases, cron jobs, SSL certificates, and third-party integrations.

Confirm what must move, what can be retired, and what should stay with the current provider.

Capture panel access, SSH/SFTP access, database credentials, and registrar access before scheduling migration.

Choose the operating image, web server stack, database version, PHP or runtime versions, and firewall baseline.

Provision backups and monitoring before production traffic is moved.

Stage the application on the new VPS and validate paths, permissions, services, and environment variables.

Lower DNS TTL before migration when possible and document the final switch timing.

Keep the old environment available until traffic, forms, payments, logins, and background jobs are verified.

Define a rollback decision point before the migration window begins.