Quick answer: Export your site files and database from the shared hosting control panel, order a Cloud2Y VPS, set up a web server and database (directly or via a control panel), import your data, test with a hosts-file override, then point your domain's DNS at the VPS. The main difference from shared hosting: on a VPS you manage the server yourself.

Overview

Shared hosting hides the server from you; a VPS gives it to you. That means more power — your own resources, any software you want, no neighbor effects — and more responsibility: you (or a control panel) handle the web server, updates and security. This guide covers the generic move; for WordPress specifically see migrating WordPress to Cloud2Y.

Before you start

  • A Cloud2Y VPS (how to order) — pick a plan with more disk than your current usage plus room to grow.
  • Access to your shared hosting panel (cPanel, Plesk or similar) to export files and databases.
  • A decision: manage the VPS directly via SSH, or install a control panel for a familiar interface.

Step-by-step guide

  1. Export from shared hosting: download a full backup or use the file manager to archive your webroot, and export each database via phpMyAdmin (Export → SQL).
  2. Prepare the VPS: install your stack — for example Nginx/Apache, PHP and MariaDB — or a free control panel, then create the site and database.
  3. Upload files: transfer the archive with SFTP or rsync and unpack it into the new webroot.
  4. Import the database: mysql -u user -p dbname < dump.sql, then update the site's config file with the new database credentials.
  5. Test before DNS: map your domain to the VPS IP in your local hosts file and click through the site — see testing before the switch.
  6. Switch DNS to the VPS IP and install SSL on the new server.

Common issues

  • PHP version differences: shared hosts often run older PHP — match it first, then upgrade deliberately.
  • File permissions: after upload, the web server user must own the webroot (chown -R www-data:www-data on Debian/Ubuntu).
  • Email surprises: shared plans bundle mailboxes; a VPS does not — plan mail separately, e.g. migrate the accounts or use a mail provider.

When to contact support

If exporting from your shared host is restricted, or you would rather not assemble the server side yourself, request a free migration — moving people off shared hosting is the most common job we do.

Frequently asked questions

Is a VPS harder to manage than shared hosting?

It gives you more responsibility: OS updates, security and the web stack are yours. Installing a free control panel restores the familiar interface while keeping VPS power.

What happens to my shared-hosting email accounts?

They do not move automatically. Plan mail separately: migrate mailboxes with imapsync to a mail server on the VPS, or switch the domain to a dedicated email provider.

Which VPS size should I choose when leaving shared hosting?

Check disk usage in your hosting panel and add growth headroom. Most sites leaving shared hosting run comfortably on an entry SSD or NVMe VPS and can upgrade later without reinstalling.

Related articles

Ready to move? Order a VPS at Cloud2Y →

Was this answer helpful? 0 Users Found This Useful (0 Votes)

Most Popular Articles

How the Cloud2Y migration process works

Quick answer: Cloud2Y offers assisted migration: you open a support ticket, our engineers audit...
How to request a free migration

Quick answer: Cloud2Y offers free assisted migration for customers moving to a Cloud2Y server....
How to prepare your website for migration

Quick answer: Before migrating, take a full backup, document your stack (PHP, database, web...
How to migrate from another VPS provider

Quick answer: With root access on both sides, VPS-to-VPS migration is the cleanest kind:...
How to migrate from Contabo to Cloud2Y

Quick answer: Provision a Cloud2Y VPS with a similar or newer OS, copy your data from the Contabo...