How to Transfer a WordPress Domain and Hosting Simultaneously

The safest way to transfer a WordPress domain and hosting simultaneously is to do them in sequence, not literally at the same second: copy the site to the new host first, test it on a temporary URL, repoint DNS, and only then start the domain registrar transfer. Domain transfers can take 5 to 7 days to complete, while a DNS change usually propagates in under an hour with a low TTL. Treating them as one event is what causes the dreaded blank white page and bounced email.

We move a few hundred sites a month, and almost every broken migration we clean up shares the same root cause: someone pulled the domain before the files and database had finished landing on the new server.

Why the order of operations decides whether you have downtime

A domain and a hosting account are two separate products that happen to point at each other. Your registrar controls the nameservers; your host controls the server that answers when those nameservers send traffic somewhere. If you transfer the domain first, control of DNS moves to a new registrar panel while your site still lives on the old host.

That gap is where things break. During a registrar transfer, some providers reset nameservers to their own defaults, which can drop your site offline for hours. Getting the site fully working on the new host before touching the registrar removes that risk entirely.

• Step 1: Copy files and database to the new host and test on a temporary URL or hosts-file preview.
• Step 2: Lower the DNS TTL at your current DNS provider to 300 seconds, at least 24 hours in advance.
• Step 3: Repoint the A record or nameservers to the new host and confirm the live site resolves correctly.
• Step 4: Unlock the domain, grab the EPP/auth code, and start the registrar transfer.
• Step 5: Reissue SSL, recheck email routing, and cancel the old plan after a 14-day overlap.

What to gather before you touch anything

Most failed migrations stall because a login is missing halfway through. Collect these first, and the whole job takes an afternoon instead of a week.

• Registrar credentials plus access to the admin email listed in WHOIS, since that address receives the transfer approval link.
• Old hosting control panel and SFTP details, including database name and user, in case an automated migration tool needs manual fallback.
• A full backup of the WordPress site: the wp-content folder, wp-config.php, and a SQL dump of the database.
• Your current DNS zone file exported or screenshotted, with MX, TXT (SPF, DKIM, DMARC), and any CNAME records for tools like Google Workspace or a help desk.
• Licence keys for premium plugins and themes that bind to a domain or an install count.

That DNS zone export matters more than people expect. Roughly a third of the support tickets we see after a self-managed move involve email, not the website, because MX records were never recreated on the new provider.

Moving the WordPress site to the new host

You have three realistic paths. A managed host will usually run the migration for you at no cost, which is what we do as part of business WordPress hosting plans. A plugin like All-in-One WP Migration or Duplicator handles small and mid-size sites well. Manual SFTP plus a phpMyAdmin database import is the fallback for anything unusual.

Plugin exports hit a wall on large sites, since free versions cap the import size (commonly 256 MB) and shared hosts often limit PHP execution time to 30 or 60 seconds. For a media-heavy magazine or a store with thousands of orders, a server-level copy is faster and less fragile. The official WordPress documentation on moving a site covers the manual file and database route in detail.

Once the copy lands, preview it before DNS changes. Edit your local hosts file to map the domain to the new server’s IP, then click through the homepage, a category archive, a single post, the checkout or contact form, and wp-admin. Fix permalinks and mixed-content warnings now, while nobody else can see them.

Repointing DNS with a short TTL

Twenty-four hours before cutover, drop the TTL on your A record and nameserver records to 300 seconds. Propagation then finishes in minutes rather than the 24 to 48 hours people still quote from the days of 86400-second TTLs.

Keep both hosting accounts running during the switch. Visitors resolving to the old server still see a working website, and visitors resolving to the new one see the fresh copy. If your site accepts orders or comments, put it in maintenance mode for the 20 minutes around the final database sync so no data lands on the server you’re about to retire.

Check SSL immediately after the DNS change. Certificates are issued per host, so the new server needs its own certificate, usually a free Let’s Encrypt one provisioned automatically. Our notes on SSL on WordPress hosting explain why the padlock sometimes lags the DNS by a few minutes.

Transferring the domain to a new registrar

Only now do you touch the registrar. Unlock the domain, disable WHOIS privacy temporarily if your provider requires it, and request the authorisation code (the EPP or auth code). Enter that code at the gaining registrar, approve the confirmation email, and wait.

Two rules trip people up. First, a domain cannot be transferred within 60 days of registration or of a previous registrar transfer, per the ICANN Transfer Policy. Second, a change of registrant contact details can trigger the same 60-day lock, so update WHOIS after the move, not before.

Transfers add one year to your registration and typically cost the standard renewal fee, around $10 to $20 for a .com. If you’d rather not deal with registrar admin at all, some plans bundle the name: our WordPress hosting with a free domain includes registration or a transfer credit for the first year.

The mistakes that cost people a weekend

• Cancelling the old account too early. Keep it for 14 days. It is your rollback, and the refund you save is never worth the risk.
• Forgetting MX and TXT records when nameservers change, which silently kills email delivery and breaks SPF alignment.
• Leaving old URLs in the database after moving from a staging domain. Run a search-replace that handles serialised data instead of a raw SQL query.
• Skipping a post-move crawl. A 200-page crawl catches broken internal links, missing images, and redirect chains in about ten minutes.
• Mismatched PHP versions. A site on PHP 7.4 dropped onto PHP 8.3 can fatal-error on an abandoned plugin, so check before cutover.

Registrar-specific quirks exist too. Moving away from GoDaddy involves an extra authorisation step in the domain manager, which we walk through in our guide to migrating from GoDaddy to managed WordPress hosting. Coming from another CMS entirely changes the sequence again, as the Joomla to WordPress migration path shows.

High-traffic publishers should also plan the cutover for their quietest hour. On magazine hosting setups we usually schedule between 2am and 4am local time, when a brief maintenance window affects a few dozen readers rather than a few thousand.

Frequently Asked Questions

How to transfer a WordPress website from one hosting to another?

Back up files and the database, copy them to the new host, test on a temporary URL, then repoint DNS: roughly 1 to 3 hours of work for a typical site. Most managed hosts will run the migration free of charge, which removes the manual file transfer and database import steps entirely.

Can I change my web hosting provider and still keep my domain name?

Yes. Your domain and your hosting are separate services, so you can move to a new host and leave the domain at its current registrar by simply updating the nameservers or A record. Many site owners keep the registrar untouched for years and only change where the site is hosted.

Is All-in-One WP Migration free?

The core plugin is free, but the free version caps imports at 256 MB, so larger sites need the paid extension (around $99 one-time) or a manual method. For anything above a few gigabytes, a server-side copy by your host is usually faster and more reliable than any plugin.

Can I move my domain from one hosting service to another?

Yes, provided the domain is at least 60 days old and not within 60 days of a previous transfer, per ICANN rules. You unlock it, request the EPP code, submit it to the gaining registrar, and approve the confirmation email, with completion usually in 5 to 7 days.

Planning your move?

If you’d rather hand the whole sequence to someone who does it daily, our team handles the copy, the DNS cutover, and the registrar paperwork while your current site stays online. Talk to our WordPress support specialists and we’ll schedule the transfer around your traffic, not ours.