Migrating from shared hosting to a Linux VPS is one of the most impactful infrastructure changes a growing business can make — but it requires careful planning to avoid data loss, email disruption, and extended downtime.

Before you initiate a server migration, you need to inventory everything on the shared host, create a verified backup, plan the DNS cutover, and confirm that applications function correctly in the new environment. AcuNett migrates dozens of servers per month from shared hosting to managed Linux VPS and dedicated server environments. Here is exactly what happens to your data — and how to protect it.

What Is Actually Stored on Your Shared Hosting Account?

Before any migration can begin, you need to understand what is on your current shared hosting account. Most businesses are surprised by how many pieces there are:

• Website files: HTML, PHP, CSS, JavaScript, images, and other assets that make up your website.
• Database(s): MySQL or MariaDB databases used by WordPress, WooCommerce, Joomla, Magento, or other platforms.
• Email accounts and messages: Email stored on the server, including sent, received, and archived messages from every mailbox on your domain.
• cPanel or control panel configuration: DNS zones, domain add-ons, subdomains, SSL certificates, and cron jobs.
• Application configuration files: wp-config.php, .env files, database connection strings, and other files containing credentials and settings.
• Log files: Access logs, error logs, and application-specific logs needed for troubleshooting or compliance.
• Addon domains and subdomains: Additional websites or staging environments hosted under the same account.

Missing any one of these components can result in a broken website, missing email, or a database error that takes time to diagnose after the DNS has been switched.

Step 1: Create a Verified Backup Before You Migrate Anything

The first rule of any server migration is: back up before you touch anything. This means a complete backup of your shared hosting account — not just the website files, but the databases, email, configuration files, and everything else in your account.

Verify the backup by doing the following: extract the archive and confirm that website files are present, check that database dump files are included and not empty, verify that email folders for each account are in the backup, and confirm that the backup includes addon domains and subdomains.

AcuNett's managed backup service uses ServerSync — our proprietary RAID-6 backup system — to maintain verified, tested backups throughout the migration process. If anything goes wrong during the migration, you have a restore point that we know works.

What Happens to Your Website Files During Migration

Website files are the most straightforward component of a migration. The process is: copy all website files from the shared host to the new Linux VPS using rsync, SCP, or by importing the cPanel backup; configure the web server (Apache or Nginx) on the VPS to serve files from the correct directory; test the website by accessing it via the VPS IP address before changing DNS; and confirm that all pages, forms, images, and functionality work correctly in the new environment.

The website continues to be served from the shared host during this entire process. Visitors see no change until DNS is updated to point to the new VPS.

What Happens to Your Databases During Migration

Database migration requires more care than file migration. The process AcuNett follows: export each database from the shared host as a SQL dump file; create matching databases and database users on the new Linux VPS; import the SQL dump files; update the application configuration files with the new database connection details; and test the application to confirm database connectivity before the DNS change.

One important note: if your database is actively updated during the migration window (orders placed, form submissions received), those changes occur on the old server and will not automatically appear on the new server. For business-critical applications, AcuNett coordinates a brief maintenance window to perform a final database sync immediately before the DNS cutover.

What Happens to Your Email During Migration

Email migration is where most self-managed migrations go wrong. Email is not static — new messages arrive continuously, and the window between moving email and updating DNS records can cause messages to go undelivered or bounce back to senders.

AcuNett's email migration process: recreate all email accounts on the new server; use IMAP synchronization tools (imapsync or offlineimap) to copy all existing email; lower the TTL on the MX DNS records 24–48 hours before the cutover; immediately after the DNS MX record change, run a final IMAP sync to capture any email that arrived on the old server during propagation; and confirm that the email accounts on the new server are receiving new messages correctly.

The DNS Cutover: Making the Switch

The DNS cutover is the moment your domain name stops pointing to the shared host and starts pointing to your new Linux VPS. To minimize the propagation window: lower the TTL on your DNS records to 300 seconds at least 24 hours before the planned cutover; confirm the new server is fully configured and tested; make the DNS change during a low-traffic period; monitor both the old and new server for traffic and errors; and keep the old shared hosting account active for at least 48–72 hours after the cutover as a fallback.

For the complete step-by-step process, see our detailed guide on Planning a Linux Server Migration Without Downtime.

How AcuNett Handles Server Migrations for Houston Businesses

AcuNett performs dozens of Linux server migrations per month for clients in Houston and worldwide. Our migration process is documented, tested, and refined over 25 years. We handle the complete migration — backup verification, server preparation, file and database transfer, email migration, DNS planning, SSL configuration, and post-migration testing. After migration, all servers enter our managed Linux server service with 24/7 monitoring and ongoing administration.

For Houston businesses with revenue-generating websites or business-critical applications, we coordinate migrations around your schedule to minimize disruption. Most migrations complete with less than 30 minutes of total downtime, and many complete with zero perceived downtime for end users.

Frequently Asked Questions: Linux Server Migration

Can I keep my old shared hosting account while migrating?

Yes, and AcuNett recommends keeping the old account active for at least 72 hours after the DNS cutover. This provides a fallback if any issues are discovered on the new server after the switch. Cancel the shared hosting account only after you have confirmed that everything is working correctly on the new Linux VPS.

How long does a shared hosting to VPS migration take?

A straightforward migration — one WordPress website, one database, standard email accounts — typically takes two to four hours of technical work. The migration timeline from start to DNS cutover is usually 24 to 48 hours to allow for testing and DNS TTL reduction. Complex migrations with multiple domains, large databases, or custom application configurations may take longer. AcuNett provides a timeline estimate before starting any migration.

Will my website be down during the migration?

With a properly managed migration, downtime is minimal — typically under 30 minutes during the DNS cutover window. The website continues operating on the old server while the new server is being prepared. Most visitors will not experience any downtime at all because DNS changes propagate gradually. AcuNett coordinates the cutover during your lowest-traffic window and monitors both servers throughout the process.

What if I discover something is missing after the migration?

AcuNett retains access to both the old server backup and the new server environment throughout the migration process and for a defined period after completion. If any files, database tables, or email messages are found to be missing after the cutover, we retrieve them from the pre-migration backup. This is why backup verification before starting the migration is so important — we need to confirm the backup is complete before we can use it as a safety net.

Do I need to update my website's database credentials after migrating to a VPS?

Yes. The database host, username, password, and database name on the new VPS will be different from the shared hosting values. AcuNett updates all configuration files (wp-config.php, configuration.php, .env, etc.) as part of the migration process. We also verify database connectivity by testing each application on the new server before the DNS cutover, so you know it is working before visitors are pointed to the new environment.