Migrating GoDaddy Email to Microsoft 365 or Google

"GoDaddy email" is two unrelated products wearing one name, and that's the first thing to settle before you migrate godaddy email to microsoft 365 or Google. One is GoDaddy Workspace Email — the older, cPanel-flavored inbox with webmail at `secureserver.net`. The other is Microsoft 365, sold and administered through GoDaddy on your behalf.

They look similar in your GoDaddy dashboard and they are not the same migration. Workspace Email needs its mail moved somewhere else. A GoDaddy-managed Microsoft 365 tenant is already Microsoft's infrastructure — you're not moving mail, you're taking the tenant's steering wheel away from GoDaddy.

This guide covers both paths: exporting Workspace Email to a new provider, and defederating a GoDaddy-sold Microsoft 365 tenant so it answers to Microsoft (or a different partner) instead. Verified against GoDaddy's own support documentation and Microsoft's migration guidance, current as of August 2026.

Neither path is instant, and neither should be attempted the same afternoon you decide to leave. The Workspace Email path is a weekend-sized project for a small mailbox count; the Microsoft 365 defederation is a support-ticket-and-wait process measured in business days, because GoDaddy gates the first step behind a human reviewing the request.

Which GoDaddy email do you actually have?#

Check your GoDaddy account's email product name before you plan anything. GoDaddy currently sells three things under "email": legacy Workspace Email, the newer Professional Email (powered by Titan), and Microsoft 365 from GoDaddy.

The tell is in the login screen and the mail server name. If your webmail login is `email.godaddy.com` or `webmail.secureserver.net` and your IMAP host is `imap.secureserver.net`, you're on legacy Workspace Email — GoDaddy has stopped actively investing in it and is nudging accounts toward Professional Email or Microsoft 365. If you log into `titan.email` or your IMAP settings reference Titan, you're on Professional Email. If you sign in at `outlook.office.com` with a GoDaddy-issued temporary password history, you have a GoDaddy-managed Microsoft 365 tenant — real Microsoft mailboxes, GoDaddy administration.

It's worth checking every mailbox on the domain separately, not just your own. Small businesses that have been with GoDaddy for years often run a mix — an owner's mailbox upgraded to Microsoft 365 at some point while two older support addresses were never migrated off legacy Workspace Email. Treat each address as its own inventory item before you plan the cutover.

• Workspace Email (legacy): imap.secureserver.net, smtpout.secureserver.net — free plans are POP-only, paid plans get IMAP
• Professional Email (Titan): separate IMAP host, its own mobile/desktop setup guide, GoDaddy's current default for new signups
• Microsoft 365 from GoDaddy: real Exchange Online mailboxes, but your domain is federated for sign-in through GoDaddy rather than Microsoft directly

What actually moves and what doesn't#

For Workspace Email and Professional Email, an IMAP-based migration carries mail, folders and most contacts. It does not carry GoDaddy-side email forwarders, autoresponders, or catch-all rules — those live on GoDaddy's mail server configuration, not in the mailbox, and have to be recreated on the new platform.

For a GoDaddy-managed Microsoft 365 tenant, nothing about the mail itself needs to move — it's already sitting in Exchange Online. What has to change is who administers the tenant and who bills for the licenses. Distribution groups, shared mailboxes and existing Outlook rules survive defederation; what doesn't survive automatically is federated single sign-on, which GoDaddy's process explicitly resets to Microsoft's own managed authentication.

Pre-migration checklist#

Do these five things before you touch a single DNS record. Skipping the export step is the single most common cause of a support ticket titled "where did my old mail go."

• Export a full copy of Workspace/Professional Email mailboxes via IMAP before changing anything — treat GoDaddy's mail server as the source of truth until the new one is confirmed complete
• List every GoDaddy-side forwarder, autoresponder and catch-all address; these have to be rebuilt manually on the destination
• Lower your domain's MX record TTL to 300 seconds at least 24–48 hours ahead, so the eventual cutover propagates fast instead of slow
• For a GoDaddy-managed Microsoft 365 tenant, confirm you have (or can get) Global Admin access — GoDaddy's defederation process requires it, and it starts with a support ticket, not a self-service toggle
• Warn every mailbox owner ahead of time that a password reset is coming for the Microsoft 365 path, and that a short mail delay is possible for the Workspace Email path — most support tickets after a migration are from users who weren't told what to expect, not from mail that actually went missing

Steps: moving Workspace Email or Professional Email to a new provider#

1. 1

   Create mailboxes on the destination

   Set up the matching mailboxes on Microsoft 365 or Google Workspace first, using the same addresses. Nothing lands correctly if the destination mailbox doesn't exist yet.

2. 2

   Run an IMAP migration batch

   Microsoft 365's admin center supports an IMAP migration batch pointed at imap.secureserver.net (or Titan's IMAP host); Google Workspace's Data Migration Service does the same against a generic IMAP source. Both pull mail and folders without touching GoDaddy's DNS yet.

3. 3

   Rebuild forwarders and autoresponders

   Recreate every GoDaddy-side forwarder and out-of-office rule on the new platform from your pre-migration list. These never traveled with the IMAP copy.

4. 4

   Cut over MX records

   Once the migrated mailboxes look complete, change the domain's MX records to point at the new provider. With a shortened TTL this typically resolves for most mail servers within a few hours.

5. 5

   Run a delta sync and decommission

   Run a second, shorter IMAP sync to catch anything that arrived at the old mailbox during cutover, confirm mail flow on the new side for a few days, then downgrade or cancel the GoDaddy email product.

Steps: taking a GoDaddy-managed Microsoft 365 tenant off GoDaddy#

This is not an export — it's a defederation, and GoDaddy gates the start of it behind a support conversation rather than a self-service button. The mail never moves; the administrative relationship does.

The five steps below match the sequence GoDaddy and Microsoft describe for taking a federated tenant to direct, managed status. Doing them out of order — buying licenses before the domain is verified directly with Microsoft, for instance — is the most common reason these tickets stall for weeks instead of days.

1. 1

   Open a move request with GoDaddy

   Contact GoDaddy support and ask specifically for a Microsoft 365 defederation, not a general email migration — the two are handled by different teams and the wrong one stalls the ticket.

2. 2

   Verify the domain directly in Microsoft's admin center

   You add and verify the domain in Microsoft 365 admin center under your own tenant relationship, independent of GoDaddy's portal.

3. 3

   Convert authentication from federated to managed

   GoDaddy (or you, with the access they grant) switches user sign-in from GoDaddy-federated authentication to Microsoft's own managed authentication. Every user should expect to reset their password immediately after this step.

4. 4

   Buy direct licenses and reassign

   Purchase new Microsoft 365 licenses directly from Microsoft or a Cloud Solution Provider, assign them to the existing mailboxes, then remove the GoDaddy-billed licenses once confirmed.

5. 5

   Point DNS at Microsoft directly

   Update MX, autodiscover and related DNS records to Microsoft's own values instead of GoDaddy's proxy records, and allow the standard propagation window before removing GoDaddy's records entirely.

What breaks during a GoDaddy email migration#

The two paths break different things, which is the whole reason to identify which product you have before you start. A Workspace Email migration breaks anything configured on GoDaddy's mail server rather than stored in the mailbox itself; a defederation breaks nothing about the mail but resets how every user signs in.

Rollback plan#

For a Workspace/Professional Email migration, keep the GoDaddy mailbox active and un-cancelled for at least a week after cutover. If MX propagation misbehaves or a rule didn't rebuild correctly, reverting the MX record sends mail back to the old mailbox with no data loss on that side.

For a Microsoft 365 defederation, rollback is harder by design — once authentication converts from federated to managed and users reset passwords, GoDaddy's process does not offer a clean one-click reversal. That's the real reason to open the support ticket during a low-stakes week, not the Monday before a product launch.

Doing it without downtime#

Mail delivery tolerates DNS propagation better than most people expect, because it retries. A sender's server that gets a temporary failure during the MX switch queues the message and tries again for hours, not minutes — so a few hours of split delivery rarely means lost mail, only delayed mail.

The two things that do cause visible downtime are a TTL you forgot to shorten in advance, and running the IMAP migration and the MX cutover on the same day instead of confirming the copy first. Separate them: migrate the mail, verify it looks complete, then cut DNS over once you trust what's on the new side.

Schedule the actual cutover — for either path — outside business hours in your busiest time zone, even though mail retries mean it's rarely strictly necessary. It buys you a quiet window to confirm the new mailbox is receiving correctly before anyone notices, which matters more for a shared support address than for a single owner's inbox.

Where AI Emaily fits once the migration is done#

Once your mail lands in Microsoft 365 or Google Workspace, the migration itself is finished — nothing about switching providers requires AI Emaily, and this guide works the same whether you ever install it. Where it's relevant is what happens the day after: a fresh Outlook or Gmail inbox with your old GoDaddy rules, forwarders and habits gone is also a clean point to add triage, drafting and follow-up that doesn't force you to migrate again if you ever change providers a second time — it connects over IMAP or the provider's own API rather than living inside one mailbox's proprietary rules.

We build AI Emaily. It connects to Microsoft 365, Google Workspace and IMAP mailboxes the same way, drafts replies from a Personal Context brain you set rather than mining your sent mail, and keeps a human approving sends by default. If you're evaluating it as part of this move, connect the new mailbox first — that's the one you're keeping.