Case Study: Moving Microsoft 365 Away From GoDaddy

Over the past few months we've moved several Perth businesses' Microsoft 365 off GoDaddy's reseller platform and onto direct management. Different industries, different tenant sizes, same underlying problem each time. This is a walkthrough of what that work actually involves, why it's a more common project than most business owners expect, and what tends to go wrong when it's attempted without a plan.

The Pattern Behind Every One of These Projects

Each business had the same origin story. They registered a domain through GoDaddy, and at some point were offered Microsoft 365 email as a bundled add-on. It's an easy yes at the time - one invoice, one login, no separate vendor to deal with. Nobody registering a domain for a five-person business is thinking about admin centre access two or three years down the track.

The problem shows up later, once the business has grown enough to need things GoDaddy's reseller panel simply doesn't expose: proper Conditional Access policies, mail flow rules, Intune enrolment, or just a straight answer from someone who isn't reading from a support script. Every change - even a small one - has to go through GoDaddy's queue, because the reseller relationship means the business was never actually a direct Microsoft customer in the first place. As one of these businesses put it to us, they didn't feel like they owned their own email system.

Why This Isn't a Migration

The instinctive fix is to treat this like any other email migration - export the old mailboxes, import them into a new tenant, cut over DNS. That's the wrong approach here, and it's the point where these projects go badly if someone gets it wrong.

GoDaddy-provisioned Microsoft 365 mailboxes already live inside a genuine Microsoft 365 tenant - it's just administered through GoDaddy's reseller layer rather than directly. That means the data doesn't need to move anywhere. In every one of these engagements, we used a tenant handover instead of a migration: transferring administrative control of the existing organisation to direct billing, while every mailbox, calendar, contact, and file stayed exactly where it was. Nothing was exported, nothing was re-imported, and nobody had to be re-provisioned. That distinction is also why "just cancel the GoDaddy subscription and buy licences directly" is the single most common way these projects go wrong - cancelling first can delete the mailbox data the handover was supposed to preserve.

What the Process Looked Like

• Audited the existing tenant first. Before touching anything, we confirmed exactly what licence types were active, which domains were connected, and whether any add-on services (backup, archiving, security add-ons) were tied to the GoDaddy billing relationship rather than the tenant itself.
• Verified ownership and admin contact details. GoDaddy's handover process requires confirming account ownership before releasing control - sorting this out upfront avoided delays once the process was under way.
• Initiated the formal handover with GoDaddy support to transfer administrative control of the Microsoft 365 organisation, rather than provisioning a new one.
• Sequenced the licence swap carefully. New Microsoft 365 licences were purchased and assigned before the GoDaddy licences were unassigned. Doing it in the wrong order is what stops mail flow mid-handover.
• Tested mail flow and sign-in at every stage, and confirmed existing MFA and security settings carried over untouched rather than resetting on the new tenant.
• Kept the client in plain-language updates throughout, since the people making the decision were usually not the people who'd understand tenant IDs or licence SKUs, and didn't need to.

The Outcome, Every Time

Every one of these handovers completed with zero data loss - no missing emails, no dropped calendar entries, no re-created contacts - and no meaningful downtime beyond a brief, controlled gap during the final licence reassignment step. Each business ended up with the same result: a Microsoft 365 tenant under direct administrative control, full access to the admin centre, and no reseller layer standing between them and Microsoft. From there, several of them moved on to things that simply weren't practical under GoDaddy's restricted panel - proper Microsoft 365 and cloud management, Conditional Access, and rolling out Teams and SharePoint properly rather than using email as their only collaboration tool.

We've written up one of these engagements in more detail in our Microsoft 365 reseller-to-direct handover case study.

Signs You're in This Situation

• Your Microsoft 365 invoice comes from GoDaddy, not Microsoft.
• Logging into admin.microsoft.com directly doesn't work, or shows a cut-down version of the admin centre.
• Any change to email settings, security policy, or licensing means opening a support ticket with GoDaddy rather than making the change yourself.
• You've been told a feature - Conditional Access, Intune, advanced mail flow rules - "isn't available" on your plan, when it's actually a standard part of Microsoft 365 that the reseller panel just doesn't surface.

GoDaddy's own documentation on moving Microsoft 365 email away from GoDaddy covers the mechanics of the handover from their side, but doesn't cover the audit, sequencing, and validation work that determines whether it goes smoothly or costs you your mail flow for an afternoon.

Frequently Asked Questions

For related reading, see our guides to email migration in Perth and our full case studies archive.