How to Migrate Microsoft 365 Away from GoDaddy – The Right Way

Why businesses leave GoDaddy for Microsoft 365

GoDaddy has been reselling Microsoft 365 for years, and for many small businesses it was a convenient starting point — domain registration, hosting, and email all under one roof. But that convenience comes with real limitations that grow more painful as your business scales.

When you purchase Microsoft 365 through GoDaddy, you're not getting a direct Microsoft tenant. GoDaddy provisions a reseller-managed tenant that sits behind their own admin layer. This means: Limited access to the full Microsoft 365 Admin Centre — many advanced features are hidden or unavailable; No access to Microsoft Entra ID (Azure AD) for Conditional Access, PIM, or identity governance; Microsoft Intune and Defender for Business are often restricted or misconfigured; You cannot self-serve tenant-level changes — everything goes through GoDaddy support; Compliance features like eDiscovery, DLP, and Purview are frequently unavailable or locked; Billing is through GoDaddy at inflated rates with no Microsoft Partner pricing; Microsoft support will often redirect you back to GoDaddy — even for core M365 problems.

Important: GoDaddy-managed tenants often have the DNS for your domain pointing to GoDaddy's nameservers. This means domain control, MX records, and SPF/DKIM/DMARC are all managed through GoDaddy's DNS — not Cloudflare, not your registrar. This is a key dependency to untangle before you migrate.

What this migration actually involves

This is not a simple "point DNS and you're done" exercise. Migrating from a GoDaddy-hosted Microsoft 365 environment involves several distinct workstreams that must be carefully sequenced to avoid email downtime, data loss, or licence gaps.

Phase 1: Discovery & Planning — Inventory all mailboxes, licences, shared mailboxes, distribution groups, and DNS records. Phase 2: New Tenant Provisioning — Spin up a fresh Microsoft 365 tenant directly through Microsoft or a CSP partner like Synex Technology. Phase 3: Mailbox Migration — Migrate email data using MigrationWiz, BitTitan, or the Microsoft Migration tool. Phase 4: DNS Cutover — Update MX, Autodiscover, SPF, DKIM, and DMARC records. Lower TTL values well in advance. Phase 5: Validation & Closeout — Test mail flow, reconfigure Outlook profiles, and cancel GoDaddy licences.

Step-by-step migration walkthrough

Step 1 — Inventory your current environment

Before touching anything, document what you have. Log into the GoDaddy Microsoft 365 admin panel and export: All user mailboxes and their current licence type (Business Basic, Standard, etc.); Shared mailboxes and their members; Distribution groups and mail-enabled security groups; Any connectors, mail flow rules, or journaling configuration; Current DNS records — especially MX, SPF, DKIM selectors, and Autodiscover CNAME; Any third-party integrations relying on OAuth or SMTP AUTH (accounting software, CRMs, scanners).

Pro tip: Run a PowerShell export against the GoDaddy tenant using Get-Mailbox | Export-Csv and Get-DistributionGroup | Export-Csv to get a clean baseline. If you don't have PowerShell access in the GoDaddy admin, this is itself a red flag about tenant control.

Step 2 — Provision your new Microsoft 365 tenant

Create a brand-new Microsoft 365 tenant through Microsoft directly, or through a Microsoft Cloud Solution Provider (CSP) like Synex Technology. A CSP gives you access to Microsoft Partner pricing, delegated admin support, and proper tenant ownership — you hold the keys, not the reseller.

1. Register the new tenant using a temporary domain (e.g., yourbusiness.onmicrosoft.com) — do not add your live domain yet. 2. Purchase the appropriate licences (Business Basic, Standard, or Premium) — match or upgrade from what you had on GoDaddy. 3. Create all user accounts in the new tenant with matching UPNs (user principal names). 4. Set up shared mailboxes, distribution groups, and any mail flow rules needed. 5. Configure MFA and Conditional Access policies before any user is onboarded.

Step 3 — Reduce DNS TTL values (do this 48 hours early)

Log into your DNS provider — whether that's GoDaddy's DNS, Cloudflare, or your registrar's nameservers — and reduce the TTL on your MX record and Autodiscover CNAME to 300 seconds (5 minutes). This ensures the DNS cutover propagates quickly when you're ready to flip. Do this at least 48 hours before your planned migration window.

Step 4 — Migrate mailbox data

For most SMB migrations (under 50 seats), the recommended tooling is MigrationWiz by BitTitan or the Microsoft native IMAP migration via the Exchange Admin Centre. For larger environments, a full Exchange Online tenant-to-tenant migration may be warranted.

1. Set up the migration endpoint in your new tenant pointing to the GoDaddy Exchange Online server. 2. Run a pre-stage migration (initial pass) to copy historical email — this can take hours or days depending on mailbox sizes. 3. Schedule the delta/cutover pass to run during your migration window (after-hours is strongly recommended). 4. Verify that mail from the last 24 hours has been synced successfully before cutting DNS.

Watch out: GoDaddy tenants often have IMAP access disabled by default. You may need to raise a support ticket with GoDaddy to enable IMAP access on mailboxes before migration tooling can connect. Budget 24–48 hours for this — plan ahead.

Step 5 — Verify domain ownership on the new tenant

Before you can set the domain as the primary email domain on your new tenant, Microsoft requires you to verify ownership via a TXT record. Add this verification TXT record to DNS, but do not yet remove the domain from the GoDaddy tenant — doing so early will break live email flow.

Step 6 — DNS cutover (the critical moment)

This is your go/no-go point. Before executing the cutover, confirm: All mailbox data has been pre-staged to the new tenant; All users exist in the new tenant with licences assigned; TTL on MX and Autodiscover records has been reduced to 300s for at least 48 hours; The domain is verified (not yet active) on the new tenant; A rollback plan is documented and the team is on standby.

Execute in this order: 1. Remove the custom domain from the GoDaddy-managed tenant (this triggers a brief mail flow interruption — minimised by the low TTL set in Step 3). 2. Add and activate the domain on the new Microsoft 365 tenant. 3. Update DNS records to point to the new tenant — MX, Autodiscover, SPF, and DKIM. 4. Run the final delta migration pass to capture any email received during the cutover window. 5. Update Outlook profiles on all client machines (or use Autodiscover to automate this).

DNS records reference — what needs to change

These are the critical DNS records that must be updated on cutover. Confirm each one is live and resolving correctly before closing the change window. MX record (@) points to yourdomain-com.mail.protection.outlook.com to route inbound email to Exchange Online. CNAME record (autodiscover) points to autodiscover.outlook.com for Outlook profile autoconfiguration. TXT record (@) contains "v=spf1 include:spf.protection.outlook.com -all" for SPF authorisation. TXT records (selector1._domainkey and selector2._domainkey) hold the DKIM signing keys generated in the M365 Admin Centre. TXT record (_dmarc) sets the DMARC policy to protect against spoofing.

After cutover: Send a test email from an external address (Gmail, another domain) to each migrated mailbox. Also test outbound — send from each mailbox and verify SPF/DKIM/DMARC pass using a tool like mail-tester.com or MXToolbox.

Common gotchas and how to avoid them

Domain removal timing: If you remove the domain from the GoDaddy tenant before adding it to the new one, Microsoft will reject the domain activation. Remove from GoDaddy then immediately add to the new tenant — treat these as a single step in the same change window.

SMTP AUTH relays breaking: Printers, scanners, and legacy apps using SMTP AUTH against the GoDaddy-hosted Exchange will break after migration. Document all SMTP relay devices and update their credentials and server settings before go-live.

Licence mismatch: GoDaddy's Microsoft 365 SKUs don't always map 1:1 to Microsoft's direct licences. Many GoDaddy customers are on Business Basic and don't realise they're missing desktop apps — included in Business Standard and Premium.

MFA not configured before cutover: Once users are on a direct tenant, Security Defaults or Conditional Access will prompt for MFA registration. Do this before the migration window — not during — to avoid a flood of support calls the next morning.

Post-migration hardening checklist

Once the migration is complete and email is flowing cleanly, use your new direct tenant access to implement security controls that simply weren't available in GoDaddy's managed environment: Enable and enforce MFA for all users via Conditional Access (or Microsoft Security Defaults as a minimum); Configure Defender for Office 365 — Safe Links, Safe Attachments, anti-phishing policies; Set up DMARC reporting to an inbox or a service like Dmarcian or EasyDMARC; Review and lock down SMTP AUTH — disable globally, whitelist only devices that genuinely need it; Enable Microsoft 365 Backup or a third-party solution such as Dropsuite or Veeam for M365 — Exchange Online does not provide long-term recycle bin recovery; Configure audit logging and alert policies in the Microsoft Purview compliance portal; Set up Microsoft 365 Groups and Teams governance policies if Teams is in use; Run a Secure Score review in the Microsoft Defender portal and work through the recommendations.

Synex recommendation: All Australian SMBs should aim for at least ACSC Essential Eight Maturity Level 1 post-migration. Your new direct Microsoft 365 tenant gives you the tools to get there — Defender for Business, Intune device management, and Entra ID Conditional Access are all included in Microsoft 365 Business Premium.

How long does this take — and what does it cost?

For a typical 10–30 seat Australian SMB, a well-planned GoDaddy-to-direct Microsoft 365 migration takes 3–5 business days end-to-end: one day for discovery and planning, one to two days for pre-stage migration and new tenant setup, and one day for the cutover and post-migration validation.

The cost of a DIY migration is deceptively high when you factor in staff time, risk of email downtime, and the likelihood of DNS errors causing mail delivery failures. A managed migration through a Microsoft CSP partner typically runs between $500–$2,500 AUD depending on seat count, mailbox sizes, and complexity — and includes a tested rollback plan if something goes wrong.

On the licensing side, moving to a direct Microsoft tenant through a CSP can actually reduce your monthly per-seat cost compared to GoDaddy's inflated reseller pricing — particularly if you've been on the wrong licence tier.