GoDaddy to Google Workspace Migration: How to Move Without Losing a Single Email

Plenty of Australian businesses started their email life on GoDaddy - it came bundled with the domain, it was cheap, and it worked well enough at three staff. Then the team grew, storage ran out, spam filtering started missing things, and someone asked why the calendar can't just work like it does at every other company. That's usually the day Google Workspace comes up.

The move is very doable - we have run it dozens of times - but GoDaddy migrations have a few traps that generic how-to guides skip. Here is the process that actually works, and the mistakes that cost people their mail history.

First: work out which GoDaddy email you actually have

GoDaddy sells three different email products, and the migration path depends on which one you are on:

• cPanel / Workspace Email (POP or IMAP): the older, cheaper hosting-bundled mailboxes. Migrated over IMAP - straightforward, but folder structures and contacts need care.

• Microsoft 365 sold through GoDaddy: a real Microsoft tenant, but federated to GoDaddy's control. You cannot simply change DNS and leave - the tenant has to be defederated first, in the right order, or you can lock yourself out of your own admin.

• Simple forwarding: some domains only forward mail to personal Gmail or Outlook addresses. Easiest to move, but there is usually no server-side history to migrate - the history lives in whichever personal mailbox received it.

Getting this wrong is the number one cause of botched GoDaddy migrations, so it is worth five minutes of checking before anything else.

The migration process we use

1. Audit - list every mailbox, alias, forwarder and distribution address on the domain, note mailbox sizes, and check where DNS is hosted (usually GoDaddy itself).
2. Stand up Google Workspace - create the tenant, verify the domain with a TXT record, create users matching the old addresses, and set up groups for the aliases.
3. Pre-stage the mail - Google's data migration tools (or a commercial migration platform for bigger jobs) copy historical mail across while the old system stays live. Staff keep working; nobody notices.
4. Cut over MX records - in a scheduled after-hours window, point the domain's MX records at Google. New mail starts landing in Workspace within minutes to a few hours.
5. Delta sync - a final pass catches anything that arrived on the old platform during the switch. This is the step DIY migrations skip, and it is exactly where the "we lost two days of email" stories come from.
6. Rebuild the trust records - SPF, DKIM and DMARC re-created for Google's servers. Skip this and your invoices start landing in customers' junk folders.
7. Devices and sign-off - Outlook profiles or the Gmail apps configured on every machine and phone, per-mailbox item counts compared, and only then does the old service get cancelled.

The GoDaddy-specific traps

DNS lives at GoDaddy even after the email leaves

Most GoDaddy customers also use GoDaddy DNS. That's fine - you don't have to move the domain to move the email - but it means the MX cutover happens in the GoDaddy DNS console, and old MX, SPF and autodiscover records need to be cleaned out properly. Leftover records are the most common cause of mail intermittently bouncing weeks later.

The Microsoft-365-via-GoDaddy defederation dance

If your Microsoft 365 is GoDaddy-resold, the tenant must be defederated from GoDaddy before you migrate away - passwords reset, admin rights recovered, billing untangled - and only then can the mailbox data be moved to Workspace. Do it out of order and you can end up with a tenant nobody can administer. This is the single most common job we get called to rescue mid-way.

Storage maths

Old cPanel mailboxes were often tiny, so people assume the move is small - then we find years of mail archived in local PST files on individual PCs. A proper audit includes those, because staff absolutely expect their archives to come along.

What it costs and how long it takes

For a typical small business - ten to thirty mailboxes - the whole process runs about a week end to end: a couple of days of pre-staging, an after-hours cutover, and a few days of device tidy-up and monitoring. We quote fixed-price from the mailbox count and data volume, and the Workspace licensing itself is the same price through us as direct from Google.

If your team is weighing up Workspace tiers at the same time, our Google Workspace plans and pricing page covers the current Australian numbers - and if the destination is Microsoft 365 instead, the same migration process applies in the other direction.