Inventory, sizing, rehearsal, DNS and rollback: the complete method to move from shared hosting to a VPS without taking your site offline.
By Mouhamed BANKOLE, CEO at ITNET Technologies · Updated 13 October 2026 · Reading time: 8 min
Your shared hosting is hitting its limits: slow pages at peak times, interrupted jobs, an imposed PHP version. Moving to a VPS looks obvious, but a failed VPS migration costs more than an undersized server: site down, lost emails, duplicate orders. This guide gives you the complete method to migrate without downtime, from inventory to rollback.
In short
- A VPS migration is justified by a measured need, not by a feeling that the site is slow.
- The inventory (domains, emails, jobs, integrations) prevents hidden failures after the switchover.
- Rehearse the migration on a test address before touching DNS.
- Lower the DNS TTL in advance and keep the old hosting active during the observation period.
- A rollback defined in advance lets you decide quickly, without pressure.
Contents
- When should you move from shared hosting to a VPS?
- What should you inventory before migrating?
- How do you size the target VPS?
- How do you prepare the VPS before the transfer?
- How do you rehearse the migration safely?
- How do you handle DNS and the final switchover?
- How do you validate the site after switching?
- How do you plan a rollback?
- What changes in day-to-day operations?
- FAQ
When should you move from shared hosting to a VPS?
Move to a VPS when a concrete need can no longer be met on shared hosting: resources, software version, long-running jobs or isolation. If the concept is still unclear, our guide on VPS in France also covers what to check with a provider.
Signals that justify the migration:
- Quotas are reached: processes, memory or execution time capped by the host.
- A software version is imposed: PHP, Node.js or a database you cannot change.
- Long jobs get cut off: imports, exports, scheduled processing.
- Several applications must run side by side with different settings.
On the other hand, a heavy theme or a badly written plugin will stay slow after the migration. Measure before concluding that shared hosting is to blame.
💡 Pro tip Also list what your shared hosting handles for you today: updates, certificates, backups, emails. On a VPS, these tasks become yours, and their cost belongs in your budget.
What should you inventory before migrating?
The inventory lists everything that must follow the site: it is what prevents hidden failures after a seemingly successful switchover.
To record before any copy:
- Domains and subdomains, with their DNS records.
- Files and databases, with their size.
- Mailboxes hosted with the old provider.
- Scheduled jobs (cron) and their timing.
- TLS certificates and redirects.
- External integrations: payment, APIs, webhooks, SMTP, analytics.
- Secrets: passwords and API keys, to rotate rather than copy.
Email is the most common trap. If your mailboxes are with the old host, plan their move to a professional email service before changing the MX records.
How do you size the target VPS?
Size the target VPS from real measurements, with headroom for peaks, without buying several years of growth on day one.
Data to collect:
- File and database volume, and monthly growth.
- Average and peak traffic.
- Memory and CPU time used by the application.
- Heavy jobs: imports, backups, report generation.
Add the consumption of the system, web server, database, monitoring and backups. For an online store, our guide on choosing a VPS for an online store details this method.
Then compare these needs with Wayhost VPS plans, checking how you move up a tier.
How do you prepare the VPS before transferring data?
The VPS must be secured and equipped before it receives the site, not after.
In this order:
- System up to date, unnecessary services disabled.
- Named accounts and SSH key login.
- Web server, runtime and database installed with documented settings.
- TLS configured following the OWASP TLS cheat sheet.
- Off-server backups, monitoring and log rotation in place.
The NIST SP 800-123 guide recommends handling server security across its whole lifecycle. On WordPress, also apply the official hardening documentation.
How do you rehearse the migration safely?
A rehearsal means migrating a copy of the site to the VPS, without touching DNS, so you know every step and how long it takes.
What to check on the copy:
- Pages, forms and logins.
- Orders and payments in test mode.
- Scheduled jobs and transactional emails.
- Absolute paths, file permissions, mixed content.
Access the site through a protected test hostname or a local host entry. Fix the procedure, then repeat until the switchover becomes routine.
| Step | During rehearsal | On the day |
|---|---|---|
| Copy of files and database | Full | Sync of changes only |
| DNS | Unchanged | Changed last |
| Tests | Exhaustive | Critical journeys |
| Old hosting | Active | Active during observation |
| Duration | Measured | Known in advance |
How do you handle DNS and the final switchover?
Prepare the switchover by lowering the DNS TTL in advance, then sync the data one last time before changing the records.
The sequence:
- Lower the TTL of the relevant records one or two days before.
- Pick a quiet window for your business.
- Pause writes if the application allows it.
- Sync the database and changed files.
- Change the DNS records, then check resolution from several networks.
If your domain is managed elsewhere, bringing your domain names and DNS zone closer to your VPS simplifies future switchovers.
How do you validate the site after switching?
Validate as a customer would, on the journeys that matter, not just the home page.
Test immediately:
- Contact form and sign-up.
- Account login.
- Test payment and confirmation email.
- TLS certificate and redirects.
Then monitor 4xx and 5xx errors, memory, CPU and the database. Compare the volume of orders or form submissions with a normal period.
How do you plan a rollback?
Define the rollback before the switchover: who decides, at what threshold, and how DNS is restored.
The three points to write down:
- The failure threshold: payment errors, lost writes, abnormal error rate.
- The procedure: restore DNS records and reconcile data written in the meantime.
- The observation period, after which the old service is shut down cleanly.
Keep configurations, logs and exports for a few weeks: they help explain a late anomaly.
What changes in operations after the migration?
After the migration, the VPS becomes a platform to operate: patches, backups, access and capacity are now your responsibility.
The routine to set up:
- Security patches on a fixed schedule.
- Regular restore tests.
- Access reviews and rotation of temporary secrets.
- Capacity tracking and a threshold for moving up a tier.
Agencies hosting several client sites can go further with our guide on VPS hosting for web agencies.
Frequently asked questions
How long does a VPS migration take?
The copy can take minutes, but inventory, rehearsal and observation take several days. Time each step during the rehearsal before setting the switchover date.
Does the site have to go offline during the migration?
Not always. A short pause in writes or a final sync is often enough. Transactional sites need a precise strategy to avoid diverging data.
When should you change DNS?
After the site has been fully validated on the VPS and the rollback is ready. Lower the TTL in advance and keep the old hosting active during observation.
What happens to my emails during a VPS migration?
They do not move automatically. If your mailboxes are with the old host, migrate them before changing the MX records, or messages may be lost.
Do you need technical skills to migrate to a VPS?
Yes, basic Linux administration is needed: SSH, web server, database, DNS. Without these skills, get support or choose a managed offer.
What should you do after the migration?
Monitor key journeys, check backups, apply a patch schedule and review access. Document the platform for the next intervention.
Key takeaways
- Migrate for a measured need, not on a feeling of slowness.
- Inventory everything, emails and integrations included, before the first copy.
- Rehearse the migration on a test address until every step is known.
- Prepare DNS and rollback before the switchover.
- Run the VPS over time: patches, backups, access, capacity.
Ready to prepare your target? Wayhost VPS plans scale up without reinstallation and run on immersion-cooled servers.
Article written by Mouhamed BANKOLE, CEO at ITNET Technologies, publisher of Wayhost.cloud.