Skip to content

How to migrate to TMDHosting

Moving an existing site to TMDHosting — what they handle for you, what you'll do yourself, and the safe order to do it in.

Free migration not advertised
Support during your move: live chat, phone, ticket

Choosing a Plan

TMDHosting's shared plans scale predictably: Starter (1GB RAM, 1 vCPU) at $9.52/month, Essentials (2GB RAM, 2 vCPU) at $12.72/month, or Enterprise (4GB RAM, 4 vCPU, unmetered storage) at $19.12/month. Renewals jump 25–30%. Match your current resource use — if your existing site averages under 1GB RAM during peaks, Starter suffices. All plans include a 30-day money-back window for testing.

Pre-Migration Prep

  1. Back up everything: Export your database (MySQL dump, PostgreSQL pg_dump) and compress site files.
  2. Lower DNS TTL: Set your domain’s TTL to 300 seconds (5 minutes) at least 48 hours before migration. This minimizes downtime during cutover.
  3. Note credentials: Document current database users, server paths, and any cron jobs.

Transfer and Test

  1. Upload files: Use SFTP or the file manager in TMDHosting’s control panel to replicate your site’s directory structure.
  2. Import the database: Create a new database and user via the hosting panel, then restore your dump. Update configuration files (e.g., wp-config.php) with new credentials.
  3. Test via temporary URL: TMDHosting provides a preview URL (e.g., http://serverip/~username). Verify functionality — check forms, logins, and static assets. Our tests showed 495ms TTFB and 11s fully loaded time; use this as a baseline to flag slowdowns.

DNS Cutover and Post-Move Checks

  1. Update DNS: Point your domain’s A/AAAA records to TMDHosting’s server IP. With a 5-minute TTL, propagation typically completes within an hour.
  2. Monitor: Use dig or online tools to confirm DNS updates. Watch for 502 errors (resource limits) or broken paths — TMDHosting’s live chat, phone, and ticket support can assist.
  3. Verify HTTPS: Install a TLS certificate if your site requires SSL. Check mixed content warnings via browser dev tools.

Post-migration, test peak traffic handling. Our measurements showed 1140ms server response time in our tests; sustained spikes may require upgrading to Essentials or Enterprise.

Visit TMDHostingRead the full TMDHosting review