HonestHostGuide is a free website. We research hosting plans, write the reviews, and keep the renewal numbers next to the intro prices so you can see what a plan really costs after year one. To keep that work going, some of the links on this site are affiliate links.

That means: if you click a link to a host we partner with and you buy a plan, we may earn a commission. You do not pay more because of that link. The price you see on the host’s own checkout is the same whether you arrive through us or go there directly.

The regular and renewal prices here are snapshots from the date shown, not guaranteed prices. They can change. Our cost projections assume today’s rates stay the same and leave out extras unless we say otherwise.

Moving WordPress hosts does not have to mean a day of “site down for maintenance.” The reliable pattern is boring: build the new copy first, test it privately, then flip DNS with a short TTL. Cancel the old plan only after the new one has been healthy for a few days.

This is a checklist, not a first-hand migration story. Where a host markets free migrations (Kinsta lists unlimited free migrations; Cloudways Autonomous lists free managed migration on Growth), treat that as the provider’s offer — read their current terms before you rely on it.

Before you touch anything

  1. Write down why you are moving. Renewal shock, need staging, need more resources, support issues — the reason decides whether you go shared → shared, shared → Cloudways, or up to managed WordPress (Kinsta).
  2. Pick the destination plan using renewal/ongoing price, not the intro banner. See our renewal-first notes in the Hostinger review, the Kinsta review and the intro vs renewal price table.
  3. Inventory the site: WordPress version, PHP version, active plugins/themes, object cache, cron jobs, CDN, forms, payment webhooks, and email (many cloud hosts do not include mailboxes — Cloudways email is an add-on).
  4. Export a full backup from the current host (files + database). Download a copy off-server. Don’t trust a single backup location.
  5. Note DNS: registrar, current A/CNAME/MX/TXT records, and whether email stays at the old host, Google Workspace, or elsewhere. MX mistakes are the silent migration killer.
  6. Lower TTL on the apex and www records to 300 seconds a day before the cutover (if your DNS host allows).

Choose a migration method

Method When it fits Watch-outs
Host-offered free / managed migration You bought a plan that includes it (e.g. Kinsta unlimited free migrations as published; Cloudways Autonomous free managed migration as published) Queue times; confirm what they migrate (files, DB, email, DNS help)
Plugin migration (Duplicator, All-in-One WP Migration, Migrate Guru) Match the tool and host limits to the site; no blanket size/zero-downtime promise All-in-One free export/backup supports any size, but free Import is constrained by the host upload limit; paid Unlimited adds one-click Restore and bypass uploads. Migrate Guru lists up to 200 GB and five site migrations/user/month. Duplicator supports migration, but free/Pro feature claims in its listing overlap: check the exact edition before assuming advanced features are free.
Manual (SFTP/SSH + phpMyAdmin/WP-CLI) You know what you are doing; complex custom setups Easy to miss uploads, .htaccess/nginx rules, or cron
Agency / freelancer Business-critical store or membership site Costs money; still follow the DNS/email checklist yourself

If you are choosing a destination, compare Hostinger (budget shared/cloud), Cloudways Flexible (managed cloud from $11/mo, 1 GB), and Kinsta (managed WP from $35/mo) on intro vs ongoing price first.

Build the new site without cutting the old one

  1. Provision the new hosting account and leave the old one paid and running.
  2. Create the empty WordPress (or empty DB + files) on the destination.
  3. Copy files (wp-content at minimum; full tree is safer) and import the database.
  4. Run a search-replace for the old domain → temporary URL or final domain carefully (serialised data-aware tool). WP-CLI wp search-replace handles PHP serialized data; use --dry-run first and keep a backup. If you test on a temporary hostname, plan a second replace at cutover.
  5. Match PHP version and required extensions to the old host as closely as practical.
  6. Re-install object cache / Redis only after basics work — or leave it off until post-cutover.
  7. Disable or reconfigure caching, security, and redirect plugins that hard-code the old host.
  8. Private test: hosts-file override or host-provided staging/temporary URL. Click login, checkout (test mode), forms, media, and wp-admin.

Don’t point public DNS at the new host until this private test passes.

How to switch WordPress hosting with minimal downtime

  1. Put the old site in maintenance mode only if you must freeze comments/orders for a final DB export. Many content sites can skip this if the final delta is small.
  2. Final data sync: export a fresh DB (and any new uploads) from the old host; import delta to the new host.
  3. Issue SSL on the new host (Let’s Encrypt or host SSL) for the real domain before or immediately as DNS flips — order depends on host DNS validation rules.
  4. Update DNS A/AAAA/CNAME to the new host. Leave MX alone unless email is also moving.
  5. Watch propagation. TTL governs record caching, not a guaranteed migration completion time. Cloudflare documents a default TTL of Auto (300 seconds) for proxied records but warns your local DNS cache may take longer; your DNS provider and previously cached TTLs matter.
  6. Smoke-test on a phone network (not your Wi-Fi that might still hit old DNS): homepage, wp-admin, cart, login, contact form.
  7. Update Search Console / analytics / payment webhook URLs if the host or URL path changed.
  8. Keep the old host running several days as rollback insurance. Only then cancel — and confirm email is not still tied there.

After the move

  • Re-enable CDN and purge caches.
  • Confirm cron runs (wp cron or real system cron as the new host recommends).
  • Check robots.txt and indexing if you used a temporary “discourage search engines” flag on staging.
  • Document the new SFTP/SSH, backup schedule, and renewal date (especially on Hostinger-style prepaid terms).
  • Re-read the destination’s refund/trial window: Hostinger 30-day MBG on hosting; Kinsta gives new customers the first month free on select plans. Its 30-day money-back guarantee for first-time customers then applies from the renewal date, once the free period ends. Cloudways offers a trial rather than a classic MBG.

Common ways migrations “fail” without the server being down

  • MX pointed at the web host by accident → email dies while the website looks fine.
  • Hard-coded old URLs in theme options or Elementor/page-builder CSS.
  • Object cache / Redis left half-configured → random blank pages.
  • PHP version mismatch → white screen of death only on the new host.
  • Cancelling the old plan too early → no rollback when DNS is sticky.

FAQ

Can I migrate with zero seconds of downtime? You can get near-zero public downtime by testing privately first and flipping DNS after a final sync. Absolute zero is rare if you need a write-freeze for ecommerce; plan a short maintenance window for stores.

Should I use the host’s free migration? If it is included and your site is straightforward, yes — still run your own backup and private test. Read what they exclude (email, multisite, huge DB).

Do I need a VPS to migrate “properly”? No. Most migrations are shared-to-shared or shared-to-managed-cloud. Buy resources for the workload, not for migration theatre.

Where should I move if renewal prices shocked me? Compare ongoing rates: Hostinger Premium $10.99/mo after intro; Cloudways Flexible from $11/mo (1 GB) on standard pay-as-you-go rates that don’t jump at renewal (time-limited promotional discounts may apply); Kinsta $35/mo for managed WP.

Read next

Sources / method note

Checklist compiled from general WordPress operations practice plus the providers’ own published terms and documentation.

See our affiliate disclosure page.