Migrate GoDaddy Email to Outlook: Domain Cutover Guide

GoDaddy bundles two very different email products under one name. The legacy Workspace Email service is a thin IMAP host with limited features; the GoDaddy-branded Microsoft 365 plans are actual Exchange Online mailboxes with GoDaddy's billing layer on top. Which one you have changes both the migration source and what's possible at the destination. This guide walks moving GoDaddy email to Outlook.com — the consumer Microsoft mail platform — with the MX record and forwarding sequence that keeps inbound mail flowing during the move.

Pick the right destination shape first#

"Outlook" can mean a few things. For this guide, the destination is outlook.com — Microsoft's free consumer mail platform. That's a different product to Microsoft 365 for Business (which can host your custom domain but costs per user per month) and different again to the Outlook desktop client (which is just a mail client connecting to any IMAP/Exchange server).

Choose outlook.com when:

• You want a free destination and don't need your custom domain hosted by Microsoft
• You're migrating personal mail off GoDaddy's hosting
• You're consolidating multiple addresses into one inbox

Choose Microsoft 365 instead when:

• You need to keep @yourbusiness.com hosted by Microsoft
• You want shared mailboxes, distribution lists, or Exchange-grade calendar features
• You have multiple users on the same domain

If Microsoft 365 is the right shape, see our Office 365 migration guide which covers tenant setup, license assignment, and MX cutover at that level. This post focuses on the outlook.com path.

Identify your GoDaddy source#

GoDaddy has sold three distinct email products over the years:

1. GoDaddy Workspace Email — the legacy IMAP-only service. Sometimes called Productivity Mail in older documentation.
2. Microsoft 365 from GoDaddy — Exchange Online mailboxes sold and billed through GoDaddy, but running on Microsoft's infrastructure.
3. Professional Email — a newer GoDaddy product that's similar in shape to Workspace Email but with different IMAP endpoints.

The migration approach differs by source:

• For Workspace Email: source is imap.secureserver.net on port 993
• For Microsoft 365 from GoDaddy: source is outlook.office365.com on port 993
• For Professional Email: source is imap.secureserver.net on port 993 (same as Workspace)

Check which one you have by signing into mail.godaddy.com or by checking the product name in your GoDaddy account billing screen.

Pre-flight checklist#

Before launching anything:

• Confirmed GoDaddy product (Workspace, GoDaddy-hosted Microsoft 365, or Professional Email)
• Active Outlook.com account or willingness to create one
• Current GoDaddy mailbox password
• Estimate of mailbox size — visible in GoDaddy's webmail dashboard
• Access to DNS records for your custom domain (you'll need this for the cutover)

Step 1: Create the Outlook.com destination#

If you don't already have an Outlook.com account, sign up at outlook.com. Choose an address you're happy to use long-term — your existing GoDaddy mail will land in this inbox.

Once the account exists:

1. Sign in to outlook.live.com
2. Open Settings (gear icon), View all Outlook settings
3. Open Sync email
4. Confirm POP and IMAP are visible — they should be by default
5. Note the destination IMAP server: outlook.office365.com on port 993

If your Outlook.com account has 2FA enabled (recommended), generate an app password at account.microsoft.com, Security, Advanced security options, App passwords. Outlook.com app passwords look like a single 16-character string with no dashes.

Step 2: Configure the source#

For GoDaddy Workspace Email:

• Server: imap.secureserver.net
• Port: 993
• SSL/TLS: yes
• Username: full GoDaddy email address
• Password: GoDaddy mailbox password

For GoDaddy-hosted Microsoft 365:

• Server: outlook.office365.com
• Port: 993
• SSL/TLS: yes
• Username: full email address
• Password: account password (if 2FA is on, generate an app password through Microsoft's account portal)

Test the source connection in a desktop client first — Mac Mail, Thunderbird, or Outlook desktop — to confirm credentials before configuring Mailbox Taxi.

Step 3: Map folders sensibly#

GoDaddy Workspace Email uses minimal folder structure:

• INBOX
• Sent
• Drafts
• Trash
• Any user-created folders

Outlook.com uses:

• Inbox
• Sent Items
• Drafts
• Deleted Items
• Junk Email
• Archive

Map explicitly:

• GoDaddy INBOX → Outlook.com Inbox
• GoDaddy Sent → Outlook.com Sent Items
• GoDaddy Drafts → Outlook.com Drafts
• GoDaddy Trash → Outlook.com Deleted Items

User folders carry their names as-is. If you have folder names with characters Outlook.com's underlying store doesn't allow (rare, but it happens with characters like : or \), Mailbox Taxi will warn you and let you remap.

Step 4: Pilot one folder#

Pick a stable folder of 200 to 500 messages. The Sent folder is usually ideal — historic, doesn't churn during the migration, and exercises most metadata fields.

On pilot completion, verify:

• Final message count matches
• Date order in Outlook.com matches GoDaddy
• Read/unread flags preserved
• Three random messages open correctly with attachments
• No folder encoding errors in the run log

Step 5: Run the full transfer#

Concurrency for this pair:

• GoDaddy Workspace as source: 2 connections (Workspace handles parallel fetch reasonably)
• Outlook.com as destination: 2 connections (Outlook.com throttles at higher counts)

Throughput: 300 to 700MB per hour, faster than iCloud-source migrations but slower than Gmail-source ones.

• 5GB mailbox: roughly 1 to 2 hours
• 25GB mailbox: roughly 5 to 12 hours
• 100GB mailbox (rare on GoDaddy): plan multi-day

GoDaddy Workspace IMAP occasionally returns slow responses during their backup windows (overnight in the US Mountain timezone). If throughput drops to near zero late at night, that's likely the cause — let it ride or pause and resume during business hours.

Step 6: The MX record question#

The historical mailbox is now in Outlook.com but inbound mail is still arriving at GoDaddy. Three options:

Option A: Forward GoDaddy to Outlook.com (simplest).

1. Sign into the GoDaddy email admin
2. Open mailbox settings, Forwarding
3. Forward all incoming mail to your Outlook.com address
4. Save

This works indefinitely as long as you keep the GoDaddy mailbox active. The downside: you're still paying GoDaddy for the mailbox.

Option B: Forward and shut down GoDaddy.

Same as A, but with a hard cutover date. Run the forward for 60 days, communicate the new address to all senders, then cancel the GoDaddy email service.

Option C: Move MX records to Microsoft.

This only works if you upgrade Outlook.com to Microsoft 365 with a custom domain. Free Outlook.com can't be an MX target for @yourbusiness.com. If you want this path, the Microsoft 365 migration guide is the better reference.

Step 7: Verify and reconcile#

Once the run finishes:

1. Folder counts side by side. Outlook.com should match GoDaddy within a few messages.
2. Spot-check by date. Open three messages from 2018, 2022, and the most recent week.
3. Test sending and receiving on the new Outlook.com address.
4. Test that the forwarding rule from GoDaddy delivers to Outlook.com (send yourself a test).

If counts are off by more than a few messages per folder, run a delta sync.

Common failure modes#

AUTHENTICATIONFAILED on GoDaddy: the GoDaddy password contains characters Mailbox Taxi escaped differently. Reset the GoDaddy password to one without special characters, then retry. GoDaddy is unusually picky about backslashes, dollar signs, and quotes in IMAP passwords.

AUTHENTICATIONFAILED on Outlook.com: 2FA is on and you used the account password rather than an app password. Generate the app password from Microsoft's security settings.

STARTTLS handshake failed on GoDaddy: the GoDaddy IMAP server occasionally drops TLS handshakes when under load. Wait 5 minutes and retry.

Message too large for destination on Outlook.com: rare, but Outlook.com has a 25MB attachment limit. Messages with larger attachments will fail and need to be moved manually. Mailbox Taxi will log them; you can re-attempt by adjusting your destination's policy if you have one.

After the migration#

• Update your address with all services that mail your old GoDaddy address
• Set up an auto-reply on the old mailbox announcing the new address (run this for 30 days)
• Don't delete the GoDaddy account immediately — keep it forwarding for 60 to 90 days to catch infrequent senders
• Export your GoDaddy contacts to CSV from the webmail interface before final shutdown
• Calendar entries export to ICS the same way

If you decide Outlook.com isn't the right destination after all, our walkthroughs for moving GoDaddy to Gmail, GoDaddy to Office 365, and GoDaddy to Google Workspace cover those alternative routes. For broader cutover sequencing, the complete email migration guide walks DNS, SPF, DKIM, and DMARC across any provider pair.