1. BitTitan Help Center
  2. Perform a Migration
  3. Microsoft 365 Migrations
  4. Microsoft Exchange Online/Office 365 Mailbox Migrations

GoDaddy-Hosted Office 365 to Microsoft O365 (Exchange Online) Mailbox Migration Guide

This guide contains all the necessary steps for migrating email data from GoDaddy-Hosted Office 365 to Microsoft 365 (Exchange Online). To migrate from GoDaddy OneDrive for Business, SPO classic team sites, Office 365 unified groups, or Microsoft Teams, use the following KB: GoDaddy-Hosted Office 365 to Microsoft O365 Migration Guidance

First time?

If this is your first time performing a migration, we have created a Migration Planning & Strategy Guide to walk you through planning, set-up, and general migration best practices. If you have never performed a migration before, we suggest reading that before beginning the steps outlined in this scenario.

Prerequisites

It is important to highlight and meet the following prerequisites for a smooth migration project.

Licensing

We recommend that you purchase User Migration Bundle licenses for this migration scenario. User Migration Bundle licenses allow the performance of multiple migrations with a single license. For questions on licensing, visit MigrationWiz Licenses.

To use your license by following the next steps:

  1. Purchase Licenses.
  2. Create a Customer.
  3. Apply Licenses.
  4. Review Considerations.
Purchase Licenses Create a Customer Apply Licenses Considerations

Purchase licenses by following the steps below:

  1. Sign in to your BitTitan account. 
  2. In the top navigation bar, click Purchase.
  3. Click the Select button and choose User Migration Bundle licenses.
  4. Enter the number of licenses you want to purchase. Click Buy Now.
  5. Enter a Billing address if applicable.
  6. Click Next.
  7. Review the Order Summary and enter a payment method.
  8. Click Place Your Order.

Limitations

  • MigrationWiz is not a sync tool. Already migrated items updated at the source mid-migration will not be updated at the destination.
  • MigrationWiz supports the capability to share migration projects across a Workgroup. When the Project Sharing feature is turned on, all active agents can view all migration projects.
  • The maximum file size for migration through MigrationWiz varies by migration type and environment, but may never exceed 60GB.
  • App password usage, MFA/2FA, and ADFS are not supported for the migration service accounts being used for this migration scenario.
  • Exchange Web Services (EWS) must be enabled for the mailboxes in GoDaddy and the Exchange Online tenant for this migration type.

Important

GoDaddy support will not release your domain from their tenant until they delete all your user accounts and all the other objects with their data. ​

This means that you must 100% complete your migration with MigrationWiz before asking GoDaddy support to release your domain. The following steps must be completed before asking for a domain release. These steps are outlined later in this guide.

  1. Pre-stage migration pass in MigrationWiz​
  2. Full (delta) migration pass in MigrationWiz​

Once you have confirmed that your data has been transferred successfully, and have verified that there are no outstanding errors that need to be further addressed, begin the domain removal process:

  1. Call GoDaddy support to delete the user account and remove the domain. 
  2. This will begin the process of deleting all the information. Be sure your migration has been completed before initiating this process.

Migrated Items

Please click the bars below to check the migrated and non-migrated items. We are constantly working to create a better migration experience for you so these items may change over time.

Which items are migrated?
  • Inbox
  • Folders
  • Email
  • Contacts
  • Calendars
  • Tasks
  • Journals
  • Notes
  • Post (when the destination is Exchange or Office 365)
  • Server-Side mailbox rules
  • Client-side mailbox rules for Outlook
  • Automatic Replies (Out of Office Messages)

    Important

    It is recommended that only Automatic Replies be migrated in the last migration pass for the user. 
  • Personal Folder and Calendar Permissions

Resource Mailboxes

We handle resource mailboxes the same way that we handle regular user mailboxes. If you can log in to the resource mailbox using a web client (i.e., Outlook Web Access), we should be able to log in as well and migrate the data. If there is no way to log in to the resource mailbox using a web client (like OWA), then we also cannot log in and migrate the data.

Sometimes, the resource mailbox is just a shared calendar that a user owns. In such cases, when the user's mailbox is migrated, we should be able to migrate the resource mailbox calendar as one of the user's calendars. Once the migration is complete, you could set sharing/permissions on the calendar so that other users can access it.​​​

Which items are not migrated?
  • Safe Sender/Block List
  • Calendar acceptance status emails

For additional features and limitations, please visit MigrationWiz: Migrated and Not Migrated Items.

Prepare the Source Environment

Modern Authentication Requirements

The steps listed in the Required Permission for Performing M365 Mailbox and Archive Migrations article apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in the mailbox and archive mailbox. Use a Global Administrator for the configuration steps.

Please review the documentation before preparing the source.

Create an Administrator Account

Regular GoDaddy admin credentials will often not work in these environments with MigrationWiz. Use the admin@example.onmicrosoft.com account the GoDaddy tenant comes with as the service account.

  1. Log in to Entra ID with your GoDaddy admin credentials to find this account.
  2. Click on your account.
  3. Select View Account.
    GoDaddy-Account.png
  4. When a new window opens, select Change Password and change your password.
  5. Log in at https://login.microsoftonline.com to complete the password reset process.

The administrator account must have full access to the user mailboxes or have the required API Permissions.

We recommend adding the necessary API permissions to the Modern Authentication app you are using for your O365 mailbox or archive mailbox endpoint. You can follow the steps outlined in this guide, as this is BitTitan's recommended approach.

Deprecation of Microsoft Application Impersonation Role

From February 2025, Microsoft has started the depreciation process to remove the Application Impersonation role from O365. Exchange On-premise and Hosted Exchange are not affected by these changes. For further information please see this article.

If you are currently using Application Impersonation for your migrations, there is no telling when that will eventually fail. It is highly recommended that you switch to using the new API permission process to avoid delays in your project due to permission failures.

Export the User List to a CSV File

This can be used when bulk-adding users to your MigrationWiz project later. You can copy and paste the user list into the Source and Destination Email columns within your MigrationWiz project dashboard under Add > Bulk Add.

To export the user list:

  1. Go to the Microsoft 365 admin portal.
  2. Click Users.
  3. Click Active Users.
  4. Click Export.
  5. Click Continue.

Be sure to save the CSV somewhere you can access it for upload later in the migration.

Prepare the Destination Environment

Modern Authentication Requirements

The steps listed in the Required Permission for Performing M365 Mailbox and Archive Migrations article apply to both the source and destination tenant when they are Exchange Online, in regards to Exchange Web Services (EWS) in the mailbox and archive mailbox. Use a Global Administrator for the configuration steps.

Please review the documentation before preparing the destination.

Create a Migration Service Account

Create a migration service account in Microsoft 365 for the tenant, this account does not require any admin role assigned. However, it must have full access to the user mailboxes or have the required API Permissions.

We recommend adding the necessary API permissions to the Modern Authentication app you are using for your O365 mailbox or archive mailbox endpoint. You can follow the steps outlined in this guide, as this is BitTitan's recommended approach.

Deprecation of Microsoft Application Impersonation Role

From February 2025, Microsoft has started the depreciation process to remove the Application Impersonation role from O365. Exchange On-premise and Hosted Exchange are not affected by these changes. For further information please see this article.

If you are currently using Application Impersonation for your migrations, there is no telling when that will eventually fail. It is highly recommended that you switch to using the new API permission process to avoid delays in your project due to permission failures.

Set Up User Accounts

Set up user accounts on the destination Office 365 tenant and assign licenses. These can be created in several ways. (The following links are to external articles.)

MigrationWiz Steps

Create a Mailbox Migration Project

  1. Click the Go to My Projects button.
  2. Click the Create Project button.
  3. Select the Mailbox Project.

    Important

    For mailbox migrations, use the migration service credentials to access mailboxes. In most migration scenarios, this account must have full access rights to the Source mailboxes.

  4. Click Next Step.
  5. Enter a Project name and select a Customer.
  6. Click Next Step.
  7. Select endpoints or follow the steps below to create new endpoints.
  8. Click Save Project.

Mailbox Migration Settings

Every setting on the project is applied to all mailboxes associated with that project. Only selected settings represented as checkboxes are applied to the project. Not selecting a checkbox does not disable a selected setting inherited from the project.

Endpoints

Endpoints are created through MigrationWiz. If you select an existing endpoint from the dropdown, it will only show ten endpoints. If you have more than ten, you may need to search it.

Consider that endpoint search is case and character-specific. For example, Cust0mer will not show up if the search is customer. We recommend keeping a list of endpoints you have created, along with any unique spellings or capitalization you may have used.

Create your Endpoints

Please review the following tabs to create your destination and source endpoints.

Source Endpoint Destination Endpoint

Create your source endpoint by following the next steps:

  1. Click New.
  2. Name the endpoint. It is recommended that the endpoint's name be unique for the project.
  3. Under Endpoint Type, select Microsoft 365 from the dropdown menu. This also applies to the GoDaddy endpoint.
  4. Enter the administrator username and password in the proper fields. This should be the global admin or the admin created in the Prepare the Source section. 
  5. Click Add.

  6. Complete the Application (client) ID, the Directory (tenant) ID, and the Client Secret fields.

  7. Click Next Step.

Application (client) ID, Directory (tenant) ID, and Client Secret

For Microsoft 365 Mailbox and Archive migrations, MigrationWiz adds the Application (client) ID, Directory (tenant) ID, and Client Secret fields.

While the Application (client) ID and the Directory (tenant) ID are mandatory, the Client Secret field is not. It will depend on the permissions of the user account that performs the migration. Please review the following information before the creation of your M365 endpoints.

  • Do not use the client secret value if you use delegated permissions (not the most recommended approach). When using delegated permissions, do not select the Use Impersonation to Authenticate checkbox in the source/destination tab of your project's advanced options.
  • The client secret value is mandatory if you using the API Permissions approach.
  • If you already have a migration service account with the Impersonation role enabled (not using the API Permissions approach) the client secret value is not mandatory. Please leave the Client Secret field empty.

    Warning

    Keep in mind that Microsoft has started removing the application impersonation role from O365, meaning there is no telling when that will eventually fail. It is highly recommended that you switch to the API Permissions approach.

For more information about how to get the Application (client) ID and Directory (tenant) ID values from the Application Registration, please review step 3 of this article.

Region of Destination Tenant

The Region of Destination Tenant feature optimizes migration performance and speed by identifying the region closest to the destination tenant (continent-level). For Microsoft 365 endpoints, MigrationWiz detects and selects the appropriate region automatically once you create and save your project.

Please note that each time you edit your project endpoints, the following message will appear at the top of your project window (where XXXX is the detected region):

Automatically detected destination tenant's region and assigned to the 'BitTitan Datacenter' in XXXX.

For this migration type, you cannot manually change the region of the destination tenant. In case you need to modify it, contact our support team.

Endpoint Validation

Once the information has been provided for both, the source and destination endpoint, and the customer selects Save and Go to Summary, MigrationWiz performs an endpoint validation check.

This validation tests the migration service credentials used in the project and the Modern Authentication setup only. If there is an issue, the screen redirects to the endpoint and provides an error message or flyout that can be selected for more information regarding the error.

Common Errors when Configuring Your Endpoint

For more information on the AADSTS700016, AADSTS90002, and ADDSTS50126 issues review the Common Errors Using Modern Authentication page.

Add Users

Add the user accounts that will be migrated to the project. This may be done in several ways, depending on the size of the project. Steps for each option are in the accordion below, simply click to show the option you select and follow the guidance there.

Small Migrations

For small migrations, it is easy to add users one at a time using Quick Add. The steps for this are below. 

Larger Migrations

For larger migrations, we recommend using the Autodiscover or Bulk Add option.

Quick Add
This option allows you to add items one at a time. To do so, you only have to provide an email address if you entered administrative credentials when setting up the project. If you did not, enter the following user information:

  • An email address.

  • Login name.

  • Password.

  • Mailbox status.

Bulk Add

Bulk Add uses a CSV containing the source and destination email addresses for the users to add the users to the project. If migrating only a specific group from a tenant, we recommend using the Bulk Add option.

MigrationWiz allows you to bulk import mailboxes into the system.

To import one or more mailboxes:

  1. Sign in to your MigrationWiz account.
  2. Select the Project for which you want to perform the bulk import.
  3. Click Add.
  4. Click Bulk Add. 
  5. Follow the instructions on the page. 

    Important

    After adding new users to the Bulk Add Items page, make sure to select the radio button All newly detected mailboxes will be migrated as shown below before clicking on the green Save button
    New Bulk Add Requirement.png
Autodiscover

The autodiscover process within MigrationWiz can be used to discover items from the Source environment so that they can be imported into your projects. This can then be edited in the project to remove users not being migrated. All users are added with the source and destination email addresses set to match the source email.

This can be changed by using the Change Domain Name button at the top of the project page. If the usernames are changing during the migration, we recommend using the Bulk Add option.

There are a few requirements for this to work:

  • The Source has to be Exchange 2007 or later, or Microsoft 365, or G Suite. If you are using Autodiscover from G Suite, all G Suite domains must be added to the list of domains in the Endpoint.
    • G Suite does not support Autodiscover when mailbox addresses are imported into MigrationWiz line items.
  • The endpoint on the Source needs to use admin credentials.
  • For mailbox migration projects, the admin account that is specified within the Source endpoint needs to have a mailbox associated with it.
  • The admin mailbox must be listed in the public Global Address List (GAL).
  • The migration project type needs to be a Mailbox migration. For the exact steps to be followed during your migration, refer to the relevant Migration Guide. All Migration Guides can be found on the Help Center site.
  • The option to add users to the project using Autodiscovery of source items will not work with Modern Authentication configured to be used with MigrationWiz.

One additional item to note here is that there is no way to restrict the IP addresses that the connection will come from.  This means that the steps outlined in our IP Lockdown guide will not apply here.  If your environment requires that any IP addresses be whitelisted, it is recommended that items be added to your project using one of the other available options.

Autodiscover of items will not work while using Modern Authentication

Autodiscover exposes the following items:

  • For mailbox migration, auto-discover will list all mailboxes at the Source.

Steps to Run Autodiscover

  1. Navigate to the project you want to import users into.

  2. Ensure that you have created an endpoint for the source project.

  3. Once in the project, click the Add drop-down on the top navigation bar, then select Autodiscover Items. This will begin the Autodiscover process.

  4. Once discovered, click the Import button, to import the items into your MigrationWiz project.

Advanced Options

The following options are most valuable for this migration scenario.

Support Tab

Consider that each Support Option includes the "=" character and is to be entered under the Support tab.

Add blank fields for new Support Options by clicking the "+" button. In case you want to delete a field click the trash can icon.

Optional Settings

  • RecipientMapping="@sourcedomainname->@destinationdomainname" If the domain name is changing, enter RecipientMapping in the advanced options of the project under support options like in the below format example: (do not use @sourcedomainname or @destinationdomainname as it is only an example).
    Please consider the following: 
    • More than one mapping expression can be used as long as the destination domain remains the same in the RecipientMapping.
    • If the User Prefix is changing for the users being migrated as well, follow the instructions here under User Prefix Changes: User Prefix Changes
    • If using both domain-level recipient mapping and user-level recipient mappings, enter them into the support options of the project so that the domain-level recipient mapping is last in the list.
      Example
      Recip_Mapping.png

Default Options for Microsoft 365 Endpoints

By default, some fields are view-only. In other words, you cannot edit or remove them from the support options page. To edit them, you need to edit the source or destination endpoint of your project.

Among these default options, you can find ModernAuthClientIdExport, ModernAuthTenantIdExport, ModernAuthClientSecretExport, ModernAuthClientIdImport, ModernAuthTenantIdImport, and ModernAuthClientSecretImport. 

The support options above are required when configuring your endpoint.

Important

Keep in mind that the ModernAuthClientSecretExport and the ModernAuthClientSecretImport support options are text-masked.

Warning

You cannot update the default Advanced Options, in case you try to modify or add new ones the following message arises.
Duplicate Support Option.png

Source/Destination Tab

For now, the new API Permissions approach does require the Use Impersonation to Authenticate box checked for your O365 endpoints along with the Client secret value that you supplied during the Endpoint creation.

Run Verify Credentials

You may verify the credentials of items in MigrationWiz without migrating data or consuming any licenses.

  1. Open the Project containing items to validate.
  2. Select the items to validate.
  3. Click the Start button in your dashboard.
  4. Select Verify Credentials from the drop-down list.

Once complete, the verification results will be shown in the Status section.​ 

Performing the Migration

Perform the migration by completing each step in the presented order.

Pre-Stage Pass

  1. Select the users.
  2. Click the Start button from the top.
  3. select Pre-Stage Migration.
  4. Uncheck the box named Automatic Replies (This option will be removed from the Pre-Stage pass at a later date)
  5. Under the Migration Scheduling section, from the drop-down list, select 90 days ago.
  6. Click Start Migration.

The 90 days is a suggestion, you can select any option you prefer. The Pre-Stage migration will migrate only older mail items. This can be run multiple times with different timeframes selected to migrate data in smaller chunks.

Full (Delta) Pass

  1. Select the users.
  2. Click the Start button from the top.
  3. Select Full Migration. 

    Important

    It is recommended to only migrate Automatic Replies in the last migration pass for the user.
  4. Click Start Migration. This migration will be completed quickly since most data is migrated during the Pre-Stage migration.
  5. Look through the user list and click any red "failed migration" errors. Review the information and act accordingly.

Run Retry Errors

Each error logged represents an item that was not migrated. MigrationWiz contains a mode in which you can resubmit the migration to retry failed items. This mode of operation is always free of charge. You may only submit mailboxes in this mode only if they satisfy all of the following conditions:

  1. The last migration pass was completed successfully.
  2. The mailbox contains at least one error.

If your mailbox does not satisfy these conditions, you will receive a warning when submitting the migration in this mode and your request will not be fulfilled.

To submit one or more mailboxes in retry mode, perform the following steps:

  1. Click the Go To My Projects button.
  2. Select the project that contains the mailboxes that you want to retry.
  3. Select the mailboxes that have migration errors.
  4. Click on the Start button.
  5. Select Retry Errors from the menu.
  6. Click the Retry Errors button.

When errors are repaired, they will disappear from the error log. Some errors may not disappear if the Source item was not reprocessed (due to filters, for example), was deleted or moved, or if the item failed again. 

If problems persist contact Support. 

MX Record Cutover

On the DNS provider's portal, change the primary MX record to reflect the DNS settings for the new Microsoft 365 organization. DNS settings to change include Autodiscover, MX, and SPF records. Also, remove the old settings for Tenant 1. These settings can be found in the Microsoft 365 admin portal, by following these steps:

  1. Inside Microsoft 365, click Admin in the header.
  2. On the Admin page, click Domains in the left pane.
  3. Click the domain name to be set up, and click the DNS Settings. This page lists the DNS records necessary to use the Microsoft 365 services.

Post-Migration

If not using DeploymentPro, users must create new Outlook profiles, set up their signatures again, and reattach any PST files that were attached to their previous profile.

Click the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. 

Remove Domain from Source

This should only be done after the final full migration pass has been completed and you have confirmed that your data has transferred successfully, and have verified that there are no outstanding errors that need to be further addressed. 

  1. Call GoDaddy support for user account deletion and domain removal. 
  2. This will begin the process of deleting all the information. 

If several domains in the Source tenant are moved to the new tenant, all of them need to be removed.

Related Topics

Was this article helpful?
1 out of 1 found this helpful

Articles in this section