← Website & VPS migration services
Independent migration planning · TheAppGuy

Still on Hostinger OpenVZ? Your legacy VPS needs a migration plan.

Hostinger is retiring its legacy OpenVZ VPS platform. These servers cannot be converted in place to KVM; the OS, files, databases and applications need to be moved or restored on another environment.

Plan before November 30, 2026OpenVZ → KVM · Linux VPS

What is changing?

Hostinger says OpenVZ plans are no longer renewable and that customers must move from legacy OpenVZ. Its current help article gives two different final dates: December 14, 2026 in the introduction and November 30, 2026 later on. Hostinger itself is not shutting down.

Because Hostinger's published article contains conflicting dates, aim to complete your move before November 30, 2026 and confirm your account's actual deadline with Hostinger. Do not assume your server or backups will remain accessible after that date.

Check the provider's official notice ↗ and any account-specific communications before deciding when to migrate.

Plan the move before the service ends

  1. Confirm that your account uses an OpenVZ-era plan rather than an existing KVM VPS. Check the plan name in the Hostinger dashboard.
  2. Document OS version, installed packages, databases, websites, email services, storage and external IP dependencies before making changes.
  3. Take complete off-server backups and database exports. Beware: Hostinger warns its direct reinstall path wipes the old server, so never run it without verified backups.
  4. Choose a compatible KVM Linux environment and restore files, databases and service configuration there. Evaluate operating-system and application version differences.
  5. Test website routes, login, email, certificates and integrations on the replacement environment; then plan DNS and IP changes and verify after cutover.

What we need to assess your server or site

  • Current provider and exact service or plan name
  • Domain(s), operating system, applications, databases, and background jobs
  • CPU, RAM, storage consumption, and typical traffic where applicable
  • Recent backup status, recovery requirements, and tolerance for downtime
  • DNS, email, firewall, certificate, integration, and IP-dependent dependencies

Independent migration support

TheAppGuy can review the workload and propose a supported destination, a migration scope, and an estimate. Any backup access, copying, test deployment or DNS cutover requires the customer's approval. We confirm compatibility and available capacity before making a commitment.

We are not affiliated with, sponsored by, or officially endorsed by Hostinger. A migration assessment is not a guarantee that we can accept every workload.

Next step

Request an assessment using the dedicated intake. Include your provider's shutdown email or deadline in the notes, but do not send passwords, tokens or private keys.

Request migration assessment →