Microsoft 365 Migration

Configure DNS for a Pilot Microsoft 365 Migration from GoDaddy

Maira Mehtab Sep 22, 2026 869 views

Question details

The user needs to configure DNS records to migrate a single pilot mailbox to Microsoft 365 while keeping the remaining users' mail flow active on GoDaddy.

Product: Microsoft 365
Device & OS: not provided
Scenario: Executing a pilot email migration from GoDaddy to Microsoft 365 involving only one user, which requires careful DNS planning at the hosting provider.
Observed behavior: Because Microsoft 365 does not natively support conventional split delivery, the primary domain's MX record must be managed correctly to avoid disrupting mail flow for non-migrated users.

Before you start

Ensure you have administrative access to your current DNS hosting provider's control panel (e.g., SiteGround) and Global Administrator rights for your new Microsoft 365 tenant.

Solution 1Recommended

Verify Domain and Keep Primary MX Record at Current Host

Use this method to verify your domain in Microsoft 365 for the pilot user while keeping the primary mail flow pointing to GoDaddy for the remaining users.

Microsoft 365 does not natively support conventional split delivery. Pointing the primary MX record to Microsoft 365 too early will disrupt email for your GoDaddy users.

Create Pilot User and Assign License

Log into the Microsoft 365 admin center, navigate to Users > Active users, create the pilot user (initially using the default .onmicrosoft.com domain), and assign the necessary license.

Add Verification Records

In the Microsoft 365 admin center, go to Settings > Domains, and select Add domain. Retrieve the TXT verification record provided by Microsoft and add it to your current DNS host (e.g., SiteGround).

Maintain Existing MX Records

During the setup wizard, uncheck the option to let Microsoft manage your DNS. Keep your primary domain's MX record pointed to GoDaddy until all remaining mailboxes are ready to be migrated.

Split Delivery Alternative: If you absolutely must route mail through Microsoft 365 first, you will need to configure advanced Exchange Online routing to forward unresolved mail back to the GoDaddy mailboxes.

Solution 2

Use a Dedicated Subdomain for the Pilot Migration

Create a unique subdomain specifically for the Microsoft 365 pilot user to safely separate the new mail flow from the existing GoDaddy users.

Free Microsoft Office alternative

Looking for a Lightweight Office Suite After Migration?

While you manage complex IT migrations and Microsoft 365 deployments, you can equip your team with WPS Office. It is a highly compatible, cost-effective alternative to Microsoft Office that easily handles documents, spreadsheets, and presentations.

1. Visit the WPS Official Website: Go to the official WPS Office website to access the latest free download.
2. Download and Install: Click 'Download' and run the lightweight installation package on your desktop.
3. Open Office Files: Launch WPS Office and immediately open or edit your existing Microsoft Word, Excel, or PowerPoint files without compatibility issues.

Highly compatible with Microsoft Office formats (DOCX, XLSX, PPTX)Lightweight installation and resource-friendly operation on older devicesFree alternative with a familiar, easy-to-use tabbed interfaceSeamless file management alongside your new email configurations

microsoft office alternative - wps office

Frequently Asked Questions

Can I use split delivery between Microsoft 365 and GoDaddy?

Conventional split delivery is not natively supported by Microsoft 365 without complex custom routing setups in Exchange Online. It is generally recommended to keep the MX record pointing to the original host or use a separate subdomain for the pilot.

Where should I manage my DNS records during the migration?

DNS records should be managed at the provider currently hosting your domain's DNS zone (e.g., SiteGround, Cloudflare, or GoDaddy). Do not change your domain nameservers to Microsoft 365 during a pilot migration.

What happens if I change the primary MX record to Microsoft 365 too early?

If you point the MX record to Microsoft 365 before all accounts are migrated, emails sent to users still hosted on GoDaddy will fail to deliver or bounce back, as Microsoft 365 will not know where to route them.

Why did I have to create the pilot account with an .onmicrosoft.com address?

The initial .onmicrosoft.com address is the default routing domain for your Microsoft 365 tenant. You can assign your custom domain to the user once the domain verification process is fully completed in the admin center.

Migration & Recovery