What needs to move
Check leaving GoDaddy where domain registration, DNS, website hosting, WordPress, email, and third-party integrations may have separate owners or subscriptions that should be mapped before cutover.
Migrate from GoDaddy
Identify which GoDaddy products currently provide your website, WordPress, email, DNS and domain registration, then plan the parts that actually need to move.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check leaving GoDaddy where domain registration, DNS, website hosting, WordPress, email, and third-party integrations may have separate owners or subscriptions that should be mapped before cutover.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
GoDaddy accounts often spread one business across several products: the domain and its DNS in one place, website hosting in another, and email on Microsoft 365 sold through the same account. Map each product before exporting anything. The website copies out as files and a database, while Microsoft 365 mail stays in its tenant and never downloads into the move.
The breakage in this move usually comes from DNS. GoDaddy zones often carry records for services the owner forgot, including verification strings and mail records for the bundled email. Capture the whole zone, recreate it at the destination with the Microsoft 365 MX, autodiscover, SPF and DKIM records intact, and test mail flow before the old products are cancelled.
Write down which GoDaddy products hold the domain, DNS, site and email. Each product closes on its own timeline after its replacement works.
Copy the Microsoft 365 MX, autodiscover CNAME, SPF and DKIM records into the new zone exactly. Mail keeps flowing to the same tenant through the move.
Exports and authorization codes can require the account owner. Confirm ownership early so the move does not stall at the first export.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.