Guides /Hosting
Hosting

How to Leave GoDaddy: Move Your Domain and Hosting Without Losing Anything

October 5, 20257 min readHostBible Team

Leaving GoDaddy sounds more complicated than it is. Most people delay because they're worried about downtime, losing emails, or accidentally breaking something. The reality is that with a methodical approach, the whole process can be done with zero downtime. Here's exactly how to do it, step by step.

First: understand what you're actually moving

Your domain name and your web hosting are two separate products that happen to live in the same GoDaddy dashboard. You can move one without moving the other, and you don't have to do both at the same time. Most people find the cleanest approach is to move hosting first while the domain stays at GoDaddy, then transfer the domain to a better registrar separately once everything is stable.

If you're also using GoDaddy for email, either their Workspace Email product or a Microsoft 365 integration, that's a third separate thing that needs its own migration plan. Don't try to move everything at once. Sequence the moves to reduce the number of things that can go wrong simultaneously.

Step 1: Back up everything before touching anything

Before you change a single setting, take a full backup of your site. If you're on WordPress, UpdraftPlus or All-in-One WP Migration will export your files and database to a zip you can store locally or in cloud storage. If your new host is handling the migration for you, they'll take their own backup, but having your own independent copy costs nothing and is the safety net if anything goes wrong during the move.

Also export your current DNS records from GoDaddy. In your domain's DNS management section, screenshot or copy every record: A records, CNAME records, MX records, TXT records (especially SPF and DKIM for email). You'll need to recreate these at your new host or at Cloudflare. Missing a single MX record during DNS cutover will break email delivery, which is the most common and painful mistake in hosting migrations.

Step 2: Set up your new hosting before changing anything at GoDaddy

Sign up for your new hosting plan and have the site fully migrated to the new server before you update a single DNS record. Most competent hosts offer free migration as part of onboarding, give them your GoDaddy credentials or the backup file, and they'll move your files, database, and email configuration. If you're migrating yourself, use cPanel's backup import tool or manually upload files via FTP and import the database via phpMyAdmin.

Do not cancel GoDaddy hosting yet. You need both environments running simultaneously while you test and then during the DNS propagation window. Cancelling early is the number one mistake people make that causes downtime.

Step 3: Test the new site thoroughly before cutting over

Your new host will give you a temporary URL, a staging domain, or instructions to modify your local hosts file so you can browse the site on the new server without changing anything live. Use this to verify everything: pages load correctly, images appear, contact forms submit successfully, and if you're running WooCommerce, complete a test checkout from start to finish.

Also check that email addresses are correctly configured on the new server if you're moving email hosting too. Send and receive test messages before you update MX records. It's much easier to identify and fix a misconfiguration before DNS is pointing to the new server than after.

Step 4: Lower your DNS TTL before the cutover

DNS records have a TTL (Time to Live) value that controls how long resolvers cache the record. If your TTL is set to 86400 (24 hours), DNS propagation after your change could take up to 24 hours for all visitors. Before you plan to switch, reduce your TTL to 300 (5 minutes) and wait 24 hours, this drains the old cached values. When you make the actual DNS change, propagation will complete in 5–15 minutes for most visitors rather than up to 48 hours.

To lower TTL, go to GoDaddy's DNS management for your domain, edit your A record, and change the TTL value. You won't see the effect immediately, but after the current TTL period expires, resolvers will check more frequently and pick up changes faster.

Step 5: Update nameservers or A record to point to your new server

Log into GoDaddy's DNS management and update either the nameservers (to point to your new host's nameservers) or the A record (to point to the new server's IP address). Nameserver changes are cleaner if your new host is managing all your DNS; A record changes are simpler if you want to keep DNS managed at GoDaddy or Cloudflare.

During propagation, some visitors will see the old server and some will see the new one. For static content sites, this is invisible. For eCommerce sites taking live orders, coordinate the cutover for a low-traffic window, typically late evening or early morning on a weekday, and accept that a small number of visitors may see the old site for up to an hour during the transition.

Step 6: Confirm the new site is live, then cancel GoDaddy hosting

Wait until DNS has fully propagated, use our DNS Propagation Checker to confirm your domain is resolving to the new server's IP from multiple global locations. Once you've confirmed the new site is live and working for visitors, cancel your GoDaddy hosting plan. GoDaddy makes cancellation deliberately inconvenient and will offer multiple retention offers during the process. The cancellation option is in Account Settings under My Products. You should receive a confirmation email once it's done.

Leave the domain registered at GoDaddy for now if it's mid-cycle. Initiating a domain transfer at the same time as a hosting migration adds unnecessary complexity. Transfer the domain to a better registrar (Cloudflare Registrar, Namecheap, or Porkbun are all reasonable choices) when it's convenient, ideally a month or two before the next renewal date.

What about GoDaddy email?

If you use GoDaddy's Workspace Email or their Microsoft 365 integration, email is a separate product on a separate billing cycle. It does not move automatically with your hosting. Plan the email migration separately: set up email accounts on your new host or at a standalone provider (Google Workspace, Zoho Mail, or Microsoft 365 direct), migrate existing email (use IMAP-to-IMAP migration tools or your email client's built-in import), then update MX records to point to the new provider. Only then cancel the GoDaddy email product.

The critical rule: never cancel GoDaddy email before your MX records are updated and confirmed working. An interrupted email migration can mean lost messages during the gap, which is the kind of mistake that's hard to recover from in a client or business context.

Free migration included on every plan

We'll move your site from GoDaddy at no charge, with zero downtime. LiteSpeed performance, daily backups, and honest renewal pricing once you're in.

View Hosting Plans