When your site starts to slow down, when you see messages about exceeding resource limits, or when you need to install software that shared hosting does not allow, it is probably time to move to a VPS server. Migrating may feel daunting: will you lose data? Will the site go down? In reality, migration is an orderly process that depends more on sequence than on expertise. In this guide, we explain step by step how to move from shared hosting to a VPS server on NVMe storage, with a practical checklist for every stage.
When Is Moving to a VPS a Necessity Rather Than a Choice?
Shared hosting is fine for small sites, but it places you in an environment whose resources are shared with many other sites. The need to migrate usually appears in clear cases:
- Frequent page-load slowdowns during traffic peaks, or messages indicating that usage limits have been exceeded.
- You need full administrative (root) privileges to install applications or change server settings.
- Restrictions on the number or size of databases, or on scheduled (cron) tasks.
- A need to run more than one site or test environment without one affecting the other.
If you encounter one or more of these situations, a VPS server gives you isolated, guaranteed resources, an independent operating system, and full control, at a monthly price higher than shared hosting but far lower than a dedicated server.
Preparation Before Migration: A Full Inventory First
The biggest migration mistakes start before the move itself, when the site owner discovers they forgot a database, a folder, or a DNS record. Take your time and complete the following inventory:
- Files: Identify the full path to your site files (root folder, images, plugins, themes) and calculate their size.
- Databases: List every database and its associated username, and export a full copy of each one.
- Domains: Write down the domain names linked to your site and the registrar that owns each domain.
- Email: If you use the hosting account's email, decide whether you will move it to the new server or to a standalone email service.
- SSL certificates: Make sure a new certificate can be issued on the new server before you cut over the old one.
- Scheduled tasks: Save a list of the current cron jobs and their schedules.
Do not start any step before you take a full backup of the current hosting and keep it in a separate, external location.
Steps to Migrate to Your New VPS Server
Once the inventory is complete, carry out the migration in the following order:
1. Order the new server: Choose a VPS plan with enough RAM and NVMe storage for your site with room to grow, and make sure it includes a dedicated IPv4 address, a control panel, and automatic backups. Open Vista servers are deployed in under 15 minutes from the my.openvista.ma portal.
2. Install the operating system: From the control panel, install an up-to-date Linux distribution (Ubuntu or Debian, for example) and save the initial login credentials in a secure place.
3. Set up the runtime environment: Install the web server and the programming language your site runs on (PHP for WordPress or Laravel, for example) as well as the database management system, then update all packages.
4. Move the files: Upload your site files to the correct path on the new server, preserving the folder structure and permissions.
5. Import the database: Create a new database and user on the new server, then import the copy you exported during the inventory phase.
6. Update the configuration files: Edit the connection files (database name, user, password, site URL) so they point to the new server.
7. Point the domain: Change the DNS records at your registrar to point to the new IPv4 address, bearing in mind that propagation may take some time.
Do not delete the old shared hosting account or cancel its subscription until you have fully confirmed that the site works on the new server.
After Launch: Testing and the Final Checklist
The migration does not end when you change DNS; finish with the most important phase:
- Test the site extensively: home and inner pages, forms, search, and any payment functions if present.
- Verify that the databases and the reports your site relies on work properly.
- Install an SSL certificate and enable HTTPS across the board.
- Reschedule the necessary cron jobs on the new server.
- Monitor CPU, memory, and storage usage from the control panel during the first few days.
- Make sure automatic backups are enabled, and test one actual restore before you need it.
- After a week of stability, quietly cancel the old hosting subscription.
Frequently Asked Questions
Q: Will my site go down during the migration?
It should not, if you follow the steps in the right order: the old hosting stays up until the files and the database are complete on the new server, and the destination changes only when you update DNS.
Q: How long does the full migration take?
It depends on the size of your site and on your experience. The technical transfer itself may take from one hour to several hours, while DNS propagation may take a few hours or even two days in some cases.
Q: What happens to my data if an error occurs during the migration?
That is why we recommend a full backup before you start, and not deleting your old account until you have confirmed that everything works on the new server.
Q: Can I start with a small plan and upgrade later?
Yes, and monthly billing with no contract on Open Vista plans lets you start with a suitable plan and upgrade or downgrade later according to your actual needs, without a long-term commitment.
Conclusion
Migrating from shared hosting to a VPS is not a gamble but a small, well-organized project: a full inventory, then the transfer in order, then careful testing before closing the old account. If you are ready to start, review the for VPS hosting from Open Vista and compare the specifications and prices yourself; to order and manage your server directly, use the my.openvista.ma. Open Vista's Arabic-speaking team is available to answer your questions before and after the migration.