Step 1: Prepare Service Accounts on Source and Destination

Create a dedicated M365 service account for migration with full mailbox access and the required API permissions. Configure the on-premises Exchange server with the correct connectivity settings and credentials for the migration account. Verify both accounts can connect before creating the MigrationWiz project. Service account failures that surface mid-migration are harder to diagnose and fix than ones caught during setup.

Step 2: Create the MigrationWiz Project

Log in to MigrationWiz and create a new migration project. Define the migration scope and parameters before moving to endpoint configuration. Scope decisions made after the project starts create rework.

Step 3: Configure the Source Exchange Endpoint

Enter the Outlook Web Access URL and administrative account credentials for the source Exchange environment. For Exchange 2013 and later, use the transport server address, not the mailbox server address. Using the wrong server address is a common source of connection failures that don’t produce an obvious error message.

Step 4: Configure the M365 Destination Endpoint

Enter the Application ID, Directory (tenant) ID, and Client Secret into the destination endpoint fields. All three values are required for the connection to save. Missing any one of them will prevent the endpoint from validating.

Step 5: Add Users and Groups to the Project

Select the users and groups being migrated by checking the boxes next to their email addresses. Verify the selection against the migration scope documented in Step 2 before running any pass.

Step 6: Run the Full Migration

Click Start and select Full Migration to begin transferring mailbox content from the source Exchange environment to M365. The pass will include all selected user data. Monitor the pass as it runs rather than reviewing results only after it completes.

Step 7: Monitor Progress and Resolve Failures

Review migration progress during the pass. For any failed item, click the entry to see the specific error before attempting a retry. Retrying without understanding the failure often produces the same result. Resolve the underlying issue first, then retry.

Step 8: Configure M365 Mail Routing

Set up mail routing rules to ensure email is delivered correctly to migrated mailboxes. Test inbound and outbound mail flow after routing is configured. Silent routing failures don’t announce themselves and show up as missing messages hours after cutover.

Step 9: Complete Post-Migration User Tasks

Users need to create new Outlook profiles, reconfigure email signatures, and reattach any PST files that were previously connected. Communicate these steps to users before cutover so they know what to expect, not after they call the help desk. BitTitan DeploymentPro automates Outlook profile configuration and reduces the help desk volume that manual profile setup generates.

Step 10: Review Migration Statistics

Click the pie chart icon in the MigrationWiz interface to generate a detailed migration report with full statistics and summary data. Review this report before closing the project. The report surfaces items that didn’t migrate cleanly and should be resolved before the source environment is decommissioned.

#Migration #CloudMigration #Azure #M365Migration #EmailMigration