Before leaving a Microsoft 365 offering supplied by GoDaddy, establish whether you are keeping the existing tenant or transferring data into another one. A tenant is the Microsoft environment containing the organization’s identities, services and data. Changing the licence provider does not always require moving every mailbox.

The right method depends on your contract, configuration, domain and services. For a small business, the first step is an inventory and confirmation of the scenario, not a DNS change or immediate cancellation.

Identify the current tenant and responsibilities

Confirm the tenant identifier, associated domains, available administrator access and the responsibilities of GoDaddy, Microsoft and the new provider. Verify that the current service is actually Microsoft 365 rather than another email offering.

If you are keeping the tenant, examine the transition of administration, authentication and licensing. If you are changing tenants, also plan the movement of data, identities and the domain. Do not create a destination before understanding the constraints of the existing environment.

GoDaddy’s guidance on moving Microsoft 365 away describes the provider’s current process and prerequisites. Confirm how they apply to your account before scheduling the transition.

Inventory more than email

Record users, primary addresses, aliases, shared mailboxes, groups, calendars and delegated access. Include data volumes, retention obligations and who will validate the outcome.

Check OneDrive, SharePoint and Teams where used, local files and dependencies on Office applications. Record Outlook versions and how desktop applications are activated. A licence change can affect available features; the new plan should not be assumed to reproduce the old one.

The guide to preparing a Microsoft 365 migration provides a foundation for pilot testing, communications and verification.

Separate the domain, DNS and subscriptions

Your domain registrar, website host and email provider may be different companies. Leaving an email offering does not necessarily require moving the domain or website.

Confirm control of DNS and save the current values. A reseller change within the same tenant does not necessarily require the same updates as a move into a new tenant. In the latter case, releasing and attaching the domain must be coordinated with identities and email.

Prepare licences, access and a pilot

Determine the required licences and when they must become active before removing anything. Set up a communication channel that remains available if email is temporarily interrupted. Check MFA, account recovery and user reconnection procedures.

The pilot should cover messages, calendars and files, as well as Outlook, phones and Office applications. Some scenarios require profiles or connections to be reconfigured. Have representative users validate those steps.

Do not promise zero interruption. Define a transition window, available support, conditions for proceeding and fallback measures. Some changes cannot be reversed immediately.

Check senders and billing after the transition

Test external sending and receiving, including applications that send for your domain. Review SPF, DKIM and DMARC for the chosen configuration. Copying old values without examining them can preserve an error or remove a legitimate sender.

Validate data and access before closing an old service. Then check renewals, commitment end dates and invoices with both GoDaddy and the new provider. A completed technical transition does not automatically end every subscription or contractual obligation.

Should we delete the old tenant?

Not as a default step. If the tenant is being retained, it remains the working environment. If data is moving elsewhere, closure requires a review of remaining information, retention and dependencies. Treat that decision separately from the email cutover.

NetBLB’s Microsoft 365 support can begin by distinguishing a provider change from an actual migration, then building a plan for your configuration.