How to Move Microsoft 365 Off GoDaddy: The Supported Process, Step by Step

If your Microsoft 365 came from GoDaddy, you have probably already hit the wall: you cannot reach parts of the Microsoft 365 admin center, you cannot buy the license you actually want, and security features you have paid for are not there to switch on. This guide covers what GoDaddy's setup is, the supported way to leave it, the timing rules that catch people out, and what genuinely changes for your users.

What GoDaddy's setup actually is

GoDaddy sets your domain up as a federated domain in Microsoft Entra ID. In plain terms: your sign-ins are pointed at GoDaddy's login system instead of Microsoft's. That is why your users sign in through GoDaddy, why GoDaddy's portal manages your mailboxes, and why parts of the Microsoft admin experience are closed to you.

Leaving flips the domain to managed, so Microsoft checks your users' sign-ins directly. Everything else — buying licenses, changing who bills you, ending GoDaddy's admin access — is separate work that has to happen around it in the right order.

The change covers the whole tenant, not just the one domain you have in mind. List every domain before you start.

Before you contact GoDaddy

GoDaddy will not start the move until a few things are true, and two of them have caught people out often enough to be worth checking first.

• Your email plans must not expire within the next five business days. GoDaddy's process needs your accounts active while the move runs. If a renewal is close, deal with it before you open the request, not during it.
• The email address on your GoDaddy account cannot be one of the addresses moving. If your GoDaddy login is [email protected] and that domain is the one leaving, change the GoDaddy account email to something outside the domain first.
• You must be able to sign in to your email and pass multi-factor authentication, because GoDaddy validates who you are before they will move anything.
• Know where your MX records point. If the tenant carries GoDaddy's Advanced Email Security add-on, incoming mail goes through Proofpoint before it reaches Microsoft 365. GoDaddy's guidance says to swap those records for Microsoft's before you leave. The trap this avoids is covered below.
• A full export of your users, so you can check everyone afterwards and run the password reset.
• A date and time your users know about. Their passwords will change and they will have to sign in again everywhere.

What GoDaddy's process does

1. You contact a GoDaddy Guide by phone or chat and ask to move your Microsoft 365 email away.
2. GoDaddy opens a move ticket for your request.
3. GoDaddy sends a temporary admin password to the email address on your GoDaddy account. Their document says to expect it by the next business day.
4. You sign in to your tenant directly at Microsoft using that temporary password. This is the moment control changes hands.
5. You buy your new plans from Microsoft or from a new reseller — now, not earlier.
6. You decide what happens to the leftover GoDaddy plans. They do not transfer, and whether you get money back is a question for GoDaddy's refund policy.

Afterwards, GoDaddy's own clock runs: seven days after your email addresses are removed from their system they suspend their plans in your organization, and once those subscriptions expire they remove themselves as your reseller. So the reseller link does not disappear the moment you take control — it ends when the GoDaddy subscriptions run out. Plan for a period where the old relationship is still visible in your tenant. GoDaddy also stops supporting you once the move is done, which is worth knowing before you need them.

The timing problem, honestly

This route is free and it works. Its weakness is scheduling. GoDaddy's document commits to a next-business-day password and nothing after that, so the move happens on their queue. Nobody on the call can book the hour your sign-ins actually change over.

That is fine for a move with a loose deadline. It is a real problem when the move sits inside a bigger cutover with a fixed date — a migration weekend, an office opening, a deadline someone has already promised a client. In that case the answer is not to route around the vendor process, it is to start it early enough that the ticket lands well before the date you care about, and to have every other piece ready so the only thing you are waiting on is GoDaddy.

What breaks, and what does not

• Passwords break. Every user needs a new one. Their old password lived with GoDaddy's login system, not in Microsoft Entra ID, so once Microsoft is checking sign-ins there is nothing there to check against. This is the single biggest source of support calls on the day. Hand out new passwords through a channel that is not the email account they have just lost access to.
• Sign-in sessions break. Outlook, Teams and mobile mail all ask people to sign in again.
• Mail flow does not break, as long as the mailboxes stay in the same tenant and nothing else is holding the mail route. Nothing is being migrated — the tenant is changing hands, not moving. The common exception is the Advanced Email Security add-on, covered next.
• Your data does not move. Mailboxes, files and Teams stay exactly where they are.
• GoDaddy's email management portal stops working. That is the point, but tell whoever used it.
• Your domain registration is not affected. Moving the email away does not release the domain. They are separate products.

The Advanced Email Security trap

If the tenant carries GoDaddy's Advanced Email Security add-on, the mail-flow note above has an exception, because your incoming mail does not go straight to Microsoft 365. The add-on is Proofpoint underneath: your MX records point at Proofpoint's servers, Proofpoint filters the mail and passes it on, and the list of people it will accept mail for is maintained from GoDaddy's side while GoDaddy runs the tenant.

Leave without re-pointing MX and that arrangement outlives the subscription, quietly and unevenly. One business found out months after a move that had otherwise gone fine: new employees were not receiving outside email. Existing staff were unaffected, internal mail worked for everyone, and every test run from inside the company came back clean, so the fault looked random and impossible to reproduce. The pattern was the hiring date. Every mailbox created before the move was still on Proofpoint's list and kept working. Every mailbox created after it did not exist as far as the routing layer knew, so outside mail to new hires failed while their internal mail, which never crosses that route, arrived normally.

Once seen, the fix was routing: point the MX records at Microsoft 365, retire the filtering layer nobody owned any more, and check delivery against the full user list. Finding it was the hard part, because the one system that explained the pattern belonged to a vendor the business believed it had already left. GoDaddy's own guidance says the same thing in one line: swap the Proofpoint MX records for Microsoft 365's before moving away. Do it as a planned step rather than as a discovery three hires later, and decide at the same time what replaces the filtering. Defender for Office 365 covers it when your licensing includes it, which Business Premium and E5 do. Microsoft 365 E3 and Office 365 E3 include only the baseline Exchange Online Protection, so on those plans the replacement is the Defender for Office 365 add-on, another filtering service, or a deliberate decision that the baseline is enough.

What older guides get wrong

They hand you a command. Most guides tell you to flip the domain yourself with PowerShell. Microsoft's position is that steps from sites other than GoDaddy's are not supported for this, and that using them can affect sign-in to SharePoint and mailboxes. Running it yourself also leaves the parts a command cannot touch — the reseller relationship, the billing, the leftover subscriptions — in a state you then have to resolve with a vendor who has no record of what you did.

They reference retired PowerShell. Older guides use the MSOnline module and commands like Set-MsolDomainAuthentication. Microsoft retired MSOnline across all tenants during April and May 2025. Those commands no longer run at all, which is a useful signal for how current the rest of that guide is.

They tell you to buy licenses first. GoDaddy's process puts the purchase after the move. Older guides put it before, and that ordering fights the process you are actually in.

After the move

• Check your DNS records — MX, Autodiscover, SPF and DKIM — and confirm they point where Microsoft expects. You do not need to move nameservers or change registrar to finish this; that is a separate decision, and doing it the same weekend adds risk for no benefit.
• Turn on security. A GoDaddy-managed tenant usually has none of it set up. Security defaults are the ten-minute version; Conditional Access is the real answer once your licensing covers it.
• Check everyone against your user export and confirm every mailbox is licensed and signing in.
• Watch for the reseller relationship to clear once the old GoDaddy subscriptions expire, and confirm it has.

If you would rather not run it yourself

The whole move is available as a fixed package: a fixed price for a standard single-domain exit, covering the move request and the work around it — the license switch, the password wave, the mail routing, and the check that everyone is working afterwards. Or talk through the problem and get a reply within one business day, with a fixed price where the scope is already clear.