Base de conocimientos | VPSGrid
BetaEspañol
EnglishBeta EspañolPortuguês (Brasil)Coming soonFrançaisComing soonDeutschComing soonBeta translation — some areas may still appear in English.
Área de cliente

Migrate from HostGator to VPSGrid VPS

hostgator to vps migration, hostgator vpsgrid, migrate wordpress hostgator, hostgator vps transfer, leave hostgator vps, hostgator dns cutover 0 found helpful

Migrate from HostGator to VPSGrid VPS

Unmanaged Migration — You Execute Cutover

VPSGrid does not offer zero-downtime migration services or managed site transfers from HostGator. You backup, sync, test, and change DNS. Keep HostGator active until the VPSGrid copy is verified.

Short answer
  1. Provision Linux VPS at vpsgrid.net and install LEMP stack
  2. Export HostGator files (FTP/SFTP or cPanel backup)
  3. Dump MySQL database from HostGator phpMyAdmin or CLI
  4. Import to VPSGrid MariaDB and rsync files to /var/www
  5. Test via VPS primary IP or hosts file
  6. Lower DNS TTL, update A record, obtain SSL with Certbot

Overview

This guide covers the steps and checks you need on an unmanaged VPSGrid VPS. Guest OS configuration remains your responsibility unless a separate managed product is documented on your account.

VPSGrid provides unmanaged KVM VPS hosting. You are responsible for backups, OS configuration, application data, and guest-level security. VPSGrid manages hypervisor infrastructure, network connectivity, power controls, and billing. Review What Is an Unmanaged VPS at VPSGrid? and Security Responsibilities on Unmanaged VPS before relying on support for guest OS tasks.

Infrastructure

Hosted on US-Based KVM infrastructure using NVMe storage.

VPSGrid operates from its US-Based infrastructure datacenter while serving customers across the United States. Plans run on KVM virtual servers on Proxmox VE with NVMe storage. Plan sizes and current pricing appear at checkout on vpsgrid.net — knowledgebase articles do not publish fixed dollar amounts because promotions and tiers change.

Why move from HostGator to VPSGrid

HostGator shared and reseller plans bundle convenience with resource limits and shared neighbors. A VPSGrid unmanaged Linux VPS gives dedicated CPU, RAM, and NVMe for your workload — you control PHP versions, caching, and firewall rules. Trade-off: you operate the stack, backups, and security patches inside the guest OS.

This guide targets typical WordPress or PHP sites leaving HostGator cPanel. Adapt paths if you run custom applications.

VPS migration cutover flow on VPSGrid Migration Cutover Flow (Customer-Executed) Source host Sync files Import DB Test on IP DNS cutover VPSGrid unmanaged VPS — no zero-downtime guarantee from provider You control timing, backups, and rollback to source IP if needed Lower DNS TTL before final A record change
Diagram: Typical customer-executed migration: sync, import, test, then DNS cutover to VPSGrid VPSGrid VPS.

Prerequisites before leaving HostGator

Step 1: Export from HostGator

Files via SFTP or rsync

From your workstation or VPSGrid server, pull files with SFTP credentials from cPanel → FTP Accounts. For large sites, rsync from VPSGrid reduces repeated manual downloads:

rsync -avz --progress user@hostgator-host:~/public_html/ /var/www/example.com/
Tip

Run rsync multiple times before cutover — final pass captures last-minute content changes with minimal downtime.

Database export

In cPanel → phpMyAdmin, export each application database as SQL. For InnoDB WordPress DBs, use custom export with --single-transaction equivalent if using SSH on HostGator Business plans:

mysqldump -u cpaneluser_dbuser -p cpaneluser_wordpress > hostgator-wp.sql

Step 2: Import on VPSGrid

Create database and user

sudo mysql -e "CREATE DATABASE wordpress DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;"
sudo mysql -e "CREATE USER 'wpuser'@'localhost' IDENTIFIED BY 'NEW_STRONG_PASSWORD';"
sudo mysql -e "GRANT ALL PRIVILEGES ON wordpress.* TO 'wpuser'@'localhost';"
sudo mysql -e "FLUSH PRIVILEGES;"
mysql -u wpuser -p wordpress < hostgator-wp.sql

Update wp-config.php

Set DB_NAME, DB_USER, DB_PASSWORD to VPSGrid MariaDB credentials. If URLs changed, plan WP-CLI search-replace after import — see Migrate WordPress from Shared Hosting to VPSGrid (Wave 2 companion).

Step 3: Configure Nginx and test

Create server block pointing root to imported files. Test with VPS primary IP before DNS changes — Point Your Domain to a VPSGrid VPS documents A record behavior.

curl -I http://YOUR_VPS_IP/

Step 4: DNS cutover (customer-executed)

Lower TTL at your DNS host 24–48 hours ahead. During maintenance window: final rsync, final DB dump/import, update A record to VPSGrid IP, verify site, then issue SSL via Let's Encrypt SSL with Certbot on VPSGrid.

No Zero-Downtime Guarantee

Concurrent writes during cutover can diverge databases. Put HostGator site in maintenance mode for the final DB export or accept brief read-only period.

Common HostGator migration mistakes

MistakeSymptomFix
Wrong document rootDefault Nginx pageMatch HostGator public_html path to Nginx root
Serialized URL replaceBroken widgetsUse WP-CLI search-replace
Missing cronScheduled posts failAdd system cron for wp-cron.php
phpMyAdmin max uploadPartial SQL importSplit dump or use CLI mysql import

Security after migration

Rotate HostGator and WordPress passwords — old credentials may exist in tickets. Enable How to Configure UFW Firewall on Ubuntu/Debian, Fail2ban Setup on VPSGrid Linux VPS, and define backups per Backup Best Practices for VPS Owners.

Rollback plan

If critical failure occurs post-DNS, revert A record to HostGator IP until issues are resolved on VPSGrid. Keep HostGator subscription active until TTL expiry and acceptance testing complete.

Need more capacity?

Compare Linux VPS plans at billing.vpsgrid.net/store/linuxvps if HostGator traffic exceeded shared limits. Open a support ticket for billing or network scope questions — not hands-on migration labor on unmanaged plans.

DNS TTL and cutover planning

Before migrating from HostGator, Bluehost, DigitalOcean, or any shared host to VPSGrid, lower DNS TTL on records you will change (A, AAAA, CNAME) to 300 seconds (five minutes) at least 24–48 hours before cutover. High TTL values cache old IPs at resolvers worldwide and extend perceived downtime even after you update the authoritative zone.

VPSGrid does not guarantee zero-downtime migrations. You execute file transfers, database imports, and DNS changes. Plan a maintenance window, communicate it to stakeholders, and keep the source site online until you verify the VPSGrid copy.

Staging versus in-place migration

A staging VPSGrid server lets you rehearse imports without touching production DNS. Clone files and database to the staging IP, test checkout flows (WooCommerce), permalinks, and cron jobs, then repeat the procedure on production during cutover. Staging adds cost but reduces rollback risk on unmanaged hosting where you own every step.

Serial number and inode preservation

rsync -avz preserves permissions and timestamps — critical for WordPress uploads and plugin licensing tied to paths. For large media libraries, initial sync may take hours; run incremental syncs until cutover minute, then a final delta sync with minimal write lock on the source database.

Database consistency during export

Logical dumps with mysqldump --single-transaction (InnoDB) avoid long table locks on busy stores. For MyISAM-heavy legacy hosts, schedule exports during low traffic. Always verify row counts and spot-check orders after import on VPSGrid MariaDB.

Email and MX records

Web migration does not automatically migrate email mailboxes. Document MX, SPF, DKIM, and DMARC before changing A records. If email stays at the old provider, only web DNS changes during VPS cutover.

Rollback strategy

Keep the source hosting active with a recent backup until DNS TTL expires and you confirm stability. If critical issues appear post-cutover, revert A records to the old IP and investigate on VPSGrid using logs — support assists with hypervisor and network scope per Security Responsibilities on Unmanaged VPS.

SSL during migration

Obtain Let's Encrypt certificates on VPSGrid only after HTTP resolves to the new server on port 80, or use DNS-01 challenges if HTTP validation is impractical during parallel hosting. Mixed-content warnings after HTTPS often trace to hard-coded http:// URLs in the database — plan search-replace with WP-CLI or similar tools.

Staging VPS rehearsal

Clone migration steps to a staging VPSGrid instance before production cutover. Staging validates import integrity without DNS risk — decommission staging after acceptance or keep for plugin testing.

Maintenance mode during final sync

Enable WordPress maintenance mode or static holding page on source host during final database export to prevent new orders or comments from being lost during cutover.

WHOIS and registrar locks

Ensure domain registrar credentials are accessible before migration weekend. DNS changes fail if registrar locks or expired domains block updates.

CDN and proxy services

If Cloudflare or similar proxies your old host, update origin IP to VPSGrid primary address and purge cache after cutover to avoid stale content.

Post-cutover monitoring

Watch error logs for 48 hours after DNS change. Spike in 404 or 502 errors often indicates incomplete URL replace or PHP-FPM misconfiguration.

Staging VPS rehearsal

Clone migration steps to a staging VPSGrid instance before production cutover. Staging validates import integrity without DNS risk — decommission staging after acceptance or keep for plugin testing.

Maintenance mode during final sync

Enable WordPress maintenance mode or static holding page on source host during final database export to prevent new orders or comments from being lost during cutover.

WHOIS and registrar locks

Ensure domain registrar credentials are accessible before migration weekend. DNS changes fail if registrar locks or expired domains block updates.

CDN and proxy services

If Cloudflare or similar proxies your old host, update origin IP to VPSGrid primary address and purge cache after cutover to avoid stale content.

Post-cutover monitoring

Watch error logs for 48 hours after DNS change. Spike in 404 or 502 errors often indicates incomplete URL replace or PHP-FPM misconfiguration.

Staging VPS rehearsal

Clone migration steps to a staging VPSGrid instance before production cutover. Staging validates import integrity without DNS risk — decommission staging after acceptance or keep for plugin testing.

Maintenance mode during final sync

Enable WordPress maintenance mode or static holding page on source host during final database export to prevent new orders or comments from being lost during cutover.

WHOIS and registrar locks

Ensure domain registrar credentials are accessible before migration weekend. DNS changes fail if registrar locks or expired domains block updates.

CDN and proxy services

If Cloudflare or similar proxies your old host, update origin IP to VPSGrid primary address and purge cache after cutover to avoid stale content.

HostGator-specific migration notes

HostGator shared and reseller plans typically use public_html as the web root. Addon domains may map to subfolders under public_html — confirm the exact path in cPanel → Domains before rsync. Compare PHP versions between HostGator and your VPSGrid LEMP stack; major PHP jumps may require plugin compatibility testing.

Email and DNS caution

Changing the website A record does not automatically move email. If MX records stay at HostGator, leave them unchanged during site migration. Document which DNS records you modify to avoid accidental mail disruption.

Should you migrate now?

Migrate when you have a tested VPSGrid copy, a maintenance window, and backups on both sides. VPSGrid does not guarantee zero downtime — plan a final delta sync during low traffic.

Frequently Asked Questions

Does VPSGrid migrate my HostGator site for me?

No. VPSGrid provides unmanaged KVM VPS. You export files and databases from HostGator and import them on your VPS. Support scope is documented in Security Responsibilities on Unmanaged VPS — guest OS migration tasks remain customer responsibility.

Can I migrate without downtime?

VPSGrid does not guarantee zero-downtime migration. You can minimize outage by syncing data before cutover, testing on the VPS IP, then lowering DNS TTL and switching A records during a planned window. Some downtime during final database sync is typical.

Do I need cPanel on VPSGrid?

VPSGrid Linux VPS does not include HostGator-style cPanel by default. You manage Nginx or Apache, PHP, and MariaDB via SSH — see How to Deploy WordPress on Ubuntu VPS for LEMP setup.

What about HostGator email?

Email mailboxes often remain at HostGator or another provider. Update only web DNS (A/AAAA) unless you also migrate MX records. Document SPF/DKIM before cutover.

Related Articles

Next steps on VPSGrid

Planning a self-managed migration? You can prepare your new environment on a VPSGrid Linux VPS and move your site when you are ready. VPSGrid does not perform managed site transfers — you control backups, sync, and DNS cutover. If you hit infrastructure blockers (provisioning, network reachability), open a support ticket with your service ID and steps already tried.

Need More Help?

Search this knowledgebase for related guides. If the issue persists, open a ticket at billing.vpsgrid.net with your service ID, primary IP, and steps already tried. See What Information to Include in a Support Request and Security Responsibilities on Unmanaged VPS for scope and required details.

¿Le ha resultado útil esta respuesta?

Artículos relacionados