How to Move a WordPress Site to a New Host Without Losing Email or Data

You can move a working WordPress site to another host by copying its files and database, testing the new server, and changing DNS only after the copy works. Keep the old hosting account active during testing and DNS propagation, and treat email as a separate service unless the new host confirms mailbox migration.

Before paying, identify your domain registrar, DNS provider, email provider, site type, file and database size, PHP requirements, and the new host's preview and migration options. A shared or managed WordPress plan may fit a small site, while cloud or VPS hosting makes more sense when you need more server control or resources.

Key takeaways

• 1Make a complete backup and export the full DNS zone before changing anything.
• 2Move files and the database first, then preview and test the new site.
• 3Preserve MX, SPF, DKIM, DMARC, and other mail records unless email is moving too.
• 4Keep the old host active until the new site, DNS, email, and backups are confirmed.
• 5Read the current US price, renewal, refund, migration, backup, and cancellation terms before paying.

What You Need Before Moving a Live WordPress Site

Start by writing down where each part of the website lives. The domain may be registered at one company, DNS may be managed somewhere else, and email may run through the current web host, Google Workspace, Microsoft 365, or another provider. Your WordPress site may be a normal single-site installation or Multisite, which affects migration eligibility.

Make a complete backup of the WordPress files and database. The files include WordPress core, themes, plugins, uploads, and configuration. The database contains posts, pages, settings, users, orders, comments, and other structured content. Keep the original backup in a location you can access if the new server needs to be restored.

Export the current DNS zone before changing A records or nameservers. Include A, CNAME, MX, TXT, SPF, DKIM, DMARC, SRV, and subdomain records. MX records direct incoming email to mail servers, while SPF, DKIM, and DMARC help receiving providers assess whether messages are authorized.

Check the new host's current PHP version, database support, storage limits, SSL process, plugin and theme requirements, and preview method. Ask for written confirmation of the migration scope, including whether it covers files, databases, email accounts, message history, cron jobs, DNS, custom SSL, and non-WordPress applications.

Keep the old host active during the move. Read its cancellation and data-retention terms before ending the account, because stored backups, email, and the old site may become inaccessible after cancellation.

The Safe Order: Backup, Build, Migrate, Test, Then Change DNS

The safest sequence is to create a recoverable copy, prepare the destination, migrate the site, test it privately, and only then change public DNS. WordPress's documented manual sequence starts with a complete backup, database export, new database and user creation, file upload, database import, and wp-config.php updates.

Open the new hosting account and confirm that your selected product fits the site. Shared hosting is usually intended for smaller sites sharing server resources. Managed WordPress hosting can reduce server administration because the provider handles more WordPress-related tasks. Cloud hosting can provide a different resource model, while VPS hosting gives you more control but also more server responsibility. A website builder, design tool, domain service, security product, email host, or SEO tool may be a separate purchase and does not replace WordPress hosting.

Create the destination database and database user, then record the database name, username, password, and server name. Upload the WordPress files and import the database. Edit wp-config.php if the database name, user, password, or server changes. If the domain stays the same, avoid changing stored URLs unless the host's instructions require a temporary preview setting.

Preview the new server through a hosts-file entry, a temporary URL, a staging environment, or a temporary domain. A hosts-file entry changes resolution only on your computer, so it lets you inspect the new server while public visitors still reach the old one. SiteGround describes a hosts file as a reliable preview method, while temporary URLs can cause domain-dependent problems when used for editing.

Check the homepage, key pages, posts, menus, images, downloads, internal links, login, admin functions, plugins, themes, users, HTTPS, redirects, permalinks, forms, checkout, transactional email, analytics, robots.txt, XML sitemap, and cookie tools. Check recent orders, comments, registrations, and form submissions against the old site.

When the destination works, lower important DNS TTL values if your DNS provider supports it. Cloudflare defines TTL as the period a DNS record stays cached and recommends about 300 seconds, or five minutes, for critical records 24 to 48 hours before a website DNS migration. Its guidance recommends lowering MX TTL to five minutes three to five days before a planned mail change.

Change the website's A record to the new server IP while keeping DNS at the current provider, or change nameservers to the new DNS provider. Nameserver changes transfer responsibility for the complete DNS zone, so copy every record first. Keep the old host active while resolvers update. Cloudflare describes nameserver propagation as typically ranging from a few minutes to 48 hours, depending on cached records and the DNS setup.

Three Ways to Move WordPress: Host Service, Plugin, or Manual Migration

A host migration service is usually the simplest choice when the site fits the provider's eligibility rules. SiteGround says its free WordPress Migrator transfers site content, themes, plugins, and databases through an encrypted connection. Its Migrator is not suitable for localhost sites or complete Multisite installations. SiteGround also describes a separate manual website transfer service.

Hostinger's free migration applies to eligible open-source CMS sites hosted elsewhere on qualifying Web, Cloud, or Agency plans. It includes website files and databases, but its published scope excludes cron jobs, DNS records, custom SSL configuration, FTP accounts, and email migration. Internal moves between Hostinger accounts or plans do not qualify for free migration. See Hostinger's current plans only after confirming eligibility in the order flow.

Bluehost provides a free WordPress migration tool for eligible sites. Its published requirements include access to website files, databases, and database contents. Its documented non-cPanel free migration route allows up to five websites and 10 GB per site. A complex, oversized, or otherwise ineligible move can follow different rules, so obtain written confirmation before purchase.

A plugin can suit you when the host's service excludes your site or when you want to control the backup. Duplicator's free version has no stated size cap, but the destination server still has storage, PHP memory, execution-time, and upload limits. All-in-One WP Migration says its free plugin exports the complete site without a built-in export size limit, while the destination host controls the upload limit during restoration. UpdraftPlus documents unlimited free download-and-restore migrations by site count, while its one-click Migration add-on is separate.

Manual migration gives you the most control and the most work. Download the files, export the database with a tool such as phpMyAdmin, create the destination database, import it, upload the files, and update wp-config.php. If the domain changes, update stored URLs carefully. Search-and-replace must preserve serialized WordPress data, because a careless replacement can damage settings and content. WordPress warns that database changes are permanent, so retain the original backup.

How To Keep Email Working During The DNS Change

Moving website hosting does not automatically move mailboxes or historical messages. If hello@example.com remains with Google Workspace, Microsoft 365, or the current mail provider, keep that provider's MX and related authentication records in the DNS zone. Change only the website records needed for the new server.

Before changing A records or nameservers, confirm the current mail provider and export the DNS zone. Record MX, SPF, DKIM, DMARC, and any provider-specific CNAME or TXT records. If you change nameservers, recreate those records at the new DNS provider before the nameserver switch. Missing mail records can affect incoming delivery, outgoing authentication, or both.

If email is moving to the new host, create the mailboxes before changing MX records and ask whether the provider migrates message history. A website migration that transfers WordPress files and databases may not include email accounts, messages, aliases, forwarding rules, or spam settings. Hostinger explicitly excludes email migration from its published migration scope.

Lower MX TTL before a planned mail change when the DNS provider supports it. Cloudflare recommends five-minute MX TTL values three to five days before the change. Keep the old mailbox service active during propagation and test sending and receiving from more than one account.

After the DNS change, check a message sent to the domain from an outside account and send a message from the domain to an outside provider. Confirm that new mail arrives in the intended mailbox, SPF and DKIM pass where applicable, DMARC behaves as expected, and aliases and forwarding still work. If mail fails, restore the prior MX records or nameservers and preserve messages received during the cutover so they can be reconciled.

What The Migration Covers, and What It Does Not

A normal WordPress migration covers the application files and database within the provider's stated limits. That usually means WordPress core, themes, plugins, uploads, pages, posts, users, settings, and other database content. It does not automatically include every service attached to the domain or server.

Email, DNS records, cron jobs, FTP accounts, custom SSL settings, server configuration, third-party licenses, and non-WordPress applications may need separate work. Hostinger explicitly excludes cron jobs, DNS records, custom SSL configuration, FTP accounts, and email migration from its published free migration scope. SiteGround excludes localhost and complete Multisite migrations from its Migrator route.

A migration also does not promise zero downtime, plugin compatibility, correct PHP behavior, intact forms, working permalinks, uninterrupted mail, or protection from security incidents. New data created on the old site during the migration window may not appear on the new copy. Keep track of orders, comments, registrations, and form submissions during the cutover.

“Unlimited” storage or bandwidth remains subject to the provider's acceptable-use and resource terms. NVMe storage, LiteSpeed, a CDN, or a stated data-center location is a documented product feature, not proof of a particular speed result. An uptime guarantee is a contract with conditions and possible credits, not observed uptime or a promise that one site cannot go down.

What Migration Costs And What Renews

The migration route may be included while the hosting account, domain, email, premium plugin, professional migration, or add-on remains paid. Before purchasing, compare the provider's current US pricing and terms page for the selected product, billing term, upfront amount, effective monthly figure, renewal price, money-back window, domain charge, email charge, and premium migration cost. Prices and terms checked October 29, 2026.

No introductory hosting price is useful on its own. If a plan page shows a promotional amount, record the renewal amount beside it and check whether the charge is for one month, one year, or a longer prepayment. Bonus time is separate from paid time and should not be counted as a lower monthly payment. A free tier, a free trial, and a money-back window are different terms.

Some hosts charge for migrations above their free limits. Bluehost, for example, says eligible VPS and Dedicated migrations can be free with a 12-month billing term and a request within 30 days of signup, and charges for some other migrations. Check the new host's migration page for any fee before you order.

SiteGround says its first migration is free and separates its free Migrator from paid manual transfer work. Hostinger's free migration applies only to eligible external sites on qualifying plans. Confirm the exact plan, billing term, site size, source platform, refund exclusions, automatic renewal date, and migration eligibility before paying.

How To Check The New Site And Know When To Cancel The Old Host

Do not cancel the old host when the new homepage merely loads. Wait until the destination passes a full check, public DNS has propagated, email works, and the old backup is stored somewhere separate from the old server.

Check the site from a normal browser, a private window, and a phone or separate network. Review:

• Pages, posts, menus, images, downloads, internal links, permalinks, redirects, 404 pages, HTTPS, canonical URLs, and mixed-content warnings.
• WordPress login, admin actions, plugins, themes, users, comments, registrations, orders, forms, checkout, and transactional email.
• A and CNAME records for the site, plus MX, SPF, DKIM, DMARC, subdomains, analytics, robots.txt, XML sitemap, and cookie settings.
• The newest database content and any files uploaded during the migration window.

Confirm the new host's backups, retention period, restore process, storage location, and restore cost. Download a fresh backup from the new environment if the product allows it. Ask the provider how to restore the prior site and revert DNS before the cutover, then write down the old A record or nameservers.

If the new site fails, restore the old DNS record or nameservers and keep the old site available. Preserve new orders, form entries, comments, registrations, and mail created during the cutover so they can be reconciled after the problem is fixed. Do not delete the old site until the new version is stable and the rollback window has passed.

Once the checks pass, cancel only through the old host's documented cancellation process after reading its retention terms. Confirm whether cancellation stops renewal or immediately deletes the account. If you are deciding between destinations, read the Hostinger review of plans and renewal prices or compare Hostinger and SiteGround before choosing a host.

Frequently asked questions

Can you transfer a WordPress site to another host?

Yes. Transfer the WordPress files and database, update destination database settings, test the new server, and point DNS to it. The domain can stay registered with its current registrar.

Can I transfer my website to a different host?

Yes, if you can access the files and database or use an eligible migration tool. The provider may set limits based on site size, platform, billing term, account type, or Multisite status.

How do I migrate my WordPress site to a new server?

Back up the old site, prepare the new account and database, copy the files and database, update wp-config.php, preview the destination, test key functions, and then change the A record or nameservers. Keep the old server active while DNS updates.

How do I change my WordPress host?

Purchase and configure the new hosting account, migrate the site, test it privately, update DNS, and verify the website and email. Cancel the old host only after the new setup and backups are confirmed.

How do I manually migrate my WordPress site?

Download the WordPress files, export the database with a tool such as phpMyAdmin, create a database and user on the new host, import the database, upload the files, and update wp-config.php. Change URLs only when the domain changes, and preserve serialized data during search-and-replace.

How do I export my entire WordPress site?

Export both the files and database. All-in-One WP Migration creates a .wpress file containing the database, media, themes, and plugins, but the destination host controls the upload limit when restoring it.

How do I move a website to a new host?

Move and test the site before changing DNS. Then change the A record to the new server or move nameservers after copying the full DNS zone, including mail and subdomain records.

What happens to my website if I cancel hosting?

The old website, backups, and email stored there may become inaccessible or be deleted under the host's terms. Keep the account active until the new site, DNS, email, and backup copies are confirmed.

How much does it cost to migrate a website to a new host?

The migration can be included for eligible customers, but the new hosting plan is still paid. Some providers charge for oversized, complex, internal, or professional migrations, so check the new host's migration page for any fee before you order.

Find more reviews and guides on Even Reviews. Spotted something to correct? Contact us and include the page title.