Why this is an ownership problem before it is a migration problem
When a business buys Microsoft 365 through GoDaddy, GoDaddy creates the tenant, federates the company domain to its own identity service, bills the licenses, and keeps a partner relationship with delegated administration. The company gets working mail and OneDrive, and for a small team that is often enough for years. The limits show up later: a plan GoDaddy does not resell, a security feature that needs a license GoDaddy cannot add, a consultant who needs Global Administrator and discovers the sign-in path runs through GoDaddy's portal, or simply a renewal price that no longer makes sense. At that point the question is not which platform to move to. The data is already in Microsoft 365. The question is who owns the tenant.
That framing is what separates this engagement from a platform switch. Our Google Workspace to Microsoft 365 migration moves mail, Drive, and shared drives from one vendor's cloud into a new tenant, and our Exchange Server to Exchange Online migration moves mailboxes and public folders off an on-premises server. Here, nothing is usually moving between clouds. Mailboxes, OneDrive libraries, and SharePoint sites stay exactly where they are. What changes is authentication, licensing, and administrative control, and the risk sits in the order those changes happen. Our Microsoft 365 migration services for small business overview sets the three routes side by side, alongside moving a file server into SharePoint.
Which GoDaddy product you have decides the whole project
GoDaddy has sold email under several names, and the label on your invoice determines whether this is a defederation or a mailbox migration. The table is the first thing we settle on the consultation call.
| What GoDaddy sold you |
What it really is |
What has to move |
The path |
| Microsoft 365 from GoDaddy |
A genuine Microsoft 365 tenant, provisioned by GoDaddy as a reseller, with the domain federated to GoDaddy for sign-in and licenses billed through GoDaddy |
Authentication, passwords, licensing, and partner access. Mail and files stay in place |
Defederate to Managed, relicense with Microsoft direct or a CSP, remove the partner relationship, cancel GoDaddy last |
| Workspace Email or Professional Email |
GoDaddy's own hosted mail, reached over IMAP and POP, with no Microsoft 365 tenant behind it |
Every mailbox, plus calendars and contacts exported separately |
Create and license your own tenant, verify the domain, run an IMAP migration into Exchange Online, then cut MX over at an agreed hour |
| A mix of both |
Common in businesses that grew in stages: leadership on Microsoft 365, front-line staff on Workspace Email, one domain shared between them |
Both of the above, sequenced so the shared domain never bounces mail |
Defederate the existing tenant first, then migrate the IMAP mailboxes into it and retire the second mail host |
The order of operations, and why it matters
Defederation itself is a small change with large consequences. The domain's authentication type in Microsoft Entra is flipped from Federated to Managed, which Microsoft exposes through the Update-MgDomain cmdlet in Microsoft Graph PowerShell (opens in new tab). The instant that runs, GoDaddy's login page stops working for your users and every account needs a password that exists only in Entra. Done at 10am on a Tuesday without a plan, that is an outage. Done in a scheduled window with passwords pre-generated, a distribution plan for them, and written sign-in instructions for Outlook, mobile mail, and Teams, it is an hour of controlled change.
Licensing is the second half, and it is where most self-service attempts go wrong. GoDaddy-billed licenses do not transfer to Microsoft; they are cancelled and replaced. Microsoft's guidance on what happens when a subscription expires (opens in new tab) describes a lifecycle that ends in data deletion, so the replacement licenses, whether bought direct from Microsoft or through a Cloud Solution Provider, are purchased and assigned first and the GoDaddy subscription is cancelled only after every mailbox, shared mailbox, and archive is confirmed licensed on the new subscription. Choosing the replacement plan is its own decision; if the move is your chance to change tiers, our comparison of Microsoft 365 Business Premium versus E3 covers the lines that actually decide it.
The third piece is administrative. A reseller tenant carries a partner relationship, and Microsoft documents how to view and remove partner relationships (opens in new tab) from the admin center. We remove GoDaddy's delegated access, confirm your own Global Administrator accounts and a documented break-glass account, and record the state of the tenant so a future engineer can see exactly what was changed and when.
The three phases of the project
The table shows scope and typical timeline rather than prices, because an honest number needs the user and domain inventory first. That principle runs through how our fixed-fee process works: one written figure for the whole project, agreed before anything changes, with the reasoning set out in fixed-fee versus hourly consulting.
| Phase |
Scope |
Typical timeline |
Fee |
| Phase 1 — Inventory and runbook |
Identify the GoDaddy product, list users, shared mailboxes, archives, and domains; capture current license assignments and DNS records; choose the replacement plan and purchasing route; write the dated runbook and the staff communication |
About 1 week |
Fixed fee — scoped after your free consultation |
| Phase 2 — Defederation and relicensing |
Switch the domain to Managed authentication, set passwords for every user, assign and verify Microsoft direct or CSP licenses, remove the GoDaddy partner relationship, confirm admin and break-glass accounts; IMAP migration runs in parallel where Workspace Email is in scope |
About 1 week, with the change itself in a single planned window |
Fixed fee — scoped after your free consultation |
| Phase 3 — Cutover, cancellation, hypercare |
Users re-sign-in on every device with written guidance, DNS re-verified, final IMAP sync and MX cutover where applicable, GoDaddy subscription cancelled, tenant documentation handed over, then 30 days of included post-delivery hypercare |
1–2 weeks, plus 30 days of hypercare |
Fixed fee — scoped after your free consultation |
Everything lands in the tenant you own, and this time that phrase is literal. The Global Administrator accounts, the licensing agreement, the runbook, and the DNS records are yours throughout, so your team can carry on in-house the moment hypercare ends.
Who this is for
The usual fit is a US company of roughly 10 to 300 people that bought Microsoft 365 through GoDaddy alongside its domain years ago, has grown into needs GoDaddy's catalogue does not cover, and now wants the same tenant with the reseller out of the loop. Often the trigger is a security requirement: conditional access, Intune, or Defender licensing that has to be bought and administered directly. The work is delivered by senior US-based engineers from our Orange County, CA base and remotely across all US states, as part of the fixed-fee Microsoft 365 consulting for small business teams that runs across this site.
Once the tenant is yours, the sensible next step is a Microsoft 365 tenant security assessment. Reseller tenants tend to have been set up for mail and nothing else, so multi-factor authentication coverage, sharing defaults, and admin role assignments are usually the first things to read now that you can finally change them.