iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To move an OpenVZ VPS to KVM, you must either use the dashboard’s KVM reinstall flow—which wipes the existing server—or build a new KVM VPS and migrate your files and configuration manually. There is no in-place conversion. Back up and verify your data before starting, then test the new server before directing your domain to its new IP.
Before you migrate: confirm the plan and deadline
Check your VPS details in your account to confirm whether it is an OpenVZ server. Hostinger identifies legacy VPS plans purchased before April 18, 2023 as OpenVZ and labels KVM plans in the dashboard. The date alone is not a substitute for checking your actual plan.
Hostinger’s current migration guide lists two different OpenVZ shutdown dates: December 14, 2026 in its opening notice and November 30, 2026 in its section about doing nothing. Because those dates conflict, do not rely on either as definitive. Check the deadline shown in your account or contact Hostinger to confirm the date that applies to your VPS. Hostinger Help Center migration guide.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsChoose the migration route that fits your server
| Route | Best fit | Main trade-off |
|---|---|---|
| Dashboard reinstall | A relatively simple server that you can recreate and restore from backups | The existing server is completely wiped. Verify your backups before you start. |
| Manual migration | A complex setup with custom services or configuration you need to rebuild carefully | You must set up the new server, transfer and restore data, test services, and switch DNS yourself. |
Hostinger describes the dashboard flow as the streamlined choice for most users and manual migration as an option for complex setups. In either case, the destination is a new KVM VPS: Hostinger says the different virtualization architectures prevent an automatic conversion. The dashboard flow selects a new KVM plan and applies credit for unused OpenVZ subscription time, according to Hostinger’s guide.
#1 Best Overall
Prepare backups and plan the transfer
- Back up the files, configuration, and other data you need. If you run a database, make a fresh dump and confirm you can access and restore it.
- Keep the backup somewhere separate from the old VPS. The dashboard reinstall wipes that server, so do not begin until you have verified that the required backup is complete.
- Choose a KVM data center that suits your users, while accounting for transfer logistics. Hostinger says OpenVZ and KVM VPSs in the same location cannot communicate for direct SCP, rsync, or WHM transfer. You can download backups and upload them to the new VPS, or choose another location for the KVM server.
- Plan for a different IP address on the KVM VPS. Note any services, allowlists, or other systems that refer to the old address so you can update them after migration.
- Schedule the work during a low-traffic period. Hostinger advises allowing up to 24 hours for DNS propagation after you change the domain’s A record.
- Check any licenses you bought through Hostinger: its guide says these do not transfer to the new VPS.
Option 1: Use the dashboard reinstall flow
- Sign in to your Hostinger account and open the VPS migration or reinstall option for the OpenVZ server.
- Select a new KVM plan and review the plan and unused-subscription credit shown in the flow.
- Before confirming, verify that your backups are complete and stored somewhere other than the server being reinstalled. Starting this process completely wipes the existing server.
- Complete the dashboard flow, then configure the new VPS and restore your data and applications.
- Test the site and other services on the new VPS. Only after they work should you update your domain’s A record to the new VPS IP.
Option 2: Migrate manually to a new KVM VPS
- Create backups of the files and configuration you need, and make fresh database dumps where applicable.
- Provision a new KVM VPS in your chosen data center and install the operating system you intend to use.
- Install the applications and services required by your environment. Hostinger gives Apache, PHP, MariaDB, Redis, and Node.js as examples; install only what your setup needs.
- Transfer the backups. If both VPSs are in the same location, Hostinger says direct SCP, rsync, or WHM transfer between them is not available. Download the backups and upload them to the KVM VPS, or use a different location for the new server.
- Stop the relevant services on the old VPS before the final transfer to reduce the risk of copying data while it is changing. Restore files to their intended locations and restore database dumps.
- Adjust configuration for the new environment, including hostnames and IP-address references where needed. Confirm that required applications and services start successfully.
- Test the site and other services on the new VPS before changing DNS. When testing passes, update the domain’s A record to the new VPS IP and allow time for DNS propagation.
After the move: verify traffic and dependent systems
Once you change DNS, check that the domain resolves to the new VPS and that the site and other services continue to work. Also update any systems that depend on the old IP, such as allowlists or integrations, and watch for failures during the DNS transition. Keep the old server available until you have confirmed the migration is complete and no needed data or service was missed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to get technical help
If you are unsure how to recreate custom configuration, restore data, or diagnose application failures, consider hiring a qualified Linux administrator or VPS migration specialist. Hostinger says its support staff cannot perform the migration on your behalf and recommends hiring a developer for configuration difficulties.
Quick Recap
Best Value
- Ultimate Freshness & Flavor: The condiment caddy’s lower compartment ingeniously holds ice cubes or crushed ice, actively keeping vegetables, sauces, or fruits succulent and fresh for hours. Each top compartment features a removable lid for easy access
- Safe, Stylish & Complete with Accessories: Crafted from sturdy, BPA-free PET plastic, our condiment organizer offers food safety and elegant aesthetics. The set includes 2 metal clips and 5 metal spoons for grabbing and scooping fruits, vegetables, and sauces. The crystal-clear design provides a seamless view of contents, perfect for beautifully presenting fruits, salads, or any treats. (Note: Avoid direct contact with hot food.)
- Modular Capacity for Every Need: Each individual lidded compartment 5.7"(14.4cm) × 3.8"(9.7cm) × 2.4"(6.2cm) holds 2.5 cups, ideal for single servings. The complete set includes 5 removable compartments fitting perfectly into the main tray 15.7"(40.6cm) × 6.2"(15.8cm) × 5.1"(13cm), offering ample total capacity
- Effortless Cleaning & Clear View: Constructed from transparent plastic, this garnish tray offers a clear view of stored food and ice. After use, it conveniently rinses clean with water. For thorough hygiene and longevity, HAND WASHING is highly recommended. (Important: Not dishwasher safe.)
- Versatility for Every Celebration: This fruit tray transforms into your go-to server for family gatherings, picnics, BBQs, and indoor/outdoor parties! Use it as a convenient hot dog/pizza toppings station, stylish bar garnish caddy, vegetable/fruit tray, or a complete taco bar serving set
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
