GoDaddy email to Microsoft 365

GoDaddy sells two very different mail products under a similar name. One is their own hosted mailbox platform, reached over IMAP, with no relationship to Microsoft at all. The other is a resold Microsoft 365 subscription, where real Exchange Online mailboxes sit inside a tenant that GoDaddy provisioned and administers on your behalf.

You can tell them apart in ten minutes. If your webmail is at GoDaddy's own domain and you have never seen a Microsoft admin centre, it is the hosted product. If Outlook connects to Exchange Online and licences appear under your GoDaddy account, it is the resold tenant. Everything about the exit follows from that answer.

This is the straightforward one. We provision a Microsoft 365 tenant that you own, copy mailboxes over IMAP, rebuild aliases and forwarders from an audit rather than guesswork, and move MX when the copy is complete. IMAP throughput is the slowest of any source platform, so the pre-sync starts early and runs quietly for several days.

The parts that catch people out are aliases and catch-all addresses. Hosted mail platforms hand these out freely and businesses come to depend on them without recording them anywhere. We enumerate them from the platform rather than from memory.

Here the mailboxes are already in Exchange Online, so nothing needs copying in the usual sense. What you lack is control: licence management, conditional access, security defaults and often the global admin role itself sit behind GoDaddy's console. The choice is to transfer the existing tenant to direct Microsoft billing, or to build a clean tenant and migrate into it.

We recommend the clean rebuild more often than not. Resold tenants routinely carry a domain configuration and a security posture chosen for GoDaddy's convenience rather than yours, and a tenant-to-tenant move is a well-worn path with a fixed price attached to it.

In both cases the nameservers are usually still at GoDaddy, and control of the domain often sits with whoever built the website years ago. Recovering that access is the single most common cause of delay, and it is entirely administrative. We ask for it in the first conversation, before any technical scoping, because a three-week project becomes a six-week project when the DNS owner is on holiday.

If the domain itself needs to move registrar, that is a separate change with its own transfer lock and waiting period. It can happen after the mail migration; it does not have to block it.