Practical guide

How to move WordPress site to new host: list the services, copy the site, switch DNS

Last reviewed October 6, 2026

Quick answerList what the site depends on, copy its files and database to the new host with a migration plugin, switch DNS, then check forms, email and HTTPS.

Prepare an inventory of the whole service

To move a WordPress site to a new host, list what it depends on, copy its files and database to the new server, then switch DNS and check each dependency; Cloudways's free WordPress Migrator plugin does the copy, and Cloudways engineers move the first site for free.

A functioning website can depend on domain registration, DNS, hosting, email, media delivery, payment services and external integrations. Inventory those dependencies before copying files. Record the service name, its purpose and the person who controls it without collecting passwords in the document. A migration that preserves the homepage but breaks order notifications or renewal access has not preserved the business service the client expected.

Cloudways's 3-day trial lets you migrate a copy of your site to a new server without a credit card.

We may earn a commission if you buy through links on this page, at no extra cost to you.

Start a 3-day Cloudways trial →

Identify changing and retained components

Mark each dependency as moving, staying or requiring a separate decision. A website can move hosts while its mailboxes remain with the same provider. That distinction matters when editing DNS: web records may change while mail-routing records should remain intact. If ownership is unclear, resolve it before a cutover depends on that access. Do not infer permission to change an account simply because a previous developer mentioned it in a handoff note.

Capture the data timing

Record when the source snapshot was taken and what can change afterward. A static brochure and a store receiving orders need different reconciliation plans. Note scheduled jobs, imports and external services that might write to the application during the move. This inventory is not a backup by itself; it explains which data and activities must be represented in the actual transfer and which could be lost if timing is ignored.

Verify the inventory at launch

After the move, check each retained or changed dependency against its original purpose. The agency running the move should be able to explain how a form reaches the intended inbox, how an administrator signs in and who pays the next invoice. Keep the old environment available according to the approved recovery plan until the new one is accepted. The inventory then becomes a useful operating record rather than a document discarded at launch.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labeled so you can separate product claims from independent evidence.

  1. Cloudways getting-started documentation — Merchant documentation · support.cloudways.com · Merchant-controlled · read September 21, 2026
  2. Cloudways sender-domain and email DNS setup — Merchant documentation · support.cloudways.com · Merchant-controlled · read September 21, 2026
  3. Cloudways free website migration page — Vendor product page · cloudways.com · read October 6, 2026
  4. How to request a managed application migration to Cloudways — Vendor documentation · support.cloudways.com · read October 5, 2026
  5. Cloudways pricing — Vendor pricing page · cloudways.com · read October 6, 2026
  6. Cloudways home page and FAQ — Vendor product page · cloudways.com · read October 6, 2026