Skip to content

AS213941 · Peering-20% on all VPS with code NVH20 · Delivered in 60 seconds

Linux VPSFrom €2.49/monthWindows VPSFrom €3.49/monthFiveM serverFrom €0.99/monthMinecraft serverFrom €1.99/month
VPS & Cloud

Ranges

Linux NVMe VPSRoot access, Debian, Ubuntu, Alma…Windows RDP VPSRemote desktop, licence includedDedicated serversIntel Xeon Gold, exclusive resourcesPterodactyl VPSGame panel preinstalled

Network and hosting

Anti-DDoSWeb hostingColocationIP transitVPN

Professionals

Reseller VPSReseller programme
Solutions

Bots and automation

AI agents VPSA server for your coding assistants and autonomous agentsOllama VPSYour private AI without a GPU, data in FranceTelegram bot VPSPython or Node.js, always reachableDiscord bot VPSMusic, moderation, tickets: no downtimeVinted bot VPSMonitor and Discord alerts 24/7n8n VPSWorkflows with no execution limitVPN VPSAn encrypted tunnel exiting in FranceWeb scraping VPSScheduled data collection, dedicated IP

Trading

Forex VPSYour robots manage positions overnightMetaTrader 4 VPSSeveral MT4 terminals on one machineMetaTrader 5 VPSForex, indices and stocks in MT5NinjaTrader VPSFutures and NinjaScript strategiesProp firm VPSChallenges and funded accounts, terminal always onlineAfrica trading VPSMetaTrader in Paris, from North or West AfricaRDP VPSWindows remote desktop, always onTrading bot VPSOpen-source crypto bots, protected API keys

Broker and prop firm VPS

FTMO VPSDedicated French IP, outside the USFundedNext VPSPrivate VPS for your EAsThe5ers VPSFixed IP, consistent locationIC Markets VPSWithout the 15 lots a month quotaPepperstone VPSMT4, MT5 and cTrader, fixed priceXM VPSNo $5,000 minimum balanceExness VPSSmall accounts welcome, 7 ms to London

Windows desktop

Windows 10 VPSFor software that requires Windows 10Windows 11 VPSA modern Windows desktop, reachable anywhereSEO VPSLarge-site crawls without tying up your PCStreaming VPSAn OBS studio streaming from the data centreWordPress VPSFast websites on NVMe disks
Marketplace

AI

OllamaLocal language models, with no external APIOpen WebUIA chat interface for your Ollama modelsAnythingLLMA private AI assistant for your documentsLangflowVisual editor for agents, RAG flows and AI APIsFlowiseBuild AI agents and chatbots visuallyQdrantVector database for RAG and semantic search

Trading

MetaTrader 5Official MT5 terminal, ready for your EAsMetaTrader 4Official MT4 terminal, ready for your EAsForex VPS pack (MT4 + MT5)MT4 and MT5 together, on a VPS tuned for tradingNinjaTrader 8NinjaTrader 8 with its prerequisitesFreqtradeOpen-source crypto trading bot, in simulation modeInteractive Brokers TWS / IB GatewayTWS or IB Gateway, official stable version

Bots and agents

Claude CodeAnthropic's coding agent, in your terminalCodex CLIOpenAI's command-line coding agentTelegram botYour Telegram bot, with automatic restartDiscord botYour Discord bot, with automatic restartOpenClawOpen-source personal AI assistant, active 24/7Hermes AgentAutonomous open-source AI agent

Deployment and automation

DockerThe container engine and Docker Composen8nYour automations, with no execution limitPortainerManage your Docker containers from your browserCoolifyDeploy your applications from Git, on your own serverUptime KumaMonitor your sites and servers, with alerts

Websites and databases

WordPressThe most widely used CMS, on a fast Nginx stackApache + PHP + MySQLApache, PHP and MariaDB, ready for your sitesMySQL (MariaDB)MySQL-compatible database serverPleskPlesk hosting panel, with your own licenceNextcloudYour own cloud for files, calendar and contacts

Network and security

WireGuardYour encrypted VPN, preinstalled free of chargeVaultwardenA self-hosted password manager

Game servers

FiveMFiveM server with txAdmin and MariaDB, ready to useMinecraftTurnkey Minecraft Java server, plugins and mods includedRustRust server with automatic updates and Oxide or CarbonCounter-Strike 2Dedicated Counter-Strike 2 server, installed for youPalworldDedicated Palworld server, installed for youValheimDedicated Valheim server, installed for you
Gaming

Game servers

FiveM servertxAdmin, ESX, QBCoreMinecraft serverJava, Bedrock, modpacksRust serverOxide, Carbon, wipesNova-Life serverNova-Life: Amboise RP

Protection and tools

FiveM Anti-DDoSFree tools
Resources

Learn

DocumentationBlog

Assistance

ContactSLA commitment
View plans Client area Peering · AS213941

Installation

Migrating a website to a VPS with no service interruption

By the NVHCloud team · 2026-09-18 · 5 min read

Moving a website to a VPS is not risky if you follow a precise order: copy everything, test everything on the new server, and only change the DNS at the very end. Throughout the preparation, visitors keep using the old hosting without noticing anything. This method works for PHP, static and Node.js sites; for WordPress, our dedicated guide migrating WordPress to a VPS with no downtime (in French) covers the steps specific to that CMS.

1. The principle

  1. You set up and fill the new server alongside the old one.
  2. You test it by fooling only your own computer about the site's address.
  3. You switch the DNS once everything works, with a short TTL so the switch is fast.
  4. You keep the old hosting active for a few days, as a safety net.

2. Take inventory

Before touching anything, list what makes up the site:

  • Files: code, media uploaded by users, configuration files.
  • Databases and their credentials.
  • Scheduled tasks (cron) on the old hosting.
  • The PHP or Node.js version and the extensions used.
  • Email: are the mailboxes with the old host? If so, they do not move with the site, and the MX records must not change.
  • The full DNS zone, exported or copied down.

3. Prepare the DNS the day before

Lower the TTL of the A, AAAA and www CNAME records to 300 seconds. Wait at least the length of the old TTL before switching: that way, on the day, every visitor follows the change within five minutes. Details in configuring DNS.

4. Prepare the VPS

Install the same software stack as the old hosting, in an equal or newer compatible version: web server, PHP or Node.js, database. Follow, as appropriate, Nginx, the PHP stack for WordPress or Node.js with PM2, without requesting a certificate yet: Let's Encrypt can only validate the domain after the DNS switch. Secure the server right away too: first steps and firewall.

5. Copy the files and databases

Files. If the old hosting provides SSH access, rsync is the ideal tool, run from the VPS:

rsync -avz --progress [email protected]:~/www/ /var/www/mysite.com/

The benefit of rsync: run a second time just before the switch, it only copies what changed in the meantime. Without SSH access, download an archive over FTP or from the host's panel, then send it to the VPS with scp.

Databases. Export from the old hosting, with mysqldump over SSH or the panel's export tool, then import:

mariadb -e "CREATE DATABASE mysite CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"
mariadb mysite < export.sql

Create the database user as described in securing MariaDB, then put the new credentials in the site's configuration. Finally, restore ownership: chown -R www-data:www-data /var/www/mysite.com.

6. Test before the switch

This is the step that makes the migration risk-free. On your computer only, pretend the domain already points to the VPS by adding a line to the hosts file:

# Windows: C:\Windows\System32\drivers\etc\hosts (editor run as administrator)
# macOS and Linux: /etc/hosts
203.0.113.10  mysite.com www.mysite.com

Open the site in a private browsing window: you see the VPS version, while the rest of the world still sees the old one. Test everything that matters: main pages, forms, login, sending email, payment in test mode, file uploads. HTTPS is not in place yet: accept the browser warning, or test over HTTP.

Also watch the server's error log during your tests: tail -f /var/log/nginx/error.log.

7. Switch over

  1. If the site receives data (orders, accounts, comments), freeze it: maintenance mode on the old hosting.
  2. Run rsync again and redo the database export and import to pick up the latest data.
  3. Change the A and AAAA records to the VPS address. Do not touch the MX records.
  4. Remove the line you added to your hosts file.
  5. As soon as dig +short mysite.com returns the new address, get the certificate: certbot --nginx -d mysite.com -d www.mysite.com --redirect.

8. After the migration

  • Keep the old hosting active for one to two weeks: a few visitors with stubborn caches still land there, and it is your fallback plan.
  • Recreate the scheduled tasks noted in the inventory.
  • Set up backups from day one: see backups with Borg.
  • Raise the TTL to an hour or more once everything is stable.
  • Watch Search Console over the following days: crawl errors point to a forgotten page or a missing redirect. See Google indexing and sitemaps.

Frequently asked questions

Does migrating to a VPS hurt SEO?

No, if page addresses stay the same and the site stays reachable during the switch. Google does not care about the host but about content, addresses and speed, which usually improves. Losses come from pages that change address without a redirect.

How long does a migration take?

Preparation takes from an hour to a day depending on the size of the site. The switch itself takes a few minutes if the TTL was lowered the day before, and visitors see no interruption.

Will my email keep working?

Yes, as long as you do not change the MX and TXT records related to email. Changing the site's address only requires editing the A and AAAA records and the www CNAME.

How do I test the site on the VPS before changing the DNS?

By adding a line to your computer's hosts file that maps the site's name to the VPS IP address. Only your computer then sees the new version; remove the line once testing is done.

WordPress VPS

Your sites on NVMe, no limits, Anti-DDoS included.