GoDaddy Move-Away That Uncovered a Data Residency Problem

A small firm in a regulated industry wanted to move its Microsoft 365 off GoDaddy and onto its own tenant, so it could control its own security and licensing. Five users, mailboxes only, no SharePoint or Teams. A routine handoff.

During the handoff I confirmed the tenant's data residency was set to South Africa, not the United States. For a regulated firm with US data residency obligations, that was a compliance exposure, and the owner had no idea their data had been sitting on another continent.

A move-away does not fix that. Moving off GoDaddy transfers control of the tenant, not its location, and an existing tenant's default data location cannot be relocated. The only compliant fix is a new tenant in the correct region plus a migration.

Phase 1, GoDaddy vendor management. Validated the account, protected access (including the account-email lockout trap), managed the GoDaddy handoff, and took ownership of the tenant. This is where the South Africa residency was confirmed.

Phase 2, compliant migration. Provisioned a new US-resident tenant, set up and assigned licenses, and migrated all five mailboxes by PST, the right-sized method for a mailbox-only environment with no SharePoint or Teams. Repointed MX, SPF, DKIM, and DMARC, reconnected every user, and decommissioned the old tenant.

Data now resident in the United States, confirmed in the Microsoft 365 admin center

5 of 5 mailboxes migrated, about 52 GB, item counts matched

Zero data loss, minimal downtime

A compliant tenant the client owns directly

When Microsoft 365 is provisioned through a reseller, the tenant's data location is set at creation and is not always your country. For a regulated business, that can be a compliance problem hiding in plain sight, and a move-away alone will not fix it. Check your data residency before you commit to keeping a tenant.