Read the information on this page carefully to ensure that your migration to VPS 2016 is as smooth as possible.

Manual or automatic migration?

The Classic VPS 2014 can only be migrated to the equivalent model in the VPS SSD 2016 range manually.
The VPS Cloud 2014 can be migrated to the equivalent model in the VPS 2016 range manually or automatically.
.

Manual migration

We will assign you a new VPS from the new range and offer you a pro-rata refund in the form of credit if the price of the new VPS is less than the price paid for the old VPS. For example:
  • You have paid for a £10 VPS for three months
  • The new model costs £5 per month
  • You will not have to renew your VPS for a further three months to reflect the decrease in price.
In reality, the migration page will show you the exact new price and the exact renewal date before the migration.

Your old VPS will remain active for five days so that you can migrate your services at your own pace. It will be suspended after this five-day period.

Your new VPS will be assigned to you as soon as you have requested it, and you will activate it the same way you would if you had ordered it: after a few minutes you will receive an email in your OVH account explaining how to access your VPS 2016.
.

Automatic migration

This is only available on VPS Cloud. Your VPS will be converted to OpenStack format and started up on the new infrastructure.
Careful! This method has the following limitations:
  • No guarantee: we have tested and successfully migrated our templates, but certain configurations made after the VPS has been assigned to you (firewall, services configured on public IP, specific network configuration, etc.) may prevent your VPS from working on the new infrastructure.

  • Service interruption: we have to turn off your VPS and copy your disk onto the new infrastructure. The operation takes at least 30 minutes, plus a variable length of time based on the size occupied by your VPS.

-Change of IP address: your VPS is going to change IP address and has to be in DHCP in order to work on the new infrastructure.
When you request your VPS to be migrated automatically, we will give you its future IP address and perform the migration six hours later. This is so you can launch it at night and have time to transfer your domain name.

To ensure a smooth migration on Linux (there is no need to do anything with Windows), please follow these steps:
  • Move to DHCP
  • # Debian based
    /etc/network/interfaces
    auto lo
    iface lo inet loopback
    auto eth0
    iface eth0 inet dhcp

    # Debian based
    /etc/network/interfaces
    auto lo
    iface lo inet loopback
    auto eth0
    iface eth0 inet dhcp

  • Deactivate the udev rules
  • #rm -f /etc/udev/rules.d/70-persistent-net.rules
    #rm -f /lib/udev/write_net_rules
If you encounter a problem, we recommend you use the KVP and rescue mode (in the Control Panel) so you can correct your VPS's configuration.
After migration, when everything is working correctly, you may:
  • Uninstall VMwareTools (they will no longer be necessary)
  • Reactivate your VPS's SLA monitoring via the Control Panel or API
We will keep your old VPS for 15 days after migration, so if you don't manage to get your VPS to work on the new infrastructure, restart your old VPS on demand within this time frame. All changes made in between will be lost.

Start my VPS migration

Before starting your migration, make sure to back up your data.
  • Make sure that you have understood the migration process. If you have any doubts or questions, contact us and we will help you make sure the migration goes as smoothly as possible.
  • Go to
  • the migration request page and log in with your OVH NIC handle.
  • Select the VPS that you want to migrate to in the dropdown list.
  • Select your preferred migration mode (automatic or manual).
  • Select the datacentre destination.
  • The page will provide you with the new price, your service's new expiration date and the new IP if you wish to migrate automatically.
  • All you have to do is accept the conditions to start the migration.